From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: hpt366-0.37.patch.bz2 K.O.
Date: Fri, 19 Mar 2004 20:23:35 +0300 [thread overview]
Message-ID: <20040319202335.4179737f.vsu@altlinux.ru> (raw)
In-Reply-To: Pine.LNX.4.10.10403190449240.2569-100000@master.linux-ide.org
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Fri, 19 Mar 2004 04:53:22 -0800 (PST) Andre Hedrick wrote:
> http://www.kernel.org/pub/linux/kernel/people/hedrick/ide-2.4.25/hpt366-0.37.patch.bz2
>
> Fixes fifo dma data corruption on RocketRaid404
> Fixes native HPT372 detection/setup for HPT372/HPT372A/HPT372N
>
> HPT372N's previous code seems kooky, but then again do not have specific
> hardware rev in question.
static void __init init_setup_hpt37x (struct pci_dev *dev, ide_pci_device_t *d)
{
+ if (d->device == PCI_DEVICE_ID_TTI_HPT372) {
+ unsigned int class_rev;
+ static char *chipset_names[] = {"HPT372", "HPT372A", "HPT372N"};
+
+ pci_read_config_dword(dev, PCI_CLASS_REVISION, &class_rev);
+ class_rev &= 0xff;
+ d->name = chipset_names[class_rev];
+ }
+
ide_setup_pci_device(dev, d);
}
This will blow up if a chip with the same PCI ID and a revision larger
than 2 ever appears.
Also, hpt366_init_one() is __devinit, but it calls d->init_setup, and
all init_setup_*() functions are __init - does not look good. Hmm,
this is present in many drivers, also in 2.6.x... apparently this is
safe because such devices cannot be hotplugged.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-19 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 12:53 hpt366-0.37.patch.bz2 K.O Andre Hedrick
2004-03-19 17:23 ` Sergey Vlasov [this message]
2004-03-19 20:54 ` Andre Hedrick
2004-03-19 21:09 ` Andre Hedrick
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=20040319202335.4179737f.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--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 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.