From: John Kinsella <rfjak@gofree.indigo.ie>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19 compile warning for AMD Athlon config
Date: Sun, 4 Aug 2002 21:56:23 +0100 [thread overview]
Message-ID: <20020804204827Z318230-685+23824@vger.kernel.org> (raw)
amd_adv_spec_cache_feature() tries to use have_cpuid_p(), which does not
exist in 2.4.x tree.
This seems to have been introduced in 2.4.19-rc1, I guess I should have noticed it before.
A case of 2.4 being too stable perhaps, as it works fine so I didn't check compile log :)
/home/compo/2.4/2.4.19/arch/i386/kernel/setup.c: In function `amd_adv_spec_cache_feature':
/home/compo/2.4/2.4.19/arch/i386/kernel/setup.c:751: warning: implicit declaration of func
tion `have_cpuid_p'
/home/compo/2.4/2.4.19/arch/i386/kernel/setup.c: At top level:
/home/compo/2.4/2.4.19/arch/i386/kernel/setup.c:2629: warning: `have_cpuid_p' was declared
implicitly `extern' and later `static'
/home/compo/2.4/2.4.19/arch/i386/kernel/setup.c:751: warning: previous declaration of `hav
e_cpuid_p'
$ grep -nr have_cpuid_p *h
arch/i386/kernel/setup.c:751: if(!have_cpuid_p())
arch/i386/kernel/setup.c:2628:static int __init have_cpuid_p(void)
arch/i386/kernel/setup.c:2708: return have_cpuid_p(); /* Check to see if CPUID now enabled? */
arch/i386/kernel/setup.c:2728: if ( !have_cpuid_p() && !id_and_try_enable_cpuid(c) ) {
arch/i386/kernel/setup.c:3164: if(!have_cpuid_p())
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_MCE=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
next reply other threads:[~2002-08-04 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 20:56 John Kinsella [this message]
2002-08-06 17:09 John Kinsella
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=20020804204827Z318230-685+23824@vger.kernel.org \
--to=rfjak@gofree.indigo.ie \
--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
all inboxes | Powered by JetHome®