All of lore.kernel.org
 help / color / mirror / Atom feed
From: gaumer <gaumer@egaumer.com>
To: linux-kernel@vger.kernel.org
Subject: APIC / ACPI Build issue
Date: Thu, 03 Jun 2004 10:03:43 -0400	[thread overview]
Message-ID: <1086271422.16648.45.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

Excuse my ignorance, I'm new to kernel development.

I've just patched my source with rc2-mm2 and there seems to be a build
issue concerning APIC / ACPI support.

The error:

  LD      init/built-in.o
  LD      .tmp_vmlinux1
arch/i386/kernel/built-in.o(.text+0xdaca): In function `acpi_register_gsi':
: undefined reference to `mp_register_gsi'
make[1]: *** [.tmp_vmlinux1] Error 1

It seems that in arch/i386/kernel/acpi/boot.c
at line 462 we have:

#ifdef CONFIG_X86_IO_APIC
        if (acpi_irq_model == ACPI_IRQ_MODEL_IOAPIC) {
                mp_register_gsi(gsi, edge_level, active_high_low);
        }
#endif

...yet mp_register_gsi is only defined if:

(line 879 of arch/i386/kernel/mpparse.c)
#if defined(CONFIG_X86_IO_APIC) && defined(CONFIG_ACPI_INTERPRETER)

So if the .config looks like:

# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
                                                                                                                                                                                   
#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y
                                                                                                                                                                                   
#
# CPU Frequency scaling

With the power management stuff turned off and SMP support enabled the
result is this build error. 

Does CONFIG_ACPI_INTERPRETER have to be defined? If so, then can we
require the definition in arch/i386/kernel/acpi/boot.c as well? This is
not an area I'm familiar with.

The last build I did was on 2.6.6-mm5 and things were okay there (same
config).



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-06-03 14:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1086271422.16648.45.camel@localhost \
    --to=gaumer@egaumer.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.