From: Grzegorz Adam Hankiewicz <gradha@titanium.sabren.com>
To: Allen Martin <AMartin@nvidia.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Linux kernel 2.6.10 sata_nv.c stops working on my hardware
Date: Tue, 27 Jun 2006 23:34:51 +0200 [thread overview]
Message-ID: <20060627213451.GA2443@noir> (raw)
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B00E48CF38@hqemmail02.nvidia.com>
On 2006-06-26, Allen Martin <AMartin@nvidia.com> wrote:
> Have you tried the 2.6.9 sata_nv.c on 2.6.10? All you should have
> to do to get it working is change the host_set->pdev references
> to use to_pci_dev().
>
> The only functional change in sata_nv that should make any
> difference is the following:
>
> static struct ata_port_info nv_port_info = {
> .sht = &nv_sht,
> .host_flags = ATA_FLAG_SATA |
> - ATA_FLAG_SATA_RESET |
> + /* ATA_FLAG_SATA_RESET | */
> ATA_FLAG_SRST |
> ATA_FLAG_NO_LEGACY,
> .pio_mask = NV_PIO_MASK,
>
>
> You can try changing that back to see if it makes a difference.
> I would also investigate changes in libata too.
Actually the change you proposed works on my system. A 2.6.10 with
the ATA_FLAG_SATA_RESET works. I did the same to a 2.6.16 kernel
but there it didn't work. I guess something else was introduced
between 2.6.10 and 2.6.16. I'll start recompiling again everything
from 2.6.10 up to 2.6.16 with that flag turned on to see where it
stops working again.
next prev parent reply other threads:[~2006-06-27 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 19:23 Linux kernel 2.6.10 sata_nv.c stops working on my hardware Grzegorz Adam Hankiewicz
2006-06-26 20:48 ` Allen Martin
2006-06-27 21:34 ` Grzegorz Adam Hankiewicz [this message]
2006-07-02 13:30 ` Grzegorz Adam Hankiewicz
2006-07-05 17:29 ` Grzegorz Adam Hankiewicz
[not found] <20060702133125.GB2606@noir>
[not found] ` <DBFABB80F7FD3143A911F9E6CFD477B014AD8D80@hqemmail02.nvidia.com>
2006-07-03 17:40 ` Grzegorz Adam Hankiewicz
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=20060627213451.GA2443@noir \
--to=gradha@titanium.sabren.com \
--cc=AMartin@nvidia.com \
--cc=linux-kernel@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