Note the extra 's'. We use "sse" and "sse2", but "ssse3". I assume it's a typo. Signed-off-by: Ulrich Drepper <[email protected]> --- arch/i386/kernel/cpu/proc.c 2007-02-15 11:21:18.000000000 -0800 +++ arch/i386/kernel/cpu/proc.c-new 2007-05-02 15:31:17.000000000 -0700 @@ -46,7 +46,7 @@ /* Intel-defined (#2) */ "pni", NULL, NULL, "monitor", "ds_cpl", "vmx", "smx", "est", - "tm2", "ssse3", "cid", NULL, NULL, "cx16", "xtpr", NULL, + "tm2", "sse3", "cid", NULL, NULL, "cx16", "xtpr", NULL, NULL, NULL, "dca", NULL, NULL, NULL, NULL, "popcnt", NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: Why ssse3?
- From: Andi Kleen <[email protected]>
- Re: Why ssse3?
- From: Ismail Dönmez <[email protected]>
- Re: Why ssse3?
- Prev by Date: Re: 2.6.21-git4 BUG: soft lockup detected on CPU#1!
- Next by Date: Re: coretemp - take3
- Previous by thread: Mysterious RTC hangs on x86_64 - fixed, sort of
- Next by thread: Re: Why ssse3?
- Index(es):
 |