public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Tim Hockin <thockin@sun.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: HPT370/366 testers needed
Date: Tue, 23 Oct 2001 15:25:47 -0400	[thread overview]
Message-ID: <20011023152547.E27797@redhat.com> (raw)
In-Reply-To: <3BD5A007.C07388ED@sun.com>
In-Reply-To: <3BD5A007.C07388ED@sun.com>; from thockin@sun.com on Tue, Oct 23, 2001 at 09:51:19AM -0700

On Tue, Oct 23, 2001 at 09:51:19AM -0700, Tim Hockin wrote:
> All,
> 
> We have this (attached) large patch for the HighPoint driver. 
> Specifically, it deals with HPT370 controllers, and should make them MUCH
> more stable (Adrian spent weeks on the phone with HighPoint).
> 
> What I'd like is for people to test this patch on other systems with
> HighPoint 370 controllers.  Also, I need people with HPT366 chips to test,
> and find any problems - we don't have HPT366 here to test.

> Volunteers?

I don't have any HighPoint controllers here, but I did spot a bug in 
the patch that's easy to fix:

> -#if 0
> -	if (test != 0x08)
> -		pci_write_config_byte(dev, PCI_CACHE_LINE_SIZE, 0x08);
> -#else
>  	if (test != (L1_CACHE_BYTES / 4))
>  		pci_write_config_byte(dev, PCI_CACHE_LINE_SIZE, (L1_CACHE_BYTES / 4));
> -#endif

This isn't correct on current Athlon and P4 machines running kernels 
compiled for i686.  One approach is to only set the cache line size if 
the bios set it to something less than we expect it to, or to leave 
this kind of pci hackery to the generic pci layer.  It's important to
note that quite a few drivers share this bug at present.  Cheers,

		-ben

  reply	other threads:[~2001-10-23 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23 16:51 HPT370/366 testers needed Tim Hockin
2001-10-23 19:25 ` Benjamin LaHaise [this message]
2001-10-23 20:45   ` Alan Cox
2001-10-24  0:50     ` Jeff Garzik
2001-10-24  3:26 ` Ricardo Ferreira
2001-10-24 10:36 ` Andrey Panin

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=20011023152547.E27797@redhat.com \
    --to=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@sun.com \
    /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