From: Jeremy Higdon <jeremy@sgi.com>
To: "Dailey, Nate" <Nate.Dailey@stratus.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_vsc.c cache line size question
Date: Wed, 17 Jan 2007 23:11:49 -0800 [thread overview]
Message-ID: <20070118071149.GB72618@sgi.com> (raw)
In-Reply-To: <92952AEF1F064042B6EF2522E0EEF43703EE3171@EXNA.corp.stratus.com>
On Mon, Jan 15, 2007 at 11:26:59AM -0500, Dailey, Nate wrote:
> Here's a patch that does what you suggest.
>
> Because the default cache line size on my system is 0x10, I tested the
> patch by checking against this value rather than 0... it worked as
> expected.
>
> This patch is against 2.6.19.2 that I just downloaded from kernel.org. I
> actually tested on RHEL4 update 4, a 2.6.9 kernel, but I'll try building
> the 2.6.19.2 on my system to make sure it works in that version as well.
>
> Nate
Hi Nate,
The patch looks fine, except that your mailer wrapped the lines.
Try sending it as a text attachment instead.
Thanks
jeremy
>
> --- sata_vsc.c.orig 2007-01-15 11:06:17.000000000 -0500
> +++ sata_vsc.c 2007-01-15 11:10:29.000000000 -0500
> @@ -340,6 +340,7 @@ static int __devinit vsc_sata_init_one (
> int pci_dev_busy = 0;
> void __iomem *mmio_base;
> int rc;
> + u8 cls;
>
> if (!printed_version++)
> dev_printk(KERN_DEBUG, &pdev->dev, "version "
> DRV_VERSION "\n");
> @@ -389,9 +390,13 @@ static int __devinit vsc_sata_init_one (
> base = (unsigned long) mmio_base;
>
> /*
> - * Due to a bug in the chip, the default cache line size can't
> be used
> + * Due to a bug in the chip, the default cache line size can't
> be
> + * used (unless the default is non-zero).
> */
> - pci_write_config_byte(pdev, PCI_CACHE_LINE_SIZE, 0x80);
> + pci_read_config_byte(pdev, PCI_CACHE_LINE_SIZE, &cls);
> + if (cls == 0x00) {
> + pci_write_config_byte(pdev, PCI_CACHE_LINE_SIZE, 0x80);
> + }
>
> probe_ent->sht = &vsc_sata_sht;
> probe_ent->port_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
next prev parent reply other threads:[~2007-01-18 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 16:26 sata_vsc.c cache line size question Dailey, Nate
2007-01-18 7:11 ` Jeremy Higdon [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-18 14:42 Dailey, Nate
2007-02-07 8:38 ` Jeremy Higdon
2007-01-12 19:45 Dailey, Nate
2007-01-14 8:03 ` Jeremy Higdon
2007-01-14 14:47 ` Alan
2007-01-14 18:21 ` Jeff Garzik
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=20070118071149.GB72618@sgi.com \
--to=jeremy@sgi.com \
--cc=Nate.Dailey@stratus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.