From: Nishanth Menon <nm@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, tony@atomide.com,
linux@arm.linux.org.uk, eduardo.valentin@ti.com
Subject: Re: [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name
Date: Tue, 29 Jan 2013 10:02:44 -0600 [thread overview]
Message-ID: <20130129160243.GA3389@kahuna> (raw)
In-Reply-To: <1359474865-15408-1-git-send-email-ruslan.bilovol@ti.com>
On 17:54-20130129, Ruslan Bilovol wrote:
> Hi,
>
> The following patches update cpuinfo to print CPU
> model name for ARM. First patch exactly makes needed
> changes for ARM architecture.
> Second patch adds this ability to OMAP4 SoCs.
>
> This adds a common approach to show SoC name.
>
> Looks like there were few attempts to do similar
> changes to cpuinfo without any luck.
>
> So - comments are welcome
>
> Ruslan Bilovol (2):
> ARM: kernel: update cpuinfo to print CPU model name
> ARM: OMAP4: setup CPU model name during ID initialisation
We had an discussion on similar lines but a generic suggestion:
https://patchwork.kernel.org/patch/98720/
SoCinfo framework which was supposed to introduce this
Would'nt that be a better approach to take than an OMAP only solution?
Ccying eduardo who had driven this for some time.
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name
Date: Tue, 29 Jan 2013 10:02:44 -0600 [thread overview]
Message-ID: <20130129160243.GA3389@kahuna> (raw)
In-Reply-To: <1359474865-15408-1-git-send-email-ruslan.bilovol@ti.com>
On 17:54-20130129, Ruslan Bilovol wrote:
> Hi,
>
> The following patches update cpuinfo to print CPU
> model name for ARM. First patch exactly makes needed
> changes for ARM architecture.
> Second patch adds this ability to OMAP4 SoCs.
>
> This adds a common approach to show SoC name.
>
> Looks like there were few attempts to do similar
> changes to cpuinfo without any luck.
>
> So - comments are welcome
>
> Ruslan Bilovol (2):
> ARM: kernel: update cpuinfo to print CPU model name
> ARM: OMAP4: setup CPU model name during ID initialisation
We had an discussion on similar lines but a generic suggestion:
https://patchwork.kernel.org/patch/98720/
SoCinfo framework which was supposed to introduce this
Would'nt that be a better approach to take than an OMAP only solution?
Ccying eduardo who had driven this for some time.
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tony@atomide.com>, <linux@arm.linux.org.uk>,
<eduardo.valentin@ti.com>
Subject: Re: [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name
Date: Tue, 29 Jan 2013 10:02:44 -0600 [thread overview]
Message-ID: <20130129160243.GA3389@kahuna> (raw)
In-Reply-To: <1359474865-15408-1-git-send-email-ruslan.bilovol@ti.com>
On 17:54-20130129, Ruslan Bilovol wrote:
> Hi,
>
> The following patches update cpuinfo to print CPU
> model name for ARM. First patch exactly makes needed
> changes for ARM architecture.
> Second patch adds this ability to OMAP4 SoCs.
>
> This adds a common approach to show SoC name.
>
> Looks like there were few attempts to do similar
> changes to cpuinfo without any luck.
>
> So - comments are welcome
>
> Ruslan Bilovol (2):
> ARM: kernel: update cpuinfo to print CPU model name
> ARM: OMAP4: setup CPU model name during ID initialisation
We had an discussion on similar lines but a generic suggestion:
https://patchwork.kernel.org/patch/98720/
SoCinfo framework which was supposed to introduce this
Would'nt that be a better approach to take than an OMAP only solution?
Ccying eduardo who had driven this for some time.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-01-29 16:02 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
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 ` Nishanth Menon [this message]
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 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=20130129160243.GA3389@kahuna \
--to=nm@ti.com \
--cc=eduardo.valentin@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.