From: Grant Grundler <grundler@parisc-linux.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Matthew Wilcox <willy@debian.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Rene Brothuhn <rene.br@web.de>,
Roman Zippel <zippel@linux-m68k.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
parisc-linux@parisc-linux.org,
Linux/PPC on APUS development
<linux-apus-devel@lists.sourceforge.net>
Subject: Re: [parisc-linux] Re: NCR53c720
Date: Tue, 30 Sep 2003 13:03:29 -0600 [thread overview]
Message-ID: <20030930190329.GC7391@dsl2.external.hp.com> (raw)
In-Reply-To: <1064935949.1930.6.camel@mulgrave>
On Tue, Sep 30, 2003 at 10:32:23AM -0500, James Bottomley wrote:
> What I did for PA was to create a parisc bus type, and attach all the
> inventoried hardware to it. This blurs the bus distinction in generic
> device because we have several inventoried buses: Runway, GSC, LASI etc.
> that are all lumped under the parisc bus.
All those busses conform to the HP IO ADC and thus could be
considered the same type of bus. Except for LASI, the above makes
sense to me.
LASI isn't a bus. This would be a candidate for "platform device"
since it's bridge-like device with integrate sub-devices.
EISA bridge chips might be a similar case.
> I was just wondering if it wouldn't make more sense now for us to be
> using platform devices too...
I don't understand "platform devices" vs "PCI devices" unless we
are talking about "custom", arch specific bridge chips.
A GSC device is a GSC device regardless of which board it's soldered to.
That's not the case for PCI?
grant
next prev parent reply other threads:[~2003-09-30 19:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0309291116250.7432-100000@vervain.sonytel.be>
[not found] ` <Pine.LNX.4.44.0309291434260.17812-100000@serv>
2003-09-29 13:33 ` [parisc-linux] Re: NCR53c720 Matthew Wilcox
2003-09-29 13:45 ` Geert Uytterhoeven
2003-09-29 16:24 ` Roman Zippel
2003-09-29 16:27 ` Matthew Wilcox
2003-09-29 20:55 ` Grant Grundler
2003-09-29 21:00 ` James Bottomley
2003-09-30 17:23 ` Grant Grundler
2003-09-29 21:25 ` Rene Brothuhn
2003-09-30 2:21 ` Matthew Wilcox
2003-09-30 8:21 ` Geert Uytterhoeven
2003-09-30 13:47 ` James Bottomley
2003-09-30 13:59 ` Matthew Wilcox
2003-09-30 15:32 ` James Bottomley
2003-09-30 19:03 ` Grant Grundler [this message]
2003-09-30 13:59 ` Rene Brothuhn
2003-09-30 14:32 ` Matthew Wilcox
2003-10-07 20:22 ` Rene Brothuhn
2003-09-30 14:55 ` Roman Zippel
2003-10-07 20:24 ` Rene Brothuhn
2004-05-04 7:22 Joel Soete
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=20030930190329.GC7391@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=James.Bottomley@steeleye.com \
--cc=geert@linux-m68k.org \
--cc=linux-apus-devel@lists.sourceforge.net \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=parisc-linux@parisc-linux.org \
--cc=rene.br@web.de \
--cc=willy@debian.org \
--cc=zippel@linux-m68k.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