From: Andre Hedrick <andre@linux-ide.org>
To: Ulf-Andre Gramstad <j1@gramstad.org>
Cc: linux-kernel@vger.kernel.org
Subject: RE: hpt374 / BUG();
Date: Thu, 22 Aug 2002 20:11:12 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10208222009540.13077-100000@master.linux-ide.org> (raw)
In-Reply-To: <IOELJIHGBNLBJNBMHABBOEACCDAA.j1@gramstad.org>
I just got a reply from HighPoint and they claim they do not have support
for a 66MHz base PLL for hpt374/hpt372.
So that make is more interesting.
On Thu, 22 Aug 2002, Ulf-Andre Gramstad wrote:
> > You have a system where it actually have the PLL already set and in
> > 66-clock base? You are the first person to ever hit this BUG().
> > I will need to work with HighPoint to finish the timing table.
> >
> > If you would have several device of various max transfer rate limits you
> > could attach without the driver being built it, it would give me a few
> > data point to verify if the table I have started is even close.
>
> My HPT374 controller works with the new 2.4.20-pre2-ac6 patch, running at
> ATA-66.
> /proc/ide/hpt366 shows only primary and secondary channel, so I guess thats
> why the hard drives on channel 3 and 4 is not working?
>
>
> -
> UAG
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
LAD Storage Consulting Group
next prev parent reply other threads:[~2002-08-23 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 14:10 jools
2002-08-20 14:28 ` Alan Cox
2002-08-20 14:36 ` Alan Cox
2002-08-20 21:03 ` Andre Hedrick
2002-08-22 20:22 ` Ulf-Andre Gramstad
2002-08-23 3:11 ` Andre Hedrick [this message]
2002-08-25 20:33 ` Ulf-Andre Gramstad
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=Pine.LNX.4.10.10208222009540.13077-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=j1@gramstad.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
all inboxes | Powered by JetHome®