Hi, ________________________________________________________________________ Thanks anyways, I got it to work with the earlier email (thanx Tapeshwar Nath :)). What I was striving for was the penguin logo :). I had to compile the driver into the kernel for that though.
probably the same would go in 2.6 too.
Its quite different in the 2.6 kernel. Its been officially included in the kernel as i810fb.
BTW, does anybody know if I can get the logo without compiling the framebuffer and the fbcon drivers into the kernel? How? I tried for days, just could'nt get it. Finally settled with bloating my kernel by a few KBs. (Sorry boss... the penguin's kinda cool ;))
Regards, Siddhesh.
On 11 Sep 2003, Siddhesh Poyarekar spake thusly:
BTW, does anybody know if I can get the logo without compiling the framebuffer and the fbcon drivers into the kernel? How? I tried for days, just could'nt get it. Finally settled with bloating my kernel by a few KBs. (Sorry boss... the penguin's kinda cool ;))
If you are going to use it, isnt it better off in the kernel? It will be fractionally faster than loading from disk.
On 12 Sep 2003, q u a s i wrote:
If you are going to use it, isnt it better off in the kernel? It will be fractionally faster than loading from disk.
Actually speed has nothing to do with it. See, using frame buffer requires switching the BIOS display mode. This can only be done while the processor is still in real mode. Once the processor enters protected mode (which is one of the first things the kernel does), it is impossible to make a BIOS call.
Read /usr/src/linux/Documentation/fb/vesafb.txt for details.
On Fri, 12 Sep 2003, Philip S. Tellis spake thusly:
On 12 Sep 2003, q u a s i wrote:
If you are going to use it, isnt it better off in the kernel? It will be fractionally faster than loading from disk.
Actually speed has nothing to do with it. See, using frame buffer requires switching the BIOS display mode. This can only be done while the processor is still in real mode. Once the processor enters protected mode (which is one of the first things the kernel does), it is impossible to make a BIOS call.
I fear I disagree. Using framebuffer does /not/ require switching the BIOS display mode. Using vesafb requires that. That is the reason, if you are using vesafb, you cannot switch modes once you boot. VESA is generic and implimented in the BIOS (or VGA BIOS).
Card specific framebuffer drivers can be loaded at runtime. Modes can be changed anytime.
He was talking about the i810 driver. And I was talking in general about putting required modules into the kernel. It saves a bit of time which modprobe requires. And i did say 'fractionally'. :-)
On 12 Sep 2003, q u a s i wrote:
I fear I disagree. Using framebuffer does /not/ require switching the
yeah, my bad on that.
He was talking about the i810 driver. And I was talking in general
I thought he was talking about the tux logo that shows up at boot time. that requires vesafb.
-
Philip S Tellis -
q u a s i -
Siddhesh Poyarekar