From: Glenn Wurster <gwurster@scs.carleton.ca>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Glenn Wurster <gwurster@scs.carleton.ca>,
Alan Cox <alan@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
andre@linux-ide.org
Subject: Re: [PATCH] ide-dma.c, ide.c, ide.h, kernel 2.4.24
Date: Tue, 27 Jan 2004 11:41:54 -0500 [thread overview]
Message-ID: <20040127164154.GB1024@desktop> (raw)
In-Reply-To: <200401271614.40542.bzolnier@elka.pw.edu.pl>
> Doh. I overlooked one place.
> IMO this check needs to be added only to two places.
True, I added the check three times to emphasise the three different
calls which could potentially OOPS (at least upon initial
observation). It could be optimized into 2 checks.
> Did you test this patch?
Yes.
> I've seen this and decided that it is not needed.
>
> If we try to program drives to DMA on non-DMA host
> something is going wrong and it is better to just OOPS.
This makes sense. Did you want to update the patch for those proposed
changes (You're more familiar with the code than I - I'm reluctant to
play too much with code unless I understand what it is doing)? I'd be
willing to test an updated patch.
> I suspect that this is caused by unfinished handling of simplex
> devices in setup-pci.c (simplex host - one DMA engine but two
> channels).
I'm really not familiar with the complexities behind DMA
programming, especially when it comes to simplex devices so I'm
probably not in much of a position to finish up handling of simplex
devices.
Glenn.
prev parent reply other threads:[~2004-01-27 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 18:32 [PATCH] ide-dma.c, ide.c, ide.h, kernel 2.4.24 Glenn Wurster
2004-01-23 21:33 ` Alan Cox
2004-01-23 22:09 ` Glenn Wurster
2004-01-23 23:45 ` Bartlomiej Zolnierkiewicz
2004-01-27 5:52 ` Glenn Wurster
2004-01-27 15:14 ` Bartlomiej Zolnierkiewicz
2004-01-27 16:41 ` Glenn Wurster [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=20040127164154.GB1024@desktop \
--to=gwurster@scs.carleton.ca \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@redhat.com \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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