LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mikko Tiihonen <mikko.tiihonen@iki.fi>
To: Nicolas Mailhot <nicolas.mailhot@laposte.net>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [PATCH 1/5] RT kernel: force detect HPET from PCI space
Date: Sat, 31 Mar 2007 11:00:52 +0300 (EEST) [thread overview]
Message-ID: <Pine.OSF.4.64.0703311053330.412261@kosh.hut.fi> (raw)
In-Reply-To: <1175294288.32441.6.camel@rousalka.dyndns.org>
On Sat, 31 Mar 2007, Nicolas Mailhot wrote:
> Le samedi 31 mars 2007 à 01:09 +0300, Mikko Tiihonen a écrit :
>>> Anyone got the same thing for CK804? I had my hopes high, and then I saw
>>> the DECLARE_PCI_FIXUP_HEADER values [and the thread title was misleading]
>>
>> I have an A8N-E motherboard with AthlonX2 and the ACPI definitions are
>> missing the HPET (standard feature of Asus motherboards).
>>
>> I too got interested to get my motherboard working. Luckily I found this
>> http://lkml.org/lkml/2006/12/17/69
>
> Oh, is looks so close to my system
>
> 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
> Subsystem: Giga-byte Technology GA-K8N Ultra-9 Mainboard
> Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> 00: de 10 50 00 0f 00 a0 00 a3 00 01 06 00 00 80 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 11 0c
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 58 14 11 0c 00 f0 ff fe fa 3e ff 00 fa 3e ff 00
> ^^^^^^^^^^^
> Usual HPET base address
> 50: fa 3e ff 00 00 5a 62 02 00 00 00 01 00 00 ff ff
> 60: 01 10 00 00 01 14 00 00 01 18 00 00 00 00 f9 ff
> 70: 10 00 ff ff c1 00 00 00 00 00 04 19 18 d2 80 0d
> ^^
> c1 => HPET disabled (according to your reference)
>
> I don't have an HPET toggle in my bios
>
>> from which I generated the following patch:
>
> I'd love to test it, but what kernel baseline did you use?
> 2.6.21-rc5-mm2?
No, I could not get the original patches to apply to any new kernel. They did
apply to 2.6.20-mm2 with very minimal collisions.
I only applied patches 1/5 and 2/5 of the original series. But now that I look
into patch 3/5 it seems that it has useful irq allocation things.
Anyway, I think the best way would be to get 2.6.20-rt8 against which the
original patch series was made. Add all 5 patches from Venkatesh and then try
with my patch added. I'll try that myself later today.
-Mikko
next prev parent reply other threads:[~2007-03-31 8:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 22:09 [PATCH 1/5] RT kernel: force detect HPET from PCI space Mikko Tiihonen
2007-03-30 22:38 ` Nicolas Mailhot
2007-03-31 8:00 ` Mikko Tiihonen [this message]
2007-03-31 10:37 ` Krzysztof Halasa
2007-03-31 11:36 ` Nicolas Mailhot
2007-03-31 15:00 ` Mikko Tiihonen
-- strict thread matches above, loose matches on Subject: below --
2007-03-30 16:50 Nicolas Mailhot
2007-03-30 16:59 ` Venki Pallipadi
2007-03-30 17:22 ` Nicolas Mailhot
2007-02-23 1:06 Venkatesh Pallipadi
2007-03-30 9:46 ` Ingo Molnar
2007-03-30 13:36 ` Pallipadi, Venkatesh
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.OSF.4.64.0703311053330.412261@kosh.hut.fi \
--to=mikko.tiihonen@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.mailhot@laposte.net \
/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).