Re: [PATCH] usbhid: add ASUS LCM to the blacklist

Hi all,

I would like to comment on the topic quoted on
https://zockertown.de/s9y/archives/882-asusoled-compilieren.html  that
states something like this:


"I wrote a patch to correct this issue:
http://lkml.org/lkml/2007/7/23/530(get & try the patch) However, it
would be nice if it has "someone"
supporters! I've already wrote one for 2.6.22-gitX cycle... but it do not
get any feedback! please go
to:http://lkml.org/lkml/bounce/2007/7/23/530<https://zockertown.de/s9y/exit.php?url=aHR0cDovL2xrbWwub3JnL2xrbWwvYm91bmNlLzIwMDcvNy8yMy81MzA=&entry_id=882>send
it to your email address, write a feedback and use "answer all!".
That's it!"


Well I installed this patch, recompiled my kernel and tried again asusoled
application in order to test the oled display.
First time everything seemed as usual as it was with a standard (no patched)
kernel, asusolded ask me to rmmod  usbhid as it was not able to get control
on the oled.
Then I removed the usbhid and tried again, it worked. Nothing new.
After this I loaded usbhid in order to use my mouse.
then I tried asusoled  and  fortunately this time it worked  this time with
usbhid loaded.

To sum up the patch works fine once I remove and load usbhid once. I tend to
think this could be a bootstrap bug as it does work well after a manual
reload of usbhid.

I'll continue testing in order to see if it was just a spontaneous  problem.


My system:

Asus G1S
4GB
Open SuSE 10.3 X86_64
Kernel: 2.6.22.9-90 (Suse Build Service) patched with/to solve:
                                      4GB + BIOS + Nvidia problem
                                      oled recognized as usbhid device


PS.
I don't know  German so it was difficult to understand the page in
https://zockertown.de/s9y/archives/882-asusoled-compilieren.html so I would
suggest to update https://launchpad.net/asusoled/ maybe I could help.

Regards,
Javier Bolaños Molina.


On 23/07/2007, Christian Lamparter <[email protected]> wrote:
>
>
> Some of ASUS' notebooks (e.g G Series) include a tiny oled display, which
> is
> attached to an internal USB bus. Unfortunatly the device reports a wrong
> DeviceDescriptor and is therefore identified as a HID device...
>
> Signed-off-by: Christian Lamparter <[email protected]>
> CC: [email protected]
> CC: [email protected]
>
> ---
> (keep the cc!)
> for those who are interested in the userspace display driver:
> https://launchpad.net/asusoled
>
>
>


-- 
Javier Bolaños Molina