v2 HAVE_OPTION_TABLE patch

This patch makes several CMOS variable reads dependent on whether there's a table to read. Otherwise you never know what you'll get from the factory BIOS. There are probably more, but these are the ones compiled into the s2895. Signed-off-by: Myles Watson <mylesgw@gmail.com> Thanks, Myles

Myles Watson wrote:
This patch makes several CMOS variable reads dependent on whether there's a table to read. Otherwise you never know what you'll get from the factory BIOS. There are probably more, but these are the ones compiled into the s2895.
Signed-off-by: Myles Watson <mylesgw@gmail.com>
Acked-by: Peter Stuge <peter@stuge.se>

On Thu, Feb 26, 2009 at 5:03 PM, Peter Stuge <peter@stuge.se> wrote:
Myles Watson wrote:
This patch makes several CMOS variable reads dependent on whether there's a table to read. Otherwise you never know what you'll get from the factory BIOS. There are probably more, but these are the ones compiled into the s2895.
Signed-off-by: Myles Watson <mylesgw@gmail.com>
Acked-by: Peter Stuge <peter@stuge.se> Rev 3959.
Thanks, Myles

On Fri, Feb 27, 2009 at 10:51 AM, Myles Watson <mylesgw@gmail.com> wrote:
On Thu, Feb 26, 2009 at 5:03 PM, Peter Stuge <peter@stuge.se> wrote:
Myles Watson wrote:
This patch makes several CMOS variable reads dependent on whether there's a table to read. Otherwise you never know what you'll get from the factory BIOS. There are probably more, but these are the ones compiled into the s2895.
FYI this is a worse problem than I thought. It happens any time you are using fallback or failover, since HAVE_OPTION_TABLE = 0 for those cases. As long as the CMOS isn't corrupted that's fine, but if you're in fallback because the CMOS checksum wasn't right... Thanks, Myles
participants (2)
-
Myles Watson
-
Peter Stuge