linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	linux-omap@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Olof Johansson <olof@lixom.net>
Subject: Re: OMAP totally fucked?
Date: Sat, 3 Mar 2012 20:52:00 +0000	[thread overview]
Message-ID: <20120303205200.GC17710@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120303203448.GD10293@atomide.com>

On Sat, Mar 03, 2012 at 12:34:48PM -0800, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [120303 11:56]:
> > * Tony Lindgren <tony@atomide.com> [120303 11:29]:
> > > * Russell King - ARM Linux <linux@arm.linux.org.uk> [120303 10:57]:
> > > > 
> > > > Even with the full config, making oldconfig I get:
> > > > 
> > > > OMAP2420 support (SOC_OMAP2420) [Y/n] (NEW) 
> > > > OMAP2430 support (SOC_OMAP2430) [Y/n] (NEW) 
> > > > OMAP3430 support (SOC_OMAP3430) [Y/n] (NEW) 
> > > > TI81XX support (SOC_OMAPTI81XX) [Y/n] (NEW) 
> > > > AM33XX support (SOC_OMAPAM33XX) [Y/n] (NEW) 
> > > > OMAP44XX support (SOC_OMAP44XX) [Y/n] (NEW) 
> > > > 
> > > > May I remind you of this mail from Linus:
> > > > 
> > > > 	https://lkml.org/lkml/2012/1/6/354
> > > > 
> > > > So really this is a rather horrid mess.
> > > 
> > > Hmm yes. Sounds like we need to remove the defaults and instead
> > > add them to omap2plus_defconfig.
> > > 
> > > I'll do a patch to fix that.
> > 
> > How about the following patch after we revert commit 72b026a4?
> > 
> > That still leaves the randconfig not necessarily selecting
> > any of ARCH_OMAP2/3/4 issue, but that can be dealt separately
> > later on.
> 
> Grr, need to look at it more.. Now it leaves out ARCH_OMAP2/3/4
> when doing a make oldconfig with some existing .config file.

There's also something else wrong:

*
* OMAP Core Type
*
OMAP2420 support (SOC_OMAP2420) [Y/n] (NEW) n
OMAP2430 support (SOC_OMAP2430) [Y/n] (NEW) n
OMAP3430 support (SOC_OMAP3430) [Y/n] (NEW) n
TI81XX support (SOC_OMAPTI81XX) [Y/n] (NEW) n
AM33XX support (SOC_OMAPAM33XX) [Y/n] (NEW) n
OMAP44XX support (SOC_OMAP44XX) [Y/n] (NEW) n
*
* OMAP Board Type
*
Generic OMAP2+ board (MACH_OMAP_GENERIC) [Y/?] y
OMAP3 debugging peripherals (OMAP3_EMU) [N/y/?] (NEW) 
Enable SDRC AC timing register changes (OMAP3_SDRC_AC_TIMING) [N/y/?] (NEW) 

Shouldn't the last two options depend on OMAP3 stuff?

And why do we have:

config ARCH_OMAP2PLUS
	select USE_OF

Do we really _need_ OF, or is it just irqdomain that's required?

  reply	other threads:[~2012-03-03 20:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 15:46 OMAP totally fucked? Russell King - ARM Linux
2012-03-03 18:04 ` Tony Lindgren
2012-03-03 18:29   ` Arnd Bergmann
2012-03-03 21:05     ` Tony Lindgren
2012-03-04 15:59       ` Russell King - ARM Linux
2012-03-05 19:07         ` Tony Lindgren
2012-03-06 19:45         ` Kevin Hilman
2012-03-06 19:55           ` Tony Lindgren
2012-03-06 20:15         ` Kevin Hilman
2012-03-06 21:23           ` Tony Lindgren
2012-03-03 18:32   ` Russell King - ARM Linux
2012-03-03 19:01     ` Tony Lindgren
2012-03-03 19:28       ` Russell King - ARM Linux
2012-03-03 20:01         ` Tony Lindgren
2012-03-03 20:28           ` Tony Lindgren
2012-03-03 20:34             ` Tony Lindgren
2012-03-03 20:52               ` Russell King - ARM Linux [this message]
2012-03-03 21:21                 ` Tony Lindgren
2012-03-03 21:57                   ` Tony Lindgren
2012-03-06 14:58                   ` Cousson, Benoit
2012-03-06 15:08                     ` Russell King - ARM Linux
2012-03-06 15:41                       ` Arnd Bergmann
2012-03-06 15:29   ` Peter Ujfalusi
2012-03-06 20:14     ` Tony Lindgren

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=20120303205200.GC17710@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arnd@arndb.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=peter.ujfalusi@ti.com \
    --cc=tony@atomide.com \
    /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).