Hi,
> On the 8100 the problem is that the maestro3-module mustn't be loaded
> when modprobe'ing irda-stuff. It even mustn't habe been loaded since
> last boot. If you load the irda-stuff prior to maestro3, there's no
> problem at all.
it was exactly the same for me (was time-consuming to figure out).
However, with kernel 2.4.18 this problem just disappeared. A good soul named
Michal Ceresna (his credits here) sent me a patch as feedback to an
installation report I published via www.linux-on-laptop.net:
That's it:
*** maestro3.c Fri Mar 1 11:18:58 2002
--- maestro3.c.org Fri Mar 1 11:16:03 2002
***************
*** 2236,2242 ****
for(i = 0; i < 5; i ++) {
dir = inw(io + GPIO_DIRECTION);
! /*dir |= 0x10;*/ /* assuming pci bus master? */
remote_codec_config(io, 0);
--- 2236,2242 ----
for(i = 0; i < 5; i ++) {
dir = inw(io + GPIO_DIRECTION);
! dir |= 0x10; /* assuming pci bus master? */
remote_codec_config(io, 0);
As you can see, the changes are minimal. With the stock 2.4.18 kernel this
patch was already integrated; now it does not matter in which order the irda
modules or maestro3 have been loaded. It just works..
Don't have tested any FIR devices, either.
Regards,
Frank
--
-------------------------------------------------------------
Frank Trenkamp ftrenkam at uos.de
PGP fprt: 5A0C 4AE9 74A5 51F0 2D34 E7DC 67FF 32C4 0357 5653
-------------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
