lkml.org 
[lkml]   [2000]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Fwd: ACPI & I4L irq confilct: bug reporting on kernel 2.4.0-test8-pre4
Date
On Wed, 06 Sep 2000, you wrote:
> On Wed, 6 Sep 2000, Guido Trentalancia wrote:
> > On Wed, 06 Sep 2000, you wrote:
> > > Guido Trentalancia schrieb:
> > > > >Motherboard: ASUS P2B-F with the latest bios bx2f113.awd (microcode
> > > > > update) ISDN: Winbond based card (Hisax type=36)
> > > > >The problem is that if I compile the kernel (2.4.0-test8
> > > > > pre1,pre2,pre3,pre4) with both ACPI support and ISDN support there
> > > > > is a conflict in irq 9. I think ACPI first get irq 9 and then Hisax
> > > > > can't get it. Consequentially Hisax doesn't work if ACPI support is
> > > > > enabled. With ACPI turned off, everything works fine as with
> > > > > previous kernel test6 and test5 and ....
> > > >
> > > > after further testing the problem seems to be in IRQ SHARING.
> > > > in fact, with acpi disabled, once the hisax has got irq 9 (it is not
> > > > possible for card type 36 to change the irq), i can load the ethernet
> > > > modules 8390 and ne2k-pci for my ethernet PCI NE2000 card, but the
> > > > ne2k-pci driver also set its irq=9, so everytime i try to do:
> > > >
> > > > ifconfig eth0 up
> > > > SIOCSIFFLAGS: resource temporarily unavailable
> > > >
> > > > why don't add the irq parameter to the hisax winbond driver and to
> > > > the ne2k-pci driver ?
> > >
> > > there is no need or even sense to add such parameter, as irqs are
> > > assigned by the bios or OS for PCI type cards. The driver is supplied
> > > with the selected irq which is normally assigned during boot by the
> > > systems bios.
> >
> > my bios irq settings are currently set to AUTO.
> > i don't know why 3 resources (ne2k-pci, the winbond isdn module and the
> > acpi) want the same irq 9 whereas there are a lot of free irqs...
> > the manteiner of the ACPI driver sayd his driver is ok for irq
> > sharing.... what about ne2k and winbond isdn ? i don't know how to
> > contact the manteiners of this drivers....
>
> The ne2k-pci driver will share IRQs.
> The 'ne' driver will work for PCI cards, but is intended for ISA cards. It
> will not share the IRQ.
>
> Documentation for the ne2k-pci driver is at
> http://www.scyld.com/network/ne2k-pci.html
>
> > 1) ACPI
> > 2) ISDN (Windbond - HiSax)
> > 3) RealTek PCI NE2000 ethernet
>
> Is the ISDN card a PCI device? If not, it cannot share IRQs.

yes it is

> If it is a PCI device, the driver is broken.

in fact this is the most probrably hypothesis of my problems....
this reply has been also forwarded to the author of the winbond driver
(a guy from the czech republic) and to cornelius (many thanx for your
comments).
to confirm this hypotesis i can just compile the kernel with both
acpi and ethernet but without the isdn driver. if irq sharing is ok
then the problem must be in the file drivers/isdn/w6692.[ch]
thanx a lot to everybody supporting linux and in particular to
those who are helping me in this tedious problem.

>
> Donald Becker becker@scyld.com
> Scyld Computing Corporation http://www.scyld.com
> 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution
> Annapolis MD 21403

--
bye,
Guido Trentalancia
please reply via email: guido.trentalancia@tin.it
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.040 / U:0.764 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site