[arch-dev-public] Kernel framebuffer logo
I've been testing various forms of the new logo for use in the kernel framebuffer and I still think the best implementation is to use no logo at all. The inherint disadvatange is that more and more monitors are widescreen these days and that means the logo proportions are distorted (short and wide) in the framebuffer since standard vga settings use a 4:3 ratio. This is just my two cents of course, but I suggest that we remove the logo from the framebuffer altogether.
Am Donnerstag, 24. Januar 2008 22:31:52 schrieb Thayer Williams:
The inherint disadvatange is that more and more monitors are widescreen these days and that means the logo proportions are distorted (short and wide) in the framebuffer since standard vga settings use a 4:3 ratio.
Isn't this configurable? E.g. I use 1280x1024 which is 5:4 and everything seems fine. -- archlinux.de
2008/1/24, Thayer Williams <thayerw@gmail.com>:
I've been testing various forms of the new logo for use in the kernel framebuffer and I still think the best implementation is to use no logo at all. The inherint disadvatange is that more and more monitors are widescreen these days and that means the logo proportions are distorted (short and wide) in the framebuffer since standard vga settings use a 4:3 ratio.
ehm, don't these users set some widescreen framebuffer modes anyway? I mean - when no framebuffer is used (thus 80x25 text mode) - no logo is visible anyway; when framebuffer is used - users set widescreen mode anyway (if possible). So I don't see a problem here. With uvesafb included in 2.6.24 users can check if their BIOS supports widescreen modes by # cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
This is just my two cents of course, but I suggest that we remove the logo from the framebuffer altogether.
-- Roman Kyrylych (Роман Кирилич)
On Jan 24, 2008 3:47 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2008/1/24, Thayer Williams <thayerw@gmail.com>:
I've been testing various forms of the new logo for use in the kernel framebuffer and I still think the best implementation is to use no logo at all. The inherint disadvatange is that more and more monitors are widescreen these days and that means the logo proportions are distorted (short and wide) in the framebuffer since standard vga settings use a 4:3 ratio.
ehm, don't these users set some widescreen framebuffer modes anyway? I mean - when no framebuffer is used (thus 80x25 text mode) - no logo is visible anyway; when framebuffer is used - users set widescreen mode anyway (if possible). So I don't see a problem here. With uvesafb included in 2.6.24 users can check if their BIOS supports widescreen modes by # cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
Thayer isn't talking about SUPPORT at all. He's saying that when a user uses a non 4:3 ration resolution, the logo is going to be stretched and ugly.
2008/1/24, Aaron Griffin <aaronmgriffin@gmail.com>:
On Jan 24, 2008 3:47 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2008/1/24, Thayer Williams <thayerw@gmail.com>:
I've been testing various forms of the new logo for use in the kernel framebuffer and I still think the best implementation is to use no logo at all. The inherint disadvatange is that more and more monitors are widescreen these days and that means the logo proportions are distorted (short and wide) in the framebuffer since standard vga settings use a 4:3 ratio.
ehm, don't these users set some widescreen framebuffer modes anyway? I mean - when no framebuffer is used (thus 80x25 text mode) - no logo is visible anyway; when framebuffer is used - users set widescreen mode anyway (if possible). So I don't see a problem here. With uvesafb included in 2.6.24 users can check if their BIOS supports widescreen modes by # cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
Thayer isn't talking about SUPPORT at all. He's saying that when a user uses a non 4:3 ration resolution, the logo is going to be stretched and ugly.
When a user uses a non 4:3 ratio resolution - (s)he would better use widescreen framebuffer mode. That's what I've said. The logo will NOT be distorted in that case. I see no reason to use 4:3 framebuffer mode on a 5:4 or 16:10 display - IMHO it's better not to use the framebuffer at all in that case. -- Roman Kyrylych (Роман Кирилич)
Thursday 24 January 2008, Thayer Williams wrote: | I've been testing various forms of the new logo for use in the | kernel framebuffer and I still think the best implementation is to | use no logo at all. The inherint disadvatange is that more and | more monitors are widescreen these days and that means the logo | proportions are distorted (short and wide) in the framebuffer | since standard vga settings use a 4:3 ratio. | | This is just my two cents of course, but I suggest that we remove | the logo from the framebuffer altogether. i'm against using no logo. either we use the linux 2.0 penguin or our official logo. how did you test it, what did you try? what was wrong besides wrong proportions (that can be fixed specifying the right size of screen to the fb)? if you need some help transforming the logo to look nice, let me know, - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
On Jan 24, 2008 3:31 PM, Thayer Williams <thayerw@gmail.com> wrote:
I've been testing various forms of the new logo for use in the kernel framebuffer and I still think the best implementation is to use no logo at all. The inherint disadvatange is that more and more monitors are widescreen these days and that means the logo proportions are distorted (short and wide) in the framebuffer since standard vga settings use a 4:3 ratio.
Hrm, Roman pointed something out that somehow slipped my mind. The framebuffer logo is X by Y pixels. It should not be stretched or distorted at all, only scaled.
Aaron Griffin schrieb:
Hrm, Roman pointed something out that somehow slipped my mind. The framebuffer logo is X by Y pixels. It should not be stretched or distorted at all, only scaled.
First of all, I want to point out that I want an Arch logo in my boot framebuffer, whether it's stretched or not. Now to the problem: My native resolution is 1280x800, but I have found no way to get this resolution in framebuffer. Therefore, I use 1024x768, which results in _non-square pixels_, thus the logo (and everything else) is somehow stretched and looks sort of ugly.
On Jan 24, 2008 4:34 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
Hrm, Roman pointed something out that somehow slipped my mind. The framebuffer logo is X by Y pixels. It should not be stretched or distorted at all, only scaled.
First of all, I want to point out that I want an Arch logo in my boot framebuffer, whether it's stretched or not.
I agree. But what Thayer is saying is simply that if it looks really ugly, it makes arch look less polished, graphically. I dunno, I'm on the fence here. I like seeing the little logo on boot, but if it starts to look really ugly, I probably wouldn't like it anymore.
Now to the problem: My native resolution is 1280x800, but I have found no way to get this resolution in framebuffer. Therefore, I use 1024x768, which results in _non-square pixels_, thus the logo (and everything else) is somehow stretched and looks sort of ugly.
Oh, I understand now. I wasn't thinking right - I actually don't have a widescreen setup at home with arch. All my monitors are square 8) Maybe I'll boot an install CD on my 17" laptop to see.
Thursday 24 January 2008, Aaron Griffin wrote: | I agree. But what Thayer is saying is simply that if it looks | really ugly, it makes arch look less polished, graphically. so does the whole screen, if you force the pixels to be wider than high :) we ARE having the arch logo in the kernel replacing the linux 2.0 pinguin (i made it). so i'm not getting the point in discussing if we want it or not. its just that somebody has to transform the new logo to the kernel-usable formats and rebuild the kernel. quite easy if you have the logo in good enough quality (or svg). - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
Am Freitag, 25. Januar 2008 01:00:31 schrieb Damir Perisa:
we ARE having the arch logo in the kernel replacing the linux 2.0 pinguin (i made it). so i'm not getting the point in discussing if we want it or not. its just that somebody has to transform the new logo to the kernel-usable formats and rebuild the kernel. quite easy if you have the logo in good enough quality (or svg).
My opinion here: Just do it. I fyou know how to format the logo, just sent it to tpowa and/or commit it into cvs. If people have problems with the logo, they could disable framebuffer mode (which is disabled by default anyway) or set the correct mode for their screen. Anyway: there are many other places where you could find our old logo. Such as KDE, OpenOffice etc.. I think we should replace them at first; any discussion if we should probably remove them can be done later. But now everything should be consistent. If needed I could help in creating such graphics. Pierre -- archlinux.de
On Jan 24, 2008 6:12 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Anyway: there are many other places where you could find our old logo. Such as KDE, OpenOffice etc.. I think we should replace them at first; any discussion if we should probably remove them can be done later. But now everything should be consistent.
A while back, I thought we actually agreed to try and NOT do that. If at all possible, we'd provide the art as secondary packages, but try to keep the existing ones free of arch logos and whatnot
participants (6)
-
Aaron Griffin
-
Damir Perisa
-
Pierre Schmitz
-
Roman Kyrylych
-
Thayer Williams
-
Thomas Bächler