All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Highpoint IDE types
Date: Tue, 08 Nov 2005 17:35:28 -0500	[thread overview]
Message-ID: <43712830.90805@tmr.com> (raw)
In-Reply-To: <1131480140.25192.98.camel@localhost.localdomain>

Alan Cox wrote:
> On Maw, 2005-11-08 at 21:02 +0200, Ville Syrjälä wrote:
> 
>>> *      HPT372                  4 (HPT366)      5     
>>> *      HPT372N                 4 (HPT366)      6     
>>> *      HPT372                  5 (HPT372)      0
>>
>>          ^^^^^^
>>
>>This one is called HPT372A by Highpoint's BIOS/Win drivers.
>>
>>Also I'm not sure if it's relevant but PCI ID 5 chips use a different
>>BIOS image than PCI ID 4 chips.
> 
> 
> I suspect it is relevant because the "372A" appears to have a different
> base clock to the HPT372.
> 
> Added to the list.
> 
May we assume that this information was gathered in the interest of 
something beyond pedantic curiousity? Will this simplify the driver 
code, improve performance or reliability, etc?

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-11-08 22:35 UTC|newest]

Thread overview: 12+ 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 [this message]
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ä
2005-11-12  2:15       ` Ville Syrjälä
2005-11-08 19:40 ` Sergei Shtylyov
2005-11-08 20:02   ` Sergei Shtylylov
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=43712830.90805@tmr.com \
    --to=davidsen@tmr.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 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.