Paul Mundt wrote:
> On Wed, Jul 20, 2005 at 07:02:53PM +0900, Miles Bader wrote:
>
>>Some archs seem to provide defconfigs for various different platforms,
>>which seems nice, and there seems to be some sort of framework for
>>doing this, but ...
>>
>
> For most of the architectures aimed at embedded systems, having an
> arch/foo/defconfig makes no sense. The basic "framework" is to have
Still, for basic compile testing and testing patches on other
architectures it would be nice, when the patch writer can test his/her
patch with a simple defconfig, without knowing a common platform for
this target arch.
So please include a defconfig with a reasonable common set of CONFIG_*
options. It's about testing the core of the architecure not about
random driver failures.
> arch/foo/configs and place all of your board-specific defconfigs in there
> (as boardname_defconfig -- the reason for this is that you get free make
> targets of the same name which copy the defconfig over, see 'make help').
>
> If you have a particular board that you can assume will be kept
> reasonably up-to-date, you can set KBUILD_DEFCONFIG in your Makefile to
> set the default config to use by name, and then you can forego having an
> arch/foo/defconfig entirely (you can look at sh and some of the other
> architectures to see this being done).
arm is another one which uses this style, ia64 for example uses configs/*
and defconfig. But on arm and sh `make defconfig` works contrary to v850.
Thanks,
--
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |