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

Dan Streetman ddstreet at us.ibm.com
Fri Mar 20 13:12:58 PDT 2009


Ah ok, so the entire HAL framework will eventually be replaced by
DeviceKit / udev-extras; including all the utility programs like
hal-get-property and such?  I assume this is the DeviceKit project
site:
http://fedoraproject.org/wiki/Features/DeviceKit

Thanks!

On Fri, Mar 20, 2009 at 2:36 PM, Tomasz Torcz <tomek at pipebreaker.pl> wrote:
> 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
>
>
> _______________________________________________
> hal mailing list
> hal at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/hal
>
>


More information about the hal mailing list