On Tue, 2007-05-22 at 16:36 -0700, Jesse Barnes wrote:
On Tuesday, May 22, 2007, Benjamin Herrenschmidt wrote:
On Tue, 2007-05-22 at 08:39 -0700, Jesse Barnes wrote:
The current code does its best to figure out what modes are available
and tries to pick a good one for each display. It
On Thu, 2007-05-17 at 15:32 -0700, Jesse Barnes wrote:
Randy just informed me that the patch limits are bigger now, so here are the
actual patches.
This patch allows for proper console unregistration via the VT layer, and
updates the FB layer to use it. This makes debugging new console
Alan Hourihane wrote:
On Fri, 2005-09-23 at 22:07 +0800, Antonino A. Daplas wrote:
Alan Hourihane wrote:
Has anyone any objections to me removing the MTRR code from the DRM.
It doesn't have the intimate knowledge needed to properly configure
MTRR's and fails in many cases.
There are two
Alan Hourihane wrote:
Has anyone any objections to me removing the MTRR code from the DRM.
It doesn't have the intimate knowledge needed to properly configure
MTRR's and fails in many cases.
There are two cases currently, one for the framebuffer and a second for
the entire AGP space.
Jon Smirl wrote:
On 8/7/05, Antonino A. Daplas [EMAIL PROTECTED] wrote:
Vladimir Dergachev wrote:
I agree that something like the above is acceptable, exept that we need
an extra field for offset and another if indexed color or not. So
something like:
A:2/0/R:10/2/G:10/12/B:10/22//I
Jon Smirl wrote:
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When green is set and red/blue are missing gray scale is set.
No, if
Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Smirl wrote:
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When
Vladimir Dergachev wrote:
I agree that something like the above is acceptable, exept that we need
an extra field for offset and another if indexed color or not. So
something like:
A:2/0/R:10/2/G:10/12/B:10/22//I
This is getting more cryptic by the minute.
Can't we have a simple field:
On Tuesday 15 March 2005 21:36, Ville Syrjälä wrote:
On Tue, Mar 15, 2005 at 09:51:40AM +0100, Geert Uytterhoeven wrote:
On Tue, 15 Mar 2005, Ville [iso-8859-1] Syrj??wrote:
If radeonfb will allocate the buffer for the second head from the top
of the memory users would basically have to
On Wednesday 26 January 2005 23:23, [EMAIL PROTECTED] wrote:
(With new savagefb X server starts, but screen is very messed, moving mouse
cursor makes things even worse. X is useless with my Twister [8d02] and
savagefb.)
Try
Option UseBIOS false
Tony
On Tuesday 14 September 2004 00:28, Jon Smirl wrote:
Doesn't the base platform need to be designed to also treat individual
heads as resources?
fbdev only sets the mode on a single head. My cards have more that one
head. When I tried adding mode setting to DRM so that I could handle
my other
On Saturday 11 September 2004 13:19, Dave Airlie wrote:
The other thing I think some people are confusing is 2.4 fbdev and 2.6...
there is no console support in 2.6 fbdev drivers, it is all in the fbcon
stuff, so the fbdev drivers are only doing 2d mode setting and monitor
detection, some
12 matches
Mail list logo
