View Single Post
Old 11-29-2010, 02:40 PM   #26
lrizzo
Member
lrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tonguelrizzo can tie a knot in a cherry stem with his or her tongue
 
Posts: 23
Karma: 22222
Join Date: Oct 2010
Device: kindle3
Quote:
Originally Posted by ankigodzi View Post
hey,
how can we use this hack of Ajaxterm for Nell (Kindle DX) which doesn't have a wifi option.
Can we use it on wan?
Is it possible throught USBNet hack. if yes how?
I have not sure but there is probably a better approach, as described below, that we might be able to implement in not too much time.

As the author of "launchpad" mentioned me, and there is code included in his latest version, see

https://www.mobileread.com/forums/showthread.php?t=97636

the Kindle's framebuffer is accessible through /dev/fb with a standard and easy API (the screen is memory mapped, and there are a few ioctls to update the screen).

So we can implement a proper terminal by merging launchpad and ajaxterm as follows:

1. extend launchpad with some option to enter a "terminal" mode where input from keyboard and fiveways is captured (so, not sent to the kindle's framework) and used as below;

2. convert kindle events into keycodes produced by a terminal (with ALT, CTRL, cursors...). This is more or less what ajaxterm.js does .

3. use the code in myts.c (the ajaxterm backend) to send keycodes to a shell, and interpret the responses to update a virtual screen (we need better ANSI emulation)

4. convert the screen into a proper bitmap that we can display in the framebuffer.

The missing code is not particularly difficult, just boring to write: for #2 is purely a translation from js to C, for #3 we need to extend the ANSI emulation, for #4 we need a 7 pixel-wide monospace font (so we can display 80 columns on the Kindle3 which has 600 pixels) and extend the blitting code so it can handle areas that are not byte-aligned (the Kindle3 has 4bpp so a 7-pixel font occupies 3.5 bytes per line; not sure if the DX has 4bpp or less).

cheers
luigi
lrizzo is offline   Reply With Quote