linux-kernel - Re: [PATCH 1/7] msm: io: I/O register definitions for MSM8960

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] [day] [month] [year] [list]

Message-id: <alpine.LFD.2.00.1101021956250.16090@xanadu.home>
Date:	Sun, 02 Jan 2011 20:04:02 -0500 (EST)
From:	Nicolas Pitre <nico@...xnic.net>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Arnd Bergmann <arnd@...db.de>, Eric Miao <eric.y.miao@...il.com>,
	linux-arm-msm@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Stepan Moskovchenko <stepanm@...eaurora.org>,
	David Brown <davidb@...eaurora.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/7] msm: io: I/O register definitions for MSM8960

On Mon, 3 Jan 2011, Russell King - ARM Linux wrote:

> On Sat, Dec 25, 2010 at 11:04:11AM -0500, Nicolas Pitre wrote:
> > On Fri, 24 Dec 2010, Arnd Bergmann wrote:
> > 
> > > On Friday 17 December 2010, David Brown wrote:
> > > > I'm not sure really what to do about PHYS_OFFSET.  This is kind of the
> > > > big thing that has kept us so far from making our SOCs multiply
> > > > selectable.  I could move this into a Kconfig option, but it would
> > > > still need to be selected by the SOC.  It is unfortunate that most of
> > > > our SOCs have different enough memory configurations that these are
> > > > mostly different.  Even 8960/8660 will probably have future variants
> > > > that are at different addresses.
> > > 
> > > I think there are people working on relocatable kernels already,
> > > and we definitely need this for the other work in progress of
> > > doing kernel binaries that work across different SoC families,
> > > as well as for doing a single kernel that can be used both for
> > > booting the system and for kdump.
> > > 
> > > You don't need to worry about PHYS_OFFSET at the platform level,
> > > we'll get there in a few months for all ARM platforms.
> > 
> > ... or in a few days even.  I'm currently working on the patch making 
> > PHYS_OFFSET patched into the kernel at run time.  I'm currently looking 
> > at what is needed to make it work also with Thumb2.
> 
> So where do we stand with:
> 
> http://lists.arm.linux.org.uk/lurker/message/20101110.175549.62a0b058.en.html
> 
> Is this something which should be queued for this merge window?

I'm working on a patch series that includes a slightly modified version 
of the above plus a few fixes for issues that turned up during testing.

I hope to have something for you to queue by tomorrow or tuesday.  This 
is damn close to the merge window, but we don't have to turn it on by 
default.

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/