linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: mainline boot: 64 boots: 62 pass, 2 fail (v3.16-rc1-2-gebe0618)
Date: Fri, 27 Jun 2014 10:40:36 +0100	[thread overview]
Message-ID: <20140627094036.GD32514@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <53AD34E6.8000302@codeaurora.org>

On Fri, Jun 27, 2014 at 02:09:58AM -0700, Laura Abbott wrote:
> On 6/26/2014 8:06 PM, Tushar Behera wrote:
>> arm_add_memory is getting called before this is being set, resulting in
>> none of the memory banks getting added[1].
>>
>> setup_machine_fdt -> early_init_dt_scan -> early_init_dt_scan_memory
>>
>> Would it make sense to re-introduce the config option ARM_NR_BANKS and
>> replace max_cnt with NR_BANKS?
>>
>> [1] http://pastebin.com/MawYD7kb
>>
>
> I was hoping to avoid re-introducing the config option but that may be
> the case if we can't make the machine_info work. I'll take a better
> look tomorrow.

The problem with the config option is that it's not single zImage
friendly.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-06-27  9:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <539fdd37.e7bc420a.76b9.ffffb583@mx.google.com>
     [not found] ` <CAGa+x85nqPbH-sye28ni=gUEdgjGdUDqHhv1+0pV5aO8y1+wHQ@mail.gmail.com>
     [not found]   ` <53A106F1.10201@gmail.com>
     [not found]     ` <CAGa+x8527FEPk6fg5kv-fbOzK3MzcFooFGE9Me12b9C_Pv=UzA@mail.gmail.com>
     [not found]       ` <53A2AE11.2050208@gmail.com>
     [not found]         ` <53A2BE94.2010308@gmail.com>
2014-06-23  3:56           ` mainline boot: 64 boots: 62 pass, 2 fail (v3.16-rc1-2-gebe0618) Tushar Behera
2014-06-23 18:32             ` Kevin Hilman
2014-06-24 17:47               ` Laura Abbott
2014-06-24 22:29                 ` Laura Abbott
2014-06-25 12:13                   ` Tushar Behera
2014-06-25 21:57                     ` Laura Abbott
2014-06-26  6:44                       ` Tushar Behera
2014-06-26 14:59                         ` Kevin Hilman
2014-06-26 15:17                           ` Russell King - ARM Linux
2014-06-26 19:42                             ` Laura Abbott
2014-06-27  3:06                               ` Tushar Behera
2014-06-27  9:09                                 ` Laura Abbott
2014-06-27  9:40                                   ` Russell King - ARM Linux [this message]
2014-06-26 17:04                           ` Andreas Färber
2014-06-27  3:28                             ` Tushar Behera
2014-06-25  2:07               ` Andreas Färber

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=20140627094036.GD32514@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).