From: "H. Peter Anvin" <hpa@zytor.com>
To: bifferos <bifferos@yahoo.co.uk>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
mingo@redhat.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: Wed, 04 Aug 2010 19:00:23 -0700 [thread overview]
Message-ID: <4C5A1B37.5070701@zytor.com> (raw)
In-Reply-To: <999475.75291.qm@web27008.mail.ukl.yahoo.com>
On 08/04/2010 05:27 PM, bifferos wrote:
>
> --- On Thu, 5/8/10, H. Peter Anvin <hpa@linux.intel.com> wrote:
>>> Without the patch RDC is misreported as Cyrix
>> Cx486SLC.
>>>
>>
>> And what problems does that cause? Presumably none,
>
> If I don't know the CPU how do I set the tick rate?
>
> http://android.git.kernel.org/?p=kernel/common.git;a=commitdiff_plain;h=e1b4d1143651fb3838be1117785b6e0386fa151f
>
That's a valid use, of course, but that wasn't sent with it. Even so,
it's really a chipset property and not a CPU property and probably
should simply be set via a PCI quirk.
So, clean up the patch, add the usage, and then it can be put into the
-tip tree for the next merge window.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-08-05 2:01 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 [this message]
2010-08-09 9:33 ` bifferos
2010-08-09 20:15 ` H. Peter Anvin
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=4C5A1B37.5070701@zytor.com \
--to=hpa@zytor.com \
--cc=bifferos@yahoo.co.uk \
--cc=florian@openwrt.org \
--cc=hpa@linux.intel.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.