Console drivers

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

Hello,

On Nov 14, 2006, at 17:15, Marco Trillo wrote:

> On 11/11/06, Marco Trillo <marcotrillogmail.com> wrote:
>> But there is still a problem: although the monitor
is set up
>> correctly, the driver thinks it's still running at
640 x 480
>> resolution mode, and so it creates a 640 x 480
display:
>>
>> radeonfb0: display 0: virtual resolution 640x480 at
32 bpp
>> radeonfb0: port 0: physical 1024x768 89Hz
>> radeonfb0: port 1: physical 1024x768 89Hz
>>
>> So it creates a small box of 640 x 480 pixels at
the left edge of the
>> screen, and the rest of the 1024 x 768 space is not
used (it appears
>> filled with a blue-ish color).
>
> Well, I finally got it working ! (a patch is attached)
>
> 'radeonfb.c' has some checks to pickup a virtual
resolution larger
> than the physical resolution, so if there are multiple
monitors
> present, the smaller one will use panning.
> But there were some places (like when the default
videomode is
> selected) when that check wasn't made.
>
> I tried to fix this, a diff to the 'radeonfb.c' file is
attached
> (hopefully Gmail won't base64-encode the patch).
>
> It works fine now for me ! Hope it doesn't break
anything !
>
> The relevant dmesg section with the new patch is:
>
> radeonfb_pickres picked 640x480
> radeonfb0: port 0: physical 1024x768 89Hz
> radeonfb0: port 1: physical 1024x768 89Hz
> radeonfb0: display 0: virtual resolution 1024x768 at 32
bpp

Thanks, I'll have a look at it.

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

iQEVAwUBRVpdLcpnzkX8Yg2nAQK2VwgArOfaMLEmRCRhnBetXi/7YJYoTrA4
cSo0
il/S9NNjKQXHR4xblyKp14OfUTehD+oMzgvMo9elMAVwVQzXkxt4ld0BEvFd
5tuv
ABbf169UZSEkTpIHKnkCDiTPMlMLzJdFmV7GkwA3AkLsTiZufviSs10/FO0e
mfM6
Nb3hmgGRxNivqkQN1GayJu/LsAj4iF+EMe5K/sw2Z35IG7pRokbzO9wAGP0g
DHrE
NRXGfl1ejIr/cnOxmww6hLKwqBnI3bVRZkDdYVSZES4SwkMhZSzEtMerJoKF
hn5B
l2HlBxxM4ny3lin9J+Kjhaq/Xt0ybw7VFdVFTfgEK0GDrVeyVjhVmw==
=4pO5
-----END PGP SIGNATURE-----