From: Adam Belay <abelay@novell.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] PCI bridge driver rewrite
Date: Mon, 28 Feb 2005 18:50:38 -0500 [thread overview]
Message-ID: <1109634638.28403.101.camel@localhost.localdomain> (raw)
In-Reply-To: <20050224100332.A26582@flint.arm.linux.org.uk>
On Thu, 2005-02-24 at 10:03 +0000, Russell King wrote:
> On Thu, Feb 24, 2005 at 01:22:01AM -0500, Adam Belay wrote:
> > 5.) write a bridge driver for Cardbus hardware
>
> We have this already - it's called "yenta".
Yes, I'm aware. It should read:
5.) adapt the Yenta driver to the new PCI bus class
:)
>
> What you need to be aware of is that cardbus hardware is special - it
> may change its resource requirements at any time, both in terms of the
> number of BUS IDs it wishes to consume, and the number and size of
> IO and memory resources.
We can have default sizes allocated for these windows. Maybe, we'll
even have rebalancing at some point.
As for BUS IDs, I'm not sure about the best behavior. I don't really
like reserving 4 positions like we do now. It has a tendency to create
conflicts, and seems to be unnecessary. How common are PCI bridge
devices that attach to cardbus controllers? Does the BIOS ever
preconfigure the cardbus bridge for this situation? I think it's
important that we get bus numbering correct. Some hardware has problems
now.
>
> Note also that if a cardbus bridge isn't on the root bus (it happens on
> some laptops) these resource changes may impact on upstream bridges and
> devices.
>
Yeah, also legacy resources can't pass through properly if the parent
bridge isn't transparent. Complex bus topologies make the problem much
more difficult when legacy hardware is involved.
Thanks,
Adam
next prev parent reply other threads:[~2005-02-28 23:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 6:22 [RFC] PCI bridge driver rewrite Adam Belay
2005-02-24 6:45 ` Jon Smirl
2005-02-24 7:03 ` Adam Belay
2005-02-24 7:25 ` Jon Smirl
2005-02-28 23:39 ` Adam Belay
2005-02-24 23:02 ` Jesse Barnes
2005-02-28 23:27 ` Adam Belay
2005-02-28 23:38 ` Jesse Barnes
2005-03-01 0:13 ` Adam Belay
2005-03-01 0:34 ` Jesse Barnes
2005-02-24 10:03 ` Russell King
2005-02-28 23:50 ` Adam Belay [this message]
2005-02-25 23:38 ` Greg KH
2005-02-28 23:58 ` Adam Belay
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 16:33 Nguyen, Tom L
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=1109634638.28403.101.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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