From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
jgarzik@pobox.com
Subject: Re: PATCH: (For review) Teach libata to tune master/slave seperately
Date: Wed, 18 Jan 2006 13:44:01 +0100 [thread overview]
Message-ID: <58cb370e0601180444i1af5a6c7y51156877db1ae826@mail.gmail.com> (raw)
In-Reply-To: <1137585865.25819.27.camel@localhost.localdomain>
On 1/18/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Mer, 2006-01-18 at 12:40 +0100, Bartlomiej Zolnierkiewicz wrote:
> > The core logic is changed (in the positive way): ata_pio_modes()
> > is finally used for obtaining PIO mask to be used.
>
> Ah yes, Jeff hadn't previously merged the small version of that change.
> Indeed description is a little incorrect.
>
> > Please update the patch description or make it a separate change.
> >
> > The other functional change is the ordering of programming host/devices:
> >
> > previously:
> > * program PIO for device 0 [host]
> > * program PIO for device 1 [host]
> > * program DMA for device 0 [host]
> > * program DMA for device 1 [host]
> > * program xfer mode for device 0 [device]
> > * program xfer mode for device 1 [device]
> >
> > now:
> > * program PIO for device 0 [host]
> > * program DMA for device 0 [host]
> > * program xfer mode for device 0 [device]
> > * program PIO for device 1 [host]
> > * program DMA for device 1 [host]
> > * program xfer mode for device 0 [device]
> >
> > This change is OK but I wonder what is the reason for it?
>
> It simply how suffling the code re-ordered it. I don't think its a
> problem but if anyone has a problem I can go and re-re-order it.
I think it is fine, no need for change.
> libata also really should do adev->pio_mode = XFER_PIO_0; ->set_piomode
> before doing its initial identify etc because there is no guarantee the
> BIOS didn't leave the hardware in a bogus state.
seconded
Bartlomiej
prev parent reply other threads:[~2006-01-18 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 21:01 Alan Cox
2006-01-18 11:40 ` Bartlomiej Zolnierkiewicz
2006-01-18 12:04 ` Alan Cox
2006-01-18 12:44 ` Bartlomiej Zolnierkiewicz [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=58cb370e0601180444i1af5a6c7y51156877db1ae826@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®