Do you mean the old cluster will only update the normal part with CAR, and don't touch the fallback part that still use romcc...?
At that case, We may need to remove the #if USE_FALLBACK_IMAGE in cache_as_ram.inc....
YH
On 12/3/05, Eric W. Biederman ebiederman@lnxi.com wrote:
Stefan Reinauer stepan@openbios.org writes:
- Richard Smith smithbone@gmail.com [051123 22:04]:
Or possibly a system like Debian has for source packages where auto builders go and try to build everything and only after it passes all archs does it get accepted. You would e-mail your patch to the autobuilder and it would spit you back a log file.
excellent idea.
This all gets you around compile problems but theres still the "Does it actually work?" issue. Somehow you have to go verify those changes actually work on the boards. Especially if your end goal is to prevent bricking the hardware.
Until we have a large distributed cluster of machines connected to promices we should stick to code reviews and assiduous maintainers.
That is part of what the fallback/normal split is about. And this is why I scream about CAR only being setup in fallback.
It isn't perfect but it should let you test 99% of everything at least to the does it boot level. If you have a working fallback you don't need a promice in your test cluster.
Eric
-- LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios