From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Please advise on modifying defconfig for Amstrad Delta
Date: Tue, 3 Nov 2009 09:24:00 -0800 [thread overview]
Message-ID: <20091103172400.GM8981@atomide.com> (raw)
In-Reply-To: <200910250340.34046.jkrzyszt@tis.icnet.pl>
* Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [091024 19:41]:
> Hi,
>
> I'm just working on a new, updated version of ams_delta_defconfig. Starting from the current version, created over 2 years ago for 2.6.22, I turned on a few device drivers that was added recently, turned on thumb instructions support, turned on EABI, kept old ABI compatibility and NWFPE, and got a resulting kernel that is ~170kB too large to be successfully booted using tools available at http://the.earth.li/pub/e3/.
>
> Of course, I am able to trim that down, even adding a few more drivers for add-on hardware that I am using, and get a kernel that works perfectly for me, but since I have never prepared a default config, I'd like to get your advice on what I can remove and what should rather be kept untouched.
>
> Instead of pasting sixteen hundred lines here, I'd rather ask about the simplest change I can see:
>
> -# CONFIG_EMBEDDED is not set
> -CONFIG_KALLSYMS=y
> +CONFIG_EMBEDDED=y
> +# CONFIG_KALLSYMS is not set
>
> That would give me a kernel that is small enough, but since only a few of arm defconfigs have CONFIG_KALLSYMS not set, I am not sure if it is generally acceptable.
Send that as a fix to this list with the minimal changes,
we should still be able to get it in as a fix during the -rc
series.
If you want to update the whole defconfig, we need to wait
for the merge window.
Just do the diff -u, then edit the patch to leave out all
the other hunks except the one above.
Regards,
Tony
prev parent reply other threads:[~2009-11-03 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 2:40 Please advise on modifying defconfig for Amstrad Delta Janusz Krzysztofik
2009-11-03 17:24 ` Tony Lindgren [this message]
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=20091103172400.GM8981@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).