Config files that aren't mach_defconfig...

Config files that aren't mach_defconfig...

[Peter Chubb]

Hi Sam,
   I've just finished porting Linux 2.6 to a new ARM board, that needs
a custom initramfs list.  My approach was to set
CONFIG_INITRAMFS_SOURCE to point to
"$(srctree)/arch/arm/configs/pleb2_initramfs" in the appropriate
defconfig for the board, as it's a default configuration item; but
Russell asks if there isn't a better place for a per-board default initramfs
script to live? 

What I'd like is for the appropriate default -- for this board --
script to be carried around and updated with the other configuration
files, somehow.

--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
The technical we do immediately,  the political takes *forever*

Re: Config files that aren't mach_defconfig...

[Sam Ravnborg]

On Tue, Nov 30, 2004 at 09:18:46AM +1100, Peter Chubb wrote:
> 
> Hi Sam,
>    I've just finished porting Linux 2.6 to a new ARM board, that needs
> a custom initramfs list.  My approach was to set
> CONFIG_INITRAMFS_SOURCE to point to
> "$(srctree)/arch/arm/configs/pleb2_initramfs" in the appropriate
> defconfig for the board, as it's a default configuration item; but
> Russell asks if there isn't a better place for a per-board default initramfs
> script to live? 

We have arch/$arch/configs for this specific purpose to store baord specific
configuration. So mixing *_defconfig and _initramfs is a natural choice.
Nothing is gained by introducing another directory for this purpose.

	Sam