linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] [ARM] Reduce the defconfig numbers for PXA
Date: Sat,  5 Jun 2010 15:55:34 +0800	[thread overview]
Message-ID: <1275724538-5075-1-git-send-email-eric.y.miao@gmail.com> (raw)

1. dma_needs_bounce() prevents it8152.c and sa1111.c from being built 
   together. Actually it8152.c is sane and dma_needs_bounce() can be
   removed simply. (Mike, could you give it a test?)

2. Currently, zaurus is not able to be built into a single kernel with
   other boards, since arch/arm/boot/compressed/head-sharpsl.S will
   try detecting the machine ID and will cause a dead loop on other
   boards at run-time. (if we stick with kexecboot or u-boot on
   zaurus, maybe we can remove head-sharpsl.S as well, and merge them
   into pxa2xx_defconfig as well)

3. All board configs with CONFIG_PXA2[57]x=y are now merged into pxa2xx_defconfig

4. All board configs with CONFIG_PXA3xx=y are now merged into pxa3xx_defconfig

The merge is rough, pxa2xx_defconfig as an example:

  1. $> cat mainstone_defconfig > .config
  2. $> for i in $(pxa2xx board defconfigs other than mainstone_defconfig); do
	    sed '/# CONFIG.*is not set/d' $i >> pxa2xx_defconfig
	done
  3. $> make oldconfig
  4. $> cp .config arch/arm/configs/pxa2xx_defconfig

The idea is to use mainstone_defconfig as a base, append all those
inclusive config options (not those "# CONFIG.*is not set").

Conflicts can happen with:

  - CONFIG_* being 'y' or 'm', this is less important provided the
    platform is sane enough to support both builtin and modules

  - CONFIG_* being a value type, the former will always be overwritten
    e.g. CONFIG_CMDLINE

That's why it's rough. I don't have time to look into those conflicts
though, I'd like each board maintainer to give it a test.

             reply	other threads:[~2010-06-05  7:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05  7:55 Eric Miao [this message]
2010-06-05  7:55 ` [PATCH 1/4] [ARM] Remove now unnecessary dma_needs_bounce() Eric Miao
2010-06-18  4:03   ` Eric Miao
2010-06-21  5:38     ` Mike Rapoport
2010-06-21 15:22       ` Eric Miao
2010-06-22  7:38         ` Mike Rapoport
2010-06-22  7:52           ` Eric Miao
2010-06-05  7:55 ` [PATCH 2/4] [ARM] pxa: merge all pxa2xx board configs into pxa2xx_defconfig Eric Miao
2010-06-05  8:03   ` Eric Miao
2010-06-05  8:04     ` Eric Miao
2010-06-05  7:55 ` [PATCH 3/4] [ARM] pxa: merge all pxa3xx board configs into pxa3xx_defconfig Eric Miao
2010-06-05  8:04   ` Eric Miao
2010-06-05  7:55 ` [PATCH 4/4] [ARM] pxa: merge {corgi, spitz}_defconfig into zaurus_defconfig Eric Miao
2010-06-05  8:05   ` [PATCH 4/4] [ARM] pxa: merge {corgi,spitz}_defconfig " Eric Miao

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=1275724538-5075-1-git-send-email-eric.y.miao@gmail.com \
    --to=eric.y.miao@gmail.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).