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: Arnd Bergmann <arnd@arndb.de>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	linux-omap@vger.kernel.org, Olof Johansson <olof@lixom.net>
Subject: Re: OMAP totally fucked?
Date: Sun, 4 Mar 2012 15:59:09 +0000	[thread overview]
Message-ID: <20120304155909.GA14466@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120303210521.GE10293@atomide.com>

On Sat, Mar 03, 2012 at 01:05:21PM -0800, Tony Lindgren wrote:
> * Arnd Bergmann <arnd@arndb.de> [120303 09:57]:
> > On Saturday 03 March 2012, Tony Lindgren wrote:
> > > Well 85631d2 builds fine, looks like now some more includes of
> > > plat/hardware.h are now needed.Have not yet tracked down which
> > > commit triggers the build errors. Eventually those should become
> > > local headers too..
> > 
> > I've tried building arm-soc/for-next and rmk/for-next, they are both
> > fine, just merging the two gives me the same build errors that Russell
> > saw.
> > 
> > Adding plat/hardware.h in all files that break solves the problems,
> > aside from the iommu dependency for rpmsg for which Ohad has provided
> > a fix already that I should pull.
> 
> Here's a patch for you to the cleanup branch to fix the hardware.h
> build errors.

Right, with this applied, things are better:

1. omap3430ldp allnoconfig is the first build without warnings, congrats.
2. omap4430sdp allnoconfig has a bunch of new section mismatch warnings,
   a couple of compiler warnings, and builds:

WARNING: arch/arm/mach-omap2/built-in.o(.text+0x183c): Section mismatch in reference from the function omap2_init_processor_devices() to the function .init.text:_init_omap_device()
The function omap2_init_processor_devices() references
the function __init _init_omap_device().
This is often because omap2_init_processor_devices lacks a __init 
annotation or the annotation of _init_omap_device is wrong.

arch/arm/mach-omap2/io.c:51: warning: 'omap24xx_io_desc' defined but not used
arch/arm/mach-omap2/omap-wakeupgen.c:181: warning: 'wakeupgen_irqmask_all' defined but not used

3. omap4430sdp randconfig built with these omap specific warnings (exluding
   ones already mentioned):

arch/arm/mach-omap2/board-n8x0.c:39: warning: 'slot1_cover_open' defined but not used
arch/arm/mach-omap2/board-n8x0.c:40: warning: 'slot2_cover_open' defined but not used
arch/arm/mach-omap2/board-n8x0.c:41: warning: 'mmc_device' defined but not used

and, of course, this is with these configs building OMAP2..OMAP4 because of
the config.

  reply	other threads:[~2012-03-04 15:59 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 [this message]
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
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=20120304155909.GA14466@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).