From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Glenn Wurster <gwurster@scs.carleton.ca>
Cc: 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 16:14:40 +0100 [thread overview]
Message-ID: <200401271614.40542.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20040127055206.GA690@electric.ath.cx>
On Tuesday 27 of January 2004 06:52, Glenn Wurster wrote:
> > Glenn, your patch hides potential problems - these functions shouldn't be
> > called if host doesn't support DMA. However there is one place when
> > ->ide_dma_host_off() shouldn't be called unconditionally, here is a
> > patch. It is not pretty but at least consistent - we check
> > hwif->ide_dma_check to see if DMA is supported in other places too. Does
> > it fix the problem?
>
> Not quite. If we go forward with a patch like that, then it must be
> updated to include at least two other places that I know of
Doh. I overlooked one place.
IMO this check needs to be added only to two places.
> immediately. The updated patch would be something similar to the one
> at the bottom of this e-mail.
Did you test this patch?
> On a further note, how should hdparm -d behave on my controller, the
> relivant lines from dmesg are:
>
> SIS5513: IDE controller at PCI slot 00:01.1
> SIS5513: chipset revision 8
> SIS5513: not 100% native mode: will probe irqs later
> SIS5513: SiS551x ATA 16 controller
> ide0: BM-DMA at 0xf870-0xf877, BIOS settings: hda:pio, hdb:pio
> SIS5513: simplex device: DMA disabled
> ide1: SIS5513 Bus-Master DMA disabled (BIOS)
> hda: WDC AC21000H, ATA DISK drive
> hdc: Maxtor 6Y080L0, ATA DISK drive
>
> "hdparm -d 1 /dev/hdc" returns an operation not permitted, but "hdparm
> -d 1 /dev/hda" is successful and results in future calls to "hdparm -d
> 1 /dev/hdc" seemingly locking the computer.
I suspect that this is caused by unfinished handling of simplex devices
in setup-pci.c (simplex host - one DMA engine but two channels).
> @@ -980,10 +981,13 @@
> drive->id->dma_1word &= ~0x0F00;
>
> #if defined(CONFIG_BLK_DEV_IDEDMA) && !defined(CONFIG_DMA_NONPCI)
> - if (speed >= XFER_SW_DMA_0)
> - hwif->ide_dma_host_on(drive);
> - else
> - hwif->ide_dma_off_quietly(drive);
> + if (speed >= XFER_SW_DMA_0) {
> + if (hwif->ide_dma_check) /* Check if host supports DMA */
> + hwif->ide_dma_host_on(drive);
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.
> + } else {
> + if (hwif->ide_dma_check) /* Check if host supports DMA */
> + hwif->ide_dma_off_quietly(drive);
> + }
Yep, I've missed this one.
Thanks,
--bart
next prev parent reply other threads:[~2004-01-27 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 18:32 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 [this message]
2004-01-27 16:41 ` Glenn Wurster
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=200401271614.40542.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@redhat.com \
--cc=andre@linux-ide.org \
--cc=gwurster@scs.carleton.ca \
--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
all inboxes | Powered by JetHome®