From: Steffen Persvold <sp@scali.no>
To: "Gérard Roudier" <groudier@club-internet.fr>
Cc: lkml <linux-kernel@vger.kernel.org>, davej@suse.de, troels@thule.no
Subject: Re: ServerWorks LE and MTRR
Date: Sun, 29 Apr 2001 16:05:39 -0500 [thread overview]
Message-ID: <3AEC8223.DD87ADFE@scali.no> (raw)
In-Reply-To: <Pine.LNX.4.10.10104291846080.1226-100000@linux.local>
Gérard Roudier wrote:
>
> On Sun, 29 Apr 2001, Steffen Persvold wrote:
>
> > Hi all,
> >
> > I just compiled 2.4.4 and are running it on a Serverworks LE motherboard.
> > Whenever I try to add a write-combining region, it gets rejected. I took a peek
> > in the arch/i386/kernel/mtrr.c and found that this is just as expected with
> > v1.40 of the code. It is great that the mtrr code checks and prevents the user
> > from doing something that could eventually lead to data corruption. Using
> > write-combining on PCI acesses can lead to this on certain LE revisions but
> > _not_ all (only rev < 5). Therefore please consider my small patch to allow the
> > good ones to be able to use write-combining. I have several rev 06 and they are
> > working fine with this patch.
>
> You wrote that 'only rev < 5' can lead to data corruption, but your patch
> seems to disallow use of write combining for rev 5 too.
>
> Could you clarify?
Oops just a typo, it should be <= 5. The patch is correct.
>
> Gérard.
>
> PS:
> >From what hat did you get this information ? as it seems that ServerWorks
> require NDA for letting know technical information on their chipsets.
>
I've learned it the hard way, I have two types : Compaq DL360 (rev 5) and a
Tyan S2510 (rev 6). On the compaq machine I constantly get data corruption on
the last double word (4 bytes) in a 64 byte PCI burst when I use write
combining on the CPU. On the Tyan however the transfer is always ok.
--
Steffen Persvold Systems Engineer
Email : mailto:sp@scali.com Scali AS (http://www.scali.com)
Norway : Tel : (+47) 2262 8950 Olaf Helsets vei 6
Fax : (+47) 2262 8951 N-0621 Oslo, Norway
USA : Tel : (+1) 713 706 0544 10500 Richmond Avenue, Suite 190
Houston, Texas 77042, USA
next prev parent reply other threads:[~2001-04-29 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-29 18:55 ServerWorks LE and MTRR Steffen Persvold
2001-04-29 17:05 ` Gérard Roudier
2001-04-29 21:05 ` Steffen Persvold [this message]
2001-04-29 22:14 ` nick
2001-04-29 22:39 ` Steffen Persvold
2001-04-30 3:35 ` Gérard Roudier
2001-04-30 8:55 ` Eric W. Biederman
2001-04-30 1:06 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 13:44 Mark_Rusk
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=3AEC8223.DD87ADFE@scali.no \
--to=sp@scali.no \
--cc=davej@suse.de \
--cc=groudier@club-internet.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=troels@thule.no \
/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