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

[Michael Lorenz <macallan%NetBSD.org@localhost>]

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

Hello,

On May 15, 2008, at 12:15, Izumi Tsutsui wrote:

> > Since this is ultimately machine dependent I don't think attempting
> > to put it into genfb would be a good idea - so far genfb is
> > completely MI and I'd like to keep it that way.
>
> That's the reason why pfb.c was in arch/bebox/pci?

I doubt it - it's probably a copy/paste job with some hacking to make  
it work, but I'm not exactly familiar with the bebox code so that's  
nothing but my gut feeling.
IMHO the right thing to do is to have MD code that puts the video  
hardware into a state genfb can use or figures out how the firmware  
set it up and then hands control over to genfb or some other driver  
if available. Early console should either use firmware calls ( like  
sparc and sparc64 do ) or set up a simple rasops console like powerpc/ 
OF does. The latter is still MD since about 90% of the code would be  
gathering parameters ( which we could cache for genfb )

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

iQEVAwUBSCxlk8pnzkX8Yg2nAQL1qwgAuqFSCo+ul9QoNCmnIAoFUwPVrUR4olgI
APgkB18Uwc17rlL/l6ssD2N9loUXtqk2eYpkzHDIQBRZvMZVeFoEPprm/NVuVSVa
ubFEM3SQJFM5ZEUPPFao/mB3+L82N7XBJPvvd/2omC+kGPvNr8HgeZdaptochphR
dvMpe2ERkt1frVQVYZqTOVU3kfNtA7ynq6LNoWmRlUN3h6/s+0OzQlWlwJVDb+JD
X0W14jnsBBe1M7k80JPFZDWYl8wn/vAyhsIol+NK2c0JVZxYAzaGKYpx6bTajLjQ
9UYGM107lmasbEsYHGLf2bqbj2x3quD9bXM3hQsmx4SLccPNvWipTw==
=I2MQ
-----END PGP SIGNATURE-----