PRS-500 Reader internals - Page 6

igorsk · 10-20-2006, 03:49 PM

The main reader application is "tinyhttp". Don't know why it's called that, but it seems it does have some http functionality. It is a thin wrapper around libtinyhttp.so, which is basically a Reader version of fsk.dll. It loads various "plugins" from the other .so and .xsb files. The process copies are spawned by the various event watchers, I beleive. USB api is handled by switcher.so, and the drivers are usbtg_core and usbtg_pd.

P.S. Not much progress so far... struggling with cramfs at the moment.

TadW · 10-20-2006, 04:01 PM

Quote:

Originally Posted by arivero

Amusing, so we are "almost inside" the iLiad and the Reader at the same time. Not enough man resources for both, eh, TadW!

True, true. And I think igorsk did an amazing job so far.

NatCh · 10-20-2006, 04:03 PM

Quote:

Originally Posted by igorsk

The main reader application is "tinyhttp". Don't know why it's called that....

Could it be related to the BBeB format being some twisted cousing of XML, maybe? You're operating so far outside my area of knowlege, that I can only offer small, rather obvious (and probably wrong) guesses.

Quote:

Originally Posted by arivero

Amusing, so we are "almost inside" the iLiad and the Reader at the same time. Not enough man resources for both, eh, TadW!

Clearly, you iLiadites have been slacking.

arivero · 10-20-2006, 06:21 PM

Quote:

Originally Posted by NatCh

Clearly, you iLiadites have been slacking.

We were promised that iRex would do all the work (and they probably will, but we are in their backburner). I am not sure about Sony, they also promised a "developers program", but from the OS architecture (all programs as ".so", and no Xserver) it seems that the learning curve is going to be, er, steeper.

Architecture notwithstanding, I suppose that we share some interests on common development: djvu, etc. But "Readers" should be interested, additionaly, on getting a wifi external card and perhaps other drivers.

arivero · 10-20-2006, 06:25 PM

Quote:

Originally Posted by igorsk

The main reader application is "tinyhttp". Don't know why it's called that, but it seems it does have some http functionality. It is a thin wrapper around libtinyhttp.so, which is basically a Reader version of fsk.dll. It loads various "plugins" from the other .so and .xsb files. The process copies are spawned by the various event watchers, I beleive. USB api is handled by switcher.so, and the drivers are usbtg_core and usbtg_pd.

P.S. Not much progress so far... struggling with cramfs at the moment.

Strange. Could you attach this wrapper tynyhttp.sh?

Usbtgcore and usbtgpd are well understood by a couple guys in the librie mailing list (at yahoogroups); they got to do a shell connection via these drivers (plus a reflash to load the needed addtional software, of course

) and then a ppp tunnel over the shell.

NatCh · 10-20-2006, 06:26 PM

Quote:

Originally Posted by arivero

We were promised that iRex would do all the work....

Yup, and my remark was even lower than that since you've had a moving target to hit. But, hey, as the Wise Man said: "Cheap shots are life's bargains." I just couldn't resist poking fun.

TadW · 10-20-2006, 06:28 PM

In all fairness, unlike iRex, Sony is not trying to prevent us from toying around with their device.

iRex makes it more difficult by being "proactive" in disabling everything we discover.

NatCh · 10-20-2006, 06:52 PM

Quote:

Originally Posted by TadW

iRex makes it more difficult by being "proactive" in disabling everything we discover.

It might not be deliberate....

TadW · 10-20-2006, 07:01 PM

Quote:

Originally Posted by NatCh

It might not be deliberate....

Maybe. Maybe not. Though I find this one quite telling:

Code:

# do_updates.sh
#
# This script facilitates updates to the non-app filesystems
#
# Author: Matthijs van de Water <matthijs.van.de.water@irextechnologies.com>
# Version: release 2.5
# Updates:
#  - update the update filesystem with a new image if available
#  - rebuild the registry, preserving the username and password
#  - check for SSH server and uninstall
#  - set the root-password to something impossible to guess
#

