> This came up when cbfs (correctly) diagnosed a rom as corrupt ... it > was a bug in cbfs, but that's how it's supposed to work -- catch a bad > rom at build time, not boot time.
> I still think the right fix is to fix cbfs file names to some value -- > e.g. 32 chars -- which would remove a lot of code. 32 chars should be long > enough for a rom file system name. I agree. Let's do that first, since it would simplify this fix. I'll review and test. Thanks, Myles -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
