uvesafb: don't treat mode info retrieval failures as errors
PATCH 1/1 uvesafb: don't treat mode info retrieval failures as errors
From: Michal Januszewski <[email protected]>
Some BIOSes return error codes when queried for information about modes from their own modelist. uvesafb treats this as an error case and bails out.
Change this behavior so that broken modes do not prevent the driver from working. Only the failure to retrieve information about any usable video mode is considered to be an error case.
---
drivers/video/uvesafb.c +8 -3
@@ -516,10 +516,12 @@ static int __devinit uvesafb_vbe_getmodes(struct uvesafb_ktask *task, err =uvesafb_exec (task);if (err || (task->t.regs.eax &0xffff ) !=0x004f ) { -printk (KERN_ERR "uvesafb: Getting mode info block " +printk (KERN_WARNING "uvesafb: Getting mode info block " "for mode 0x%x failed (eax=0x%x, err=%d)\n" , *mode, (u32 )task->t.regs.eax, err); -return -EINVAL ; + mode++; + par->vbe_modes_cnt--; +continue ; } mib = task->buf;
@@ -548,7 +550,10 @@ static int __devinit uvesafb_vbe_getmodes(struct uvesafb_ktask *task, mib->depth = mib->bits_per_pixel; } -return 0 ; +if (par->vbe_modes_cnt >0 ) +return 0 ; +else +return -EINVAL ; }/*
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/