Port-powerpc archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Where arch/bebox/pci/pfb.c?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On May 18, 2008, at 11:46, Tim Rightnour wrote:

On 17-May-2008 Michael Lorenz wrote:
And I have a new problem.  Both of the match() of vga and genfb
returns 1.
Therefore, which attaching is tried cannot be specified.  Isn't it
return
value revokable dynamic in some methods we?

genfb is intended to be a catch-all fallback for graphics cards where
we can find the framebuffer but don't have a native driver for it.
Drivers like chipsfb, machfb etc. all return 100 they match something
so they'd win against genfb.

If vga works I'd say stick with it.

It's my understanding that the vga device driver is useless on bebox. If you have genfb working, is there any reason you want vga to attach? I would think
once you have genfb working, you yank vga from the config.

From what I can tell, the vga driver is only really useful on i386/ amd64. For
all other ports, framebuffer drivers seem to be the way to go.

vga works on shark for instance, and probably on alpha. Reminds me, I need to split up chipsfb and write chipsfb at ofbus glue ( or steal about 95% of it from igsfb at ofbus ) I'd say use a framebuffer console if the firmware sets one up. If the firmware uses VGA text mode use that instead ( and optionally a framebuffer console for high resolution )

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBSDBSacpnzkX8Yg2nAQKQvQf+MzsBu8YM+hn2y41Xo2p357fTBU/N6nf+
NvJGDodJXgPAtqci6hLx8YP0u7afY1fBYWM8PmlINg+dgKpATHZ2E6T0+Il28DOC
t+b9XjJPEY/d1KKY/aW8OFIgklQu2tAf+WzHXuvuqWSguPyi+TYZiImJaK38KT6k
snIAey0qkZEwD4RMLlCNwRb6OHnTqjme+OKT0feie5Z0yrJDSeZT38kYYXXbxY30
xVWYR8BOG3yY4n6gNry/dTCRrYR2zu5ToidlybyTfsyiXNjwmJV2gxAJsgGitThT
cr0nevKWDZ4TLwxAND5hdTDLg/Taz+S5XywgETH5rjgEDha/ESsYGQ==
=SBMr
-----END PGP SIGNATURE-----


Home | Main Index | Thread Index | Old Index