No, ROM CRC is useful for detecting between some device revisions, but not 
OMAp3430 vs OMAP3530.

----- Original Message -----
From: Koen Kooi <[EMAIL PROTECTED]>
To: linux-omap@vger.kernel.org <linux-omap@vger.kernel.org>
Cc: Kridner, Jason
Sent: Tue Aug 05 05:10:40 2008
Subject: Re: [PATCH] Added support for OMAP35x processor series


Op 5 aug 2008, om 11:50 heeft Igor Stoppa het volgende geschreven:

> On Tue, 2008-08-05 at 15:09 +0530, ext Premi, Sanjeev wrote:
>> This patch is needed to ensure that we can make decisions based on
>> the processor capabilities.
>> E.g. OMAP3503 does not contain a DSP. We shouldn't be trying to
>> disable/ manage the clocks for
>> DSP on this processor. Same for SGX.
>
> Why can't the detection happen at runtime?

AIUI the ID bits are the same (linux misdetect the 3530 on my beagle
for a 3430). I heard that the only definitive way to do it at runtime
is to CRC check the ROM code.

Jason, is that correct?

regards,

Koen

>> Enabling NEON is support iby default is just based on the number of
>> requests I have been getting
>> from various users.
>
> Huh?
>
>
> --
>
> Cheers, Igor
>
> ---
>
> Igor Stoppa
> Maemo Software - Nokia Devices R&D - Helsinki
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> omap" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

N�����r��y����b�X��ǧv�^�)޺{.n�+����{��f��{ay�ʇڙ�,j��f���h���z��w���
���j:+v���w�j�m��������zZ+�����ݢj"��!�i

Reply via email to