Samsung SoCs naming rules

[tommy.hong]

I agree eric,also TI OMAP naming is a good example,you can use
s3c-armv6,s3c-armv7 ?just make people clear of ARM instruction version?

Tommy

2010/6/21 tommy.hong <hongjiujing at gmail.com>

> I agree eric,also TI OMAP naming is a good example,you can use
> s3c-armv6,s3c-armv7 ?just make people clear of ARM instruction version?
>
>
>
> Tommy
>
> 2010/6/21 Eric Miao <eric.y.miao at gmail.com>
>
> On Mon, Jun 21, 2010 at 6:00 PM, Kyungmin Park <kmpark at infradead.org>
>> wrote:
>> > Dear all,
>> >
>> > Now Samsung SoCs doesn't have any special rules include chip name.
>> >
>> > Historically s5pc100 is successor form s3c6410 and this chip from
>> > s3c2410 series.
>> > on the other hand, s5pc110 (cortex a8) and s5pc64xx (armv6) is
>> > different from previous chips.
>>
>> Don't be shy, Samsung is not the only vendor messes the naming of their
>> SoCs. Marvell might have done a better job on this :-)
>>
>> >
>> > So it's not good idea grouping with the prefix. e.g., s5p series. and
>> > the reason to create the samsung.
>> >
>>
>> My guess is your s5p will focus more on Cortex-A8 (or A9 possibly),
>> even with subsequent processors. And only s5pc100 is an exception,
>> that's fine, you can still put s5pc100 into mach-s3c6410, and people
>> will know it's actually closer to s3c6410. And other SoCs will share the
>> common s5p prefix.
>>
>> > we tried to find a common name several times but failed to get proper
>> > name, I hope community give good name rules.
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>
>
>
> --
> concentrate for work && keep calm and carry on,Achievement provides the
> only real pleasure in life!
>



-- 
concentrate for work && keep calm and carry on,Achievement provides the only
real pleasure in life!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100621/3edb3c52/attachment.html>