Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Matthew Wilcox <willy@debian.org>
Cc: 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: 30 Sep 2003 10:32:23 -0500	[thread overview]
Message-ID: <1064935949.1930.6.camel@mulgrave> (raw)
In-Reply-To: <20030930135914.GW24824@parcelfarce.linux.theplanet.co.uk>

On Tue, 2003-09-30 at 08:59, Matthew Wilcox wrote:
> It makes a lot of sense to treat all the devices that firmware tells us
> about as parisc_devices since we treat them all the same way.  If we
> were stepping over ourselves saying "well, yes, this is a pluggable
> device and therefore we have to access it like that, but this one's
> on the motherboard and therefore we treat it like that", I'd agree.
> But all these devices are in the same namespace, firmware tells us
> about all of them in the same way, so I think we should continue with
> the parisc_device.

Yes, I was just musing about the way we did it.  In theory, the
difference between a "platform" device and a generic device is that a
generic device has a bus, and a platform one doesn't.  The
platform_device also has a resource pointer and a few other bits and
pieces the generic device doesn't.

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.

I was just wondering if it wouldn't make more sense now for us to be
using platform devices too...

James


> >From a historical perspective, we've had parisc_devices in
> one form or another since the very start of the project.
> They were called hp_devices until about August 2001.  See
> http://ftp.parisc-linux.org/patches/parisc_device-2.diff for the
> conversion.
> 
> I don't know much about Amiga/Zorro.  Maybe it'd make sense for Amiga
> platform devices to be faked as zorro_devices, but I doubt it.  In
> any case, the 4000T SCSI is a 53c710, not a 720.
> 
> -- 
> "It's not Hollywood.  War is real, war is primarily not about defeat or
> victory, it is about death.  I've seen thousands and thousands of dead bodies.
> Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-09-30 15:33 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 [this message]
2003-09-30 19:03                 ` Grant Grundler
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=1064935949.1930.6.camel@mulgrave \
    --to=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