Citando Alan Stern <[email protected]>:
> On Tue, 11 Sep 2007 [email protected] wrote:
>
> > Hi again,
> >
> > I have been thinking, why not use /sys/block/sdX/removable to know whether
> USB
> > device needs USB_QUIRK_RESET_RESUME.
>
> Lots of devices set the Removable flag incorrectly.
I got it.
> > If the device is not removable then it is
> > safe to use USB_QUIRK_RESET_RESUME, right?
>
> No. The one has nothing to do with the other. USB_QUIRK_RESET_RESUME
> should always be safe -- except that many drivers don't support it.
Ok.
> > That is true for ClassmatePC since
> > you must disassemble it to remove the internal flash memory. Using
> > /sys/block/sdX/removable could make USB_QUIRK_RESET_RESUME list short in
> > quick.c, don't you think?
>
> No. You don't seem to understand what USB_QUIRK_RESET_RESUME means.
> It doesn't mean that it is "safe" to reset the device during a resume.
> It means that the device _must_ be reset during a resume because
> otherwise the resume won't work.
Sorry, I was thinking about usb persist and USB_QUIRK_RESET_RESUME together.
Anyway if /sys/block/sdX/removable is set incorrectly sometimes then it will not
help for usb persist.
Another question, ClassmatePC uses Ralink's rt73 usb wireless card. I asked
Ralink's engineers to implement .suspend() and .resume() callbacks in their
driver. They did it but they have one doubt that I could not answer:
"We have several success trial for the suspend and resume now. One thing I don't
quite understand is the resume process of USB.
When I doing the suspend to RAM, the suspend call back function is called and
work well.
When resume, usb subsystem will call disconnect call back (remove module) then
call the close call back function. Seem unreasonable. Since resume and our
driver in the kernel space why remove the module and do the probe again? Any
setting we can configure for the CMPC?"
I found this mailling list thread
http://sourceforge.net/mailarchive/message.php?msg_id=1188828970.8195.39.camel%40localhost
where you answered to someone that has a similar problem. In this thread
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=21976&sid=14bd99cbf92c3d7d90838d1ba3e06ae9
someone suggest that it is a kernel bug. Do you think it is a kernel? Do you
know where Ralink can get documentation about Linux USB subsystem in order to
make it work with suspend?
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.