linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, linux-ide@vger.kernel.org,
	albertcc@tw.ibm.com, alan@lxorguk.ukuu.org.uk
Cc: htejun@gmail.com
Subject: [PATCHSET] libata: reorganize configuration and implement revalidation
Date: Fri, 27 Jan 2006 00:39:11 +0900	[thread overview]
Message-ID: <1138289951261-git-send-email-htejun@gmail.com> (raw)
In-Reply-To: 

Hello, again.

This patchset is against

upstream-2.6.17 (7db74a4780cf9cc6b2ea97582cdc8031d5f22ccd)
 + various fixes related to EH patchset [1]
 + three AHCI updates [2][3][4]
 + new reset mechanism patchset [5]
 + fixes regarding configuration patchset [6]

This patchset is consisted of 16 patches and can be categorized into
the following three parts.

#01-07		: prepare for ata_dev_identify() reorganization
#08-12		: reorganize ata_dev_identify() into ata_dev_read_id()
		  and ata_dev_configure()
#13-16		: implement and use revalidation using ata_dev_read_id()
		  and ata_dev_configure()

Also, please pay attention to the following.  It's taken from #08's
description.

  This function is probably the place to set transfer mode to PIO0
  before IDENTIFY.  However, reset -> identify -> init_dev_params
  order should be kept for pre-ATA4 devices so we cannot set transfer
  mode before IDENTIFY for them.  How do we know if a device is
  post-ATA4 before IDENTIFY?

How should we do this?  Ignore pre-ATA4 devices?

Thanks.

--
tejun

[1] http://marc.theaimsgroup.com/?l=linux-ide&m=113798939526779&w=2
[2] http://marc.theaimsgroup.com/?l=linux-ide&m=113800194919594&w=2
[3] http://marc.theaimsgroup.com/?l=linux-ide&m=113800459922438&w=2
[4] http://marc.theaimsgroup.com/?l=linux-ide&m=113804195925385&w=2
[5] http://marc.theaimsgroup.com/?l=linux-ide&m=113809002924734&w=2
[6] http://marc.theaimsgroup.com/?l=linux-ide&m=113828912301267&w=2



             reply	other threads:[~2006-01-26 15:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 15:39 Tejun Heo [this message]
2006-01-26 15:39 ` [PATCH 12/16] libata: reorganize ata_bus_probe() Tejun Heo
2006-01-26 15:39 ` [PATCH 04/16] libata: separate out ata_id_major_version() Tejun Heo
2006-01-26 15:39 ` [PATCH 11/16] libata: fold ata_dev_config() into ata_dev_configure() Tejun Heo
2006-01-26 15:39 ` [PATCH 09/16] libata: kill ata_dev_reread_id() Tejun Heo
2006-01-26 15:39 ` [PATCH 01/16] libata: implement ata_dev_id_c_string() Tejun Heo
2006-01-26 15:39 ` [PATCH 05/16] libata: make ata_dump_id() take @id instead of @dev Tejun Heo
2006-01-26 15:39 ` [PATCH 07/16] libata: convert dev->id to pointer Tejun Heo
2006-01-26 15:39 ` [PATCH 02/16] libata: use ata_dev_id_c_string() Tejun Heo
2006-01-26 15:39 ` [PATCH 15/16] libata: implement ata_dev_revalidate() Tejun Heo
2006-01-26 15:39 ` [PATCH 16/16] libata: revalidate after transfer mode configuration Tejun Heo
2006-01-26 15:39 ` [PATCH 13/16] libata: re-initialize parameters before configuring Tejun Heo
2006-01-26 17:42 ` [PATCHSET] libata: reorganize configuration and implement revalidation Mark Lord

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=1138289951261-git-send-email-htejun@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albertcc@tw.ibm.com \
    --cc=jgarzik@pobox.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).