From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: wje@fir.esd.sgi.com (William J. Earl)
Cc: knobi@munich.sgi.com, alambie@wellington.sgi.com,
shaver@neon.ingenia.ca, linux@cthulhu.engr.sgi.com
Subject: Re: init=/bin/sh and serial devices
Date: Wed, 9 Apr 1997 11:40:47 -0700 (PDT) [thread overview]
Message-ID: <199704091840.LAA21362@yon.engr.sgi.com> (raw)
In-Reply-To: <199704091831.LAA27695@fir.esd.sgi.com> from "William J. Earl" at Apr 9, 97 11:31:04 am
:
:Martin Knoblauch writes:
:...
: > this brings up the question: do we already have drivers for
: > the textport? Not to speak of an X-Server? How are we (SGI)
: > going to handle this? As far as I know we never published
: > the hardware dependent parts on the X11 distribution, did we?
:...
:
: With management authorization, I provided the technical details
:for the graphics hardware (and all the other Indy hardware) to David
:Miller, who I believe got a textport driver working.
:
Also, the agreement we signed with David was that all the Linux work
including those low level drivers will be released under the GPL
i.e. anyone who cares would be able to look at these driver sources.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: "William J. Earl" <wje@fir.esd.sgi.com>
Cc: knobi@munich.sgi.com, alambie@wellington.sgi.com,
shaver@neon.ingenia.ca, linux@cthulhu.engr.sgi.com
Subject: Re: init=/bin/sh and serial devices
Date: Wed, 9 Apr 1997 11:40:47 -0700 (PDT) [thread overview]
Message-ID: <199704091840.LAA21362@yon.engr.sgi.com> (raw)
Message-ID: <19970409184047.SMkQBullMG3Hzwdl3b9dJ-db7kbEFjfiFcqIvAMVJfs@z> (raw)
In-Reply-To: <199704091831.LAA27695@fir.esd.sgi.com> from "William J. Earl" at Apr 9, 97 11:31:04 am
:
:Martin Knoblauch writes:
:...
: > this brings up the question: do we already have drivers for
: > the textport? Not to speak of an X-Server? How are we (SGI)
: > going to handle this? As far as I know we never published
: > the hardware dependent parts on the X11 distribution, did we?
:...
:
: With management authorization, I provided the technical details
:for the graphics hardware (and all the other Indy hardware) to David
:Miller, who I believe got a textport driver working.
:
Also, the agreement we signed with David was that all the Linux work
including those low level drivers will be released under the GPL
i.e. anyone who cares would be able to look at these driver sources.
--
Peace, Ariel
next prev parent reply other threads:[~1997-04-09 18:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-09 2:09 init=/bin/sh and serial devices Mike Shaver
1997-04-09 14:22 ` Alistair Lambie
[not found] ` <alambie>
1997-04-09 14:29 ` Alistair Lambie
1997-04-09 14:31 ` Alistair Lambie
1997-04-09 14:24 ` Alistair Lambie
1997-04-09 4:29 ` Alex deVries
1997-04-09 18:46 ` Ariel Faigon
1997-04-09 18:46 ` Ariel Faigon
1997-04-09 7:06 ` Martin Knoblauch
1997-04-09 18:31 ` William J. Earl
1997-04-09 18:40 ` Ariel Faigon [this message]
1997-04-09 18:40 ` Ariel Faigon
1997-04-09 19:30 ` Alistair Lambie
1997-04-14 8:17 ` David S. Miller
1997-04-14 18:05 ` William J. Earl
1997-04-15 2:09 ` David S. Miller
1997-04-18 22:35 ` Alistair Lambie
1997-04-18 22:35 ` Alistair Lambie
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=199704091840.LAA21362@yon.engr.sgi.com \
--to=ariel@yon.engr.sgi.com \
--cc=alambie@wellington.sgi.com \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=knobi@munich.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=shaver@neon.ingenia.ca \
--cc=wje@fir.esd.sgi.com \
/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