From: Jeff Garzik <jgarzik@pobox.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sata_via: PATA support, resubmit
Date: Mon, 08 Jan 2007 08:04:25 -0500 [thread overview]
Message-ID: <45A24159.7060001@pobox.com> (raw)
In-Reply-To: <20070108122659.00c22754@localhost.localdomain>
Alan wrote:
> This is a clean version of the PATA support for the sata_via hardware.
> I'm resubmitting it since nothing has happened since the last submission
> despite promises of libata core changes. Given users actually need to use
> this stuff today and the code is clean it should get merged irrespective
> of any longer term plans for per channel operations structs and the like.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
Re-explanation since you missed it the first time:
Per-channel operations structs work /today/.
The problem you need to fix or work around is ata_probe_ent, which
doesn't properly fill in ata_port info for this situation. Tejun has
posted patches that kill ata_probe_ent, which you were pointed to.
Mikael Pettersson just posted a sata_promise example that uses
->port_start to work around this problem, setting the cable type and
ata_port::ops properly at runtime, based on SATA or PATA. See "[RFC]
sata_promise: handle TX2plus PATA locally", I believe you were CC'd on
my response.
So, working code for both the short term workaround and long term fix
exist /today/.
If you get the setup right, you don't bloat each hook with "is this port
PATA?" tests. At present, your sata_via patch introduces these needless
tests.
Jeff
next prev parent reply other threads:[~2007-01-08 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 12:26 [PATCH] sata_via: PATA support, resubmit Alan
2007-01-08 13:04 ` Jeff Garzik [this message]
2007-01-08 15:42 ` Alan
2007-01-08 15:51 ` Jeff Garzik
2007-01-08 16:40 ` Alan
2007-01-08 16:34 ` Jeff Garzik
2007-01-08 17:11 ` Alan
2007-01-09 10:39 ` Jeff Garzik
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=45A24159.7060001@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.