From: "Oskar Liljeblad" <oskar@osk.mine.nu>
To: Drew Winstel <DWinstel@Miltope.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards
Date: Tue, 3 May 2005 19:28:46 +0200 [thread overview]
Message-ID: <20050503172845.GA12944@oskar> (raw)
In-Reply-To: <66F9227F7417874C8DB3CEB05772741704514D@MILEX0.Miltope.local>
On Tuesday, May 03, 2005 at 11:53, Drew Winstel wrote:
> I think I know what the problem is.
>
> In include/linux/libata.h, make sure the preprocessor declarations are as
> follows. I think the defaults have ATA_ENABLE_PATA undefined.
>
> #define ATA_ENABLE_ATAPI /* undefine to disable ATAPI support */
> #define ATA_ENABLE_PATA /* define to enable PATA support in some
> * low-level drivers */
Thanks, now it loads correctly. Unfortunately the clock drift still occurs
with pata_pdc2027x. I'm guessing here, but can clock drift have anything
to do with IRQs? Also, is it normal to see errors in /proc/interrupt?
# cat /proc/interrupts
CPU0
0: 954189 XT-PIC timer
2: 0 XT-PIC cascade
8: 16 XT-PIC rtc
9: 0 XT-PIC acpi
10: 1630 XT-PIC eth1
11: 103147 XT-PIC libata
12: 9990 XT-PIC eth0
14: 5993 XT-PIC ide0
15: 145866 XT-PIC libata
NMI: 0
LOC: 0
ERR: 23672
MIS: 0
Regards,
Oskar Liljeblad (oskar@osk.mine.nu)
next prev parent reply other threads:[~2005-05-03 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 16:07 clock drift with two Promise Ultra133 TX2 (PDC 20269) cards Drew Winstel
2005-05-03 17:28 ` Oskar Liljeblad [this message]
2005-05-04 17:59 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2005-05-05 14:45 Drew Winstel
2005-05-03 18:29 Drew Winstel
2005-05-04 20:10 ` Oskar Liljeblad
2005-05-03 15:13 Drew Winstel
2005-05-03 16:02 ` Oskar Liljeblad
2005-05-03 14:18 Drew Winstel
2005-05-03 14:40 ` Oskar Liljeblad
2005-05-02 19:28 Oskar Liljeblad
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=20050503172845.GA12944@oskar \
--to=oskar@osk.mine.nu \
--cc=DWinstel@Miltope.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 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).