linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [PATCH] em7210: fix memory size
Date: Wed, 23 Sep 2009 21:43:52 +0200	[thread overview]
Message-ID: <87ljk578g7.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <e9c3a7c20908301645v4cfdec4ehe2ed1e6efaf261ed@mail.gmail.com> (Dan Williams's message of "Sun\, 30 Aug 2009 16\:45\:25 -0700")

Dan Williams <dan.j.williams@intel.com> writes:
Hi,

> [ replied to wrong mailing list ]
>
>
> ---------- Forwarded message ----------
> From: Dan Williams <dan.j.williams@intel.com>
> Date: Sun, Aug 30, 2009 at 4:31 PM
> Subject: Re: [PATCH] em7210: fix memory size
> To: Arnaud Patard <arnaud.patard@rtp-net.org>
> Cc: linux-arm-kernel at lists.arm.linux.org.uk
>
>
> On Wed, Jul 29, 2009 at 4:56 AM, Arnaud Patard<arnaud.patard@rtp-net.org> wrote:
>>
>> The default memory module size on the ss4000e is 256M but Redboot has
>> been hardcoded to pass 512M to the kernel through ATAG. As getting a new
>> redboot is more than unlikely, it has to be fixed in the kernel
>> (unfortunately). This patch does that.
>>
>
> I am on the fence on this one. ?On the one hand it makes sense in that
> the kernel is usable without a "mem=256M..." command line option on
> default configured platforms. ?Users that have upgraded the memory can
> pass a "mem=512M..." to use their extra memory. ?However, it still
> seems that this will appear as a regression to any current 512M
> platforms that are not passing a command line option, and a "don't
> care" to everyone who must be passing "mem=256M..." to get a
> functional platform.
>
> Hmm... ?can you say a bit more about this comment "solving this issue will help
> also people porting the d-i on the device." [1] That might help tip the balance.

I've asked more details and I'm going to try to sum up the point. I hope
I won't make any mistake as I'm not familiar with d-i internals at
all. Please bear with me.

      reply	other threads:[~2009-09-23 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k51ru2gw.fsf@lechat.rtp-net.org>
     [not found] ` <e9c3a7c20908301631j50ccb0d6q8ab1ee61a2f4d247@mail.gmail.com>
2009-08-30 23:45   ` Fwd: [PATCH] em7210: fix memory size Dan Williams
2009-09-23 19:43     ` Arnaud Patard (Rtp) [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=87ljk578g7.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --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).