[lkml]   [1998]   [Jun]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Fixes for vgafb on 2.1.107
In article <Pine.LNX.3.95q.980628155357.354C-100000@cassiopeia.home>,
Geert Uytterhoeven <> wrote:
>Other related question: will the changed initialization order in the vger tree
>(memory and PCI much earlier) make it in the standard tree? If you want to
>probe for a graphics board in frame buffer device code, you're hosed ATM.

No, it won't make it into the standard tree.

If you need PCI and memory management to be initialized, don't use
"console_init()". You should use the normal "chrdev_init()" which is
placed appropriately for a character device, surprise, surprise.

"console_init()" is placed early exactly because there are people who
want to see kernel panics on the screen even when they happen early in
the bootup sequence (ie me).

In short, the vger order is bad, and will never be accepted. It makes
no sense to have console_init() be placed later, because if it was
placed later it shouldn't be there at all, as chrdev_init() comes into


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to

 \ /
  Last update: 2005-03-22 13:43    [W:0.057 / U:0.464 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site