From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 3/13] siimage: fix wrong ->swdma_mask
Date: Sat, 10 Mar 2007 23:37:47 +0100 [thread overview]
Message-ID: <200703102337.47122.bzolnier@gmail.com> (raw)
In-Reply-To: <45F3219C.5040500@ru.mvista.com>
On Saturday 10 March 2007, Sergei Shtylyov wrote:
> Hello.
>
> Bartlomiej Zolnierkiewicz wrote:
>
> > [PATCH] siimage: fix wrong ->swdma_mask
>
> > This driver doesn't support SWDMA so use the correct ->swdma_mask.
>
> > While at it:
>
> > * no need to call config_chipset_for_pio() in config_chipset_for_dma(),
> > if DMA is not available config_chipset_for_pio() will be called
> > by siimage_config_drive_for_dma() and if DMA is available
> > config_siimage_chipset_for_pio() will be called by siimage_tune_chipset()
>
> Ugh, this driver has such a messy code PIO-wise! There seems to be
> completely no point in calling config_siimage_chipset_for_pio() from
> siimage_tune_chipset(). Not mentioning that tuneproc() method fails to
> actually control IORDY (it only twiddles IORDY bits for taskfile access). Ah,
> and tuneproc() fails to set the drive's own mode (as usual)... :-)
> I was going to post patches but then figured out that we don't actually
> support this driver, so the priority has significatly dropped. :-)
Does it mean that I should expect more patches for other drivers? ;-)
If so I could take care of this one... :-)
Bart
next prev parent reply other threads:[~2007-03-10 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 21:12 [PATCH 3/13] siimage: fix wrong ->swdma_mask Bartlomiej Zolnierkiewicz
2007-03-10 21:22 ` Sergei Shtylyov
2007-03-10 22:37 ` Bartlomiej Zolnierkiewicz [this message]
2007-03-12 13:19 ` Sergei Shtylyov
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=200703102337.47122.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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 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.