linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] omap2/3/4: Add Kconfig option to compile in typical omap	features
Date: Wed, 30 Jun 2010 10:24:44 +0300	[thread overview]
Message-ID: <20100630072443.GW2822@atomide.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C5E4124A@dbde02.ent.ti.com>

* Shilimkar, Santosh <santosh.shilimkar@ti.com> [100630 09:41]:
> > -----Original Message-----
> > From: Tony Lindgren [mailto:tony at atomide.com]
> > Sent: Wednesday, June 30, 2010 11:47 AM
> > To: Shilimkar, Santosh
> > Cc: linux-arm-kernel at lists.infradead.org; linux-omap at vger.kernel.org
> > Subject: Re: [PATCH 6/6] omap2/3/4: Add Kconfig option to compile in
> > typical omap features
> > 
> > * Shilimkar, Santosh <santosh.shilimkar@ti.com> [100629 17:40]:
> > > > >
> > > > With your series OMAP4 build breaks because of PM and SMP
> > dependencies.
> > > > To ensure that build doesn't break on OMAP4, I needed below change.
> > With
> > > > This change I tried your series and it boots OK on OMAP4430 SDP
> > 
> > Hmm the build does not break for me?
> >
> Looks like I am missing something here. How do you build OMAP4 alone with
> these new changes ??

Use your old config file, or just unselect CONFIG_ARCH_OMAP2
and CONFIG_ARCH_OMAP3. Note that if you now do:

$ yes "" | ARCH=arm make oldconfig

with your old omap4 only config file, then by default the
typical features get added by default. So what you probably
want to do is (untested):

$ echo "# CONFIG_ARCH_OMAP2PLUS_TYPICAL is not set" >> .config
$ yes "" | ARCH=arm make oldconfig

Then it should not change your old config file.

To see how the boards and features show up, you can also play
with it with make xconfig:

System Type -> TI OMAP2/3/4 Specific Features

Uncheck TI OMAP2 and TI OMAP3 so only TI OMAP4 is selected.

Regards,

Tony

  reply	other threads:[~2010-06-30  7:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 11:47 [PATCH 0/6] omap Kconfig improvments for 2.6.36 merge window Tony Lindgren
2010-06-29 11:47 ` [PATCH 1/6] omap: Disable VGA console for omaps Tony Lindgren
2010-06-29 12:07   ` Anton Vorontsov
2010-06-29 14:21     ` Tony Lindgren
2010-06-30  6:33       ` [PATCH] ARM: Disable VGA console for ARM in most cases (Re: [PATCH 1/6] omap: Disable VGA console for omaps) Tony Lindgren
2010-06-29 11:47 ` [PATCH 2/6] omap: Use 32KiHZ timer by default Tony Lindgren
2010-06-29 11:47 ` [PATCH 3/6] omap: Make omap specific features appear under Kconfig menu Tony Lindgren
2010-06-29 11:47 ` [PATCH 4/6] omap2/3/4: Move Kconfig options to mach-omap2/Kconfig Tony Lindgren
2010-06-29 11:47 ` [PATCH 5/6] omap2/3/4: Select all omaps and boards by default Tony Lindgren
2010-06-29 11:47 ` [PATCH 6/6] omap2/3/4: Add Kconfig option to compile in typical omap features Tony Lindgren
2010-06-29 13:53   ` Shilimkar, Santosh
2010-06-29 14:46     ` Shilimkar, Santosh
2010-06-30  6:17       ` Tony Lindgren
2010-06-30  6:47         ` Shilimkar, Santosh
2010-06-30  7:24           ` Tony Lindgren [this message]
2010-07-01 10:34             ` Shilimkar, Santosh

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=20100630072443.GW2822@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).