From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: libata iomap, PATA, etc.
Date: Thu, 10 Aug 2006 07:45:20 -0400 [thread overview]
Message-ID: <44DB1C50.6050905@garzik.org> (raw)
Tejun,
Since you are poking around in this area, I wanted to remind you of the
promise-sata-pata branch.
A problem with the current libata API is that probe_ent and related code
does not easily permit two -vastly different- port technologies (SATA
and PATA, in this case) to be driven by the same hardware.
promise-sata-pata branch has not been merged because its solution is
highly ugly.
A better solution will emerge when... you guessed it... probe_ent goes
away, and host_set can be initialized directly. This allows the LLDD to
directly configure host_set and associated ata_port structures to its needs.
There are also a few other controllers (SiS, VIA) which have similar
SATA+PATA configurations to be supported.
Jeff
reply other threads:[~2006-08-10 11:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44DB1C50.6050905@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--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 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).