mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter Bortas" <bortas@gmail.com>
To: "Paul Mundt" <lethal@linux-sh.org>,
	"Peter Bortas" <bortas@gmail.com>,
	"Marcus Comstedt" <marcus@mc.pp.se>,
	"Adrian McMenamin" <adrianmcmenamin@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix DMA on Dreamcast
Date: Sat, 28 Jul 2007 03:50:02 +0200	[thread overview]
Message-ID: <7e5f60720707271850pd744157w9bea603be2719fa9@mail.gmail.com> (raw)
In-Reply-To: <20070726130635.GA28375@linux-sh.org>

On 7/26/07, Paul Mundt <lethal@linux-sh.org> wrote:
> On Thu, Jul 26, 2007 at 02:59:51PM +0200, Peter Bortas wrote:
> > On 7/26/07, Marcus Comstedt <marcus@mc.pp.se> wrote:
> > > "Peter Bortas" <bortas@gmail.com> writes:
> > > > On 7/21/07, Adrian McMenamin <adrianmcmenamin@gmail.com> wrote:
> > > >> On 21/07/07, Peter Bortas <bortas@gmail.com> wrote:
> > > >> > Sidenote: Does Linux handle the Dreamcast DMA errata?
> > > >>
> > > >> You need to explain what you mean (at least to me!).
> > > >>
> > > >> If you mean will it degrade gracefully - not without this patch if set
> > > >> to the (correct) defconfig. With iffy settings it will.
> > > >
> > > > If I remember correctly (and that's a big if since I last looked at it
> > > > in 2001) some revisions of the Dreamcast hardware would sporadically
> > > > lock up if you scheduled a new DMA request to quickly after a previous
> > > > one, even if you checked the ready bit. It's worked around by a delay
> > > > of X microseconds as recommended by Sega engineers. I don't remember
> > > > the value of X, nor where exactly in the flow this workaround should
> > > > be applied.
> > > >
> > > > Adding Marcus in case he has a better memory than me.
> > >
> > > I don't remeber any such delay.  Are you sure you're not thinking
> > > about the G2 bus problem (where accesses need to be programatically
> > > serialized, whether they are PIO or DMA)?
> >
> > In that case my memory is worse than I thought. I'll see if I can dig
> > up my old notes.
> >
> We've never hit any problems with the SH DMAC, so it would be interesting
> if you had some more information on this. The G2 problems are well known
> and documented, and the driver takes care of those issues already.

After grep-ing through some 8GiB of archived mails and notes it seems
marcus is absolutely correct, I'm thinking of the known G2 problem.

-- 
Peter

      reply	other threads:[~2007-07-28  1:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 19:30 Adrian McMenamin
2007-07-20 19:04 ` Andrew Morton
2007-07-21 10:22   ` Adrian McMenamin
2007-07-21 11:24     ` Peter Bortas
2007-07-21 12:06       ` Adrian McMenamin
2007-07-21 14:13         ` Peter Bortas
2007-07-26 10:10           ` Marcus Comstedt
2007-07-26 12:59             ` Peter Bortas
2007-07-26 13:06               ` Paul Mundt
2007-07-28  1:50                 ` Peter Bortas [this message]

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=7e5f60720707271850pd744157w9bea603be2719fa9@mail.gmail.com \
    --to=bortas@gmail.com \
    --cc=adrianmcmenamin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus@mc.pp.se \
    /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

all inboxes | Powered by JetHome®