linux-kernel - Re: Strange transmit corruption in jsm driver on geode sc1200 system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 28 Aug 2006 15:18:29 -0400
From:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Alexey Dobriyan <adobriyan@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Strange transmit corruption in jsm driver on geode sc1200 system

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/