linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bob Ham <rah@bash.sh>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-ide@vger.kernel.org
Subject: Re: hpt374 sata (Highpoint Rocket 1540)
Date: Sun, 05 Aug 2007 22:10:21 +0400	[thread overview]
Message-ID: <46B6128D.8050101@ru.mvista.com> (raw)
In-Reply-To: <20070801234229.1e330ad0@the-village.bc.nu>

Hello.

Alan Cox wrote:

>>>hpt37x: Bus clock 66 MHz, using DPLL.

>>    Oh?! hpt366.c detected 33 MHz... :-O

> Interesting as it should be using the same algorithm as hpt366 now.

    Actually not: when pata_hpt37x decides to use DPLL, it reports the chosen 
*DPLL* clock instead of the PCI clock.  The question is why it chose 66 MHz on 
HPT374... Looks like it's because of this wrong mask which should be 0xc0:

		dpll = 2;
                 if (port->udma_mask & 0xE0)
                         dpll = 3;

>>>ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 16 (level, low) -> IRQ 17
>>>scsi2: pata_hpt37x
>>>scsi3: pata_hpt37x
>>>ata3: PATA max UDMA/100 cmd 0x0001efa0 ctl 0x0001ef9e bmdma 0x0001ec00 irq 17
>>>ata4: PATA max UDMA/100 cmd 0x0001ef90 ctl 0x0001ef9a bmdma 0x0001ec00 irq 17

> and it also knows about the bridge knobbling stuff. Most curious

    Not curious at all now. ;-) The former HPT374 clocking fix just remained 
ineffective.

MBR, Sergei

  reply	other threads:[~2007-08-05 18:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 11:08 hpt374 sata (Highpoint Rocket 1540) Bob Ham
2007-07-31 12:23 ` Alan Cox
2007-07-31 20:12   ` Bob Ham
2007-07-31 13:29 ` Sergei Shtylyov
2007-07-31 15:35   ` Brad Campbell
2007-07-31 17:52   ` Sergei Shtylyov
2007-07-31 21:22     ` Bob Ham
2007-07-31 21:32       ` Bartlomiej Zolnierkiewicz
2007-07-31 22:06         ` Bob Ham
2007-08-01 13:40         ` Sergei Shtylyov
2007-08-01 15:52           ` Bob Ham
2007-08-01 15:58             ` Sergei Shtylyov
2007-08-01 17:15               ` Bob Ham
2007-08-01 18:19                 ` Sergei Shtylyov
2007-08-01 22:43                   ` Alan Cox
2007-08-02 12:41                     ` Sergei Shtylyov
2007-08-02 13:12                       ` Alan Cox
2007-08-01 21:03               ` Bob Ham
2007-08-01 21:08                 ` Sergei Shtylyov
2007-08-01 22:42                   ` Alan Cox
2007-08-05 18:10                     ` Sergei Shtylyov [this message]
2007-08-01 21:07           ` Bartlomiej Zolnierkiewicz
2007-08-01 21:16             ` Sergei Shtylyov
2007-08-01 21:29               ` Bartlomiej Zolnierkiewicz
2007-08-01 16:14       ` Alan Cox

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=46B6128D.8050101@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=rah@bash.sh \
    /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;
as well as URLs for NNTP newsgroup(s).