linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH-RFC] (was: Re: Sata Sil3512 bug?;  Promise SATA300 TX4)
@ 2007-10-27 14:53 Mikael Pettersson
  2007-10-27 15:32 ` [PATCH-RFC] Promise SATA300 TX4 Alexander Sabourenkov
  0 siblings, 1 reply; 3+ messages in thread
From: Mikael Pettersson @ 2007-10-27 14:53 UTC (permalink / raw)
  To: linux-ide, screwdriver; +Cc: MisterE2002, benh, htejun, jeff, jgarzik

On Sat, 27 Oct 2007 17:24:32 +0400, Alexander Sabourenkov wrote:
> There appears to be a hardware bug in that it chokes on scatterlist
> if the last item is larger than 164 bytes.
> 
> The patch that follows fixes my problem on 2.6.22.
> 
> I can't think of a way to avoid second pass over scatterlist without
> duplicating code (ata_qc_prep() and ata_fill_sg() from libata-core.c).
> 
> 
> --- a/drivers/ata/sata_promise.c	2007-07-09 03:32:17.000000000 +0400
> +++ b/drivers/ata/sata_promise.c	2007-10-27 17:20:03.000000000 +0400

Interesting, but can you please give more background information?
I.e., how did you determine the existence of this bug?

And please cc: the sata_promise maintainer on sata_promise patches.
(Hint: that's me)

And please choose a Subject: that makes it absolutely clear what
the post is about. "Sata Sil3512 bug" doesn't exactly sound like
something the sata_promise maintainer needs to look at.

Meanwhile I'll check the Promise driver(s) to see if there's
something about SG table formatting restrictions there.

/Mikael

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-10-28  8:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-27 14:53 [PATCH-RFC] (was: Re: Sata Sil3512 bug?; Promise SATA300 TX4) Mikael Pettersson
2007-10-27 15:32 ` [PATCH-RFC] Promise SATA300 TX4 Alexander Sabourenkov
2007-10-28  8:29   ` Jeff Garzik

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).