Fwd: Using HAL to disable USB hub "wakeup" setting

Tomasz Torcz tomek at pipebreaker.pl
Fri Mar 20 11:36:30 PDT 2009


On Fri, Mar 20, 2009 at 01:44:35PM -0400, Dan Streetman wrote:
> On Fri, Mar 20, 2009 at 11:39 AM, Andrey Borzenkov <arvidjaar at mail.ru> wrote:
> > I have been doing similar things in udev; something like
> >
> > ACTION=="add" SUBSYSTEM=="usb" ATTR{product}=="OHCI Host Controller"
> > ATTR{power/autosuspend}="0"
> 
> I was temporarily using udev also with
> 
> SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
> ENV{TYPE}=="9/*", ATTR{power/wakeup}="disabled"
> 
> 
> So the udev rule I was using, above, works fine if I am ok with
> manually dropping it on each system where it needs to be, and
> disabling all the hubs' remote wakeup.  But I'm part of the Linux
> enablement team for this hardware, this isn't a personal system, so I
> need this be part of a standard package (like HAL) so all Linux
> distros work out-of-the-box on the hardware.

  HAL was going to be replaced by DeviceKit. Now DK was renamed to
udev-extras. So it's natural that udev rule is the way to go.

-- 
Tomasz Torcz       ,,(...) today's high-end is tomorrow's embedded processor.''
xmpp: zdzichubg at chrome.pl                      -- Mitchell Blank on LKML

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 237 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/hal/attachments/20090320/4c914ee4/attachment.pgp 


More information about the hal mailing list