From: Thierry Vignaud <tvignaud@mandriva.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [Fwd: [BUG] sata_via doesn't detect anymore my disks (broken between rc1 and rc3)]
Date: Fri, 25 Aug 2006 15:56:07 +0200 [thread overview]
Message-ID: <m2irkgor60.fsf@vador.mandriva.com> (raw)
In-Reply-To: <44EEEA29.1010008@gmail.com> (Tejun Heo's message of "Fri, 25 Aug 2006 21:16:41 +0900")
Tejun Heo <htejun@gmail.com> writes:
> >>> Can you please test two patches attached in this mail? Just
> >>> quick result will be enough. If both don't work, I'll go ahead
> >>> and create a third one - which emulates the old phy hardreset
> >>> exactly as I did for softreset of vt6420.
> >> I'll.
> >>
> >> As, I've tested that using:
> >> - ata_std_prereset + ata_std_softreset didn't work
> >> - vt6420_prereset + ata_std_softreset worked
> >> - vt6420_prereset w/o ata_std_softreset didn't work
> >>
> >> I simple interdiff between your two patches makes me think the
> >> odds're higher the second will succeed but you've done some extra
> >> changes since your previous patch.
> >> I'll you tell you more about this tomorrow.
> > none of both these patches worked :-(
>
> The second didn't work? But you said the following one liner
> worked.
Worked on top of *your original patch*.
What's more,
> + return ata_bmdma_drive_eh(ap, vt6420_prereset, ata_std_softreset,
> sata_std_hardreset, ata_std_postreset);
is different from:
+ return ata_bmdma_drive_eh(ap, vt6420_prereset, ata_std_softreset,
+ NULL, ata_std_postreset);
Note also that I tested my one liner on top of 2.6.18-rc4-mm1 + your
patch whereas I tested your latest patches on top of 2.6.18-rc4-mm2
//\\
Can this make a difference?
> The second patch is essentially identical to what you did the one
> liner. Can you please check it once more? I'll prepare old-sequence
> hardreset in the meantime.
I'll.
You won't have any answer before monday though.
next prev parent reply other threads:[~2006-08-25 13:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D98E7E.3060208@pobox.com>
[not found] ` <44E29AEF.8030606@gmail.com>
[not found] ` <20060816051408.GI6371@htj.dyndns.org>
[not found] ` <m2wt98bio1.fsf@vador.mandriva.com>
[not found] ` <m2sljwbil7.fsf@vador.mandriva.com>
[not found] ` <44E37BD4.8010709@pobox.com>
[not found] ` <m23bbva9cs.fsf@vador.mandriva.com>
[not found] ` <44E46E0E.4060703@gmail.com>
[not found] ` <m2fyfv7a8s.fsf@vador.mandriva.com>
2006-08-22 16:37 ` [Fwd: [BUG] sata_via doesn't detect anymore my disks (broken between rc1 and rc3)] Tejun Heo
2006-08-23 20:17 ` Thierry Vignaud
2006-08-25 10:29 ` Thierry Vignaud
2006-08-25 12:16 ` Tejun Heo
2006-08-25 13:55 ` Tejun Heo
2006-08-25 14:09 ` Thierry Vignaud
2006-08-25 15:03 ` Tejun Heo
2006-08-25 15:30 ` Thierry Vignaud
2006-08-28 14:34 ` Thierry Vignaud
2006-08-28 15:24 ` Tejun Heo
2006-08-28 15:43 ` Thierry Vignaud
2006-10-03 15:00 ` Thierry Vignaud
2006-10-20 18:59 ` Thierry Vignaud
2006-08-25 13:56 ` Thierry Vignaud [this message]
2006-08-25 14:02 ` Thierry Vignaud
2006-08-25 15:02 ` Tejun Heo
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=m2irkgor60.fsf@vador.mandriva.com \
--to=tvignaud@mandriva.com \
--cc=htejun@gmail.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).