From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc4-mm1 HPET compile problems on AMD64
Date: Mon, 11 Oct 2004 12:54:21 -0700 [thread overview]
Message-ID: <20041011125421.106eff07.akpm@osdl.org> (raw)
In-Reply-To: <1097509362.12861.334.camel@dyn318077bld.beaverton.ibm.com>
Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> I get following error while linking kernel on 2.6.9-rc4-mm1.
> x86_64/kernel/time.c seems to have a dependency on char/hpet.c
> driver. Its forcing me to use CONFIG_HPET.
>
> LD .tmp_vmlinux1
> arch/x86_64/kernel/built-in.o(.init.text+0x2071): In function
> `late_hpet_init':
> arch/x86_64/kernel/entry.S:259: undefined reference to `hpet_alloc'
> make: *** [.tmp_vmlinux1] Error 1
>
> ...
>
> [hpet_alloc_fix.patch text/plain (638 bytes)]
> --- linux.org/arch/x86_64/kernel/time.c 2004-10-11 09:17:15.613107488 -0700
> +++ linux/arch/x86_64/kernel/time.c 2004-10-11 09:14:05.983935504 -0700
> @@ -727,6 +727,7 @@ static unsigned int __init pit_calibrate
> return (end - start) / 50;
> }
>
> +#ifdef CONFIG_HPET
> static __init int late_hpet_init(void)
> {
> struct hpet_data hd;
> @@ -773,6 +774,7 @@ static __init int late_hpet_init(void)
> return 0;
> }
> fs_initcall(late_hpet_init);
> +#endif
I assume you have CONFIG_HPET=n and CONFIG_HPET_TIMER=n?
Andi, what's going on here? Should the hpet functions in
arch/x86_64/kernel/time.c be inside CONFIG_HPET_TIMER?
next prev parent reply other threads:[~2004-10-11 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 15:42 Badari Pulavarty
2004-10-11 19:54 ` Andrew Morton [this message]
2004-10-11 20:26 ` Badari Pulavarty
2004-10-11 21:06 ` Andrew Morton
2004-10-11 21:25 ` Andi Kleen
2004-10-11 21:42 ` Badari Pulavarty
2004-10-11 22:05 ` Andi Kleen
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=20041011125421.106eff07.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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