From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata/pata_it821x: Improve handling of poorly compatible emulations
Date: Tue, 30 Oct 2007 09:27:04 -0400 [thread overview]
Message-ID: <47273128.4090406@garzik.org> (raw)
In-Reply-To: <20071025142116.7e38ee86@the-village.bc.nu>
Alan Cox wrote:
> Some it821x RAID firmwares return 0 for the err return off both devices.
> A similar issue occurs with the slave returning 0 not 1 if you plug a
> gigabyte sata ramdisk into a controller that fakes two SATA ports as
> master/slave on an SFF channel.
>
> The patch does the following
>
> - Allow the 'failed diagnostics' case on both master and slave
> - Move the HORKAGE_DIAGNOSTIC check after ->dev_config
>
> This second change also allows IT821x to fix up a problem where we report
> drive diagnostic failures when in fact the drive is fine but the
> microcontroller firmware doesn't appear to get it right. IT821x clears
> the flag again to avoid giving the user bogus warnings about their disk.
>
> The other IT821x change is a bit ugly, we slightly abuse the cable type
> hook to fiddle with the identify data for the devices. We could add a new
> hook for this but as we have only one offender and no more seeming likely
> it seems better to keep libata-core clean.
>
> Please let this sit in -mm briefly, just in case the relaxed checking
> breaks some other emulated interface.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
Two questions:
1) should I queue for 2.6.24-rc?
2) why is ->dev_config() insufficient?
next prev parent reply other threads:[~2007-10-30 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 13:21 [PATCH] libata/pata_it821x: Improve handling of poorly compatible emulations Alan Cox
2007-10-25 20:11 ` Andrew Morton
2007-10-25 22:34 ` Alan Cox
2007-10-30 13:27 ` Jeff Garzik [this message]
2007-10-30 13:33 ` Alan Cox
2007-10-30 13:39 ` Jeff Garzik
2007-10-30 13:43 ` Alan Cox
2007-10-30 13:57 ` 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=47273128.4090406@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).