public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <abelay@novell.com>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] PCI bridge driver rewrite
Date: Mon, 28 Feb 2005 19:13:17 -0500	[thread overview]
Message-ID: <1109635997.28403.123.camel@localhost.localdomain> (raw)
In-Reply-To: <200502281538.18881.jbarnes@sgi.com>

On Mon, 2005-02-28 at 15:38 -0800, Jesse Barnes wrote:
> On Monday, February 28, 2005 3:27 pm, Adam Belay wrote:
> > How can we specify which bus to target?
> 
> Maybe we could have a list of legacy (ISA?) devices for drivers like vgacon to 
> attach to?  The bus info could be stuffed into the legacy device structure 
> itself so that the platform code would know what to do.

Are these devices actually legacy, or PCI with compatibility interfaces?

I think a "struct isa_device" would be be useful.  Would a pointer to
the "struct pci_bus" do the trick?

> 
> > Also is the legacy IO space mapped to IO Memory on the other side of the
> > bridge?
> 
> How do you mean?  Legacy I/O port accesses just become strongly ordered memory 
> transactions, afaik, and legacy memory accesses are dealt with the same way.
> 
> Jesse

I was just wondering if we have to reserve a memory range for this?

Thanks,
Adam



  reply	other threads:[~2005-03-01  0:14 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 [this message]
2005-03-01  0:34             ` Jesse Barnes
2005-02-24 10:03 ` Russell King
2005-02-28 23:50   ` Adam Belay
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=1109635997.28403.123.camel@localhost.localdomain \
    --to=abelay@novell.com \
    --cc=greg@kroah.com \
    --cc=jbarnes@sgi.com \
    --cc=jonsmirl@gmail.com \
    --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