Salut,
à éplucher le changelog du kernel-2.6.9rc1 ya des amélioration côté
ACPI :
http://kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.9-rc1
un petit extract des logs avec comme recherche "usb" (+ une question à
la fin) :
<[EMAIL PROTECTED]>
[PATCH] USB: add CONFIG_USB_SUSPEND
This is the core of the USB_SUSPEND functionality. Please merge.
This adds an experimental CONFIG_USB_SUSPEND option, which supports the
USB "suspend" state. Linux-USB hosts have previously ignored that
state.
- New driver API calls, usb_suspend_device() and its
sibling usb_resume_device().
- Access to those calls through sysfs, such as
echo -n 2 > power/state
echo -n 0 > power/state
That can be used to reduce the power consumption of any given USB
device,
then re-activate it later. Eventually, most USB device drivers should
probably suspend idle USB devices.
One problem with this patch: USB drivers without suspend() callbacks
may badly misbehave. Right now only hub drivers know suspend(). If the
driver core didn't self-deadlock when we try it, unbinding those drivers
from those devices (then re-enumerating on resume) would be perfect...
the current compromise is just to emit a warning message.
In conjunction with host controller driver support (already merged for
OHCI and EHCI), PCI host controllers will issue the PME# wakeup signal
when a USB keyboard starts remote wakeup signaling. (But the keyboard
wasn't usable later, since HID doesn't try to suspend.)
I understand some ACPI patches are circulating, and maybe already in
the MM tree, to make a suspended system wake up given PME# signaling.
It'd be great if someone made that work transparently with USB, but
for now I'm told it'll need some sysfs setup first.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
[PATCH] USB: usb hub docs and locktree()
Please merge; the CONFIG_USB_SUSPEND patch depends on it.
This hub patch:
- updates internal docs about locking, matching current usage
for device state spinlock and dev->serialize semaphore
- adds locktree() to use with signaling that affect everything
downstream of a given device ... right now just khubd uses it,
but usb_reset_device() should too (not just with hub resets...)
- adds hub_quiesce()/hub_reactivate() ... former is used now
during shutdown, both are needed in suspend/resume paths
Net change in behavior for current systems should be nothing.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
[PATCH] USB: gcc-3.5 fixes
From: Andi Kleen <[EMAIL PROTECTED]>
Trivial gcc-3.5 build fixes.
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
[PATCH] USB: Hackish fix for cyberjack driver
The following patch is in use by REINER-SCT customres for some time and
works for them in about 90% of all cases. I would really appreciate
this going in before 2.6.8-final, since the device doesn't work at all
with current 2.6.x driver.
Changes:
- bump version number
- open interrupt endpoint in startup() rather than open
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
[PATCH] USB: usbnet: replace schedule_timeout() with msleep()
Use msleep() instead of schedule_timeout() to guarantee the task delays
for the desired time. Delete unused UNLINK_TIMEOUT_JIFFIES #define.
<[EMAIL PROTECTED]>
[PATCH] USB: usb_get_descriptor, more error checks
I've had different versions of this floating around for a while;
basically, the goal is to be more robust against devices that
misbehave by returning garbage descriptors in certain cases.
Add an extra check when fetching descriptors: the type must be
correct. This guards against different types of firmware (or maybe
hardware) errors than the two checks already being made.
Question : qui est abonné à [EMAIL PROTECTED] ???
@++
Ben'. aka baud123
