From: "Michael Stiller" <michael@toyland.ping.de>
To: "Erik Mouw" <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cardbus Bridge no IRQ in 2.4.6
Date: 16 Jul 2001 09:02:06 +0200 [thread overview]
Message-ID: <20010716070206.2056.qmail@toyland.ping.de> (raw)
In-Reply-To: Your message of "Mon, 16 Jul 2001 00:31:08 +0200." <20010716003107.I13239@arthur.ubicom.tudelft.nl>
>
> Let me guess: a Lucent Orinico PCI adapter, right? It should work with
> linux-2.4.6, I submitted a patch for 2.4.6-pre8 (or so) and it is
> included in linux-2.4.6. I currently have it working on two non-SMP
> systems (ALi 1541 and Intel 440FX chipsets).
Actually it is something compatible from ELSA.
I tried your suggestions and it didn't work. On your machines, does the card
get an interrupt from the bios during init?
My Bios (PCI v2.1) only prints CardBus Adapter, no IRQ is assigned.
I already tried different slots. I guess it's a bios problem but i'm interested
to make it work without the help of the bios. At least the bios is only
a pice of software...
> Make sure that the Cardbus driver is not a module. IOW: your kernel
> configuration should have these lines:
Did that. Interesting messages during kernel boot:
PCI->APIC IRQ transform: (B1,I0,P0) -> 16
got res[20000000:20000fff] for resource 0 of Texas Instruments PCI1410 \
PCcard Cardbus Controller
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus]
PCI: Enabling device 00:13.0 (0000 -> 0002)
PCI: No IRQ known for interrupt pin A of device 00:13.0. Probably buggy MP
table.
Isn't it possible to assign an interrupt to INT A of this device ? IOW, fix
what
is considered a buggy MP table ?
Yenta IRQ list 0000, PCI irq0
Socket status: 10000047
Cheers,
-Michael
prev parent reply other threads:[~2001-07-16 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-15 12:58 Michael Stiller
2001-07-15 22:31 ` Erik Mouw
2001-07-16 7:02 ` Michael Stiller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010716070206.2056.qmail@toyland.ping.de \
--to=michael@toyland.ping.de \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®