linux-kernel - Re: [PATCH v2 02/11] msm: Generalize timer register mappings

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]

Message-ID: <8ya7hdr70fw.fsf@huya.qualcomm.com>
Date:	Wed, 26 Jan 2011 14:41:07 -0800
From:	David Brown <davidb@...eaurora.org>
To:	Dima Zavin <dmitriyz@...gle.com>
Cc:	Daniel Walker <dwalker@...eaurora.org>,
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 02/11] msm: Generalize timer register mappings

On Wed, Jan 26 2011, Dima Zavin wrote:

> On Mon, Jan 24, 2011 at 2:44 PM, David Brown <davidb@...eaurora.org> wrote:

> To be honest I don't understand why you would want to do this at
> runtime. You cannot select multiple SoCs in the kernel build anyway,
> nor would you want to. Trying to have same kernel to boot on ARM v6
> and ARM v7 would already be freaky enough. On top of that mixing 7201a
> with all the baggage that it comes with 8x60 just wouldn't make sense.
> These architectures are so different that it I can't see that ever
> being useful. When would you ever envision building for multiple of
> these SoCs at the same time?

People (especially distributions) want to be able to build one arm
kernel rather than multiple ones.  The issues about CPU detection and
base addresses are being worked on now.

Other targets, especially omap, are already way ahead of MSM in this
area.

David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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/