I did a clean checkout again, crossgcc again, and it all works now. I'm flummoxed.
ron On Sun, Mar 9, 2014 at 9:13 PM, David Hubbard < [email protected]> wrote: > On Sunday, March 09, 2014 08:26:05 PM you wrote: > > On Sunday, March 09, 2014 05:14:51 PM you wrote: > > > Story so far: > > > > > > 1. pick q35 chipset > > > 2. qemu -M q35 etc. etc. > > > > $ qemu-system-i386 -M q35 --bios build/coreboot.rom > > > > -ENOREPRODUCE > > > > > 1. pick i440fx chipset. > > > 2. qemu -M pc etc. etc. > > > > qemu-system-i386 --bios build/coreboot.rom > > > > -ENOREPRODUCE > > > > > Endless repetitions of > > > qemu: unsupported keyboard cmd cmd=0x00 > > > or 0x80 > > > > -ENOREPRODUCE > > > > Same with qemu-kvm. > > > > > This is with crossgcc. > > > I'm disappointed it's this fragile. I'm worried that feature push has > > > gotten ahead of reliability push. > > > > Or your qemu installation is b0rk3d. > > Perhaps if it is that easy to break the installation -- remember, he did a > clean checkout -- then there could be a broken dependency, or something > similar which involves digging deeply into the build system. > > In other words, even if what you say is true, we still need to have this > conversation. > > I feel like Coreboot is a bit fiddly to get set up right. To a degree, > that helps communicate that working with coreboot is hard stuff. But still, > we should implement some better quality controls, imho. > > Hopefully we can figure out what Ron ran into. That would be a good start. > > David >
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
