From: Jeff Garzik <jgarzik@pobox.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata dev_config call order wrong.
Date: Sun, 29 Aug 2004 13:29:44 -0400 [thread overview]
Message-ID: <41321288.4090403@pobox.com> (raw)
In-Reply-To: <41320DAF.2060306@wasp.net.au>
Brad Campbell wrote:
> Well, well, well - Three holes in the ground.
>
> My bridge boards *are* choking on > 200 sector transfers.
>
> I patched sata_via in the same way sata_sil was patched to tell the
> controller to use 200 as max_sectors the same way sata_sil uses 15 as
> max_sectors on the seagates.
>
> The problem is that ata_scsi_slave_config in libata-scsi.c is getting
> called *after* .dev_config in sata_via and resetting my value of 200 to
> 2048.
Take a look at what ATA_DFLAG_LOCK_SECTORS does ;-) Here's hoping
that's the last piece of the puzzle...
BTW I just sent email to SiI to see if there is a way to detect a
PATA->SATA bridge.
Jeff
next prev parent reply other threads:[~2004-08-29 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 17:09 libata dev_config call order wrong Brad Campbell
2004-08-29 17:29 ` Jeff Garzik [this message]
2004-08-29 17:47 ` Brad Campbell
2004-08-29 17:59 ` Jeff Garzik
2004-08-29 18:25 ` Jeff Garzik
2004-08-29 18:59 ` Alan Cox
2004-08-30 9:12 ` Brad Campbell
2004-08-30 13:22 ` Alan Cox
2004-08-30 14:38 ` Brad Campbell
2004-08-30 14:42 ` [PATCH] libata ATA vs SATA detection and workaround Brad Campbell
2004-08-30 14:57 ` Brad Campbell
2004-08-30 16:06 ` Jeff Garzik
2004-08-30 16:34 ` Brad Campbell
2004-08-30 16:37 ` Jeff Garzik
2004-08-30 17:17 ` Brad Campbell
2004-08-30 17:59 ` Jeff Garzik
2004-08-31 7:47 ` Brad Campbell
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=41321288.4090403@pobox.com \
--to=jgarzik@pobox.com \
--cc=brad@wasp.net.au \
--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).