From: Anand Gadiyar <gadiyar@ti.com>
To: linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: RE: linux-next-20100201 - OMAP2+ defconfig broken with CONFIG_DEBUG_LL
Date: Tue, 1 Feb 2011 14:53:47 +0530 [thread overview]
Message-ID: <4af2a35f6d08ddcb33eb86aa3c784fb5@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinF+dpKvuRztChBM01MAjgL-foGp_yVq3uC9ghu@mail.gmail.com>
Gadiyar, Anand wrote:
> Hi all,
>
> I tried to build linux-next as of 20100201 with
> omap2plus_defconfig. In addition
> I turned on CONFIG_DEBUG_LL and hit the following error.
>
> AS arch/arm/kernel/debug.o
> arch/arm/kernel/debug.S: Assembler messages:
> arch/arm/kernel/debug.S:174: Error: garbage following instruction --
> `ldreq r1,=
> __virt_to_phys(omap_uart_phys)'
> arch/arm/kernel/debug.S:174: Error: garbage following instruction --
> `ldrne r1,=
> __phys_to_virt((0x80000000+0x3ffc))'
> arch/arm/kernel/debug.S:174: Error: garbage following instruction --
> `ldreq r2,=
> __virt_to_phys(omap_uart_phys)'
> arch/arm/kernel/debug.S:174: Error: garbage following instruction --
> `ldreq r2,=
> __virt_to_phys(omap_uart_phys)'
> arch/arm/kernel/debug.S:178: Error: garbage following instruction --
> `ldreq r2,=
> __virt_to_phys(omap_uart_lsr)'
> arch/arm/kernel/debug.S:190: Error: garbage following instruction --
> `ldreq r1,=
> __virt_to_phys(omap_uart_phys)'
> arch/arm/kernel/debug.S:190: Error: garbage following instruction --
> `ldrne r1,=
> __phys_to_virt((0x80000000+0x3ffc))'
> arch/arm/kernel/debug.S:190: Error: garbage following instruction --
> `ldreq r2,=
> __virt_to_phys(omap_uart_phys)'
> arch/arm/kernel/debug.S:190: Error: garbage following instruction --
> `ldreq r2,=
> __virt_to_phys(omap_uart_phys)'
> make[1]: *** [arch/arm/kernel/debug.o] Error 1
> make: *** [arch/arm/kernel] Error 2
>
> Will try and bisect this down later. Just reporting for now.
>
Hi Russell,
This appears to be introduced after this commit from you:
8397c0703b5aa99fdb7c4e5177c4e2fc3b97c835 is the first bad commit
commit 8397c0703b5aa99fdb7c4e5177c4e2fc3b97c835
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Tue Jan 4 19:09:43 2011 +0000
ARM: P2V: introduce phys_to_virt/virt_to_phys runtime patching
This idea came from Nicolas, Eric Miao produced an initial version,
which was then rewritten into this.
The build failure seems to be omap-specific; I don't see this when
I build a mx51_defconfig for instance, but I do get a similar error
when building for omap1_defconfig.
I'll try and dig deeper.
Thanks in advance for any pointers.
- Anand
next prev parent reply other threads:[~2011-02-01 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 5:39 linux-next-20100201 - OMAP2+ defconfig broken with CONFIG_DEBUG_LL Gadiyar, Anand
2011-02-01 9:22 ` Russell King - ARM Linux
2011-02-01 9:25 ` linux-next-20100201 - OMAP2+ defconfig broken withCONFIG_DEBUG_LL Anand Gadiyar
2011-02-01 9:23 ` Anand Gadiyar [this message]
2011-02-01 9:26 ` linux-next-20100201 - OMAP2+ defconfig broken with CONFIG_DEBUG_LL Santosh Shilimkar
2011-02-04 19:59 ` 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=4af2a35f6d08ddcb33eb86aa3c784fb5@mail.gmail.com \
--to=gadiyar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).