What do you define as useable?
at two extremes:
do you mean a kernel that fully supports the board and all it's features?
do you mean a kernel that will compile and boot, but may not be able to
talk to the outside world as it doesn't know about any I/O that the chip
may have.
I don't think that defconfig can work for the first case (every single
system would hae it's own defconfig, which just doesn't scale)
and I'm not sure the second is very useful (and it should be covered by
the kconfig defaults)
if you are looking for something in between, where do you draw the line?
back when linux ran on x86 with IDE only, defconfig made a lot of sense,
but that was because the hardware was very standardized, nowdays even in
the x6 space there is enough variation that it's questionable how useful a
defconfig is.
What would be far better would be some tool that would take some hardware
defintition (either autodetecting from a currenlty running system on x86,
or from the device_tree stuff that's being worked on for other
architectures) and create a kernel config from that that would fully
support the hardware detected.
David Lang
--
