[coreboot] When should we retire newconfig?

[joe at settoplinux.org]

On January 8, 2010 at 4:56 PM Myles Watson <mylesgw at gmail.com> wrote:

> > > All boards still work on newconfig - once we drop that, there are
> > > several possibilities for cleaning up.
> > >
> > > Boards that were recently tested with kconfig and tinybootblock:
> > > emulation/qemu-x86
> > > kontron/986lcd-m
> > > amd/serengeti_cheetah_fam10
> > > asus/m2v-mx_se
> with kconfig, but not with tiny bootblock:
> I've tested:
> tyan/s2895
> tyan/s2892 
> Hugh's tested:
> arima/hdama

Yes you can add Thomson IP1000 and RCA RM4100 to the list. They build fine with
Kconfig.
In fact they do not build the old way anymore, only with Kconfig.
> 
> > Is there some kind of guilde line or list of things that need to be done
> > to cleanup/convert on each board?
> 
> I would say:
> 1. Run util/kbuildall/kbuildall vendor/board
> 2. Fix Kconfig mismatches in src/mainboard/vendor/board/Kconfig
> 3. Build and boot test (and report to the list)
> 
> Soon we'll need to start only reporting Kconfig build errors on the mailing
> list.  Then we can fix kbuildall to use an older version of newconfig for
> its comparisons, then we'll be able to phase it out.
> 
ok but what needs to be done to use tinybootblock?

Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org