mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: jh@sgi.com
Cc: linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org
Subject: Re: driver location for platform-specific drivers
Date: Mon, 11 Feb 2002 15:57:49 -0500	[thread overview]
Message-ID: <200202112057.g1BKvnE03302@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1013455503.17805.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1013455503.17805.linux-kernel2news@redhat.com>

> For SGI's upcoming Linux platform (nicknamed Scalable Node, or SN),
> we have some platform specific device drivers.  Where should these go?

>     1) Integrate in drivers/*.

I'd do this, unless you have dozens of them.
E.g. drivers/net/sunhme.c.

>     2) Company (sgi) directory.

That's nonsense, IMHO.

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

I think this is only done if API is different. Often these
directories cannot be processed by a build process on other
architectures, so they are kept outside to have Makefiles smaller.
See also drivers/sbus, which could be called "drivers/sun" just
as well. But really, it's separate because of sparc_alloc_io().

I appreciate a lot that drivers/acpi is so easy to exclude
from builds - it breaks on anything but Intel stuff.

>     4) New architecture directory.
>        Another suggestion is to create an architecture directory,
>        in this case drivers/ia64/{char,net,etc.}/.

See #3. The ia64 uses standard APIs.

> I'm happy with whatever you'll accept.

Yeah, lessee what penguins say, and also I think DaveM may
lend some good expirience here.

-- Pete

       reply	other threads:[~2002-02-11 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1013455503.17805.linux-kernel2news@redhat.com>
2002-02-11 20:57 ` Pete Zaitcev [this message]
2002-02-11 19:17 John Hesterberg
2002-02-11 19:54 ` Tom Rini
2002-02-11 22:58 ` Mike Mackovitch
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=200202112057.g1BKvnE03302@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=jh@sgi.com \
    --cc=linux-ia64@linuxia64.org \
    --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

all inboxes | Powered by JetHome®