On Sat, 2013-11-16 at 13:39 +1000, Dave Airlie wrote: > On Sat, Nov 16, 2013 at 6:15 AM, Adam Jackson <[email protected]> wrote: > > On UEFI machines you'd prefer fbdev to grab efifb instead of vesa trying > > to initialize and failing in a way we can't unwind from. On BIOS > > machines this is harmless: either there is an fbdev driver and it'll > > probably be more capable, or there's not and vesa will kick in anyway. > > Won't this mean on machines where grub2 sets up vesafb we'll end up > just using vesafb?
If you don't have a real driver, it does, I have difficulty thinking of that as a real problem though. > I was thinking on UEFI we could just make vesa fail harder earlier. That'd be fine to do too. It still makes sense to move "driver that doesn't need direct hardware access" before "driver that might". - ajax _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
