Thread: PRS-500 Reader internals
View Single Post
Old 10-20-2006, 02:24 PM   #75
porkupan
Fanatic
porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.
 
porkupan's Avatar
 
Posts: 556
Karma: 1057213
Join Date: Sep 2006
Location: North Eastern U.S.
Device: Sony Reader
Quote:
Originally Posted by arivero
I do not undestand this process tree. First, where are the Reader applications? Do they switch off automatically when you switch on the USB? Second, the only living thing is this tinyhttp.sh shell script. Is is related to usb? How? Is it a httpd process or a series of http gets going on continously?
Yeah, it looks like all Reader UI apps get switched off automatically when the USB is connected.

How are the USB comms handled? Perhaps by the interrupts and device drivers (loadable modules) on the Reader side.

Here is the list of kernel modules:
Code:
usbtg_pd                6916   1
usbtg_core             22300   0 [usbtg_pd]
snsc_mpu110_rtc         7328   1
libroi2s                9956   0
soundcore               3984   2 [libroi2s]
sd                     53200   2
ms_sep                 47188   2
librofb                52308  64
Last edited by porkupan; 10-20-2006 at 02:30 PM.
porkupan is offline   Reply With Quote