From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
torvalds@osdl.org, linux-ide@vger.kernel.org
Subject: Re: PATCH: 2.6.10 - IT8212 IDE
Date: Wed, 29 Dec 2004 22:32:12 +0100 [thread overview]
Message-ID: <58cb370e04122913323cdf05e8@mail.gmail.com> (raw)
In-Reply-To: <1104351122.31052.9.camel@localhost.localdomain>
On Wed, 29 Dec 2004 20:12:04 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Mer, 2004-12-29 at 17:29, Bartlomiej Zolnierkiewicz wrote:
> > Let me complain once again :-), libata based driver would be better...
>
> Eventually probably but libata's PATA support is pretty pathetic right
> now, it doesn't know anything about PATA drive errata. I did look at it
> and when it grows up into a real IDE layer for PATA I'm all for moving
> *every* IDE driver to it because some of the IDE error path corner cases
OK
> are almost rewrite level fixes (eg DMA changedown, timer/interrupt CD
> race oops)
fully agreed
> > > + * If we are in pass through mode then not much
> > > + * needs to be done, but we do bother to clear the
> > > + * IRQ mask in case the drives are PIO (eg rev 0x10)
> > > + * for now.
> > > + */
> >
> > comment or code is wrong, unmask is turned on unconditionally
>
> Disagree. It says "e.g."
"e.g." is okay, "in case the drives are PIO" is not,
unmask also affects DMA (I believe it is not needed for DMA but ...)
> > > + hwif->ide_dma_off_quietly(drive);
> > > +#ifdef CONFIG_IDEDMA_ONLYDISK
> > > + if (drive->media == ide_disk)
> > > +#endif
> > > + hwif->ide_dma_check(drive);
> >
> > hack, it looks like fixup code in ide-probe.c need to be moved to probe_hwif()
>
> I'm not sure of the best way to do that cleanly. What do you have in
> mind ?
moving ->fixup() execution from probe_hwif_init_with_fixup() to probe_hwif()
(just before code which does PIO / DMA tuning)
>From what I see it shouldn't affect current ->fixup users
(and is saner because currently "undecoded slave" is also tuned).
> Thanks. I'll go and polish these up.
Thanks.
next prev parent reply other threads:[~2004-12-29 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 15:16 PATCH: 2.6.10 - IT8212 IDE Alan Cox
2004-12-29 5:44 ` Andre Hedrick
2004-12-29 17:29 ` Bartlomiej Zolnierkiewicz
2004-12-29 20:12 ` Alan Cox
2004-12-29 21:32 ` Bartlomiej Zolnierkiewicz [this message]
2004-12-29 21:24 ` Alan Cox
2004-12-29 22:38 ` Bartlomiej Zolnierkiewicz
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=58cb370e04122913323cdf05e8@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).