From: Grant Grundler <grundler@parisc-linux.org>
To: Julien Cristau <julien.cristau@ens-lyon.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: Linux v2.6.17 - PCI Bus hidden behind transparent bridge
Date: Mon, 17 Jul 2006 09:31:28 -0600 [thread overview]
Message-ID: <20060717153128.GA16679@colo.lackof.org> (raw)
In-Reply-To: <20060717142917.GJ5299@bryan.is-a-geek.org>
On Mon, Jul 17, 2006 at 04:29:17PM +0200, Julien Cristau wrote:
> Loading the driver with modprobe doesn't change anything (it just
> outputs the 'Loaded prism54 driver' line), the device still doesn't
> appear in lspci or ifconfig -a.
Uhm, that's a different symptom than "doesn't work" :)
thanks for clarifying.
Sounds more like a problem with the Cardbus controller not providing
access to PCI config space, not telling PCI generic code there is a
PCI bus below it, or something like that.
Can you post "lspci -vvv -s 02:09" output for 2.6.17 as well?
I'd like to compare the CardBus bridge config info for both (2:09.0
and 02:09.1) controllers on both kernel releases.
thanks,
grant
next prev parent reply other threads:[~2006-07-17 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 1:59 Linux v2.6.17 Linus Torvalds
2006-06-18 2:06 ` Linus Torvalds
2006-06-18 3:30 ` Brice Goglin
2006-06-18 3:47 ` Linus Torvalds
2006-06-19 1:39 ` Petr Baudis
2006-06-18 13:49 ` Adrian Bunk
2006-06-18 16:44 ` Linus Torvalds
2006-06-19 21:25 ` Adrian Bunk
2006-06-19 14:23 ` Mark Lord
2006-06-18 10:54 ` Michael Buesch
2006-06-18 16:47 ` Andre Tomt
2006-06-18 17:05 ` Michael Buesch
2006-07-16 19:34 ` Linux v2.6.17 - PCI Bus hidden behind transparent bridge Julien Cristau
2006-07-17 14:13 ` Grant Grundler
2006-07-17 14:29 ` Julien Cristau
2006-07-17 15:31 ` Grant Grundler [this message]
2006-07-17 16:13 ` Julien Cristau
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=20060717153128.GA16679@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=julien.cristau@ens-lyon.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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