Lines Matching full:it

20 required to behave as though the device has been unplugged.  It's a
23 device is still attached or perhaps it was removed and a different
29 though they had disconnected.  This is always safe and it is the
35 system woke up, who cares?  It'll still work the same when you type on
36 it.
52 it's as though you had unplugged all the USB devices.  Yes, it's
64 the system can't be suspended at all.  (All right, it _can_ be
65 suspended -- but it will crash as soon as it wakes up, which isn't
72 The kernel includes a feature called USB-persist.  It tries to work
76 It works like this.  If the kernel sees that a USB host controller is
78 reset or otherwise had lost power) then it applies a persistence check
80 "persist" attribute is set.  It doesn't try to resume the device; that
81 can't work once the power session is gone.  Instead it issues a USB
87 kernel treats the device as though it had merely been reset instead of
105 devices for which it is enabled.  You can enable the feature by doing
113 doesn't even exist, so you only have to worry about setting it for
114 devices where it really matters.
124 with it, unplug the flash device, plug it back in later, and still
126 it would be more far-reaching than USB-persist.
129 job and using it would require significant input from the user.  This
130 solution is much quicker and easier -- and it exists now, a giant
134 just mass-storage devices.  It might turn out to be equally useful for
153 Furthermore it's quite possible to leave a USB device exactly the same
156 way to know you did it.  The kernel will assume that nothing has
160 If the kernel gets fooled in this way, it's almost certain to cause
171 most of it.