Messages in this thread | | | Date | Sat, 09 Aug 2008 22:15:08 +0200 | From | Rene Herman <> | Subject | Framebuffer drivers that break the boot on systemswithout the hardware |
| |
Hi Antonino.
At:
http://lkml.org/lkml/2008/8/1/96
Ingo Molnar posted a list of drivers he found to break the boot during testing of randconfig kernels and among them are a number of FB drivers:
FB_CIRRUS FB_ASILIANT FB_VGA16 FB_VESA FB_RADEON FB_CYBLA (and FB_VIRTUAL)
Looking at some of them there wouldn't seem to be too many very sensible options to avoid this at the individual driver level. Would you perhaps have an idea how to avoid the issue generically for these?
More of the drivers in that list will be considered fine as is but I was fixing some of the old legacy ISA ones as ofcourse any driver not needing special avoidance treatment is one less to have to deal with.
The randconfig testing IS useful in finding bugs, so...
Rene.
| |