NatCh · 10-20-2006, 07:06 PM

Hmmm, that is rather ... pointed, isn't it?

gseryakov · 10-20-2006, 07:34 PM

Quote:

Originally Posted by TadW

Code:

# do_updates.sh
...
#  - set the root-password to something impossible to guess
#

Brute force is the answer.

Slava · 10-20-2006, 08:22 PM

Quote:

Originally Posted by igorsk

P.S. Not much progress so far... struggling with cramfs at the moment.

Come on, Igor, you can do it !-)

arivero · 10-20-2006, 09:22 PM

Quote:

Originally Posted by Slava

Come on, Igor, you can do it !-)

If exhausted, go librie at yahoogroups.com and search old posts on cramfs. They got also very nervous about it two years ago because it was not straightforward how to mount it on loop.

TadW · 10-21-2006, 06:03 PM

I think there is no more need...

https://www.mobileread.com/forums/sho...?threadid=8179

kovidgoyal · 10-31-2006, 03:30 PM

igor a quick question. File permissions information is transmitted in the last 4 bytes of the packet. However, looking at my USB logs, the last 4 bytes are always zeroed (i.e., the reader sends no information). Looking at ebook.py you seem to assign the file permissions arbitrarily. Is that correct?

10-31-2006, 03:30 PM	#90
kovidgoyal creator of calibre Posts: 45,604 Karma: 28548974 Join Date: Oct 2006 Location: Mumbai, India Device: Various	file permissions igor a quick question. File permissions information is transmitted in the last 4 bytes of the packet. However, looking at my USB logs, the last 4 bytes are always zeroed (i.e., the reader sends no information). Looking at ebook.py you seem to assign the file permissions arbitrarily. Is that correct?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PRS-500 Reader Internals 2.0 (pics!)	lint	Sony Reader Dev Corner	60	11-18-2013 08:25 AM
Kindle DX Internals	revilo	Amazon Kindle	0	06-15-2009 04:50 AM
Kindle 2 Internals	JSWolf	Amazon Kindle	19	02-27-2009 02:45 PM
PRS-500 Connect internals	igorsk	Sony Reader Dev Corner	1	10-12-2006 04:50 AM
iLiad Iliad internals	ali	iRex Developer's Corner	39	07-21-2006 04:28 AM

10-20-2006, 03:49 PM	#76
igorsk Wizard Posts: 3,442 Karma: 300001 Join Date: Sep 2006 Location: Belgium Device: PRS-500/505/700, Kindle, Cybook Gen3, Words Gear	The main reader application is "tinyhttp". Don't know why it's called that, but it seems it does have some http functionality. It is a thin wrapper around libtinyhttp.so, which is basically a Reader version of fsk.dll. It loads various "plugins" from the other .so and .xsb files. The process copies are spawned by the various event watchers, I beleive. USB api is handled by switcher.so, and the drivers are usbtg_core and usbtg_pd. P.S. Not much progress so far... struggling with cramfs at the moment.

10-20-2006, 06:28 PM	#82
TadW Uebermensch Posts: 2,583 Karma: 1094606 Join Date: Jul 2003 Location: Italy Device: Kindle	In all fairness, unlike iRex, Sony is not trying to prevent us from toying around with their device. iRex makes it more difficult by being "proactive" in disabling everything we discover.

10-20-2006, 07:06 PM	#85
NatCh Gizmologist Posts: 11,615 Karma: 929550 Join Date: Jan 2006 Location: Republic of Texas Embassy at Jackson, TN Device: Pocketbook Touch HD3	Hmmm, that is rather ... pointed, isn't it?

10-21-2006, 06:03 PM	#89
TadW Uebermensch Posts: 2,583 Karma: 1094606 Join Date: Jul 2003 Location: Italy Device: Kindle	I think there is no more need... https://www.mobileread.com/forums/sho...?threadid=8179

Advert

Advert