Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-)
From: Alex Stewart <hidden>
Date: 2004-04-28 23:36:12
Possibly related (same subject, not in this thread)
- 2004-04-30 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · James Simmons <hidden>
- 2004-04-29 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · Otto Solares <hidden>
- 2004-04-21 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · Benjamin Herrenschmidt <benh@kernel.crashing.org>
- 2004-04-21 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · James Simmons <hidden>
- 2004-04-21 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · Benjamin Herrenschmidt <benh@kernel.crashing.org>
quoted
The tty layer alreasy stores the resolution. See asm/termios.h. What it lacks is depth and frequency. I have to do some digging to see if the VT220 dealt with that data. I bet it did. Well, for what it's worth, I think that's wrong too.Well it's the POSIX standard.
Yeah, I know, but that doesn't mean I have to agree with it. :) Anyway, my point is just that ttys should only care about characters. In the console system, fbcon is what does the translation from a character-based display to a pixel-based display. Thus, nothing above fbcon should have any notion (or any need to have a notion) of pixels, color depths, frequency timings, or any of that. -alex ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click