From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-11 13:56:23
|
> according to some pages referring to my laptop model, the=20 > irda chip used in my laptop is a toshiba satellite 1800. The Toshiba Satellite 1800 is a laptop computer, not an irDA chip. So this is definitely not correct. > For=20 > the configuration I followed this link=20 > http://personal.eunet.fi/pp/joakim/nx7010.html#irda. With the=20 > appropriate changes for my distribution (gentoo with a 2.6.17=20 > kernel, smcinit version 0.4). Having a look at my logs and=20 > dmesg, is more or less confusing:=20 Smcinit has been merged into the kernel. It needs to know about all devices that need pre-initialization like this. > [tosh1800-smcinit] PCI device 0x10b9:0x1533 not found This initializer looks for an ALi ISA bridge. It's not there. I think you have an Intel 82801DBM LPC bridge. Do this (as root): > lspci Is "ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge" in the list? Then notice the device number (like 0.1f.0) then: > lspci -n -v Post the output for the 0.1f.0 (or whatever) device here. We are especially interested in the subsystem ID that will be needed for Autodetection and configuration. Linus |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-11 14:05:05
|
BTW, as it says:=20 > [tosh1800-smcinit] LPC47N227 chip (ver 0x5a, rev 0x0)=20 > configuration successfully ended Sep 11 12:09:50=20 This is an LPC47N227 chip, which is supported by the smsc-ircc2 driver under Linux... Linus |
From: Andreas G. <and...@we...> - 2006-09-11 15:11:50
|
Am Montag, 11. September 2006 16:04 schrieb Linus Walleij (LD/EAB): > BTW, as it says: > > [tosh1800-smcinit] LPC47N227 chip (ver 0x5a, rev 0x0) > > configuration successfully ended Sep 11 12:09:50 > > This is an LPC47N227 chip, which is supported by the smsc-ircc2 > driver under Linux... > > Linus > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users Ok, so here's the output of lspc for the corresponding bridge: 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01) and from lspci -n -v: 00:1f.0 0601: 8086:24cc (rev 01) Flags: bus master, medium devsel, latency 0 Andreas |
From: Andreas G. <and...@we...> - 2006-09-11 21:04:24
|
Maybe the output of lspci -n -vvv is more useful: 00:1f.0 0601: 8086:24cc (rev 01) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Greets Andreas |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-12 06:28:14
|
> Maybe the output of lspci -n -vvv is more useful:=20 Yeah hm, I realized this thing that the nxNNNN and ncNNNN laptops have not subsystem ID but no worry, I surfed the web and found out that the nx7010 is subsystem 0e11:0860. I just wanna take a sweep and see what other nxNNNN and=20 what have you that have this chip so I can make a largeish patch fixing a whole bunch of HP/Compaq laptops. Linus |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-13 07:55:35
Attachments:
smsc-ircc2.c.patch
|
Andreas and other HP/Compaq ncNNNN nxNNNN users: Here is a patch for smsc-ircc2.c I'd like you to test. It adds support for a few more HP Compaq laptops, but as can be seen from my comments there are still some missing entries, so I need help to test and adjust this. Please report on any success on this. Simply modprobe:in the driver and pasting the dmesg Results here will be very helpful. Linus |
From: Andreas G. <and...@we...> - 2006-09-13 14:04:23
|
Am Mittwoch, 13. September 2006 09:55 schrieb Linus Walleij (LD/EAB): > Andreas and other HP/Compaq ncNNNN nxNNNN users: > > Here is a patch for smsc-ircc2.c I'd like you to test. > It adds support for a few more HP Compaq laptops, > but as can be seen from my comments there are still > some missing entries, so I need help to test and adjust > this. > > Please report on any success on this. > > Simply modprobe:in the driver and pasting the dmesg > Results here will be very helpful. > > Linus Hi, I tried to apply your patch, but I received an error message: patching file smsc-ircc2.c Hunk #1 FAILED at 2354. 1 out of 3 hunks FAILED -- saving rejects to file smsc-ircc2.c.rej Btw., my kernel version is the gentoo-kernel-2.6.17-r7. Greets Andreas |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-14 12:14:30
|
> I tried to apply your patch, but I received an error message:=20 > patching file smsc-ircc2.c > Hunk #1 FAILED at 2354. > 1 out of 3 hunks FAILED -- saving rejects to file smsc-ircc2.c.rej This patch is against David Millers net-2.6 git tree, that is what we use for irda development. (David merge patches into mainline.) You can get a clone of Davids tree and its smsc-ircc2.c file with git-clone git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git Then patch that file instead. Linus |
From: Andreas G. <and...@we...> - 2006-09-21 12:43:22
|
Am Donnerstag 14 September 2006 14:14 schrieb Linus Walleij (LD/EAB): > > I tried to apply your patch, but I received an error message: > > patching file smsc-ircc2.c > > Hunk #1 FAILED at 2354. > > 1 out of 3 hunks FAILED -- saving rejects to file smsc-ircc2.c.rej > > This patch is against David Millers net-2.6 git tree, that is what we > use for irda development. (David merge patches into mainline.) > > You can get a clone of Davids tree and its smsc-ircc2.c file with > > git-clone > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git > > Then patch that file instead. > > Linus > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > irda-users mailing listgit-clone > > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users My computer had to undergo a major update (change to gcc 4.1 and glibc 2.4), but now I'm ready to test your patch once more. First of all I'm not familiar with the kernel development tools. So before I get something wrong, I'd like to know, if I receive a complete kernel version, when I download git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git. If so I move it to my /usr/src directory, patch the file and start my computer with that kernel right? Greets Andreas |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-21 13:21:33
|
> First of all I'm not familiar with the kernel=20 > development tools. So before I get something wrong, I'd like=20 > to know, if I receive a complete kernel version, when I=20 > download=20 > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git. Not that I consider myself an expert either. I just clone the GIT tree (maninly the /trunk track) then work on the files I need. > If so I move it to my /usr/src directory, patch the file and=20 > start my computer with that kernel right? Well unless many other things changed in the kernel interfaces, it should be OK to copy smsc-ircc2.c and patch it. Linus |
From: Andreas G. <and...@we...> - 2006-09-21 14:28:56
|
Am Donnerstag, 21. September 2006 15:21 schrieb Linus Walleij (LD/EAB): > > First of all I'm not familiar with the kernel > > development tools. So before I get something wrong, I'd like > > to know, if I receive a complete kernel version, when I > > download > > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git. > > Not that I consider myself an expert either. I just clone the > GIT tree (maninly the /trunk track) then work on the files > I need. > > > If so I move it to my /usr/src directory, patch the file and > > start my computer with that kernel right? > > Well unless many other things changed in the kernel interfaces, > it should be OK to copy smsc-ircc2.c and patch it. > > Linus > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users Well I just gave it a try, downloaded the git sources patched the file, rebooted into the new kernel, but still have the exact same symptoms as before. Sep 21 15:48:39 [tosh1800-smcinit] tosh1800-smcinit 0.4 Daniele Peri Sep 21 15:48:39 [tosh1800-smcinit] LPC47N227 chip (ver 0x5a, rev 0x0) found. Configuring: Sep 21 15:48:39 [tosh1800-smcinit] set sirbase=0x2e8, firbase=0x2f8, dma=3, irq=7 Sep 21 15:48:39 [tosh1800-smcinit] set UART 2 IR mode to IrDA, auto powerdown on and powered up Sep 21 15:48:39 [tosh1800-smcinit] LPC47N227 chip (ver 0x5a, rev 0x0) configuration successfully ended Sep 21 15:48:39 [tosh1800-smcinit] PCI device 0x10b9:0x1533 not found So maybe there's another ID for the bridge... Greets Andreas |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-21 14:33:28
|
> Sep 21 15:48:39 [tosh1800-smcinit] tosh1800-smcinit 0.4=20 > Daniele Peri Sep 21 15:48:39 [tosh1800-smcinit] LPC47N227=20 > chip (ver 0x5a, rev 0x0) found.=20 Don't use the smcinit program, it's deprecated. Just modprobe smsc-ircc2 and dmesg... Does it load? Is it on "lsmod"? modprobe smsc-ircc2 modprobe ircomm-tty irattach irda0 -s irdadump Does something happen after this sequence... Linus |
From: Andreas G. <and...@we...> - 2006-09-22 08:46:54
|
Am Donnerstag 21 September 2006 16:33 schrieb Linus Walleij (LD/EAB): > > Sep 21 15:48:39 [tosh1800-smcinit] tosh1800-smcinit 0.4 > > Daniele Peri Sep 21 15:48:39 [tosh1800-smcinit] LPC47N227 > > chip (ver 0x5a, rev 0x0) found. > > Don't use the smcinit program, it's deprecated. Just modprobe > smsc-ircc2 and dmesg... Does it load? Is it on "lsmod"? > > modprobe smsc-ircc2 > modprobe ircomm-tty > irattach irda0 -s > irdadump > > Does something happen after this sequence... > > Linus > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users This is what I get: modprobe smsc-ircc2 FATAL: Error running install command for smsc_ircc2 dmesg says nothing and my system log refers to smcinit: Sep 21 23:36:54 [tosh1800-smcinit] tosh1800-smcinit 0.4 Daniele Peri Sep 21 23:36:54 [tosh1800-smcinit] LPC47N227 chip (ver 0x5a, rev 0x0) found. Configuring: Sep 21 23:36:54 [tosh1800-smcinit] set sirbase=0x2e8, firbase=0x2f8, dma=3, irq=7 Sep 21 23:36:54 [tosh1800-smcinit] set UART 2 IR mode to IrDA, auto powerdown on and powered up Sep 21 23:36:54 [tosh1800-smcinit] LPC47N227 chip (ver 0x5a, rev 0x0) configuration successfully ended Sep 21 23:36:54 [tosh1800-smcinit] PCI device 0x10b9:0x1533 not found Andreas |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-22 09:49:30
|
> modprobe smsc-ircc2 > FATAL: Error running install command for smsc_ircc2 You can also try just brutally poking it in: insmod smsc-ircc2.ko in the dir where you built it. However this I've never seen before and I think it is a bit hard for me to debug remotely, tho I assume it is generic driver compilation/installation know-how. Please consult the Linux device drivers book: http://lwn.net/Kernel/LDD3/ Linus |
From: Andreas G. <and...@we...> - 2006-09-22 10:25:19
|
Am Freitag 22 September 2006 11:49 schrieb Linus Walleij (LD/EAB): > > modprobe smsc-ircc2 > > FATAL: Error running install command for smsc_ircc2 > > You can also try just brutally poking it in: > insmod smsc-ircc2.ko > > in the dir where you built it. > > However this I've never seen before and I think it is a bit > hard for me to debug remotely, tho I assume it is generic > driver compilation/installation know-how. > > Please consult the Linux device drivers book: > http://lwn.net/Kernel/LDD3/ > > Linus > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users Insmod worked, this time I had no reference to smcinit neither in dmesg nor in the system logs, so I guess the error I receive, when I run modprobe has something to do with smcinit intercepting. I even remember that I modified a config file, which could've caused this. Did I understand you correctly that I probably only need to copy smsc-ircc2.c from the net-2.6 sources file to my "normal" kernel sources and patch it afterwards? Anyway many thanks for your support! Greets Andreas |
From: Andreas G. <and...@we...> - 2006-09-22 11:24:58
|
Am Freitag 22 September 2006 12:25 schrieb Andreas Gick: > Am Freitag 22 September 2006 11:49 schrieb Linus Walleij (LD/EAB): > > > modprobe smsc-ircc2 > > > FATAL: Error running install command for smsc_ircc2 > > > > You can also try just brutally poking it in: > > insmod smsc-ircc2.ko > > > > in the dir where you built it. > > > > However this I've never seen before and I think it is a bit > > hard for me to debug remotely, tho I assume it is generic > > driver compilation/installation know-how. > > > > Please consult the Linux device drivers book: > > http://lwn.net/Kernel/LDD3/ > > > > Linus > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your opinions on IT & business topics through brief surveys -- and earn > > cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > irda-users mailing list > > ird...@li... > > http://lists.sourceforge.net/lists/listinfo/irda-users > > Insmod worked, this time I had no reference to smcinit neither in dmesg nor > in the system logs, so I guess the error I receive, when I run modprobe has > something to do with smcinit intercepting. I even remember that I modified > a config file, which could've caused this. > > Did I understand you correctly that I probably only need to copy > smsc-ircc2.c from the net-2.6 sources file to my "normal" kernel sources > and patch it afterwards? > > Anyway many thanks for your support! > > Greets Andreas > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users Now also modprobe works, the driver shows up in lsmod, but irattach doesn't like the irq or something. This is what dmesg tells me after irattach: IRQ handler type mismatch for IRQ 7 [<c012e509>] setup_irq+0x168/0x17e [<e1cc098c>] smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] [<c012e596>] request_irq+0x77/0x94 [<e1cc0680>] smsc_ircc_net_open+0x2e/0xb6 [smsc_ircc2] [<e1cc098c>] smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] [<c03113f0>] sys_sendto+0x11a/0x147 [<c031a561>] dev_open+0x2b/0x5f [<c031915e>] dev_change_flags+0x4a/0xeb [<c031a1f7>] dev_ifsioc+0x12a/0x392 [<c031a96b>] dev_ioctl+0x33b/0x403 [<c012f808>] find_get_page+0x12/0x2d [<c0131baf>] filemap_nopage+0x9d/0x2da [<c0154475>] do_ioctl+0x19/0x4e [<c01546a2>] vfs_ioctl+0x1f8/0x20a [<c01546fc>] sys_ioctl+0x48/0x64 [<c0102a7d>] sysenter_past_esp+0x56/0x79 And for the sake of completeness this is the output of dmesg after modprobe smsc-ircc2: msc_ircc_present: can't get sir_base of 0x3f8 Detected unconfigured Compaq x1000 family SMSC IrDA chip, pre-configuring device. Setting up Intel 82801 controller and SMSC device found SMC SuperIO Chip (devid=0x5a rev=00 base=0x002e): LPC47N227 smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7, mode: 0x0e Seems ok, doesn't it? Greets Andreas |
From: Samuel O. <sa...@so...> - 2006-09-25 00:54:01
|
Hi Andreas, On Fri, Sep 22, 2006 at 01:24:48PM +0200, Andreas Gick wrote: > Now also modprobe works, the driver shows up in lsmod, but irattach doesn't > like the irq or something. This is what dmesg tells me after irattach: > > IRQ handler type mismatch for IRQ 7 > [<c012e509>] setup_irq+0x168/0x17e > [<e1cc098c>] smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] > [<c012e596>] request_irq+0x77/0x94 > [<e1cc0680>] smsc_ircc_net_open+0x2e/0xb6 [smsc_ircc2] > [<e1cc098c>] smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] > [<c03113f0>] sys_sendto+0x11a/0x147 > [<c031a561>] dev_open+0x2b/0x5f > [<c031915e>] dev_change_flags+0x4a/0xeb > [<c031a1f7>] dev_ifsioc+0x12a/0x392 > [<c031a96b>] dev_ioctl+0x33b/0x403 > [<c012f808>] find_get_page+0x12/0x2d > [<c0131baf>] filemap_nopage+0x9d/0x2da > [<c0154475>] do_ioctl+0x19/0x4e > [<c01546a2>] vfs_ioctl+0x1f8/0x20a > [<c01546fc>] sys_ioctl+0x48/0x64 > [<c0102a7d>] sysenter_past_esp+0x56/0x79 Could you try to check if this patch fixes your problem ? You should apply it on top of the latest one you got from Linus: diff --git a/drivers/net/irda/smsc-ircc2.c b/drivers/net/irda/smsc-ircc2.c index 22358ff..da7acf2 100644 --- a/drivers/net/irda/smsc-ircc2.c +++ b/drivers/net/irda/smsc-ircc2.c @@ -1605,7 +1605,7 @@ static int smsc_ircc_request_irq(struct { int error; - error = request_irq(self->io.irq, smsc_ircc_interrupt, 0, + error = request_irq(self->io.irq, smsc_ircc_interrupt, IRQF_SHARED, self->netdev->name, self->netdev); if (error) IRDA_DEBUG(0, "%s(), unable to allocate irq=%d, err=%d\n", Cheers, Samuel. |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-22 11:05:44
|
> Insmod worked, You mean the entire driver works? > this time I had no reference to smcinit=20 > neither in dmesg nor in the system logs, What does dmesg say? It should say something about preconfiguring the chip... > Did I understand you correctly that I probably only need to=20 > copy smsc-ircc2.c from the net-2.6 sources file to my=20 > "normal" kernel sources and patch it afterwards? Yes. Linus |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-22 11:51:29
|
> This is what=20 > dmesg tells me after irattach: >=20 > IRQ handler type mismatch for IRQ 7 > [<c012e509>] setup_irq+0x168/0x17e > [<e1cc098c>] smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] =20 > [<c012e596>] request_irq+0x77/0x94 [<e1cc0680>]=20 > smsc_ircc_net_open+0x2e/0xb6 [smsc_ircc2] [<e1cc098c>]=20 > smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] [<c03113f0>]=20 > sys_sendto+0x11a/0x147 [<c031a561>] dev_open+0x2b/0x5f =20 > [<c031915e>] dev_change_flags+0x4a/0xeb [<c031a1f7>]=20 > dev_ifsioc+0x12a/0x392 [<c031a96b>] dev_ioctl+0x33b/0x403 =20 > [<c012f808>] find_get_page+0x12/0x2d [<c0131baf>]=20 > filemap_nopage+0x9d/0x2da [<c0154475>] do_ioctl+0x19/0x4e =20 > [<c01546a2>] vfs_ioctl+0x1f8/0x20a [<c01546fc>]=20 > sys_ioctl+0x48/0x64 [<c0102a7d>] sysenter_past_esp+0x56/0x79 Aha, hm, yeah .... I guess the IRQ framework is changed a bit in Millers tree, so this file will not work unless you use all of that kernel code I fear. You would have to build your entire kernel based off the net-2.6 sources, can you do that? (I know this is a bit much to ask...) What you could do is take your old kernel file and duplicate the actual changes I made to smsc-ircc2.c instead of applying the patch. It's nothing advanced, just a few lines of code. > And for the sake of completeness this is the output of dmesg=20 > after modprobe > smsc-ircc2: > msc_ircc_present: can't get sir_base of 0x3f8 Detected=20 > unconfigured Compaq x1000 family SMSC IrDA chip,=20 > pre-configuring device. > Setting up Intel 82801 controller and SMSC device found SMC=20 > SuperIO Chip (devid=3D0x5a rev=3D00 base=3D0x002e): LPC47N227 > smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7,=20 > mode: 0x0e > > Seems ok, doesn't it? Yes it preconfigures correctly, that's real nice! However you don't know if the ports, IRQ and DMA are correct until you get it working all the way... Linus |
From: Andreas G. <and...@we...> - 2006-09-22 12:45:49
|
Am Freitag 22 September 2006 13:51 schrieb Linus Walleij (LD/EAB): > > This is what > > dmesg tells me after irattach: > > > > IRQ handler type mismatch for IRQ 7 > > [<c012e509>] setup_irq+0x168/0x17e > > [<e1cc098c>] smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] > > [<c012e596>] request_irq+0x77/0x94 [<e1cc0680>] > > smsc_ircc_net_open+0x2e/0xb6 [smsc_ircc2] [<e1cc098c>] > > smsc_ircc_interrupt+0x0/0x4da [smsc_ircc2] [<c03113f0>] > > sys_sendto+0x11a/0x147 [<c031a561>] dev_open+0x2b/0x5f > > [<c031915e>] dev_change_flags+0x4a/0xeb [<c031a1f7>] > > dev_ifsioc+0x12a/0x392 [<c031a96b>] dev_ioctl+0x33b/0x403 > > [<c012f808>] find_get_page+0x12/0x2d [<c0131baf>] > > filemap_nopage+0x9d/0x2da [<c0154475>] do_ioctl+0x19/0x4e > > [<c01546a2>] vfs_ioctl+0x1f8/0x20a [<c01546fc>] > > sys_ioctl+0x48/0x64 [<c0102a7d>] sysenter_past_esp+0x56/0x79 > > Aha, hm, yeah .... I guess the IRQ framework is changed a bit in > Millers tree, so this file will not work unless you use all of > that kernel code I fear. You would have to build your entire > kernel based off the net-2.6 sources, can you do that? (I know > this is a bit much to ask...) > > What you could do is take your old kernel file and duplicate > the actual changes I made to smsc-ircc2.c instead of applying > the patch. It's nothing advanced, just a few lines of code. > > > And for the sake of completeness this is the output of dmesg > > after modprobe > > smsc-ircc2: > > msc_ircc_present: can't get sir_base of 0x3f8 Detected > > unconfigured Compaq x1000 family SMSC IrDA chip, > > pre-configuring device. > > Setting up Intel 82801 controller and SMSC device found SMC > > SuperIO Chip (devid=0x5a rev=00 base=0x002e): LPC47N227 > > smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7, > > mode: 0x0e > > > > Seems ok, doesn't it? > > Yes it preconfigures correctly, that's real nice! > > However you don't know if the ports, IRQ and DMA are correct until > you get it working all the way... > > Linus > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users Well I've used the net-2.6 kernel already, but nevertheless this problem occurs. If I do dmesg grep -i irq, I get: ACPI: PCI Interrupt Link [C0C2] (IRQs 5 *10) ACPI: PCI Interrupt Link [C0C3] (IRQs 5 *10) ACPI: PCI Interrupt Link [C0C4] (IRQs *5 10) ACPI: PCI Interrupt Link [C0C5] (IRQs *5 10) ACPI: PCI Interrupt Link [C0C6] (IRQs 5 10) *0, disabled. ACPI: PCI Interrupt Link [C0C7] (IRQs 5 10) *11 ACPI: PCI Interrupt Link [C0C8] (IRQs 5 10) *0, disabled. ACPI: PCI Interrupt Link [C0C9] (IRQs *5 10) PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report ACPI: PCI Interrupt Link [C0C4] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [C0C4] -> GSI 5 (level, low) -> IRQ 5 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A 00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ACPI: PCI Interrupt Link [C0C3] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [C0C3] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [C0C4] -> GSI 5 (level, low) -> IRQ 5 ICH4: not 100% native mode: will probe irqs later ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 PNP: PS/2 Controller [PNP0303:C1A3,PNP0f13:C1A4] at 0x60,0x64 irq 1,12 serio: i8042 AUX0 port at 0x60,0x64 irq 12 serio: i8042 AUX1 port at 0x60,0x64 irq 12 serio: i8042 AUX2 port at 0x60,0x64 irq 12 serio: i8042 AUX3 port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 ACPI: PCI Interrupt Link [C0C2] enabled at IRQ 10 ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [C0C2] -> GSI 10 (level, low) -> IRQ 10 ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[90200000-902007ff] Max Packet=[1024] IR/IT contexts=[4/8] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [C0C3] -> GSI 10 (level, low) -> IRQ 10 eth0: RealTek RTL8139 at 0xe0aaa000, 00:02:3f:6b:98:ee, IRQ 10 parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [C0C3] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0C2] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [C0C2] -> GSI 10 (level, low) -> IRQ 10 uhci_hcd 0000:00:1d.0: irq 10, io base 0x000048c0 ACPI: PCI Interrupt Link [C0C5] enabled at IRQ 5 ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [C0C5] -> GSI 5 (level, low) -> IRQ 5 uhci_hcd 0000:00:1d.1: irq 5, io base 0x000048e0 ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [C0C4] -> GSI 5 (level, low) -> IRQ 5 uhci_hcd 0000:00:1d.2: irq 5, io base 0x00004c00 ACPI: PCI Interrupt Link [C0C9] enabled at IRQ 5 ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [C0C9] -> GSI 5 (level, low) -> IRQ 5 ehci_hcd 0000:00:1d.7: irq 5, io mem 0xa0000000 ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [C0C3] -> GSI 10 (level, low) -> IRQ 10 smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7, mode: 0x0e IRQ handler type mismatch for IRQ 7 [<c012e509>] setup_irq+0x168/0x17e [<c012e596>] request_irq+0x77/0x94 Apparently the parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] also uses irq 7, which nowadays doesn't mean much considering irq sharing etc.. But maybe this could be a hint... Greets Andreas |
From: Linus W. \(LD/EAB\) <lin...@er...> - 2006-09-24 21:06:47
|
> smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7,=20 > mode: 0x0e IRQ handler type mismatch for IRQ 7 [<c012e509>]=20 > setup_irq+0x168/0x17e [<c012e596>] request_irq+0x77/0x94 >=20 > Apparently the parport0: PC-style at 0x378 (0x778), irq 7=20 > [PCSPP,TRISTATE] also uses irq 7, which nowadays doesn't mean=20 > much considering irq sharing etc.. But maybe this could be a hint... You can pass in arguments to the module with insmod/modprobe and the=20 preinit will respect them. So try playing around with them, example: modprobe smsc-ircc2 = ircc_dma=3D3,ircc_irq=3D9,ircc_fir=3D0x2f8,ircc_sir=3D0x2e8 (ircc_cfg is obviously correct since you can communicate with the chip.) Get the "Maintenance and Service Guide" for nx7010 from the HP website if there is such a document: the port assignments and IRQ:s are sometimes listed in it! Linus |
From: Andreas G. <and...@we...> - 2006-09-25 11:14:10
|
Am Sonntag, 24. September 2006 23:06 schrieb Linus Walleij (LD/EAB): > > smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7, > > mode: 0x0e IRQ handler type mismatch for IRQ 7 [<c012e509>] > > setup_irq+0x168/0x17e [<c012e596>] request_irq+0x77/0x94 > > > > Apparently the parport0: PC-style at 0x378 (0x778), irq 7 > > [PCSPP,TRISTATE] also uses irq 7, which nowadays doesn't mean > > much considering irq sharing etc.. But maybe this could be a hint... > > You can pass in arguments to the module with insmod/modprobe and the > preinit will respect them. > > So try playing around with them, example: > modprobe smsc-ircc2 ircc_dma=3,ircc_irq=9,ircc_fir=0x2f8,ircc_sir=0x2e8 > > (ircc_cfg is obviously correct since you can communicate with the chip.) > > Get the "Maintenance and Service Guide" for nx7010 from the HP website > if there is such a document: the port assignments and IRQ:s are > sometimes listed in it! > > Linus > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users Now modprobe doesn't seem to work anymore, although no error message is being reported. But after insmod the driver shows up in lsmod. Unfortunately I couldn't manage to pass arguments to the device with insmod. So I get the same error messages about irq mismatch as before. Are there any guides on how to make modprobe work, if insmod works? Regards, Andreas |
From: Andreas G. <and...@we...> - 2006-09-25 14:19:01
|
Am Montag, 25. September 2006 13:13 schrieb Andreas Gick: > Am Sonntag, 24. September 2006 23:06 schrieb Linus Walleij (LD/EAB): > > > smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7, > > > mode: 0x0e IRQ handler type mismatch for IRQ 7 [<c012e509>] > > > setup_irq+0x168/0x17e [<c012e596>] request_irq+0x77/0x94 > > > > > > Apparently the parport0: PC-style at 0x378 (0x778), irq 7 > > > [PCSPP,TRISTATE] also uses irq 7, which nowadays doesn't mean > > > much considering irq sharing etc.. But maybe this could be a hint... > > > > You can pass in arguments to the module with insmod/modprobe and the > > preinit will respect them. > > > > So try playing around with them, example: > > modprobe smsc-ircc2 ircc_dma=3,ircc_irq=9,ircc_fir=0x2f8,ircc_sir=0x2e8 > > > > (ircc_cfg is obviously correct since you can communicate with the chip.) > > > > Get the "Maintenance and Service Guide" for nx7010 from the HP website > > if there is such a document: the port assignments and IRQ:s are > > sometimes listed in it! > > > > Linus > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your opinions on IT & business topics through brief surveys -- and earn > > cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > irda-users mailing list > > ird...@li... > > http://lists.sourceforge.net/lists/listinfo/irda-users > > Now modprobe doesn't seem to work anymore, although no error message is > being reported. But after insmod the driver shows up in lsmod. > Unfortunately I couldn't manage to pass arguments to the device with > insmod. So I get the same error messages about irq mismatch as before. Are > there any guides on how to make modprobe work, if insmod works? > > Regards, > Andreas > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users After having a look at the device under windows, I found out that it uses the irq 7 there, so I removed the printer modules and now it seems to work: irdadump shows something: 15:36:30.839116 xid:cmd d55879b6 > ffffffff S=6 s=0 (14) 15:36:30.927063 xid:cmd d55879b6 > ffffffff S=6 s=1 (14) 15:36:31.015084 xid:cmd d55879b6 > ffffffff S=6 s=2 (14) 15:36:31.103074 xid:cmd d55879b6 > ffffffff S=6 s=3 (14) 15:36:31.191079 xid:cmd d55879b6 > ffffffff S=6 s=4 (14) 15:36:31.279085 xid:cmd d55879b6 > ffffffff S=6 s=5 (14) 15:36:31.367091 xid:cmd d55879b6 > ffffffff S=6 s=* andisschleppes hint=0400 [ Computer ] (30) Btw. andisschleppes is the name of my laptop. But still there's no irda0 device in /dev. This is what dmesg says after running irdattach irda0 -s: Sep 25 14:21:42 [irattach] executing: '/sbin/modprobe irda0' Sep 25 14:21:42 [irattach] executing: 'echo andisschleppes > /proc/sys/net/irda/devname' Sep 25 14:21:42 [irattach] executing: 'echo 1 > /proc/sys/net/irda/discovery' Sep 25 14:21:42 [irattach] Starting device irda0 My mobile phone isn't recognized either, cat /proc/sys/net/irda/discovery still gives 1, when the infrared of my mobile is started. Greets Andreas |
From: <sa...@so...> - 2006-09-25 15:12:26
|
Hi Andreas, On 9/25/2006, "Andreas Gick" <and...@we...> wrote: >Am Montag, 25. September 2006 13:13 schrieb Andreas Gick: > >After having a look at the device under windows, I found out that it uses th= e >irq 7 there, so I removed the printer modules and now it seems to work: > >irdadump shows something: >15:36:30.839116 xid:cmd d55879b6 > ffffffff S=3D6 s=3D0 (14) >15:36:30.927063 xid:cmd d55879b6 > ffffffff S=3D6 s=3D1 (14) >15:36:31.015084 xid:cmd d55879b6 > ffffffff S=3D6 s=3D2 (14) >15:36:31.103074 xid:cmd d55879b6 > ffffffff S=3D6 s=3D3 (14) >15:36:31.191079 xid:cmd d55879b6 > ffffffff S=3D6 s=3D4 (14) >15:36:31.279085 xid:cmd d55879b6 > ffffffff S=3D6 s=3D5 (14) >15:36:31.367091 xid:cmd d55879b6 > ffffffff S=3D6 s=3D* andisschleppes hint= =3D0400 [ >Computer ] (30) > >Btw. andisschleppes is the name of my laptop. But still there's no irda0 >device in /dev. This is what dmesg says after running irdattach irda0 -s: There won't be any irda0 device in /dev, as irda0 is a network interface. Could you try to keep the paralell port driver in and apply the patch I sent to you yesterday ? This might fix your problem. Cheers, Samuel. > >Sep 25 14:21:42 [irattach] executing: '/sbin/modprobe irda0' >Sep 25 14:21:42 [irattach] executing: 'echo andisschleppes >> /proc/sys/net/irda/devname' >Sep 25 14:21:42 [irattach] executing: 'echo 1 > /proc/sys/net/irda/discovery= ' >Sep 25 14:21:42 [irattach] Starting device irda0 > >My mobile phone isn't recognized either, cat /proc/sys/net/irda/discovery >still gives 1, when the infrared of my mobile is started. > >Greets Andreas > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDEV= DEV >_______________________________________________ >irda-users mailing list >ird...@li... >http://lists.sourceforge.net/lists/listinfo/irda-users |
From: Andreas G. <and...@we...> - 2006-09-26 16:48:25
|
Am Montag, 25. September 2006 17:12 schrieben Sie: > Hi Andreas, > > On 9/25/2006, "Andreas Gick" <and...@we...> wrote: > >Am Montag, 25. September 2006 13:13 schrieb Andreas Gick: > > > >After having a look at the device under windows, I found out that it uses > > the irq 7 there, so I removed the printer modules and now it seems to > > work: > > > >irdadump shows something: > >15:36:30.839116 xid:cmd d55879b6 > ffffffff S=3D6 s=3D0 (14) > >15:36:30.927063 xid:cmd d55879b6 > ffffffff S=3D6 s=3D1 (14) > >15:36:31.015084 xid:cmd d55879b6 > ffffffff S=3D6 s=3D2 (14) > >15:36:31.103074 xid:cmd d55879b6 > ffffffff S=3D6 s=3D3 (14) > >15:36:31.191079 xid:cmd d55879b6 > ffffffff S=3D6 s=3D4 (14) > >15:36:31.279085 xid:cmd d55879b6 > ffffffff S=3D6 s=3D5 (14) > >15:36:31.367091 xid:cmd d55879b6 > ffffffff S=3D6 s=3D* andisschleppes > > hint=3D0400 [ Computer ] (30) > > > >Btw. andisschleppes is the name of my laptop. But still there's no irda0 > >device in /dev. This is what dmesg says after running irdattach irda0 -s: > > There won't be any irda0 device in /dev, as irda0 is a network interface. > Could you try to keep the paralell port driver in and apply the patch I > sent > to you yesterday ? This might fix your problem. > > Cheers, > Samuel. > > >Sep 25 14:21:42 [irattach] executing: '/sbin/modprobe irda0' > >Sep 25 14:21:42 [irattach] executing: 'echo andisschleppes > > > >> /proc/sys/net/irda/devname' > > > >Sep 25 14:21:42 [irattach] executing: 'echo 1 > > > /proc/sys/net/irda/discovery' Sep 25 14:21:42 [irattach] Starting device > > irda0 > > > >My mobile phone isn't recognized either, cat /proc/sys/net/irda/discovery > >still gives 1, when the infrared of my mobile is started. > > > >Greets Andreas > > > >------------------------------------------------------------------------- > >Take Surveys. Earn Cash. Influence the Future of IT > >Join SourceForge.net's Techsay panel and you'll get the chance to share > > your opinions on IT & business topics through brief surveys -- and earn > > cash > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV > > _______________________________________________ > >irda-users mailing list > >ird...@li... > >http://lists.sourceforge.net/lists/listinfo/irda-users Tried your patch, but the patch command tells me: patch -p0 < smsc-ircc2.c.2.patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: =2D------------------------- |diff --git a/drivers/net/irda/smsc-ircc2.c b/drivers/net/irda/smsc-ircc2.c |index 22358ff..da7acf2 100644 |--- a/drivers/net/irda/smsc-ircc2.c |+++ b/drivers/net/irda/smsc-ircc2.c =2D------------------------- =46ile to patch: /usr/src/linux/drivers/net/irda/smsc-ircc2.c patching file /usr/src/linux/drivers/net/irda/smsc-ircc2.c patch: **** malformed patch at line 6: =A0{ Greets Andreas |