Messages in this thread | | | From | Marcus Metzler <> | Date | Mon, 6 Sep 2004 18:03:33 +0200 | Subject | Re: [Transmeta hardware] Update of the CMS under Linux ? |
| |
>>>>> "Emmanuel" == Emmanuel Fleury <fleury@cs.aau.dk> writes:
Emmanuel> On Mon, 2004-09-06 at 10:50, Marcus Metzler wrote: >> I read the description of your bug and discovered that my >> problems with my Fujitsu Biblo Loox T93C notebook (AFAIK the >> Japanese version of the Lifebook 2120) seem to have the same >> cause. Since you seem to be collecting a list of hardware that >> has this bug, here is my information: I am using debian testing >> with kernel 2.6.4 (from kernel.org) and XFree86 Version >> 4.3.0.1. dmesg gives the following information about the CMS >> version: >> >> CPU: After generic identify, caps: 0084893f 0081813f 00000000 >> 00000000 CPU: After vendor identify, caps: 0084893f 0081813f >> 000000ce 00000000 CPU: L1 I Cache: 64K (64 bytes/line), D cache >> 64K (32 bytes/line) CPU: L2 Cache: 512K (128 bytes/line) CPU: >> Processor revision 1.4.1.0, 933 MHz CPU: Code Morphing Software >> revision 4.3.3-9-562 CPU: 20030107 01:17 official release >> 28.0.1-4.3.3#1 CPU serial number disabled. CPU: After all >> inits, caps: 0080893f 0081813f 000000ce 00000000 CPU: >> Transmeta(tm) Crusoe(tm) Processor TM5800 stepping 03
Emmanuel> Thanks for your input !
Emmanuel> I just added it to my list (I keep a more detailled Emmanuel> description of each plateform in my archives).
Emmanuel> It's the first 4.3.3 that is reported to have the Emmanuel> bug. :)
I might add that, although I don't have quantitative data, it seems that since the last X11 upgrade the bug seems to be less frequent.
Marcus
-- /--------------------------------------------------------------------\ | Dr. Marcus O.C. Metzler | | | mocm@metzlerbros.de | http://www.metzlerbros.de/ | \--------------------------------------------------------------------/ |>>> Quis custodiet ipsos custodies <<<| - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |