linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Javier Bolaños Molina" <javinovich@gmail.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] usbhid: add ASUS LCM to the blacklist
Date: Wed, 10 Oct 2007 20:11:05 -0500	[thread overview]
Message-ID: <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com> (raw)
In-Reply-To: <200707240228.39421.chunkeey@web.de>

[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]

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 <chunkeey@web.de> 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 <chunkeey@web.de>
> CC: linux-input@atrey.karlin.mff.cuni.cz
> CC: linux-usb-devel@lists.sourceforge.net
>
> ---
> (keep the cc!)
> for those who are interested in the userspace display driver:
> https://launchpad.net/asusoled
>
>
>


-- 
Javier Bolaños Molina

[-- Attachment #2: Type: text/html, Size: 4044 bytes --]

  parent reply	other threads:[~2007-10-11  1:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24  0:28 [PATCH] usbhid: add ASUS LCM to the blacklist Christian Lamparter
2007-07-26 22:27 ` Andrew Morton
2007-07-26 23:10   ` Christian Lamparter
2007-07-30 12:45     ` Jiri Kosina
2007-07-30 14:11       ` Chr
2007-07-31  8:39         ` Jiri Kosina
2007-07-31 21:24           ` Cleaning up the USBHID's blacklist Chr
2007-08-01 12:11             ` Jiri Kosina
2007-10-11  1:11 ` Javier Bolaños Molina [this message]
2007-10-12  8:49   ` [PATCH] usbhid: add ASUS LCM to the blacklist Chr
2007-10-12 15:59     ` Javier Bolaños Molina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com \
    --to=javinovich@gmail.com \
    --cc=chunkeey@web.de \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).