Re (4): Display on IBM ThinkPad A22m
- To: firstname.lastname@example.org
- Cc: email@example.com
- Subject: Re (4): Display on IBM ThinkPad A22m
- From: firstname.lastname@example.org
- Date: Sun, 5 Aug 2012 14:56:59 -0700
- Message-id: <email@example.com>
- References: <20120218125411.GD20674@khazad-dum.debian.net> <firstname.lastname@example.org> <20120718001120.GA20440@khazad-dum.debian.net>
* From: Henrique de Moraes Holschuh <email@example.com>
* Date: Tue, 17 Jul 2012 21:11:20 -0300
> Contact him directly, it is probably the only way.
For anyone else interested in the r128 this is Connor's
> ... radeon driver as of 2005 had a lot of obsolete code for mode
> validation. I assume this code is still in r128. At some time between
> 2005 and 2012 when UMS was dropped, radeon got switched over to a
> different type of UMS that used functions in the X server that are more
> correct. Fixing this sounds like quite a project.
> I'm pretty sure the problem has been solved for UMS and KMS. It's just
> that the KMS solution in the current radeon driver wouldn't be
> applicable to r128 unless we also edit the r128 kernel module to support
> KMS (something I hope to do eventually). Radeon has seen a progression
> from "old UMS code" -> "new UMS code" -> KMS while r128 is still stuck
> with old UMS code. Getting it to use new UMS code seems like the more
> realistic thing to do. And if I learn a decent amount of stuff from that
> effort, I might know enough to try KMS after.
So in some aspects, r128 is significantly outdated; there is plenty of work
for anyone interested. Meanwhile a working VESA driver could be better than
broken other driver.
Regards, ... Peter E.
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Telephone 1 360 639 0202. Bcc: peter at easthope.ca
http://carnot.yi.org/ "http://members.shaw.ca/peasthope/index.html#Itinerary "