From: "Ville Syrjälä" <syrjala@sci.fi>
To: linux-kernel@vger.kernel.org
Cc: linux-ide@vger.kernel.org
Subject: Re: Highpoint IDE types
Date: Sat, 12 Nov 2005 04:15:02 +0200 [thread overview]
Message-ID: <pan.2005.11.12.02.15.00.646462@sci.fi> (raw)
In-Reply-To: <4374F633.6020006@ru.mvista.com>
On Fri, 11 Nov 2005 22:51:15 +0300, Sergei Shtylylov wrote:
> Hello.
>
> Ville Syrjälä wrote:
>> On Tue, 08 Nov 2005 17:38:02 +0000, Alan Cox wrote:
>
>>>Ok thanks to Sergei I can now post what I think is the complete table of
>>>HPT chip versions:
>
> Another correction coming in... :-)
>
>>> Chip PCI ID Rev
>>> * HPT366 4 (HPT366) 0
>>> * HPT366 4 (HPT366) 1
>>> * HPT368 4 (HPT366) 2
>>> * HPT370 4 (HPT366) 3
>>> * HPT370A 4 (HPT366) 4
>>> * HPT372 4 (HPT366) 5
>>> * HPT372N 4 (HPT366) 6
>>> * HPT372 5 (HPT372) 0
>>
>> ^^^^^^
>>
>> This one is called HPT372A by Highpoint's BIOS/Win drivers.
>
> According to Highpoint's driver code 372A has rev. ID 1...
>
>> Also I'm not sure if it's relevant but PCI ID 5 chips use a different
>> BIOS image than PCI ID 4 chips.
>>
>>
>>> * HPT372N 5 (HPT372) > 0
>
> And 372N has rev. ID 2...
Right you are. Their opensource driver doesn't list any PCI ID 5,6 or 7
chips with revision 0. All rev 1 chips are apparently non-N models and all
rev 2 chips are N models.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
next prev parent reply other threads:[~2005-11-12 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 17:38 Alan Cox
2005-11-08 19:02 ` Ville Syrjälä
2005-11-08 20:02 ` Alan Cox
2005-11-08 22:35 ` Bill Davidsen
2005-11-08 23:38 ` Alan Cox
2005-11-10 14:23 ` PATA libata patches (and HPT) Alan Cox
2005-11-11 19:51 ` Highpoint IDE types Sergei Shtylylov
2005-11-12 2:15 ` Ville Syrjälä [this message]
2005-11-09 10:27 ` Karsten Desler
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=pan.2005.11.12.02.15.00.646462@sci.fi \
--to=syrjala@sci.fi \
--cc=linux-ide@vger.kernel.org \
--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
Powered by JetHome