| 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
| ||
|
Message-ID: <e68bb3470912040620v7d6d9c67s176f6e8aef8a3638@mail.gmail.com>
Date: Fri, 4 Dec 2009 22:20:51 +0800
From: Wan ZongShun <mcuos.com@...il.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4]ARM: NUC900: enable uart support for nuc932
2009/12/4 Russell King - ARM Linux <linux@....linux.org.uk>:
> On Wed, Dec 02, 2009 at 09:58:25PM +0800, Wan ZongShun wrote:
>> diff --git a/arch/arm/mach-w90x900/clock.h b/arch/arm/mach-w90x900/clock.h
>> index b9ea2e6..2a2a54a 100644
>> --- a/arch/arm/mach-w90x900/clock.h
>> +++ b/arch/arm/mach-w90x900/clock.h
>> @@ -14,8 +14,10 @@
>>
>> #ifndef CONFIG_CPU_NUC932
>> #define EXTCLK 15000000
>> +#define UARTCLK 11313600
>> #else
>> #define EXTCLK 27000000
>> +#define UARTCLK 57139200
>> #endif
>
> As far as I can see, these are the only thing which prevent a single
> kernel being built to cover both NUC900 and NUC932.
>
> Can we make their selection something which is done at runtime instead
> of compile time? This comments goes for patch 5837/1 in the patch
> system as well.
>
Do you mean that I should use following form instead?
"if (machine_is_nuc932evb())"
code....
--
linux-arm-kernel mailing list
linux-arm-kernel@...ts.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
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/
Powered by blists - more mailing lists