All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uli Luckas <luckas@musoft.de>
To: sparclinux@vger.kernel.org
Subject: Re: sun4c driver/dma problems
Date: Tue, 13 Jul 2004 21:39:00 +0000	[thread overview]
Message-ID: <200407132339.00544.luckas@musoft.de> (raw)
In-Reply-To: <200406020818.13705.luckas@musoft.de>

Am Dienstag, 8. Juni 2004 17:53 schrieb Keith M Wesolowski:
> On Tue, Jun 08, 2004 at 09:22:44AM +0200, Uli Luckas wrote:
> > the above cited DMA message seems to be the root of the driver problems.
> > From the 2.2.26 kernel I know it should read:
> > dma0: Revision 1
> >
> > 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.
>
> Reading your messages, I'm uncertain exactly how well 2.2.26 works.
> Can you please clarify?  If it's perfect, then I may invest a few
> hours trying to fix this for you in 2.6.  If there's no known-working
> kernel, it's unlikely that it ever will be fixed.

Dear Keith,
thanks for your 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?

Regards
Uli

  parent reply	other threads:[~2004-07-13 21:39 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 [this message]
2004-07-14 22:23 ` Keith M Wesolowski
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=200407132339.00544.luckas@musoft.de \
    --to=luckas@musoft.de \
    --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.