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

On Maw, 2005-11-08 at 17:35 -0500, Bill Davidsen wrote:
> 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?

Something like that

I've been collecting the data to get the libata driver right, and in
doing so even with the partial data I had came across some chunks of
data that are wrong in the ide/pci driver.

Its not made easier by the fact hpt seem to have taken down their own
drivers for older (now "unsupported" I suspect) chips.

The frequency and chip id data is needed to correctly tune the PLLs and
to identify the right base frequency for timing.

  reply	other threads:[~2005-11-08 23:38 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
2005-11-08 23:38       ` Alan Cox [this message]
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=1131493110.25192.112.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --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.