Date: Tue, 10 Jul 2007 16:42:29 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: jhb@freebsd.org Cc: zhangweiwu@realss.com, smithi@nimnet.asn.au, freebsd-mobile@freebsd.org Subject: Re: unable to map IRQ for my pccard Message-ID: <20070710.164229.763346042.imp@bsdimp.com> In-Reply-To: <200707101518.59366.jhb@freebsd.org> References: <Pine.BSF.3.96.1070708235221.20740C-100000@gaia.nimnet.asn.au> <1183942480.6901.15.camel@joe.realss.com> <200707101518.59366.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200707101518.59366.jhb@freebsd.org>
John Baldwin <jhb@freebsd.org> writes:
: On Sunday 08 July 2007 08:54:40 pm Zhang Weiwu wrote:
: > > > cbb0: <TI1250 PCI-CardBus Bridge> mem 0x20822000-0x20822fff at
: > > > device 2.0 on pci0 pccard0: <16-bit PCCard bus> on cbb0
: > > > cbb1: <TI1250 PCI-CardBus Bridge> mem 0x20821000-0x20821fff at
: > > > device 2.1 on pci0 pccard1: <16-bit PCCard bus> on cbb1
: > > > $PIR: ROUTE_INTERRUPT failed.
: > > > cbb: Unable to map IRQ...
: > > > device_attach: cbb1 attach returned 12
:
: We tried to set the IRQ for your device and the BIOS choked. Can you get the
: output from /usr/src/tools/tools/pirtool for your machine?
Once upon a time, I encountered many BIOSes that would happily map the
first interrupt on an interrupt pin at the PIC. Further ones would
result in an error, so I made the code ignore errors all the time.
Looks like they are no longer ignored. I never found out if ignoring
the error was OK or not, since the documentation was a bit thin in
that area.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070710.164229.763346042.imp>