From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chr Subject: Re: [PATCH] usbhid: add ASUS LCM to the blacklist Date: Fri, 12 Oct 2007 10:49:33 +0200 Message-ID: <200710121049.34149.chunkeey@web.de> References: <200707240228.39421.chunkeey@web.de> <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-usb-devel-bounces@lists.sourceforge.net Errors-To: linux-usb-devel-bounces@lists.sourceforge.net To: Javier =?iso-8859-15?q?Bola=F1os?= Molina Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net List-Id: linux-input@vger.kernel.org On Thursday, 11. October 2007, Javier Bola=F1os 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 patch= ed) > kernel, asusolded ask me to rmmod usbhid as it was not able to get contr= ol > 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 wi= th > 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 recompi= led 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 wou= ld > suggest to update https://launchpad.net/asusoled/ maybe I could help. > = > Regards, > Javier Bola=F1os Molina. > = The project moved to sourceforge.net. The new maintainer is: Adilson Oliveira Thanks, Chr. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759354AbXJLIts (ORCPT ); Fri, 12 Oct 2007 04:49:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751122AbXJLItk (ORCPT ); Fri, 12 Oct 2007 04:49:40 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:42770 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750906AbXJLItj convert rfc822-to-8bit (ORCPT ); Fri, 12 Oct 2007 04:49:39 -0400 From: Chr To: "Javier =?iso-8859-15?q?Bola=F1os?= Molina" Subject: Re: [PATCH] usbhid: add ASUS LCM to the blacklist Date: Fri, 12 Oct 2007 10:49:33 +0200 User-Agent: KMail/1.9.7 Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net, linux-input@atrey.karlin.mff.cuni.cz References: <200707240228.39421.chunkeey@web.de> <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com> In-Reply-To: <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200710121049.34149.chunkeey@web.de> X-Provags-ID: V01U2FsdGVkX1/hDvdPD+7bf5lqJde9ymI5MAGbQsOF/j1TwDNy XryzGbVBWZCjRnyroPiNQxan+NbZyrmJpOnmriKD2WHfzL7m2c gAkccZ9Ck= Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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 Thanks, Chr.