[Bug 14795] Irda: nsc-ircc needs module options to work correctly

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Wed Dec 14 02:01:25 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14795
Ubuntu | linux





------- Additional Comments From mika.fischer at gmx.de  2005-12-14 02:01 UTC -------
After checking again it seems that the problem does not occur anymore. 
The way /etc/init.d/irda-setup loads the module works now as the driver finds the right dma channel by itself. 
So the kernel/driver is OK now. 
 
There is another problem however: It seems that something is loading the module without the dongle_id parameter. 
Perhaps it has something to do with the udev/hotplug thing. 
 
If I unload the module after booting and reload with dongle_id=0x09 everything is OK. 
 
Here the output at boot: 
17179586.172000] nsc_ircc_pnp_probe() : Found cfg_base 0x000 ; firbase 0x2F8 ; irq 3 ; dma 3. 
[17179586.172000] nsc-ircc, Found chip at base=0x000 
[17179586.172000] nsc-ircc, driver loaded (Dag Brattli) 
[17179586.172000] nsc_ircc_open(), can't get iobase of 0x2f8 
[17179586.172000] nsc-ircc, Found chip at base=0x02e 
[17179586.172000] nsc-ircc, driver loaded (Dag Brattli) 
[17179586.172000] nsc_ircc_open(), can't get iobase of 0x2f8 
 
And here when loading with dongle_id=0x09: 
[17180315.692000] nsc_ircc_pnp_probe() : Found cfg_base 0x000 ; firbase 0x2F8 ; irq 3 ; dma 3. 
[17180315.692000] nsc-ircc, Found chip at base=0x000 
[17180315.692000] nsc-ircc, driver loaded (Dag Brattli) 
[17180315.696000] IrDA: Registered device irda0 
[17180315.696000] nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500 
[17180315.696000] nsc-ircc, Found chip at base=0x02e 
[17180315.696000] nsc-ircc, driver loaded (Dag Brattli) 
[17180315.696000] nsc_ircc_open(), can't get iobase of 0x2f8 
 
Feel free to reassign/retitle. 

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kernel-bugs mailing list