From: James Bottomley <James.Bottomley@steeleye.com>
To: Helge Deller <deller@gmx.de>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] 32bit parisc kernel 2.6.1 and pcmcia
Date: 19 Jan 2004 09:38:54 -0500 [thread overview]
Message-ID: <1074523135.2201.6.camel@mulgrave> (raw)
In-Reply-To: <200401191007.19929.deller@gmx.de>
On Mon, 2004-01-19 at 04:07, Helge Deller wrote:
> Yenta: CardBus bridge found at 0000:00:02.0 [0000:0000]
> Yenta: ISA IRQ mask 0x0000, PCI irq 98
> Socket status: 30000007
> Yenta: CardBus bridge found at 0000:00:02.1 [0000:0000]
> Yenta: ISA IRQ mask 0x0000, PCI irq 99
> Socket status: 30000007
Hmm, that's not too good. It should look something like
Yenta: CardBus bridge found at 0000:00:02.0 [0000:0000]
Yenta: setting irqmux to INTA,INTB
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta: ISA IRQ mask 0x0000, PCI irq 98
Socket status: 30000410
cs MEM ports 0xf0804000-0xf0804fff allocated in parent Dino parisc8:0
LMMIO 0
others)
cs IO ports 0x0-0x3f allocated in parent Dino I/O Port
The relevant points are the lines routing all the interrupts to PCI
(because we can't do ISA interrupts).
The fixes I put into yenta were only for the PCI1410 (well, 13xx) yenta
sockets, probably something extra has to be done to fix this one up.
James
next prev parent reply other threads:[~2004-01-19 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 19:59 [parisc-linux] 32bit parisc kernel 2.6.1 and pcmcia Helge Deller
2004-01-18 23:44 ` James Bottomley
2004-01-19 9:07 ` Helge Deller
2004-01-19 14:38 ` James Bottomley [this message]
2004-01-19 5:59 ` Grant Grundler
2004-01-19 9:03 ` Helge Deller
2004-01-19 14:35 ` James Bottomley
2004-01-19 21:48 ` Helge Deller
2004-01-20 0:50 ` Grant Grundler
2004-01-20 1:16 ` James Bottomley
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=1074523135.2201.6.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=deller@gmx.de \
--cc=parisc-linux@lists.parisc-linux.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