From: Bob Hartley <bob.hartley@rogers.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Fwd: [9fans] VBE 1.2/2.0+ functions for Plan9
Date: Thu, 25 Nov 2004 22:03:44 -0500 [thread overview]
Message-ID: <C8C3EA7A-3F57-11D9-BC96-000A9573A128@rogers.com> (raw)
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.
If so, would it be possible to create some sort of adapter code that
would wrap the x11 device drivers for Plan9 use?
Sorry if this is a naive/misbegotten thought,
regards,
Robert
> On Nov 25, 2004, at 1:57 PM, Devon H. O'Dell wrote:
>
>> rog@vitanuova.com wrote:
>>>> I got some tips to look in Inferno code, since Roger Peppe had
>>>> implemented a VESA driver there. After looking through the Inferno
>>>> source, it appears that any VESA code has been left out of the
>>>> public
>>>> source.
>>> the code is here:
>>> http://www.vitanuova.com/dist/vesa.tgz
>
> <snip>
>
>>> cheers,
>>> rog.
>>
>> Thanks for this code, Roger! I'm definitely going to take a look at
>> it. I think I'm going to start with a VBE3.0 driver, since that can
>> be implemented fully in protected mode, and then look at implementing
>> some kind of emulation (similar to what XFree86 might do) for VBE 1.2
>> and 2.0. This is a real help for that, in any case. You'll definitely
>> hear from me if I've got questions :).
>>
>> Kind regards,
>>
>> Devon H. O'Dell
>>
>
next reply other threads:[~2004-11-26 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 3:03 Bob Hartley [this message]
2004-11-26 3:04 ` boyd, rounin
2004-11-26 3:08 ` Russ Cox
2004-11-26 4:19 ` Bob Hartley
2004-11-26 5:52 ` 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=C8C3EA7A-3F57-11D9-BC96-000A9573A128@rogers.com \
--to=bob.hartley@rogers.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).