From: Dan Malek <dan@embeddededge.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org,
Gill Becky-BGILL <becky.bruce@freescale.com>,
linuxppc64-dev@ozlabs.org, Tom Rini <trini@kernel.crashing.org>
Subject: Re: RFC: proposed arch/powerpc directory structure
Date: Thu, 11 Aug 2005 19:29:57 -0400 [thread overview]
Message-ID: <c74341910a387ed9114187e7af1661e0@embeddededge.com> (raw)
In-Reply-To: <DE2CC80C-91A2-4860-B452-6AD171F3588A@freescale.com>
On Aug 11, 2005, at 7:07 PM, Kumar Gala wrote:
> ...... The idea being that we might be able to build kernels in
> either directory that supported a large number of boards with one
> image.
Please don't go there :-) I'm having enough trouble meeting reasonable
performance goals in 2.6 on embedded systems that I don't need the
overhead
of code bloat or extra cycles to determine what board I'm on. Contrary
to
the belief of developers, products don't have the resource wealth we see
on these evaluation and ODM boards. Embedded products still require
we build kernels (and everything else) as concisely and efficient as
possible.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-08-11 23:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 16:45 RFC: proposed arch/powerpc directory structure Becky Bruce
2005-08-10 17:01 ` Dan Malek
2005-08-10 21:35 ` John W. Linville
2005-08-11 0:09 ` Stephen Rothwell
2005-08-11 1:10 ` Olof Johansson
2005-08-11 19:59 ` Tom Rini
2005-08-11 20:13 ` Kumar Gala
2005-08-11 20:18 ` Tom Rini
2005-08-11 22:41 ` Becky Bruce
2005-08-11 23:07 ` Kumar Gala
2005-08-11 23:19 ` Tom Rini
2005-08-12 2:34 ` Kumar Gala
2005-08-12 3:38 ` Tom Rini
2005-08-11 23:29 ` Dan Malek [this message]
2005-08-12 2:09 ` Josh Boyer
2005-08-12 3:49 ` Paul Mackerras
2005-08-12 4:14 ` Tom Rini
2005-08-15 18:25 ` Segher Boessenkool
2005-08-11 20:25 ` Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c74341910a387ed9114187e7af1661e0@embeddededge.com \
--to=dan@embeddededge.com \
--cc=becky.bruce@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=trini@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).