From: Albert Lee <albertcc@tw.ibm.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Fabio Comolli <fabio.comolli@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Schedule for adding pata to kernel?
Date: Fri, 21 Apr 2006 14:38:09 +0800 [thread overview]
Message-ID: <44487DD1.30000@tw.ibm.com> (raw)
In-Reply-To: <20060421011233.GE25726@htj.dyndns.org>
Tejun Heo wrote:
> On Thu, Apr 20, 2006 at 06:48:31PM -0400, Jeff Garzik wrote:
>
>>Tejun Heo wrote:
>>
>>>Hello, all.
>>>
>>>[adding Jeff and linux-ide to cc list]
>>>
>>>On Tue, Apr 18, 2006 at 01:00:13PM +0100, Alan Cox wrote:
>>>
>>>>On Maw, 2006-04-18 at 13:44 +0200, Fabio Comolli wrote:
>>>>
>>>>>In case PIIX/ICH driver should not make it in 2.6.17, are you planning
>>>>>to release patches for 2.6.17-rc release cycle?
>>>>
>>>>I've been on holiday and am now tied up in other work until the start of
>>>>May, at which point Jeff goes off and gets married so there may be some
>>>>delay.
>>>>
>>>>2.6.17-rc actually has 95% of the stuff needed to drop the PATA drivers
>>>>in and I will try to do patches at least versus 2.6.17 final. The -rcs
>>>>will depend upon available time and also what gets integrated that
>>>>causes additional work (notably Tejun Ho's stuff will make much merge
>>>
>>>BTW, my name is Tejun Heo. Tejun Ho sounds horrible in Korean.
>>>
>>>
>>>>work, although its work I'm very glad to do as the improvements and
>>>>hotplug support are all needed).
>>>
>>>I'm currently working on port multiplier support. My working tree now
>>>successfully probes and attaches all devices over the PM and I'm
>>>currently trying to get EH and hotplug to work with it nicely.
>>>EH/hotplug are being changed to support PM. Effects on LLDDs are
>>>minimal but you can probably save some work by waiting for the next
>>>round of patches before porting to new EH.
>>>
>>>I think/hope this can be finished in this week and bombard Jeff with
>>>patches (updated EH, NCQ, hotplug and PM) before the weekend, so that
>>>Jeff can have some time to review and hopefully merge some of it into
>>>#upstream before he goes off on honeymoon. In some convoluted way,
>>>the patches will be my marriage gift, heh heh.
>>>
>>>Jeff, *BIG* congratulations. I wish you a great marriage.
>>
>>Thanks :) And thanks for working on this stuff... As you see, once the
>>EH hurdle is cleared, it is much easier to add new features. New
>>features will start flooding in, from you and others.
>>
>>BTW don't forget we want to push Albert's irq-pio branch into upstream
>>sometime soon after your EH work settles. I would put irq-pio in front
>>of NCQ and PM, particularly.
>
>
> Hmmm... EH, NCQ, PM stuff doesn't really interfere with irq-pio. The
> only thing which needs special attention is hotplug support for
> sata_sil as the driver requires PIO HSM implementation but needs to
> use its own interrupt handler. So, we need to separate out PIO HSM
> from ata_host_intr() and allow LLDD irq handlers to drive it.
In the irq-pio branch, the HSM code has been seperated out from
ata_host_intr() to ata_hsm_move() as static function currently.
Maybe we can export ata_hsm_move() as external?
I didn't look into how sil3611 hotplug interacts with PIO HSM.
Don't know whether this is good enough for the need of sata_sil.
--
albert
prev parent reply other threads:[~2006-04-21 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1142869095.20050.32.camel@localhost.localdomain>
[not found] ` <4422F10B.9080608@bootc.net>
[not found] ` <44266499.3070809@t-online.de>
[not found] ` <1143393969.2540.5.camel@localhost.localdomain>
[not found] ` <b637ec0b0604180444y7828ac5aobb349324f87201c2@mail.gmail.com>
[not found] ` <1145361613.18736.44.camel@localhost.localdomain>
2006-04-18 12:13 ` Schedule for adding pata to kernel? Tejun Heo
2006-04-20 22:48 ` Jeff Garzik
2006-04-21 1:12 ` Tejun Heo
2006-04-21 6:38 ` Albert Lee [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=44487DD1.30000@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=fabio.comolli@gmail.com \
--cc=htejun@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).