[CC'd LKML for broader testing]
Hi,
On Sat, Aug 04, 2007 at 12:58:20PM -0400, David Edwards wrote:
> Andreas Mohr wrote:
> >> Same for "hpet-force-enable-on-vt8235-37-chipsets.patch" (I use this
> >> one on my Asrock P4VT8+ motherboard (VT8237 based) with no pb).
> >
> > What!?!?!?
> > Why did nobody tell me that VT8235 *does* actually have a HPET
> > implementation? ;)
> > I've been investigating this during a couple evenings some months ago,
> > with apparently negative result for my VT8235 (blank I/O area at the
> > place where VT8237 has its HPET, and I wasn't able to activate anything),
> > which I then reported on LKML.
> > And now you report that one found that it's actually possible. Yay!!
>
> Erm... Don't get too excited. The HPET patch does not enable the HPET on
> my VT8235 (EPIA ME-6000 mini-itx board), so it may not be universally
> functional.
>
> > I'm going to test this patch on my EPOX 8K5A2+ (VT8235, i.e. PCI ID 0x3177).
>
> Cool. Let me know if it works for you. :)
Err... nope. :((
I've added the full 2.6.23-rc1-hrt1 patchset
(http://www.tglx.de/projects/hrtimers/2.6.23-rc1/patch-2.6.23-rc1-hrt1.patch),
and I do get the "Failed to force enable HPET",
so I know it's running that function, however it fails
since the 0x80 bit is NOT set after the force-enable
(which sadly happens to match my experience during my much earlier efforts
to try to get HPET to work on this board).
So, *please* (I'd *love* to get this working somehow):
whoever has a VT8235 and is listening here,
- give a "lspci -nn" (two 'n'!), to figure out details of chipset revision etc.
- give a "lspci -d 1106:3177 -xxx", to try to figure out whether there happen
to be additional magical "enable" bits to map in those HPET I/O areas which
some BIOS versions configure and some don't (that's my fragile theory
at least)
- oh, and don't forget to tell whether HPET works or not
For my system (again, it's EPOX 8K5A2+ with VT8235):
root@andi:/usr/src/linux-2.6.23-rc1-hrt1# lspci -nn
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8366/A/7 [Apollo
KT266/A/333] [1106:3099]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8366/A/7 [Apollo
KT266/A/333 AGP] [1106:b099]
00:09.0 FireWire (IEEE 1394) [0c00]: Duet Technologies Unknown device
[1306:3044] (rev 46)
00:0a.0 Multimedia audio controller [0401]: Aureal Semiconductor Vortex
2 [12eb:0002] (rev fe)
00:0c.0 Ethernet controller [0200]: Intel Corporation 82557/8/9
[Ethernet Pro 100] [8086:1229] (rev 08)
00:0d.0 Multimedia audio controller [0401]: Aztech System Ltd 3328 Audio
[122d:50dc] (rev 10)
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller [1106:3038] (rev 80)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller [1106:3038] (rev 80)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller [1106:3038] (rev 80)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0
[1106:3104] (rev 82)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge
[1106:3177]
00:11.1 IDE interface [0101]: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev
06)
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102
[Rhine-II] [1106:3065] (rev 74)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon
RV250 If [Radeon 9000] [1002:4966] (rev 01)
01:00.1 Display controller [0380]: ATI Technologies Inc Radeon RV250
[Radeon 9000] (Secondary) [1002:496e] (rev 01)
root@andi:/usr/src/linux-2.6.23-rc1-hrt1# lspci -d 1106:3177 -xxx
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00: 06 11 77 31 87 00 10 02 00 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 06 11 77 31
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
40: 44 00 f8 0b 00 00 00 00 0c 20 00 00 04 00 0a 08
50: 81 1d 09 00 00 20 22 20 43 80 00 00 00 00 f0 40
60: 00 00 00 00 00 00 02 04 00 00 00 00 00 00 00 00
70: 06 11 77 31 00 00 00 00 00 00 00 00 20 00 00 00
80: 20 84 59 00 ba 10 00 00 01 40 00 00 da 10 00 00
90: 00 4a 00 88 a0 40 03 00 00 b7 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 50 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 04 08 02 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00
Thanks a lot,
Andreas Mohr
> Hi,
Hi,
> So, *please* (I'd *love* to get this working somehow):
> whoever has a VT8235 and is listening here,
> - give a "lspci -nn" (two 'n'!), to figure out details of chipset revision etc.
> - give a "lspci -d 1106:3177 -xxx", to try to figure out whether there happen
> to be additional magical "enable" bits to map in those HPET I/O areas which
> some BIOS versions configure and some don't (that's my fragile theory
> at least)
> - oh, and don't forget to tell whether HPET works or not
VT8235 does *NOT* have a HPET(*). Only part which has HPET is VT8237. It is device
00:17.0 too, but only 1106:3227 has HPET enable and memory base registers.
VT8235 one and only feature which doesn't have driver yet seems to be hardware
watchdog.
>
> Thanks a lot,
>
> Andreas Mohr
(*) Datasheet revision 2.03 March 16, 2005
Regards
Rafał
----------------------------------------------------------------------
Jak najszybciej dostac sie na wymarzona plaze?
Znajdz trase ekspresowa
>>>http://link.interia.pl/f1b0c
On Mon, 06 Aug 2007 23:39:30 +0200 Rafał Bilski (RB) wrote:
RB> VT8235 does *NOT* have a HPET(*). Only part which has HPET is VT8237. It
RB> is device 00:17.0 too, but only 1106:3227 has HPET enable and memory
RB> base registers. VT8235 one and only feature which doesn't have driver
RB> yet seems to be hardware watchdog.
RB> (*) Datasheet revision 2.03 March 16, 2005
We have an Asrock K7VT4A+ board with VT8235 southbridge in our lab and it
does have an HPET. Just because the datasheet does not document HPET does
not mean it is not implemented.
My guess is that newer revisions of VT8235 have HPET whereas older revisions
do not. I'll get an lspci dump from our box tomorrow.
Cheers,
- Udo
On Mon, 6 Aug 2007, Andreas Mohr wrote:
> whoever has a VT8235 and is listening here,
> - give a "lspci -nn" (two 'n'!), to figure out details of chipset revision etc.
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8623 [Apollo CLE266] [1106:3123]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] [1106:b091]
00:0d.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. IEEE 1394 Host Controller [1106:3044] (rev 80)
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 82)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 74)
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics [1106:3122] (rev 03)
> - give a "lspci -d 1106:3177 -xxx", to try to figure out whether there happen
> to be additional magical "enable" bits to map in those HPET I/O areas which
> some BIOS versions configure and some don't (that's my fragile theory
> at least)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00: 06 11 77 31 87 00 10 02 00 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 06 11 01 aa
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
40: 45 00 f0 00 00 00 00 00 0c 20 00 00 44 00 0a 08
50: 81 1d 09 00 00 b0 a5 b0 03 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00
70: 06 11 01 aa 00 00 00 00 00 00 00 00 20 00 00 00
80: 20 84 59 00 b2 30 00 00 01 04 00 00 00 18 00 00
90: 00 07 10 88 a0 c0 00 00 00 7f 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 05 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 14 88 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 05 00 00 00 00 00 00 00 00 00
> - oh, and don't forget to tell whether HPET works or not
Nope.
>
> For my system (again, it's EPOX 8K5A2+ with VT8235):
>
> root@andi:/usr/src/linux-2.6.23-rc1-hrt1# lspci -nn
> 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8366/A/7 [Apollo
> KT266/A/333] [1106:3099]
> 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8366/A/7 [Apollo
> KT266/A/333 AGP] [1106:b099]
> 00:09.0 FireWire (IEEE 1394) [0c00]: Duet Technologies Unknown device
> [1306:3044] (rev 46)
> 00:0a.0 Multimedia audio controller [0401]: Aureal Semiconductor Vortex
> 2 [12eb:0002] (rev fe)
> 00:0c.0 Ethernet controller [0200]: Intel Corporation 82557/8/9
> [Ethernet Pro 100] [8086:1229] (rev 08)
> 00:0d.0 Multimedia audio controller [0401]: Aztech System Ltd 3328 Audio
> [122d:50dc] (rev 10)
> 00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1 Controller [1106:3038] (rev 80)
> 00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1 Controller [1106:3038] (rev 80)
> 00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1 Controller [1106:3038] (rev 80)
> 00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0
> [1106:3104] (rev 82)
> 00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge
> [1106:3177]
> 00:11.1 IDE interface [0101]: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev
> 06)
> 00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc.
> VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
> 00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102
> [Rhine-II] [1106:3065] (rev 74)
> 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon
> RV250 If [Radeon 9000] [1002:4966] (rev 01)
> 01:00.1 Display controller [0380]: ATI Technologies Inc Radeon RV250
> [Radeon 9000] (Secondary) [1002:496e] (rev 01)
>
> root@andi:/usr/src/linux-2.6.23-rc1-hrt1# lspci -d 1106:3177 -xxx
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
> 00: 06 11 77 31 87 00 10 02 00 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 06 11 77 31
> 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
> 40: 44 00 f8 0b 00 00 00 00 0c 20 00 00 04 00 0a 08
> 50: 81 1d 09 00 00 20 22 20 43 80 00 00 00 00 f0 40
> 60: 00 00 00 00 00 00 02 04 00 00 00 00 00 00 00 00
> 70: 06 11 77 31 00 00 00 00 00 00 00 00 20 00 00 00
> 80: 20 84 59 00 ba 10 00 00 01 40 00 00 da 10 00 00
> 90: 00 4a 00 88 a0 40 03 00 00 b7 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 01 50 01 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 04 08 02 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00
>
> Thanks a lot,
>
> Andreas Mohr
>
>
> RB> VT8235 does *NOT* have a HPET(*). Only part which has HPET is VT8237. It
> RB> is device 00:17.0 too, but only 1106:3227 has HPET enable and memory
> RB> base registers. VT8235 one and only feature which doesn't have driver
> RB> yet seems to be hardware watchdog.
> RB> (*) Datasheet revision 2.03 March 16, 2005
>
> We have an Asrock K7VT4A+ board with VT8235 southbridge in our lab and it
> does have an HPET. Just because the datasheet does not document HPET does
> not mean it is not implemented.
>
> My guess is that newer revisions of VT8235 have HPET whereas older revisions
> do not. I'll get an lspci dump from our box tomorrow.
Indeed datasheet lies. I have VIA EPIA M10000 Rev. B motherboard.
% uname -r
2.6.23-rc1-hrt1
% dmesg | grep -i hpet
Force enabled HPET at base address 0xfed00000
hpet clockevent registered
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 32-bit timers, 14318180 Hz
Time: hpet clocksource has been installed.
% cat /proc/timer_list
[...]
Tick Device: mode: 1
Clock Event Device: hpet
max_delta_ns: 2147483647
min_delta_ns: 3352
mult: 61496110
shift: 32
mode: 3
next_event: 672664000000 nsecs
set_next_event: hpet_legacy_next_event
set_mode: hpet_legacy_set_mode
event_handler: hrtimer_interrupt
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc. Unknown device aa01
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00: 06 11 77 31 87 00 10 02 00 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 06 11 01 aa
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
40: 45 00 f0 00 00 00 00 00 0c 20 00 00 44 00 0a 08
50: 81 1d 09 00 00 b0 a5 30 03 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 04 80 00 d0 fe 00 00 00 00
70: 06 11 01 aa 00 00 00 00 00 00 00 00 20 00 00 00
80: 20 84 59 00 b2 30 00 00 01 04 00 00 00 18 00 00
90: 00 1f 50 88 b0 c0 00 00 00 97 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 05 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 14 88 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 16 00 00 00 00 00 01 00 00 00
> Cheers,
>
> - Udo
Regards
Rafał
----------------------------------------------------------------------
Plaza plazy nierowna
Kliknij
>>>http://link.interia.pl/f1af7
Hi,
On Tue, Aug 07, 2007 at 10:36:59AM +0200, Rafa?? Bilski wrote:
> >RB> VT8235 does *NOT* have a HPET(*). Only part which has HPET is VT8237.
> >It
> >RB> is device 00:17.0 too, but only 1106:3227 has HPET enable and memory
> >RB> base registers. VT8235 one and only feature which doesn't have driver
> >RB> yet seems to be hardware watchdog.
> >RB> (*) Datasheet revision 2.03 March 16, 2005
> >
> >We have an Asrock K7VT4A+ board with VT8235 southbridge in our lab and it
> >does have an HPET. Just because the datasheet does not document HPET does
> >not mean it is not implemented.
> >
> >My guess is that newer revisions of VT8235 have HPET whereas older
> >revisions
> >do not. I'll get an lspci dump from our box tomorrow.
> Indeed datasheet lies. I have VIA EPIA M10000 Rev. B motherboard.
Many datasheets are incorrect and don't follow realities of chipset
design evolution. Which is why I started this quest in the first place ;)
> % dmesg | grep -i hpet
> Force enabled HPET at base address 0xfed00000
> hpet clockevent registered
> hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
> hpet0: 3 32-bit timers, 14318180 Hz
> Time: hpet clocksource has been installed.
Lucky bastard! :)
> 00: 06 11 77 31 87 00 10 02 00 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 06 11 01 aa
> 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
> 40: 45 00 f0 00 00 00 00 00 0c 20 00 00 44 00 0a 08
> 50: 81 1d 09 00 00 b0 a5 30 03 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 04 80 00 d0 fe 00 00 00 00
> 70: 06 11 01 aa 00 00 00 00 00 00 00 00 20 00 00 00
> 80: 20 84 59 00 b2 30 00 00 01 04 00 00 00 18 00 00
> 90: 00 1f 50 88 b0 c0 00 00 00 97 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 01 05 01 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 14 88 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 16 00 00 00 00 00 01 00 00 00
Thanks a lot!
I'll do a diff on this versus the "non-working"
dumps and have a peek at the VT8235/VT8237 datasheet
to see whether there can something be done about it.
I still don't entirely buy the "different chipset revision"
theory, hopefully I'm correct and it's just another bit to
tweak (but hopefully it's not a "write-only" bit that needs
tweaking...).
BTW, is there any obvious chipset ecosystem difference
in your system? Are any other important PCI IDs/revs
different from mine?
Further working/non-working dumps greatly appreciated!
Andreas Mohr
> Hi,
>
> BTW, is there any obvious chipset ecosystem difference
> in your system? Are any other important PCI IDs/revs
> different from mine?
I don't see any differences.
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8623 [Apollo CLE266] [1106:3123]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] [1106:b091]
00:0d.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. IEEE 1394 Host Controller [1106:3044] (rev 80)
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 82)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 74)
00:14.0 Multimedia controller [0480]: Philips Semiconductors SAA7134/SAA7135HL Video Broadcast Decoder [1131:7134] (rev 01)
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics [1106:3122] (rev 03)
> Andreas Mohr
Regards
Rafał
----------------------------------------------------------------------
Plaza plazy nierowna
Kliknij
>>>http://link.interia.pl/f1af7
On Mon, 6 Aug 2007 23:57:52 +0200 Udo A. Steinberg (UAS) wrote:
UAS> My guess is that newer revisions of VT8235 have HPET whereas older
UAS> revisions do not. I'll get an lspci dump from our box tomorrow.
Here is the lspci dump from our K7VT4A+ board, where HPET works.
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]
00:11.0 0601: 1106:3177
00: 06 11 77 31 87 00 10 02 00 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 49 18 77 31
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
40: 44 00 78 00 00 00 00 00 0c 01 00 00 44 00 08 08
50: 81 1d 09 00 00 00 00 00 43 00 ff 01 00 00 04 08
60: 00 00 00 00 10 00 02 04 00 00 00 00 00 00 00 00
70: 49 18 77 31 00 00 00 00 00 00 00 00 10 00 00 00
80: 20 84 59 00 9a 10 00 00 01 08 00 00 04 18 00 00
90: 00 77 d8 00 b4 c5 08 00 10 92 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 04 08 c0 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 16 00 00 00 00 00 01 00 00 00
Cheers,
- Udo
Hi,
On Tue, Aug 07, 2007 at 01:11:31PM +0200, Udo A. Steinberg wrote:
> On Mon, 6 Aug 2007 23:57:52 +0200 Udo A. Steinberg (UAS) wrote:
>
> UAS> My guess is that newer revisions of VT8235 have HPET whereas older
> UAS> revisions do not. I'll get an lspci dump from our box tomorrow.
>
> Here is the lspci dump from our K7VT4A+ board, where HPET works.
Thanks for all your reports!
Unfortunately I was NOT successful in trying to get it to work here.
The EPOX 8K5A2+ probably(?) is a KT333 chipset (or KT333A?),
and thus possibly the first one to sport a HPET is KT400 (plus its
correspondingly modern VT8235 companion chip) or even more modern chipsets.
Here is my hexdump analysis, and unfortunately I was unable to
get any bit to enable the HPET range.
I didn't want to get too brave, since this is obviously also
rather dangerous... (I adhered to the specs rather closely without
trying too many exciting things)
xAM 00: 06 11 77 31 87 00 10 02 00 00 01 06 00 00 80 00
xDE 00: 06 11 77 31 87 00 10 02 00 00 01 06 00 00 80 00
*RB 00: 06 11 77 31 87 00 10 02 00 00 01 06 00 00 80 00
*US 00: 06 11 77 31 87 00 10 02 00 00 01 06 00 00 80 00
== EQUAL ==
xAM 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
xDE 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*RB 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*US 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
== EQUAL ==
xAM 20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 77 31
xDE 20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
*RB 20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
*US 20: 00 00 00 00 00 00 00 00 00 00 00 00 49 18 77 31
== PCI ID differences ==
xAM 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
xDE 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
*RB 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
*US 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
== EQUAL ==
xAM 40: 44 00 f8 0b 00 00 00 00 0c 20 00 00 04 00 0a 08
xDE 40: 45 00 f0 00 00 00 00 00 0c 20 00 00 44 00 0a 08
*RB 40: 45 00 f0 00 00 00 00 00 0c 20 00 00 44 00 0a 08
*US 40: 44 00 78 00 00 00 00 00 0c 01 00 00 44 00 08 08
== nothing suspicious ==
xAM 50: 81 1d 09 00 00 20 22 20 43 80 00 00 00 00 f0 40
xDE 50: 81 1d 09 00 00 b0 a5 b0 03 00 00 00 00 00 00 00
*RB 50: 81 1d 09 00 00 b0 a5 30 03 00 00 00 00 00 00 00
*US 50: 81 1d 09 00 00 00 00 00 43 00 ff 01 00 00 04 08
== nothing suspicious ==
(except for *maybe* 0x57, which is IRQ routing only)
xAM 60: 00 00 00 00 00 00 02 04 00 00 00 00 00 00 00 00
xDE 60: 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00
*RB 60: 00 00 00 00 00 00 00 04 80 00 d0 fe 00 00 00 00
*US 60: 00 00 00 00 10 00 02 04 00 00 00 00 00 00 00 00
== nothing suspicious ==
xAM 70: 06 11 77 31 00 00 00 00 00 00 00 00 20 00 00 00
xDE 70: 06 11 01 aa 00 00 00 00 00 00 00 00 20 00 00 00
*RB 70: 06 11 01 aa 00 00 00 00 00 00 00 00 20 00 00 00
*US 70: 49 18 77 31 00 00 00 00 00 00 00 00 10 00 00 00
== nothing suspicious ==
xAM 80: 20 84 59 00 ba 10 00 00 01 40 00 00 da 10 00 00
xDE 80: 20 84 59 00 b2 30 00 00 01 04 00 00 00 18 00 00
*RB 80: 20 84 59 00 b2 30 00 00 01 04 00 00 00 18 00 00
*US 80: 20 84 59 00 9a 10 00 00 01 08 00 00 04 18 00 00
== nothing suspicious ==
xAM 90: 00 4a 00 88 a0 40 03 00 00 b7 00 00 00 00 00 00
xDE 90: 00 07 10 88 a0 c0 00 00 00 7f 00 00 00 00 00 00
*RB 90: 00 1f 50 88 b0 c0 00 00 00 97 00 00 00 00 00 00
*US 90: 00 77 d8 00 b4 c5 08 00 10 92 00 00 00 00 00 00
==
0x91 bit 4 is interesting, but writing e.g. 1f still keeps 4a there for me
0x92 bit 6 is interesting, but...
0x94 bit 4 is interesting. can be changed, but HPET still cannot be enabled
0x99 bit 6 is interesting, but changing doesn't work
xAM a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
xDE a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*RB a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*US a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
== EQUAL ==
xAM b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
xDE b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*RB b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*US b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
== EQUAL ==
xAM c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
xDE c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
*RB c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
*US c0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
== EQUAL ==
xAM d0: 01 50 01 00 00 00 00 00 00 00 00 00 00 00 00 00
xDE d0: 01 05 01 00 00 00 00 00 00 00 00 00 00 00 00 00
*RB d0: 01 05 01 00 00 00 00 00 00 00 00 00 00 00 00 00
*US d0: 01 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00
== nothing suspicious ==
xAM e0: 00 00 00 00 04 08 02 00 00 00 00 00 00 00 00 00
xDE e0: 00 00 00 00 14 88 00 00 00 00 00 00 00 00 00 00
*RB e0: 00 00 00 00 14 88 00 00 00 00 00 00 00 00 00 00
*US e0: 00 00 00 00 04 08 c0 00 00 00 00 00 00 00 00 00
== nothing suspicious ==
xAM f0: 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00
xDE f0: 00 00 00 00 00 00 05 00 00 00 00 00 00 00 00 00
*RB f0: 00 00 00 00 00 00 16 00 00 00 00 00 01 00 00 00
*US f0: 00 00 00 00 00 00 16 00 00 00 00 00 01 00 00 00
== hmm, 0xf6 bit 4/1 or 0xfc bit 0? ==
0xf6 is not modifiable, but 0xfc is, but HPET still cannot be enabled
Oh, my i815E P3 notebook (== ICH2, 8086:244c) does NOT allow me
to enable HPET either, the corresponding bit (on 0xD2, IIRC)
does not stick (since ICH3 is said to be the first chipset to enjoy
force-enable support, and I wanted to verify this).
About SiS support... SiS 964 is said to contain HPET support,
so possibly 963, 962, ... secretly have it, too?
Some of those might need some force-enabling as well...
I don't have any such machines, though, only a rotten SiS 735 board ;)
(the well-known K7S5A).
Andreas Mohr