public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylylov <sshtylyov@ru.mvista.com>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Highpoint IDE types
Date: Fri, 11 Nov 2005 22:51:15 +0300	[thread overview]
Message-ID: <4374F633.6020006@ru.mvista.com> (raw)
In-Reply-To: <pan.2005.11.08.19.02.09.190896@sci.fi>

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...

WBR, Sergei

  parent reply	other threads:[~2005-11-11 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 17:38 Highpoint IDE types 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   ` Sergei Shtylylov [this message]
2005-11-12  2:15     ` Highpoint IDE types Ville Syrjälä
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=4374F633.6020006@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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