From: Keith M Wesolowski <wesolows@foobazco.org>
To: sparclinux@vger.kernel.org
Subject: Re: sun4c driver/dma problems
Date: Wed, 14 Jul 2004 22:23:45 +0000 [thread overview]
Message-ID: <20040714222345.GA12558@foobazco.org> (raw)
In-Reply-To: <200406020818.13705.luckas@musoft.de>
On Tue, Jul 13, 2004 at 11:39:00PM +0200, Uli Luckas wrote:
> > > So what can I do to help, getting this fixed? Who works on this code?
> > > I already know, it's not only the version detection. Defining a new
> > > version 70000000 "Revision 1 broken" and initialising it just as a
> > > "Revision 1" works around the above message, but all the device drivers
> > > report all kind of DMA related problems later on and of course don't
> > > work.
> As I have read, you are retiering from sparc32 kernel development. Is there
> any hint that could get me going on fixing the above problems myself? Do you
> have asumptions on where the problem can be found?
I do not know the cause of this problem. However, it's entirely
possible it's just a detection issue. You might consider grepping for
these messages in the source, then diffing between a working and
non-working kernel to see what's changed. If it's not simple
detection, it may be related to the hypersparc DMA issue I've noted,
which has not been diagnosed.
--
Keith M Wesolowski
next prev parent reply other threads:[~2004-07-14 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 6:18 sun4c driver/dma problems Uli Luckas
2004-06-02 6:41 ` Uli Luckas
2004-06-08 7:22 ` Uli Luckas
2004-06-08 15:53 ` Keith M Wesolowski
2004-06-08 16:12 ` Uli Luckas
2004-06-17 6:16 ` Uli Luckas
2004-07-13 21:39 ` Uli Luckas
2004-07-14 22:23 ` Keith M Wesolowski [this message]
2004-07-15 6:21 ` Uli Luckas
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=20040714222345.GA12558@foobazco.org \
--to=wesolows@foobazco.org \
--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.