On Fri, 2008-04-04 at 11:38 -0500, Olof Johansson wrote: > On Fri, Apr 04, 2008 at 10:14:34AM -0600, Grant Likely wrote: > > On Fri, Apr 4, 2008 at 10:11 AM, Grant Likely <[EMAIL PROTECTED]> wrote: > > > > > > I'm thinking 'optimized' defconfigs should go into a subdirectory. > > > > > > > > > > This requires a change to the top-level Makefile and shepherding this > > > > > change upstream. Could we perhaps try to avoid this by having > > > optimized > > > > > defconfigs in the form of, for example: > > > > > > I don't think changes are required to put them in a subdir: > > > > > > $ mkdir arch/powerpc/configs/optimized > > > $ cp arch/powerpc/configs/mpc5200_defconfig > > > arch/powerpc/configs/optimized/lite5200_defconfig > > > $ make optimized/lite5200_defconfig > > > > > > This works for me. > > > > However, I'm not sure what the naming scheme should be for subdirectories. > > > > board vendor? > > host processor? > > just one big directory for board specific defconfigs? > > > > Olof, Kumar, Josh; any thoughts? > > > > Not that it matters much; files are easy to move around later. > > I really like the idea. It would probably make sense to organize it in > the same way as the platforms are done today, i.e. per processor/platform > family. And then have shared/merged configs in the main config directory.
Yes. I was thinking the same already for 4xx. Essentially: configs/ppc44x_defconfig configs/ppc40x_defconfig configs/44x/<board>_defconfig configs/40x/<board>_defconfig josh _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
