From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: udelay(500) in amd8111 and nforce2
Date: Thu, 19 May 2005 06:24:27 +0000 [thread overview]
Message-ID: <20031130085556.7f6d1b79.khali@linux-fr.org> (raw)
In-Reply-To: <3FC94B6F.FA363E5E@paradyne.com>
> This is definitely no good.
> The preferred implementation is #if'ed out in nforce2.
> Does somebody have these chips to test the fix or
> should we just change it w/o testing first?
My girlfriend has ordered a new motherboard a few days ago, and should
receive it soon. I think it has a nForce2 on it, so I might be able to
do some tests on it at that time (say in one week or so).
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 udelay(500) in amd8111 and nforce2 Mark Studebaker
2005-05-19 6:24 ` Jean Delvare [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=20031130085556.7f6d1b79.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@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.