All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: Ross HyperSPARC DMA
Date: Sun, 01 Aug 2004 01:18:42 +0000	[thread overview]
Message-ID: <20040801011842.GL2334@holomorphy.com> (raw)
In-Reply-To: <20040731212044.GF2334@holomorphy.com>

On Sat, Jul 31, 2004 at 02:20:44PM -0700, William Lee Irwin III wrote:
> Could a volunteer please identify which 2.3.x kernel introduced the
> HyperSPARC DMA failure? Binary search to narrow it down to a point
> release is all I'm looking for right now.

It looks like Rob Radez is working this on my hardware remotely atm.

The regression I'm referring to here is for SMP only. There was a
second regression, somewhere between then and 2.6.x-CURRENT, which
breaks DMA on HyperSPARC for UP also, i.e. all remaining HyperSPARCs.
If other volunteers could find what release broke that, I'd be much
obliged.

I don't have enough hardware to supply a second person so plan
accordingly.


-- wli

  reply	other threads:[~2004-08-01  1:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 21:20 Ross HyperSPARC DMA William Lee Irwin III
2004-08-01  1:18 ` William Lee Irwin III [this message]
2004-08-01  6:21 ` Keith M Wesolowski

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=20040801011842.GL2334@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@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.