Quote:
Originally Posted by eschwartz
knc1 -- you indicated that /mnt/us/ is actually pretending to be a USB device. How do I see that for myself? Is this only when the device is connected via USB to a computer?
Details!  |
Hmm...
(I'll call the electronics a "chip" even if it is something built into the SoC).
On the external (world accessible) side of the chip is the USB connector on the case.
I don't think there is any software connection to that side of the chip from the Kindle.
On the internal side of the chip is Kernel USB storage module.
That (**should be**) controlling the USB functions of the chip AND providing the storage area (physically using partition 4) so that the combination looks like a USB storage device.
I haven't looked at the code (for ages), but that seems to be a reasonable description.
I __imagine__ that the usbip demon expects a **physical** USB device (not some virtual thingy, the wet dream of the kernel driver
).
I don't know if, on the Kindle side of the kernel driver, the *faked* USB storage device ever gets added to the USB device enumeration.
It would be simpler if it did - but I don't expect our life to be that easy.
So having given the situation the above, additional thought - -
I think we would have to modify the usbipd daemon to connect to the Kernel USB storage driver.
And modify the Kernel USB storage driver to have places for usbipd to hook into.
Not as easy as I thought it would be. Sorry.