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,
linux-pci@atrey.karlin.mff.cuni.cz, len.brown@intel.com
Subject: Re: [RFC][PATCH] PCI bridge driver rewrite (rev 02)
Date: Mon, 07 Mar 2005 18:57:22 -0500 [thread overview]
Message-ID: <1110239842.12485.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200503071543.31089.jbarnes@sgi.com>
On Mon, 2005-03-07 at 15:43 -0800, Jesse Barnes wrote:
> On Monday, March 7, 2005 3:39 pm, Jon Smirl wrote:
> > How is sys/bus/platform/* going to work for IA64 machine line SGI SVN?
> > SVN supports multiple simultaneously active legacy spaces, that means
> > that there can be multiple floppy, serial, ps/2, etc controllers.
> > Should these devices be hung off from the bridge they are on?
>
> Probably, though no one in their right mind is going to put anything like that
> on these machines (sn2 btw) :). VGA cards will hopefully be the only devices
> of this type that we'll have installed.
>
> Jesse
Well, if the system supports ACPI, then in theory it could have any
number/configuration of legacy devices, and we'd know everything about
them including exactly where to put them in the device tree. However, I
agree that legacy hardware will be less common in this architecture.
Adam
prev parent reply other threads:[~2005-03-08 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 22:32 [RFC][PATCH] PCI bridge driver rewrite (rev 02) Adam Belay
2005-03-07 23:03 ` Jon Smirl
2005-03-08 0:20 ` Adam Belay
2005-03-08 4:56 ` Kyle Moffett
2005-03-07 23:39 ` Jon Smirl
2005-03-07 23:43 ` Jesse Barnes
2005-03-07 23:57 ` Adam Belay [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=1110239842.12485.3.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=greg@kroah.com \
--cc=jbarnes@sgi.com \
--cc=jonsmirl@gmail.com \
--cc=len.brown@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.