From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
tony@atomide.com, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/2] ARM: kernel: update cpuinfo to print CPU model name
Date: Wed, 30 Jan 2013 11:22:50 +0530 [thread overview]
Message-ID: <5108B532.6000706@ti.com> (raw)
In-Reply-To: <CAB=otbR+MA3NUhxqRdo=w81gz9sTLAsLV5ELcpp77UxizMiaKw@mail.gmail.com>
On Wednesday 30 January 2013 04:42 AM, Ruslan Bilovol wrote:
> Hi,
>
> On Tue, Jan 29, 2013 at 6:08 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> On Tue, Jan 29, 2013 at 05:54:24PM +0200, Ruslan Bilovol wrote:
>>> CPU implementer : 0x41
>>> CPU name : OMAP4470 ES1.0 HS
>>
>> Sigh. No. Look at what you're doing - look carefully at the above.
>>
>> "CPU implementer" - 0x41. That's A. For ARM Ltd. ARM Ltd implemented
>> this CPU. Did ARM Ltd really implement OMAP4470 ? I think TI would be
>> very upset if that were to be the case.
>
> Yes, it would be very surprisingly :)
>
>>
>> So no, OMAP4470 is _NOT_ a CPU. It is a SoC. The CPU inside the SoC is
>> a collection of ARM Ltd Cortex A9 _CPUs_.
>>
>> See? Please, learn what a CPU is as opposed to a SoC.
>
> Completely agree with you. I will fix this
>
Thank god you agreed to drop your current approach. Please elaborate
what you are going to fix and also state what user-space features
changes from OMAP4460 to OMAP4470.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/2] ARM: kernel: update cpuinfo to print CPU model name
Date: Wed, 30 Jan 2013 11:22:50 +0530 [thread overview]
Message-ID: <5108B532.6000706@ti.com> (raw)
In-Reply-To: <CAB=otbR+MA3NUhxqRdo=w81gz9sTLAsLV5ELcpp77UxizMiaKw@mail.gmail.com>
On Wednesday 30 January 2013 04:42 AM, Ruslan Bilovol wrote:
> Hi,
>
> On Tue, Jan 29, 2013 at 6:08 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> On Tue, Jan 29, 2013 at 05:54:24PM +0200, Ruslan Bilovol wrote:
>>> CPU implementer : 0x41
>>> CPU name : OMAP4470 ES1.0 HS
>>
>> Sigh. No. Look at what you're doing - look carefully at the above.
>>
>> "CPU implementer" - 0x41. That's A. For ARM Ltd. ARM Ltd implemented
>> this CPU. Did ARM Ltd really implement OMAP4470 ? I think TI would be
>> very upset if that were to be the case.
>
> Yes, it would be very surprisingly :)
>
>>
>> So no, OMAP4470 is _NOT_ a CPU. It is a SoC. The CPU inside the SoC is
>> a collection of ARM Ltd Cortex A9 _CPUs_.
>>
>> See? Please, learn what a CPU is as opposed to a SoC.
>
> Completely agree with you. I will fix this
>
Thank god you agreed to drop your current approach. Please elaborate
what you are going to fix and also state what user-space features
changes from OMAP4460 to OMAP4470.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
<tony@atomide.com>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH 1/2] ARM: kernel: update cpuinfo to print CPU model name
Date: Wed, 30 Jan 2013 11:22:50 +0530 [thread overview]
Message-ID: <5108B532.6000706@ti.com> (raw)
In-Reply-To: <CAB=otbR+MA3NUhxqRdo=w81gz9sTLAsLV5ELcpp77UxizMiaKw@mail.gmail.com>
On Wednesday 30 January 2013 04:42 AM, Ruslan Bilovol wrote:
> Hi,
>
> On Tue, Jan 29, 2013 at 6:08 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> On Tue, Jan 29, 2013 at 05:54:24PM +0200, Ruslan Bilovol wrote:
>>> CPU implementer : 0x41
>>> CPU name : OMAP4470 ES1.0 HS
>>
>> Sigh. No. Look at what you're doing - look carefully at the above.
>>
>> "CPU implementer" - 0x41. That's A. For ARM Ltd. ARM Ltd implemented
>> this CPU. Did ARM Ltd really implement OMAP4470 ? I think TI would be
>> very upset if that were to be the case.
>
> Yes, it would be very surprisingly :)
>
>>
>> So no, OMAP4470 is _NOT_ a CPU. It is a SoC. The CPU inside the SoC is
>> a collection of ARM Ltd Cortex A9 _CPUs_.
>>
>> See? Please, learn what a CPU is as opposed to a SoC.
>
> Completely agree with you. I will fix this
>
Thank god you agreed to drop your current approach. Please elaborate
what you are going to fix and also state what user-space features
changes from OMAP4460 to OMAP4470.
Regards,
Santosh
next prev parent reply other threads:[~2013-01-30 5:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 15:54 [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name Ruslan Bilovol
2013-01-29 15:54 ` Ruslan Bilovol
2013-01-29 15:54 ` Ruslan Bilovol
2013-01-29 15:54 ` [RFC PATCH 1/2] ARM: kernel: " Ruslan Bilovol
2013-01-29 15:54 ` Ruslan Bilovol
2013-01-29 15:54 ` Ruslan Bilovol
2013-01-29 16:08 ` Russell King - ARM Linux
2013-01-29 16:08 ` Russell King - ARM Linux
2013-01-29 23:12 ` Ruslan Bilovol
2013-01-29 23:12 ` Ruslan Bilovol
2013-01-30 5:52 ` Santosh Shilimkar [this message]
2013-01-30 5:52 ` Santosh Shilimkar
2013-01-30 5:52 ` Santosh Shilimkar
2013-01-30 7:42 ` anish singh
2013-01-30 7:42 ` anish singh
2013-01-29 15:54 ` [RFC PATCH 2/2] ARM: OMAP4: setup CPU model name during ID initialisation Ruslan Bilovol
2013-01-29 15:54 ` Ruslan Bilovol
2013-01-29 15:54 ` Ruslan Bilovol
2013-01-29 16:02 ` [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name Nishanth Menon
2013-01-29 16:02 ` Nishanth Menon
2013-01-29 16:02 ` Nishanth Menon
2013-01-29 23:08 ` Ruslan Bilovol
2013-01-29 23:08 ` Ruslan Bilovol
2013-01-29 23:38 ` Nishanth Menon
2013-01-29 23:38 ` Nishanth Menon
2013-01-29 23:38 ` Nishanth Menon
2013-01-30 13:20 ` Ruslan Bilovol
2013-01-30 13:20 ` Ruslan Bilovol
2013-01-30 13:20 ` Ruslan Bilovol
2013-01-29 16:11 ` Rob Herring
2013-01-29 16:11 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5108B532.6000706@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ruslan.bilovol@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.