[haiku-development] Re: Makeshift patch for PPC

> "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote:
> > "Urias McCullough" <umccullough@xxxxxxxxx> wrote:
> > > has to be worked around still). I also removed vesa from the PPC
> > > image, as the vm86 changes clearly make it somewhat x86-specific
> > > now.
> >
> > Yeah, that will have to be changed again, as the VESA driver is
> > needed
> > at the minimum. Well, maybe we could create an OpenFirmware driver
> > for
> > PPC, but we'll probably going to need the same mechanism in
> > "Screen" as
> > before on x86 -- I must admit I completely forgot about that when I
> > applied Jan's changes.
>
> Oops. Quite frankly I was well aware that I introduced this
> dependency with my
> patches. But as the VESA VBE is x86 specific by definition I didn't
> care
> much. I assumed that it's built on x86 only but that doesn't seem to
> be the
> case...

I recall seeing a Linux-ppc patch to implement vm86 emulation on ppc to
be able to run the VESA BIOS on those, that seemed a bit clumsy but
maybe the only way to really get some cards working.

Does app_server actually hardcode "vesa" ?
As long as there is a device published it should try it before using
vesa anyway, so if we make sure to publish an of-fb device it shouldn't
be a problem.

The same problem with be there for m68k anyway.

What about instead of using a "fallback_" or other prefix or suffix,
like "vesa_fallback", and filtering out strstr("_fallback") at the
first pass when finding devices ?

Another option is to have a "fallback" symlink pointing to "vesa" or
"of" or whatever, but that requires the driver publishing it via devfs.

Picking the first one won't work anymore when we want to support
multiple card/screens anyway.

François.

Other related posts: