public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: florian@openwrt•org (Florian Fainelli)
To: linux-arm-kernel@lists•infradead.org
Subject: ARM realview breakages w/ 3.7 under qemu
Date: Mon, 17 Dec 2012 15:06:10 +0100	[thread overview]
Message-ID: <50CF26D2.1040008@openwrt.org> (raw)
In-Reply-To: <20121217134246.GE11558@mudshark.cambridge.arm.com>

Le 12/17/12 14:42, Will Deacon a ?crit :
> On Fri, Dec 14, 2012 at 10:37:04AM +0000, Florian Fainelli wrote:
>> Le 12/14/12 10:40, Russell King - ARM Linux a ?crit :
>>> On Thu, Dec 13, 2012 at 05:48:17PM +0000, Will Deacon wrote:
>>>> On Thu, Dec 13, 2012 at 05:26:25PM +0000, Florian Fainelli wrote:
>>>>> - PBX A9: booting with less than 1024MBytes of RAM causes this:
>>>>> [    0.000000] Truncating RAM at 20000000-3fffffff to -3f7fffff (vmalloc
>>>>> region overlap).
>>>>> [    0.000000] Ignoring RAM at 80000000-8fffffff (vmalloc region overlap).
>>>>>
>>>>> Do these issues sounds familiar to any of you? The kernel config is
>>>>> attached in case that helps.
>>> I don't have the original email to reply to (so I don't have the .config
>>> either) but my guess for the above would be that HIGHMEM is disabled.
>> The original mail containing the .config file was actually rejected by
>> the mailing-list manager. I have uploaded it here:
>> http://alphacore.org/~florian/openwrt/realview-eb-config
>>
>> You are right, HIGHMEM is disabled. Even though enabling HIGHMEM does
>> not allow me booting either without at least 1Gbyte of RAM:
>>
>> [    0.000000] Memory policy: ECC disabled, Data cache writealloc
>> and we are stuck.
> I just dusted off my pbx and it boots fine with your .config and a 3.7
> kernel when passing mem=128M on the command line.
Ok, there must be something specific to qemu, can you also try with it?

>
> For EB, can you try the following diff please?

Works for me, thank you! I realized that I had this patch for 3.3 
already, but not in 3.7. This means that Realview EB has been broken 
since 3.3-rc and specifically commit 34ae6c96 (ARM: 7298/1: realview: 
fix mapping of MPCore private memory region).

>
> Will
>
> --->8
>
> diff --git a/arch/arm/mach-realview/include/mach/board-eb.h b/arch/arm/mach-realview/include/mach/board-eb.h
> index 124bce6..a301e61 100644
> --- a/arch/arm/mach-realview/include/mach/board-eb.h
> +++ b/arch/arm/mach-realview/include/mach/board-eb.h
> @@ -47,7 +47,7 @@
>   #define REALVIEW_EB_USB_BASE           0x4F000000      /* USB */
>   
>   #ifdef CONFIG_REALVIEW_EB_ARM11MP_REVB
> -#define REALVIEW_EB11MP_PRIV_MEM_BASE  0x1F000000
> +#define REALVIEW_EB11MP_PRIV_MEM_BASE  0x10100000
>   #define REALVIEW_EB11MP_L220_BASE      0x10102000      /* L220 registers */
>   #define REALVIEW_EB11MP_SYS_PLD_CTRL1  0xD8            /* Register offset for MPCore sysctl */
>   #else

  reply	other threads:[~2012-12-17 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 17:26 ARM realview breakages w/ 3.7 under qemu Florian Fainelli
2012-12-13 17:48 ` Will Deacon
2012-12-13 17:55   ` Florian Fainelli
2012-12-14  9:40   ` Russell King - ARM Linux
2012-12-14 10:37     ` Florian Fainelli
2012-12-14 10:47       ` Russell King - ARM Linux
2012-12-14 10:50         ` Florian Fainelli
2012-12-17 13:42       ` Will Deacon
2012-12-17 14:06         ` Florian Fainelli [this message]
2012-12-17 15:13           ` Will Deacon
2012-12-17 15:23             ` Florian Fainelli

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=50CF26D2.1040008@openwrt.org \
    --to=florian@openwrt$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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