[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1213067676.3213.27.camel@moss.renham>
Date: Tue, 10 Jun 2008 13:14:36 +1000
From: Ben Nizette <bn@...sdigital.com>
To: Tim Bird <tim.bird@...sony.com>
Cc: Rob Landley <rob@...dley.net>, Adrian Bunk <adrian.bunk@...ial.fi>,
linux-tiny <Linux-tiny@...enic.com>,
linux-embedded <linux-embedded@...r.kernel.org>,
linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: mainlining min-configs...
On Mon, 2008-06-09 at 18:37 -0700, Tim Bird wrote:
> Rob Landley wrote:
> > On Friday 06 June 2008 18:47:47 Tim Bird wrote:
> >> At a minimum, it would be nice to have a few nice examples
> >> of really, really small configs for things like qemus for different
> >> architectures (just to give embedded developers who are working
> >> on size a starting point).
> >
> > That's more or less what I'm trying to do with my Firmware Linux project:
> > creating cross compilers and minimal native build environments for every qemu
> > target.
>
> Any chance of getting your minimal configs from Firmware Linux mainlined?
allnoconfig? ;-)
>
> Does anyone else think this would be valuable? If not in mainline, it
> would be nice to collect them somewhere, to compare what options different
> developers decide turn on or off.
Seriously though I maintain a bunch of AVR32 minimal configs. I keep
them as a smallest-working-config baseline to build on; I'm sure others
would get value from having easy access to that kind of thing.
IMO It'd be nice to wire them to an automagic bloat-o-meter as well, but
I suspect no-one would really take notice anyway.
--Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists