linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: mvebu: Fix the memory size on the Mirabox
Date: Thu, 04 Apr 2013 15:55:01 +0200	[thread overview]
Message-ID: <515D8635.4080903@free-electrons.com> (raw)
In-Reply-To: <20130329193716.GA7127@localhost>

On 03/29/2013 08:37 PM, Ezequiel Garcia wrote:
> On Fri, Mar 29, 2013 at 11:09:23AM -0700, Ryan Press wrote:
>> Hi Jason,
>>
>> On Fri, Mar 29, 2013 at 11:04 AM, Jason Cooper <jason@lakedaemon.net> wrote:
>>> On Fri, Mar 29, 2013 at 10:51:17AM -0700, Ryan Press wrote:
>>>> The memory size in the device tree is only 512 MB, but the
>>>> Mirabox actually has 1 GB.
>>>>
>>>> Tested the change with memtester and no problems found.
>>>>
>>>> Signed-off-by: Ryan Press <ryan@presslab.us>
>>>> ---
>>>>  arch/arm/boot/dts/armada-370-mirabox.dts | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> Thanks for the patch.  It looks good, but please don't forget to Cc: the
>>> maintainers (Andrew Lunn, Gregory Clemente, and myself).  I almost
>>> missed this one. :)
>>>
> 
> As far as I can remember, Gregory has a Mirabox with only 512 MiB,
> which means some boards were shipped with 512 MiB and some with 1 GiB.
> Moreover, apparently nothing can distinguish one from the other.
> 
> @Gregory: can you confirm this?

I saw that you eventually found a solution, but just in case you still
wait for my answer: I confirm that my board have only 512MiB (according to
U-Boot)

> 
> If Gregory confirms this, then we shouldn't apply this patch.
> Don't forget in-kernel DTS are only meant for developers and
> for reference. The vendor (Globalscale in this case) has to ship
> a proper DTS for each board.
> 
>>> thx,
>>>
>>> Jason.
>>
>> Okay I didn't know I needed to do that.  Thanks!
>>
> 
> Although it's not mandatory, you can do a 'git blame' on the file you're
> patching and find out who should you put on Cc.
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2013-04-04 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 17:51 [PATCH] arm: mvebu: Fix the memory size on the Mirabox Ryan Press
2013-03-29 18:04 ` Jason Cooper
2013-03-29 18:09   ` Ryan Press
2013-03-29 19:37     ` Ezequiel Garcia
2013-03-29 19:44       ` Jason Cooper
2013-03-30  3:30         ` Ryan Press
2013-03-30 19:20           ` Jason Cooper
2013-03-30 19:28             ` Jason Cooper
2013-03-30 19:40             ` Ryan Press
2013-03-30 20:12               ` Jason Cooper
2013-04-03 10:46       ` Thomas Petazzoni
2013-04-04 13:55       ` Gregory CLEMENT [this message]

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=515D8635.4080903@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --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).