public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: "Javier Bolaños Molina" <javinovich@gmail.com>
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: Fri, 12 Oct 2007 10:49:33 +0200	[thread overview]
Message-ID: <200710121049.34149.chunkeey@web.de> (raw)
In-Reply-To: <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com>

On Thursday, 11. October 2007, Javier Bolaños Molina wrote:
> Hi all,
> [...]
> 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.
> 

hmm, sounds like the old usbhid module is still around... 
My first guess: Do you use a initrd? Have you updated it, after you recompiled your kernel?

> [...]
> 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.
> 

The project moved to sourceforge.net. The new maintainer is:

Adilson Oliveira <adilson@linuxembarcado.com.br>

Thanks,
	Chr.

      parent reply	other threads:[~2007-10-12  8:49 UTC|newest]

Thread overview: 9+ 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
     [not found] ` <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com>
2007-10-12  8:49   ` Chr [this message]

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=200710121049.34149.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=javinovich@gmail.com \
    --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