From: r n j. <rnjacobs@MIT.EDU> - 2005-02-18 20:01:32
|
Hello, > r n jacobs wrote: > > The code for the application button (it only has a single one) is 11 > > (0xB), rather than 1 or 2 or 7 or anything else convenient. (I > > modified my copy of apanel to interpret 11 as 1, and it seems to work > > correctly). > could you please compile the driver with debugging enabled (#define > DEBUG in the driver's source) and post the dmesg output of it? maybe > it's possible to detect this... I was unable to insmod a clean (unpatched) copy; I think I've got a gcc version mismatch. But my version (seems to work so far) prints the following with debug enabled: apanel: type = 11, access = 2 chip = 4, slave = 0x19 apanel: Application Buttons found, slave address = 0x19 apanel: type = 4, access = 2 chip = 4, slave = 0x19 apanel: LED found, slave address = 0x19 apanel: Fujitsu Application Panel Driver v1.1 (API v1.0) apanel: Copyright (c) 2001-2003 by Jochen Eisinger <jo...@pe...> apanel: driver loaded at address 0x19... I believe the only difference would have been-- apanel: Application Buttons found, slave address = 0x19 with a clean copy-- apanel: unknown device 11 found The short patch was: --- apanel.c.old 2005-01-20 05:45:04.000000000 -0500 +++ apanel.c 2005-02-18 14:57:21.898598896 -0500 @@ -727,6 +727,10 @@ case 7: devno = 1; break; + + case 11: + devno = 1; + break; } Hope this is useful, - robert jacobs |