Thread (7 messages) 7 messages, 3 authors, 2005-11-14

Re: Use of 'reserved' fields in var_screeninfo

From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: 2005-11-14 20:00:46

On Mon, 14 Nov 2005, Kevin Hilman wrote:
Kevin Hilman wrote:
quoted
Geert Uytterhoeven wrote:
quoted
What do you want to export there?
I'm just weighing the options of whether I should just add a new
device-specific ioctl, or try to export this as part of the var_screeninfo.
Come to think of it, no matter what I added to the screeninfo struct,
fbcon_switch() would have to be hacked to not disrupt any new fields since it
does a memset-to-zero.

I think a device-specific ioctl is the way to go.
That's indeed the best solution for now, until we have a real API for handling
multiple planes.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help