linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Bastien-Filiatrault <joe@dastyle.net>
To: linux-ide@vger.kernel.org
Subject: ICH7: proposition for supporting AHCI along with native IDE
Date: Thu, 16 Aug 2007 13:51:56 -0400	[thread overview]
Message-ID: <46C48EBC.9030708@dastyle.net> (raw)

Hello,

Early experimentation on my part seems to show that it is possible to 
put an ICH SATA controller booted in SATA compatibility mode in full 
native AHCI mode. The drawback of having the ICH7 chip in AHCI mode is 
that the PATA ports are not claimed or used by any driver, rendering the 
PATA ports unusable.

Suggestion:

Make a new driver (ata_hci7 ?) which claims the following IDs (all 
vendor 8086/intel):
27c0: Desktop ICH7 SATA, IDE mode
27c1: Desktop ICH7 SATA, AHCI mode
27c4: Mobile ICH7 SATA, IDE mode
27c5: Mobile ICH7 SATA, AHCI mode

Driver initialization would be as follows:

1. Claim the device for itself
2. If the SATA chip is in IDE mode, initialize AHCI mode.
3. Use functions in ahci.ko to enable AHCI functionality (will need some 
EXPORT_SYMBOL_GPL).
4. Use the functions in ata_piix.ko to enable PATA functionality (more 
EXPORT_SYMBOL_GPL).

On driver unload, the driver would put back the controller in IDE mode 
if it was before module load.

Such a driver would provide enhanced performance for users who cannot 
enable AHCI for their machine in the bios. It would also mean that ICH7 
users would be able to use AHCI along with PATA.

Example (and current testing) system:
- Dell Latitude D620

SATA P0: main disk drive
SATA P2: external SATA ?
PATA Secondary master "hdc": DVD-Rom ejectable drive bay.

Please let me know what you think,
Thank you,
Jonathan

                 reply	other threads:[~2007-08-16 17:51 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=46C48EBC.9030708@dastyle.net \
    --to=joe@dastyle.net \
    --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).