From: "David S. Miller" <davem@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Bob McElrath <rsmcelrath@students.wisc.edu>,
Jeff Golds <jgolds@resilience.com>,
Wakko Warner <wakko@animx.eu.org>,
Pierfrancesco Caci <p.caci@seabone.net>,
linux-kernel@vger.kernel.org
Subject: Re: es1371 and recent kernels
Date: Tue, 12 Jun 2001 14:47:38 -0700 (PDT) [thread overview]
Message-ID: <15142.36346.932239.542996@pizda.ninka.net> (raw)
In-Reply-To: <3B268CF6.5197EA21@mandrakesoft.com>
In-Reply-To: <873d95lnqr.fsf@paperino.int-seabone.net> <20010612111503.A870@draal.physics.wisc.edu> <20010612164204.A21504@animx.eu.org> <3B2681A8.567992F6@resilience.com> <20010612163150.C16885@draal.physics.wisc.edu> <3B268CF6.5197EA21@mandrakesoft.com>
Jeff Garzik writes:
> > Argh, I had one of those, gave it away because it would hang my alpha
> > hard (I'm told the card is pretty nonconformant to the PCI spec).
> > *sigh*
>
> Now you tempt me to find this card and fix the alpha problem :)
I get instant master aborts on Sparc64 with the es1371, but I think
this is because the card recognizes less than the full 32-bits of
address lines on PCI.
So the thing is basically useless to me, and I believe the alpha
platform issues have to do with es1371's bogus handling of some WRITE
pci transactions.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-06-12 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 15:30 es1371 and recent kernels Pierfrancesco Caci
2001-06-12 15:53 ` Luigi Genoni
2001-06-12 16:15 ` Bob McElrath
2001-06-12 20:42 ` Wakko Warner
2001-06-12 20:55 ` Jeff Golds
2001-06-12 21:31 ` Bob McElrath
2001-06-12 21:43 ` Jeff Garzik
2001-06-12 21:55 ` Wakko Warner
2001-06-12 21:47 ` David S. Miller [this message]
2001-06-12 17:05 ` James Stevenson
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=15142.36346.932239.542996@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=jgolds@resilience.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.caci@seabone.net \
--cc=rsmcelrath@students.wisc.edu \
--cc=wakko@animx.eu.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;
as well as URLs for NNTP newsgroup(s).