linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Jeffries <lkml@andyjeffries.co.uk>
To: linux-kernel@vger.kernel.org
Subject: HPT372 on KR7A-RAID
Date: Thu, 21 Feb 2002 09:13:19 +0000	[thread overview]
Message-ID: <20020221091319.37e74cba.lkml@andyjeffries.co.uk> (raw)


Hi there,

The HPT chipset on the KR7A-RAID is not detected.  It comes through with a
revision 5, which crashes the Kernel (panic) on 2.4.16.  The patch below
adds the revision for the HPT372 chipset which is the relevant one,
however this will break again when a new revision comes out.  I would like
to be able to print a warning if the revision is higher than the one in
the array and if it is allow a parameter to fake the chipset as being a
lower one (at the users risk), but quite frankly my Kernel programming is
not that good!!

I don't know if this has been fixed in 2.4.17/18, if it has...sorry! :-)

--- linux-2.4.16/drivers/ide/hpt366.c	Wed Feb 20 10:35:25 2002
+++ linux/drivers/ide/hpt366.c	Wed Feb 20 10:37:37 2002
@@ -207,7 +207,7 @@
 	char *p		= buffer;
 	u32 bibma	= bmide_dev->resource[4].start;
 	u32 bibma2 	= bmide2_dev->resource[4].start;
-	char *chipset_names[] = {"HPT366", "HPT366", "HPT368", "HPT370", "HPT370A"};
+	char *chipset_names[] = {"HPT366", "HPT366", "HPT368", "HPT370", "HPT370A", "HPT372"};
 	u8  c0 = 0, c1 = 0;
 	u32 class_rev;
 
--- linux-2.4.16/drivers/ide/ide-pci.c	Wed Feb 20 10:35:25 2002
+++ linux/drivers/ide/ide-pci.c	Wed Feb 20 10:37:22 2002
@@ -828,7 +828,7 @@
 	ide_pci_device_t *d2;
 	unsigned char pin1 = 0, pin2 = 0;
 	unsigned int class_rev;
-	char *chipset_names[] = {"HPT366", "HPT366", "HPT368", "HPT370", "HPT370A"};
+	char *chipset_names[] = {"HPT366", "HPT366", "HPT368", "HPT370", "HPT370A", "HPT372"};
 
 	if (PCI_FUNC(dev->devfn) & 1)
 		return;



-- 
Andy Jeffries
Linux/PHP Programmer

- Windows Crash HOWTO: compile the code below in VC++ and run it!
main (){for(;;){printf("Hung up\t\b\b\b\b\b\b");}}

             reply	other threads:[~2002-02-21  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0202210427050.27301-100000@bugs.home.shadowstar.net>
2002-02-21  9:13 ` Andy Jeffries [this message]
2002-02-21  9:46   ` HPT372 on KR7A-RAID Andy Jeffries
2002-02-21 13:16   ` Andy Jeffries
2002-02-21 13:22   ` Alan Cox
2002-03-04 15:40   ` Andy Jeffries
2002-03-04 16:51     ` Alan Cox

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=20020221091319.37e74cba.lkml@andyjeffries.co.uk \
    --to=lkml@andyjeffries.co.uk \
    --cc=linux-kernel@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).