From: Jeff Garzik <jgarzik@pobox.com>
To: Erik Benada <erikbenada@yahoo.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] PATA port support for PDC2037x
Date: Wed, 29 Sep 2004 23:39:22 -0400 [thread overview]
Message-ID: <415B7FEA.2060209@pobox.com> (raw)
In-Reply-To: <20040930023013.13192.qmail@web60304.mail.yahoo.com>
Erik Benada wrote:
> Jeff,
>
> included is patch to add support for PATA port on Promise PDC2037x controllers.
> Patch is against 2.6.8.1 vanilla kernel.
> I tested this patch on my PDC20378 on-board controller with 1 PATA drive attached.
> I didn't do any large testing but my drive was detected properly and I was able to
> mount and use filesystem on it.
>
> I tried to minimize changes to libata code. I just added flags for each port to ata_probe_ent
> structure and modified ata_host_init() function.
>
> Promise SATA driver was changed to use new ata_probe_ent->port_flags, check for presence of
> PATA port and pdc_phy_reset will use different reset code for PATA and SATA ports.
>
> Any comments, suggestions?
Very nice!
I don't see any bugs in the code... my main concern is that I
definitely want to see host controllers (struct ata_host_set) support
multiple ata_port_operations structures. That would eliminate the need
to do
+ if (ap->flags & ATA_FLAG_SATA)
+ sata_phy_reset(ap);
+ else
+ pdc_pata_phy_reset(ap);
and also eliminate a few other roadblocks.
However, implementing such is not a simple as your solution.
I will definitely merge this patch into my libata-dev queue, so that
others can download and test it (and/or simply get their PATA port
working). We'll see where it goes from there. If nobody (including
me) implements the ata_port_operations solution I described, then I will
probably push this into upstream 2.6.x as an incremental step towards
the proper solution.
Thanks,
Jeff
next prev parent reply other threads:[~2004-09-30 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 2:30 [PATCH] PATA port support for PDC2037x Erik Benada
2004-09-30 3:39 ` Jeff Garzik [this message]
2004-09-30 13:22 ` Erik Benada
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=415B7FEA.2060209@pobox.com \
--to=jgarzik@pobox.com \
--cc=erikbenada@yahoo.ca \
--cc=linux-ide@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.