From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Parag Warudkar <parag.lkml@gmail.com>
Cc: Andreas Herrmann <andreas.herrmann3@amd.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc8+ - first impressions
Date: Tue, 7 Oct 2008 21:07:53 -0400 [thread overview]
Message-ID: <20081008010753.GA20753@anvil.corenet.prv> (raw)
In-Reply-To: <f7848160810070507n1a75034dta6fb97880174d22a@mail.gmail.com>
On Tue, Oct 07, 2008 at 08:07:49AM -0400, Parag Warudkar wrote:
> On Tue, Oct 7, 2008 at 7:37 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > Hmm, that unfortunately does not work because I have SB4X0 revision 0x11
> > and the patch cuts off everything below 0x82. Is there anything that can
> > be done to enable HPET on early revisions?
> >
>
> Later BIOS revisions for the 6115 "enable Vista support" which
> actually means HPET is properly enabled in BIOS for Vista to work.
> (i.e. there won't be a need to force enable it with later BIOS versions.)
>
> Any reason you could not try the BIOS upgrade I pointed out earlier?
>
I just did not want to do that on the road.
I do not see any difference with regard to timer wiring or hpet behavior
(hpet is disabled in BIOS, hpet=force causes hang) with the latest
(F.12) BIOS.
--
Dmitry
next prev parent reply other threads:[~2008-10-08 1:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 18:36 Dmitry Torokhov
2008-10-05 18:59 ` Rafael J. Wysocki
2008-10-05 19:06 ` Dmitry Torokhov
2008-10-05 19:19 ` Rafael J. Wysocki
2008-10-05 19:27 ` Thomas Gleixner
2008-10-05 21:18 ` Dmitry Torokhov
2008-10-05 21:40 ` Parag Warudkar
2008-10-05 22:29 ` Rafael J. Wysocki
2008-10-06 6:23 ` Dmitry Torokhov
2008-10-06 9:59 ` [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes (Re: 2.6.27-rc8+ - first impressions) Rafael J. Wysocki
2008-10-06 14:54 ` Linus Torvalds
2008-10-06 15:00 ` Ingo Molnar
2008-10-06 17:17 ` Rafael J. Wysocki
2008-10-06 17:51 ` Maciej W. Rozycki
2008-10-06 17:54 ` Ingo Molnar
2008-10-06 20:59 ` Andi Kleen
2008-10-06 21:39 ` Maciej W. Rozycki
2008-10-06 22:11 ` [PATCH] x86: SB450: skip IRQ0 override if it is not routed to INT2 of IOAPIC Andreas Herrmann
2008-10-07 3:41 ` Ingo Molnar
2008-10-07 3:51 ` Dmitry Torokhov
2008-10-07 4:57 ` Ingo Molnar
2008-10-07 11:19 ` Dmitry Torokhov
2008-10-07 15:25 ` Maciej W. Rozycki
2008-10-07 20:31 ` Rafael J. Wysocki
2008-10-06 23:10 ` [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes (Re: 2.6.27-rc8+ - first impressions) Andi Kleen
2008-10-07 1:35 ` Maciej W. Rozycki
2008-10-07 4:42 ` Ingo Molnar
2008-10-07 5:38 ` Andi Kleen
2008-10-07 11:45 ` Matthew Garrett
2008-10-07 12:04 ` Ingo Molnar
2008-10-08 8:23 ` Peter Zijlstra
2008-10-06 17:15 ` Rafael J. Wysocki
2008-10-06 17:54 ` Maciej W. Rozycki
2008-10-05 19:10 ` 2.6.27-rc8+ - first impressions Arjan van de Ven
2008-10-06 6:28 ` Dmitry Torokhov
2008-10-06 19:53 ` Andreas Herrmann
2008-10-07 3:42 ` Dmitry Torokhov
2008-10-07 9:10 ` Andreas Herrmann
2008-10-07 11:37 ` Dmitry Torokhov
2008-10-07 12:07 ` Parag Warudkar
2008-10-08 1:07 ` Dmitry Torokhov [this message]
2008-10-07 13:19 ` Andreas Herrmann
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=20081008010753.GA20753@anvil.corenet.prv \
--to=dmitry.torokhov@gmail.com \
--cc=andreas.herrmann3@amd.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=parag.lkml@gmail.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome