linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Carlos Pardo <Carlos.Pardo@siliconimage.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.11.5 ] sata_sil: Fix FIFO PCI Bus Arbitration
Date: Thu, 24 Mar 2005 23:39:49 -0500	[thread overview]
Message-ID: <42439615.8000605@pobox.com> (raw)
In-Reply-To: <2E9B8131C44AF746B1E06BF9B15A434B045D7EF5@zima.siliconimage.com>

Carlos Pardo wrote:
> This patch set default values for the FIFO PCI Bus Arbitration to avoid data corruption. The root cause is due to our PCI bus master handling mismatch with the chipset PCI bridge during DMA xfer (write data to the device). The patch is to setup the DMA fifo threshold so that there is no chance for the DMA engine to change protocol. We have seen this problem only on one motherboard.
> 
> Signed-off-by: Silicon Image Corporation <cpardo@siliconimage.com

Patch applied to libata-2.4 and libata-2.6 queues, and will be sent 
upstream ASAP.  Thanks.

One slight problem with your submission:  your mailer encoded the 
plaintext patch using base64 encoding, which makes the patch difficult 
to review.

The preferred method of submitting patches is pasting them inline. 
However many Windows mailers will corrupt the whitespace in the patch, 
or wrap long lines, if you do this.

On Unix, the best way to accomplish this is described at

	http://lkml.org/lkml/2005/2/24/3

On Windows, the free (open source) Mozilla Thunderbird or Mozilla Mail 
applications should correctly attach plaintext patches without encoding 
them.

Regards,

	Jeff



  parent reply	other threads:[~2005-03-25  4:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 17:11 [PATCH 2.6.11.5 ] sata_sil: Fix FIFO PCI Bus Arbitration Carlos Pardo
2005-03-23 19:12 ` Jeff Garzik
2005-03-25  4:39 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-23 19:23 Carlos Pardo

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=42439615.8000605@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Carlos.Pardo@siliconimage.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).