Date: Mon, 11 Feb 2002 14:58:33 -0800
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
Message-ID: <20020211145833.A3635@wacko.asicdesigners.com>
In-Reply-To: <20020211131744.A16032@sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.15i
In-Reply-To: <20020211131744.A16032@sgi.com>; from jh@sgi.com on Mon, Feb 11, 2002 at 01:17:44PM -0600
Sender: linux-kernel-owner@vger.kernel.org

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/