From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] VBE 1.2/2.0+ functions for Plan9
Date: Thu, 25 Nov 2004 22:08:47 -0500 [thread overview]
Message-ID: <ee9e417a04112519082e8380e3@mail.gmail.com> (raw)
In-Reply-To: <C8C3EA7A-3F57-11D9-BC96-000A9573A128@rogers.com>
> Please correct me if I am wrong on this:
> Is it true that the XFree86 device driver modules are platform
> portable, as long as they are for the same instruction set
> architecture? For some rason I thought the Linux and BSD mobs could
> swap video drivers around amoungst themselves.
As long as you want to use them for X.
> If so, would it be possible to create some sort of adapter code that
> would wrap the x11 device drivers for Plan9 use?
Possible? Yes. Particularly easy? Nowhere close.
The X interface is much more complicated than the
Plan 9 interface, and the interface is very different.
In particular Plan 9 splits the job between user space
and the kernel, while X goes through some hoops to
do everything in user space. I doubt I would want to load
X modules into the kernel, even if someone did do the
huge amount of work to pull it off.
I wonder if instead there is a way to pull the relevant
information out of the code and generate a Plan 9
driver in its place. That would still be a lot of work, but
the final pieces might be better for our use.
Russ
next prev parent reply other threads:[~2004-11-26 3:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 3:03 Fwd: " Bob Hartley
2004-11-26 3:04 ` boyd, rounin
2004-11-26 3:08 ` Russ Cox [this message]
2004-11-26 4:19 ` Bob Hartley
2004-11-26 5:52 ` Devon H. O'Dell
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 16:44 Devon H. O'Dell
2004-11-25 17:13 ` rog
2004-11-25 18:57 ` Devon H. O'Dell
2004-11-29 20:21 ` Jack Johnson
2004-11-30 12:51 ` rog
2004-11-30 10:40 ` Devon H. O'Dell
2004-11-30 11:08 ` Tiit Lankots
2004-11-30 11:21 ` Devon H. O'Dell
2004-11-30 11:28 ` Tiit Lankots
2004-11-30 11:37 ` Devon H. O'Dell
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=ee9e417a04112519082e8380e3@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/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).