linux-kernel - Re: [PATCH 1/3] SPEAr13xx_defconfig: Enable Memory split 2G/2G needed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 8 Feb 2013 12:49:22 -0500 (EST)
From:	Nicolas Pitre <nicolas.pitre@...aro.org>
To:	Viresh Kumar <viresh.kumar@...aro.org>
cc:	Vijay Kumar Mishra <vijay.kumar@...com>, linux@....linux.org.uk,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	spear-devel <spear-devel@...t.st.com>
Subject: Re: [PATCH 1/3] SPEAr13xx_defconfig: Enable Memory split 2G/2G
 needed

On Fri, 8 Feb 2013, Viresh Kumar wrote:

> Hi Vijay,
> 
> By mistake you have added an ST internal list in cc, fixed it now.
> 
> Subject should be:
> 
> ARM: SPEAr13xx: Enable 2G/2G Memory split in defconfig
> 
> On 8 February 2013 16:16, Vijay Kumar Mishra <vijay.kumar@...com> wrote:
> > Memory split 2G/2G is enabled as needed for SPEAr1310 RevC board to boot.
> > Before enabling this option the boot was hanging at uncompressing linux.

I disagree.  The subject could have been "put our head in the sand and 
paper over bugs".

Please don't do that.  There is no reason for any machine not to boot 
way past "Uncompressing Linux" with the default split.  The likely 
reason it works with the 2G:2G split is because in that case the virtual 
and physical RAM addresses in the kernel are the same, and therefore 
missing p2v or v2p conversions are invisible.

Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/