From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp)) Date: Wed, 23 Sep 2009 21:43:52 +0200 Subject: Fwd: [PATCH] em7210: fix memory size In-Reply-To: (Dan Williams's message of "Sun\, 30 Aug 2009 16\:45\:25 -0700") References: <87k51ru2gw.fsf@lechat.rtp-net.org> Message-ID: <87ljk578g7.fsf@lechat.rtp-net.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Dan Williams writes: Hi, > [ replied to wrong mailing list ] > > > ---------- Forwarded message ---------- > From: Dan Williams > Date: Sun, Aug 30, 2009 at 4:31 PM > Subject: Re: [PATCH] em7210: fix memory size > To: Arnaud Patard > Cc: linux-arm-kernel at lists.arm.linux.org.uk > > > On Wed, Jul 29, 2009 at 4:56 AM, Arnaud Patard 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.