public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: driver location for platform-specific drivers
Date: Mon, 11 Feb 2002 19:54:58 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698806032@msgid-missing> (raw)

On Mon, Feb 11, 2002 at 01:17:44PM -0600, John Hesterberg wrote:

>     3) New platform directory.
>        Create a platform directory for SN, probably drivers/sn.
>        There is precedence for this with the drivers/macintosh


Being a PPC person, I sometimes wonder if this wsn't a horrible idea
sometimes.  Much of whats in thereshould be in a 'drivers/adb' or so,
ince it's all specific to the ADB bus, with the exception of things like
'rtc.c' (which works on all PPC except APUS).  Keep in mind other
'macintosh' specific drivers, like network ones, are in drivers/net/.

Wer also have an arch/ppc/{8xx,8260}_io/ directories for other
platform-specific drivers, which I want to kill in 2.5.x timeframe.

> I'm happy with whatever you'll accept.  To give you something to
> either agree with or shoot down, I'll suggest #3.  SGI's Scalable
> Node product will be different enough, with enough platform specific
> drivers, that it justifies it's own subdirectory, and that this
> should be called drivers/sn.

What excelty are the specific to tho?  Are these all for a new bus?
If these are just variopus network, io, whatnot drivers, just put them
in drivers/whatever.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


             reply	other threads:[~2002-02-11 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 19:54 Tom Rini [this message]
2002-02-11 20:57 ` [Linux-ia64] Re: driver location for platform-specific drivers Pete Zaitcev
2002-02-12  5:19 ` Linus Torvalds

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=marc-linux-ia64-105590698806032@msgid-missing \
    --to=trini@kernel.crashing.org \
    --cc=linux-ia64@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