From: Thomas Dodd <ted@cypress.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>
Subject: Re: Contacts within AMD? AMD-756 USB host-controller blacklisted due to
Date: Wed, 04 Apr 2001 14:12:22 -0500 [thread overview]
Message-ID: <3ACB7216.9F12D286@cypress.com> (raw)
In-Reply-To: <E14kWCc-0000EF-00@the-village.bc.nu>
Alan Cox wrote:
>
> > 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?
>
> We are working on that currently via the Red Hat contact.
>
> > 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.
>
> because we dont know the full scope of the problem yet.
Exactly how many bug reports has this caused?
What kind of problems?
I know I had trouble onece, but it was a CONFIG problem
with the 2.4.2ac series and the extra DEBUG options.
-Thomas
next prev parent reply other threads:[~2001-04-04 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 17:46 Contacts within AMD? AMD-756 USB host-controller blacklisted due to erratum #4 Miles Lane
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 [this message]
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=3ACB7216.9F12D286@cypress.com \
--to=ted@cypress.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.