mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Erico Nunes <nunes.erico@gmail.com>, <michal.simek@xilinx.com>
Cc: <monstr@monstr.eu>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] microblaze: Add missing PVR version codes
Date: Mon, 5 Jan 2015 12:30:20 +0100	[thread overview]
Message-ID: <3f1aeed9398e4d47baeec954d0987a97@BY2FFO11FD036.protection.gbl> (raw)
In-Reply-To: <1420166433-12712-1-git-send-email-nunes.erico@gmail.com>

On 01/02/2015 03:40 AM, Erico Nunes wrote:
> PVR version code was missing in the cpu_ver_lookup table for the following
> versions: 8.50.b 8.50.c 9.2 9.3
> 
> This caused /proc/cpuinfo to display "CPU-Ver: Unknown" for these versions.
> 
> This was detected and the patch tested with MicroBlaze version 8.50.c.
> The other codes were taken from the Xilinx MicroBlaze Processor Reference
> Guides UG081 (v14.7) and UG984 (v2014.1).
> 
> Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
> ---
>  arch/microblaze/kernel/cpu/cpuinfo.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/microblaze/kernel/cpu/cpuinfo.c b/arch/microblaze/kernel/cpu/cpuinfo.c
> index 234acad..b60442d 100644
> --- a/arch/microblaze/kernel/cpu/cpuinfo.c
> +++ b/arch/microblaze/kernel/cpu/cpuinfo.c
> @@ -41,8 +41,12 @@ const struct cpu_ver_key cpu_ver_lookup[] = {
>  	{"8.40.a", 0x18},
>  	{"8.40.b", 0x19},
>  	{"8.50.a", 0x1a},
> +	{"8.50.b", 0x1c},
> +	{"8.50.c", 0x1e},
>  	{"9.0", 0x1b},
>  	{"9.1", 0x1d},
> +	{"9.2", 0x1f},
> +	{"9.3", 0x20},
>  	{NULL, 0},
>  };
>  
> 

Applied.

Thanks,
Michal

      reply	other threads:[~2015-01-05 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02  2:40 Erico Nunes
2015-01-05 11:30 ` Michal Simek [this message]

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=3f1aeed9398e4d47baeec954d0987a97@BY2FFO11FD036.protection.gbl \
    --to=michal.simek@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=nunes.erico@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®