From: Nigel Roles <nigel@9fs.org>
To: Vester Thacker <vester.thacker@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Generic Plan 9 to Linux video api shim.
Date: Mon, 20 Sep 2004 14:01:29 +0100 [thread overview]
Message-ID: <414ED4A9.3090404@9fs.org> (raw)
In-Reply-To: <32a656c2040920043066bdbefe@mail.gmail.com>
Vester Thacker wrote:
>Hi Everyone,
>
>A friend of mine wrote asking "Why doesn't somebody write a generic
>Plan9-to-Linux-video-api shim? It would be inefficient as all getout,
>I suppose, but anybody who can't live without playing Doom on Plan 9
>is perverted enough that a quick call to hyaku-to-ban is in order."
>
>Being a Plan 9 advocate, I'm sure that I'll get this asked this question again.
>I don't have an answer for him. Anyone care to comment?
>
>--Vester "Vic" Thacker
>
>p.s. Hyaku-to-ban is japanese for police station.
>
>
>
Not sure what you are proposing. Do you mean incorporate Linux drivers into
Plan 9? I think you are referring to graphics drivers, but you might
mean video
(as in video for linux). Whatever way up it is, it's not a shim. Drivers
are not
standalone objects in any operating system; they rely on a whole environment
provided by other parts of the operating system.
If you want graphics drivers, then you probably actually want a 'shim' to
XFree86 as that is where Linux gets most of its graphics drivers from.
Alternatively, you could work with the framebuffer device drivers; there
are less of them, but more than there are for Plan 9!
Is this what you had in mind?
next prev parent reply other threads:[~2004-09-20 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 11:30 Vester Thacker
2004-09-20 13:01 ` Nigel Roles [this message]
2004-09-20 13:45 ` Vester Thacker
2004-09-20 14:03 ` Nigel Roles
2004-09-20 14:16 Caerwyn B Jones
2004-09-20 15:04 ` Nigel Roles
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=414ED4A9.3090404@9fs.org \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.edu \
--cc=vester.thacker@gmail.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;
as well as URLs for NNTP newsgroup(s).