Re: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/04/2010 05:27 PM, bifferos wrote:
> 
> --- On Thu, 5/8/10, H. Peter Anvin <hpa@xxxxxxxxxxxxxxx> 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.

--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux