From: Andreas Tobler <toa@pop.agri.ch>
To: mlan@cpu.lu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: pci-detection of Cardbus cards.
Date: Tue, 28 Mar 2000 12:11:04 +0200 [thread overview]
Message-ID: <38E08532.F607A0F5@pop.agri.ch> (raw)
In-Reply-To: 200003271944.VAA01622@piglet.grunz.lu
Hi Michel,
Michel Lanners wrote:
[snip]
> > Also, how would it be best to integrate the detection of such cards? In
> > the patch above the special bridge TI1131 was hardcoded. But as I know,
> > other PB's (Lombard) uses different (TI1211 or so) chips.
> > Is it necessary to code all different chips or is there a generaL approach?
>
> No, search by device class:
> (from include/linux/pci_ids.h)
> #define PCI_CLASS_BRIDGE_CARDBUS 0x0607
>
> .... which is what's being done:
> +#if defined(SCAN_CARDBUS)
> + if ((dev->class >> 8) == PCI_CLASS_BRIDGE_PCI ||
> + (dev->class >> 8) == PCI_CLASS_BRIDGE_CARDBUS) {
> +#else
> if ((dev->class >> 8) == PCI_CLASS_BRIDGE_PCI) {
> +#endif
>
You mean adding this to the 2399p3 code would show some more results?
Have to try.
[snip]
> > 01:00.0 Ethernet controller: Xircom: Unknown device 0003 (rev 03)
> > Subsystem: Unknown device 115d:1181
> > 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: 20 min, 40 max, 40 set
> > Interrupt: pin A routed to IRQ 255
> > Region 0: I/O ports at <unassigned>
>
> Hmmm... memory got assigned, but not IO ports? Who's supposed to assign
> those? And IRQ info is wrong... Are you sure the above patch is run
> _before_ the existing fixup function? It doesn't seem to cooperate
> well... See also this in your previous mail:
The IRQ is wrong, but when I run the pcmcia_cs package the IRQ got on
22/23 as expected from ti1131. And as long as it works without
bombing....
Well here I have to clarify, the patch I spoke about I only applied to
2215p14 and not to the 2399p3 where the PCI-fixup is added.
> > Found 00:99 [104c/ac15] 000607 02
> > Fixups for bus 00
> > Scanning CardBus bridge 00:13.0
> > Scanning CardBus bridge 00:13.1
> > Bus scan for 00 returning with max=09
> ^^
> A bit high, the number of PCI buses so far ;-)
>
> Plus, bus 1 (the one with your CardBus devices) never gets scanned, so
> it's probably not in the chain of buses, and doesn't get resources
> assigned.
I have to play around with the sources.
Hope so today.
Thanks,
Andreas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-03-28 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-27 17:31 pci-detection of Cardbus cards Andreas Tobler
2000-03-27 19:44 ` Michel Lanners
2000-03-27 21:09 ` Andreas Tobler
2000-03-28 10:11 ` Andreas Tobler [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=38E08532.F607A0F5@pop.agri.ch \
--to=toa@pop.agri.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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;
as well as URLs for NNTP newsgroup(s).