Quote:
Originally Posted by ixtab
I don't think that really matters.
|
It might. There are two machines involved, both responding to "hot plug" events.
Let's walk this through in a bit of detail.
Quote:
Originally Posted by ixtab
To re-phrase the OP's question differently (if I understood it correctly): After the drive was ejected from the computer, but the cable is still plugged in, is there a way to (programmatically) set the Kindle to USB drive mode again?
|
"Drive ejected from the computer" - that is done on the "host end" computer. You have just told the "host" that the USB drive should be disconnected (from the OS).
? Does the Kindle detect that ? (I don't have a working kindle at the moment to test this).
If the Kindle did not detect that - then nothing has changed at the Kindle "device end" of the connection. And there is nothing to be done at/on the Kindle.
What you need is to "reattach" the USB device on the host end after the "eject" on the host end.
How that gets done depends on the OS the host end is running.
If the Kindle did detect that ("eject" or "safely remove") - then you would have to "reattach" the USB device in both the Kindle/Linux OS and in the host/whatever OS.
Need more details than where provided to answer either case above.
Quote:
Originally Posted by ixtab
I am not aware of any solution.
However, the same question would be interesting for USB Network: after turning on USB network, you also have to unplug and replug the cable for the device to be recognized as a "new one". Maybe there is some software solution to "reset" the USB port which would act as if the cable was unplugged/replugged? This certainly must be possible, but I'm completely lost when it comes to electronics and circuitery, so I probably can't be of any help.
|
We know what OS is being run at the "device end" - still would need to know what OS is being run at the "host end".
The how-to fake a "hot plug" (or "plug&play") event differs by OS.
I hope that helps clarify the reasons for my question.