On Tue, 2008-02-05 at 08:08 +0100, [EMAIL PROTECTED] wrote:
Hi,
Few days ago, a bug was reported that the i810fb uses mode_option
parameters while other framebuffers uses the mode parameter to set initial
mode. It was spotted later that some drivers uses mode_option, some uses
mode and
On Tue, 2008-02-05 at 12:42 +0100, Alain Kalker wrote:
P.S.: Krzysztof, maybe it would be a good idea to update fbmode.txt
too, as there are now many more framebuffer drivers which support video
mode naming.
I have to rephrase that, the situation is much more complicated (sigh).
The only
Alain Kalker napisał:
From Documentation/fb/modedb.txt:
---
When a frame buffer device receives a video= option it doesn't know, it
should consider that to be a video mode option. If no frame buffer
device is specified in a video= option, fbmem considers that to be a
global video mode
On Tue, 2008-02-05 at 13:09 +0100, Alain Kalker wrote:
parameter name 'video_mode'
That should be 'mode_option'.
Need More Coffee ASAP
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Tue, 2008-02-05 at 13:40 +0100, [EMAIL PROTECTED] wrote:
Alain Kalker napisał:
From Documentation/fb/modedb.txt:
---
When a frame buffer device receives a video= option it doesn't know, it
should consider that to be a video mode option. If no frame buffer
device is specified in a
5 matches
Mail list logo
