All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: bifferos <bifferos@yahoo.co.uk>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	florian@openwrt.org, mark@bifferos.com, tglx@linutronix.de,
	Ingo Molnar <mingo@elte.hu>,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is
Date: Mon, 09 Aug 2010 13:15:26 -0700	[thread overview]
Message-ID: <4C6061DE.4030300@linux.intel.com> (raw)
In-Reply-To: <66994.33108.qm@web27001.mail.ukl.yahoo.com>

On 08/09/2010 02:33 AM, bifferos wrote:
> 
> The quick fix for this is:
> 
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index 490dac6..06a2dac 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -497,6 +497,9 @@ static void __cpuinit get_cpu_vendor(struct cpuinfo_x86 *c)
>                if (!cpu_devs[i])
>                        break;
> 
> +               if (!cpu_devs[i]->c_ident[0])
> +                       continue;
> +
>                if (!strcmp(v, cpu_devs[i]->c_ident[0]) ||
>                    (cpu_devs[i]->c_ident[1] &&
>                     !strcmp(v, cpu_devs[i]->c_ident[1]))) {
> 
> 
> however, Peter's requirement to remove c_ident renders my patch 
> somewhat less useful back on RDC.  /proc/cpuinfo then lists the 
> vendor as 'RDC' (an improvement over not applying the patch) and 
> the model name as '486' (also an improvement), but for some 
> reason the variants in my case statement then no longer make it 
> through to /proc/info.  I don't think this is a big deal, and I
> still think the patch is worth applying with this change.
> 

Well, as I said, the generic code probably needs to change somewhat to
print that stuff.

	-hpa

      reply	other threads:[~2010-08-09 20:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201008031815.09764.florian@openwrt.org>
2010-08-03 17:48 ` [tip:x86/cpu] x86, cpu: CPU detection for RDC System-on-Chip tip-bot for Mark Kelly
2010-08-03 17:49 ` [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is tip-bot for H. Peter Anvin
2010-08-03 19:25   ` Ingo Molnar
2010-08-04  9:12     ` bifferos
2010-08-04  9:25       ` Ingo Molnar
2010-08-04 20:14       ` H. Peter Anvin
2010-08-04 22:59         ` bifferos
2010-08-04 23:09           ` H. Peter Anvin
2010-08-05  0:27             ` bifferos
2010-08-05  2:00               ` H. Peter Anvin
2010-08-09  9:33     ` bifferos
2010-08-09 20:15       ` H. Peter Anvin [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=4C6061DE.4030300@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=bifferos@yahoo.co.uk \
    --cc=florian@openwrt.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mark@bifferos.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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.