All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Strange transmit corruption in jsm driver on geode sc1200 system
Date: Mon, 28 Aug 2006 15:18:29 -0400	[thread overview]
Message-ID: <20060828191829.GO13639@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1156792178.6271.46.camel@localhost.localdomain>

On Mon, Aug 28, 2006 at 08:09:38PM +0100, Alan Cox wrote:
> That is worth fixing.

Well changing

case 4:

to

case 4:
case 11:
	dir0_msn = 4;

Makes the geode code appear to be called, and nothing is broken so
far.  Minimal testing so far actually seems to indicate a slight
performance improvement.  And /proc/cpuinfo no longer shows Unknown
model.  I am pretty sure in the past I have seen the model name show
MediaGX, so I suspect sometime in the last year there was a revision
change or something in the cpu modules we are using, since it now shows
Unknown.

> The databook is available from www.amd.com I believe. You'd need to look
> at that and see what needs setting. It is quite similar so it probably
> will benefit a little - but that also depends what the BIOS does for you
> and with ACPI that should be handled by the ACPI.

This BIOS has no ACPI.  At best it could do APM.

Seems the amd site requires an NDA to get at anything useful.  Maybe I
looked in the wrong place.

--
Len Sorensen

      reply	other threads:[~2006-08-28 19:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 20:30 Strange transmit corruption in jsm driver on geode sc1200 system Lennart Sorensen
2006-08-25 21:20 ` Alan Cox
2006-08-25 21:03   ` Lennart Sorensen
2006-08-25 21:24     ` Alexey Dobriyan
2006-08-25 21:57       ` Lennart Sorensen
2006-08-28 17:30         ` Lennart Sorensen
2006-08-28 18:11         ` Lennart Sorensen
2006-08-28 19:09           ` Alan Cox
2006-08-28 19:18             ` Lennart Sorensen [this message]

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=20060828191829.GO13639@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=adobriyan@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.