On Sat, 2007-06-23 at 12:49 +0200, Michal Januszewski wrote:
My apologies for the delayed response. I had problems with my ISP.
> uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
> version of vesafb and a direct successor of vesafb-tng [1].
>
> uvesafb uses a userspace h
On Tue, Jun 26, 2007 at 11:42:41AM +0100, Jonathan McDowell wrote:
> Have you considered using libx86[1] in v86d? It looks very similar to
> what you have at present and there are plans to extend it to non
> x86(_64) archs.
It looks like an interesting solution and it is indeed similar to what
I'
On Sat, Jun 23, 2007 at 12:49:20PM +0200, Michal Januszewski wrote:
> uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
> version of vesafb and a direct successor of vesafb-tng [1].
>
> uvesafb uses a userspace helper application (v86d, [2]) to run the x86
> Video BIOS code.
On Sat, Jun 23, 2007 at 02:04:09PM +0200, Arnd Bergmann wrote:
> On Saturday 23 June 2007, Michal Januszewski wrote:
> > The current implementation of v86d can use either LRMI or
> > x86emu to run the BIOS code and supports both x86 and x86_64.
>
> Is there a fundamental reason why you can't also
On Saturday 23 June 2007, Michal Januszewski wrote:
> The current implementation of v86d can use either LRMI or
> x86emu to run the BIOS code and supports both x86 and x86_64.
Is there a fundamental reason why you can't also run it on
non-x86 machines, or has this simply not been tested so far?
uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
version of vesafb and a direct successor of vesafb-tng [1].
uvesafb uses a userspace helper application (v86d, [2]) to run the x86
Video BIOS code. This makes it possible to include in uvesafb all the
standard features (refr
6 matches
Mail list logo
