From: Mike Mackovitch <macko@chelsio.com>
To: John Hesterberg <jh@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: driver location for platform-specific drivers
Date: Mon, 11 Feb 2002 14:58:33 -0800 [thread overview]
Message-ID: <20020211145833.A3635@wacko.asicdesigners.com> (raw)
In-Reply-To: <20020211131744.A16032@sgi.com>
In-Reply-To: <20020211131744.A16032@sgi.com>; from jh@sgi.com on Mon, Feb 11, 2002 at 01:17:44PM -0600
On Mon, Feb 11, 2002 at 01:17:44PM -0600, John Hesterberg wrote:
>
> For SGI's upcoming Linux platform (nicknamed Scalable Node, or SN),
> we have some platform specific device drivers. Where should these go?
> I see several precedents in the current kernels.
>
> [...]
>
> 2) Company (sgi) directory.
> There is already an sgi directory, strangely enough.
> I *think* this was meant to be a platform directory for the
> discontinued SGI 320/540 Visual Workstations. However, maybe
You are mistaken. The cruft in drivers/sgi mostly dates back to the
attempts on the SGI Indy platform to get SGI's IRIX X server *binary*
running under Linux (note that this work was NOT done by SGI).
The SGI Visual Workstation work was mostly done within the i386 arch
code; the framebuffer driver (sgivwfb.[ch]) was put in drivers/video;
and some other drivers had some modifications that were guarded
by CONFIG_VISWS or CONFIG_VISWS_HACKS. (There was also a project that
enabled multi-process accelerated/direct-rendered graphics on that
platform, but that code was never released due to the fact that the
project was killed the week it was demonstrated at SIGGRAPH'99.)
--macko
next prev parent reply other threads:[~2002-02-11 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 19:17 John Hesterberg
2002-02-11 19:54 ` Tom Rini
2002-02-11 22:58 ` Mike Mackovitch [this message]
2002-02-12 5:19 ` Linus Torvalds
[not found] <mailman.1013455503.17805.linux-kernel2news@redhat.com>
2002-02-11 20:57 ` Pete Zaitcev
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=20020211145833.A3635@wacko.asicdesigners.com \
--to=macko@chelsio.com \
--cc=jh@sgi.com \
--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®