public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcus Metzler <mocm@mocm.de>
To: Emmanuel Fleury <fleury@cs.aau.dk>
Cc: mocm@mocm.de, Linux Kernel Mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: [Transmeta hardware] Update of the CMS under Linux ?
Date: Mon, 6 Sep 2004 18:03:33 +0200	[thread overview]
Message-ID: <16700.35413.648707.198360@mocm.de> (raw)
In-Reply-To: <1094486295.4125.16.camel@rade7.e.cs.auc.dk>

>>>>> "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                 <<<|

  reply	other threads:[~2004-09-06 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22  8:58 [Transmeta hardware] Update of the CMS under Linux ? Emmanuel Fleury
2004-09-03  2:43 ` Kalin KOZHUHAROV
2004-09-06  8:05   ` Emmanuel Fleury
2004-09-06  8:50     ` Marcus Metzler
2004-09-06 15:58       ` Emmanuel Fleury
2004-09-06 16:03         ` Marcus Metzler [this message]
2004-09-06 14:29     ` Kalin KOZHUHAROV
2004-09-06 16:10       ` Emmanuel Fleury
2004-09-06 17:07         ` Marcus Metzler

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=16700.35413.648707.198360@mocm.de \
    --to=mocm@mocm.de \
    --cc=fleury@cs.aau.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox