Date: Mon, 15 Sep 2008 01:59:25 -0300 From: "Carlos A. M. dos Santos" <unixmania@gmail.com> To: "Xin LI" <delphij@delphij.net> Cc: FreeBSD Current <current@freebsd.org>, olli@freebsd.org Subject: Re: Why VESA and DPMS are available only for i386? Message-ID: <e71790db0809142159q54ed6f03u710a86b199e3f064@mail.gmail.com> In-Reply-To: <48CD837C.9050206@delphij.net> References: <e71790db0809021849q1c22690sec4f3c6e7f5f8b34@mail.gmail.com> <48CD837C.9050206@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 14, 2008 at 6:34 PM, Xin LI <delphij@delphij.net> wrote: > Carlos A. M. dos Santos wrote: >> Hello, >> >> Several PRs were closed based on the argument that FreeBSD/amd64 >> cannot call to the VESA BIOS. XFree86 solved this problem by means of >> the INT10 module. I believe that it would be possible to do the same >> on the FreeBSD kernel. >> >> Is there any ongoing effort to enable the VESA kernel moule on >> non-i386 platform? Is there any particular difficulty for doing this, >> besides depending on VM86? >> > According to VESA's VBE 3.0 standard, there is a "Protected Mode Entry > Point" [optionally] provided by BIOS, which OS or application is > supposed to copy to a place where it is writable. The code there would > be written in 16-bit protected mode. Therefore I think it's do-able... > > http://www.vesa.org/public/VBE/vbe3.pdf > > Cheers, I'm reading the specification and digging at the code of the X server and the X VESA driver. Look promising. -- cd /usr/ports/sysutils/life make clean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e71790db0809142159q54ed6f03u710a86b199e3f064>