From: Miles Lane <miles@megapathdsl.net>
To: linux-kernel@vger.kernel.org
Cc: David Brownell <david-b@pacbell.net>
Subject: Contacts within AMD? AMD-756 USB host-controller blacklisted due to erratum #4.
Date: Tue, 03 Apr 2001 10:46:43 -0700 [thread overview]
Message-ID: <3ACA0C83.1E5A6020@megapathdsl.net> (raw)
Running 2.4.2-ac28, I get the following error:
usb-ohci.c: 00:07.4 (Advanced Micro Devices [AMD] AMD-756 [Viper] USB):
blacklisted, erratum #4
David Brownell recently added this check to the usb-ohci driver
since noone has gotten information from AMD for the workaround,
which is rumored to exist, for this bug.
Do any of you have contacts within AMD who might be able to
get an explanation of the workaround to David Brownell?
The bug is that the NDP value sent by the AMD-756 is sometimes
bogus. The following examples, collected before the chip
was blacklisted, show the failure. As you can see, the bogus
value given varies. Rereading NDP seems to give a valid value.
I am not really clear why we don't simply read the value twice
whenever the host-controller is detected to be an AMD-756.
Mar 4 17:20:52 aerie kernel: usb-ohci.c: bogus NDP=128 for OHCI
usb-00:07.4
Mar 4 17:20:52 aerie kernel: usb-ohci.c: rereads as NDP=4
Mar 4 17:50:29 aerie kernel: usb-ohci.c: bogus NDP=245 for OHCI
usb-00:07.4
Mar 4 17:50:29 aerie kernel: usb-ohci.c: rereads as NDP=4
Mar 6 21:11:07 aerie kernel: usb-ohci.c: bogus NDP=210 for OHCI
usb-00:07.4
Mar 6 21:11:07 aerie kernel: usb-ohci.c: rereads as NDP=4
Thanks,
Miles
next reply other threads:[~2001-04-03 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 17:46 Miles Lane [this message]
2001-04-03 19:10 ` Contacts within AMD? AMD-756 USB host-controller blacklisted due to Alan Cox
2001-04-04 19:12 ` Thomas Dodd
2001-04-04 18:54 ` Miles Lane
2001-04-04 22:19 ` Joachim 'roh' Steiger
2001-04-04 21:40 ` Miles Lane
2001-04-04 23:50 ` Ryan Butler
2001-04-04 23:00 ` David Brownell
2001-04-05 0:08 ` Contacts within AMD? AMD-756 USB host-controller blacklisted dueto Thomas Dodd
2001-04-05 0:27 ` Alan Cox
2001-04-05 20:29 ` Thomas Dodd
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=3ACA0C83.1E5A6020@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=david-b@pacbell.net \
--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