From: aris@cathedrallabs.org (Aristeu Sergio Rozanski Filho)
To: Robert Picco <Robert.Picco@hp.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm3
Date: Mon, 17 May 2004 12:51:37 -0300 [thread overview]
Message-ID: <20040517155136.GA25157@cathedrallabs.org> (raw)
In-Reply-To: <40A8D4D9.2020703@hp.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> >>+hpet-driver.patch
> >>
> >>HPET clock driver (needs work)
> >>
> >>
> >this doesn't compiles if ACPI isn't present. patch attached.
> >
> >
> >
> So you have HPET hardware which can be discovered without ACPI? How is
nope, I don't have any hw with HPET.
> the HPET detected? Are you just using the HPET addresses documented for
> Southbridge?
then this should be done instead:
- --- 2.6-mm-clean/drivers/char/Kconfig 2004-05-17 09:38:03.000000000 -0300
+++ 2.6-mm/drivers/char/Kconfig 2004-05-17 12:52:16.000000000 -0300
@@ -940,6 +940,7 @@ config RAW_DRIVER
config HPET
bool "HPET - High Precision Event Timer"
default n
+ depends on ACPI
help
If you say Y here, you will have a device named "/dev/hpet/XX" for
each timer supported by the HPET. The timers are
- --
Aristeu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAqN+IRRJOudsVYbMRAgeuAKCCK5zZHhRDoV2ZsdXfhewo7aKKBwCgiO0u
btq6DvF9SkZUpbAD3d9gg14=
=AxUi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-05-17 15:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 9:55 2.6.6-mm3 Andrew Morton
2004-05-16 10:35 ` 2.6.6-mm3 Prakash K. Cheemplavam
2004-05-16 11:00 ` 2.6.6-mm3 Gene Heskett
2004-05-16 16:29 ` 2.6.6-mm3 Andrew Morton
2004-05-16 18:38 ` 2.6.6-mm3: USB console.c doesn't compile Adrian Bunk
2004-05-17 16:32 ` Greg KH
2004-05-16 20:15 ` [patch] 2.6.6-mm3: more PC9800 removal Adrian Bunk
2004-05-16 20:35 ` [patch] 2.6.6-mm3: remove PC9800 from should-fix Adrian Bunk
2004-05-17 11:52 ` 2.6.6-mm3 Eric W. Biederman
2004-05-17 12:57 ` 2.6.6-mm3 Aristeu Sergio Rozanski Filho
2004-05-17 15:06 ` 2.6.6-mm3 Robert Picco
2004-05-17 15:51 ` Aristeu Sergio Rozanski Filho [this message]
2004-05-17 13:09 ` Scroll wheel on PS/2 Logitech MouseMan Wheel no longer works (was Re: 2.6.6-mm3) Sean Neakums
2004-05-17 18:10 ` Dmitry Torokhov
[not found] ` <6u4qqejiny.fsf@zork.zork.net>
[not found] ` <200405191256.32335.dtor_core@ameritech.net>
2004-05-20 7:49 ` Sean Neakums
2004-05-26 3:40 ` Dmitry Torokhov
2004-06-06 17:49 ` Vojtech Pavlik
2004-05-17 16:14 ` 2.6.6-mm3 Tom Rini
2004-05-17 16:30 ` 2.6.6-mm3 Robert Picco
2004-05-17 16:38 ` 2.6.6-mm3 Tom Rini
2004-05-17 17:56 ` 2.6.6-mm3 Tom Rini
2004-05-18 13:45 ` [Kgdb-bugreport] 2.6.6-mm3 Amit S. Kale
2004-05-17 17:20 ` 2.6.6-mm3 Chris Wright
2004-05-17 17:42 ` [PATCH][PPC32] Update Motorola LoPEC and Sandpoint defconfigs Tom Rini
2004-05-17 17:54 ` [PATCH][PPC32] Remove 'mem_pieces_append' Tom Rini
2004-05-17 18:06 ` [PATCH][PPC32] Some fixes for 'make O=...' Tom Rini
2004-05-18 2:08 ` 2.6.6-mm3: i810 agpgart module can't be initialized Clemens Schwaighofer
-- strict thread matches above, loose matches on Subject: below --
2004-05-16 17:01 2.6.6-mm3 Jan Killius
2004-05-17 14:43 ` 2.6.6-mm3 Robert Picco
2004-05-17 18:39 ` 2.6.6-mm3 Jan Killius
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=20040517155136.GA25157@cathedrallabs.org \
--to=aris@cathedrallabs.org \
--cc=Robert.Picco@hp.com \
--cc=akpm@osdl.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