From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Ricky lloyd <ricky.lloyd@gmail.com>
Cc: Raj <inguva@gmail.com>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Build problems with APM/Subarch type
Date: Tue, 12 Oct 2004 22:21:34 -0700 [thread overview]
Message-ID: <416CBB5E.7050803@osdl.org> (raw)
In-Reply-To: <1a50bd370410122221ebb3796@mail.gmail.com>
Ricky lloyd wrote:
>>>Did all the configuration properly, except that i fumbled on the keyboard and
>>>the option 'Subarchitecture Type' somehow got set to
>>>'(SGI 320/540 Visual Workstation)'.
>>
>>Using an editor or make *config? which *config?
>
>
> make menuconfig.
>
>
>>>The build failed with an error 'Undefined reference to machine_real_restart'
>>
>>Yep, I see that also.
>>
>>
>>>It seems that , unless Subarch is PC-Compatible ( CONFIG_PC ) ,
>>>CONFIG_X86_BIOS_REBOOT will not be set and thusly, reboot.c would not be
>>>compiled.
>>>
>>>( yeah, i know messing around with configs is suicidal, but.... )
>>>
>>>Can this be fixed ?? At the very least, hide APM options #if !(CONFIG_PC) ??
>>
>>Do you/we/maintainer know that APM is not applicable to all of the
>>other PC sub-arches?
>>
>
> afaics, i found 'apm.c' only in arch/i386/kernel and arch/arm/kernel.
> does that really
> confirm that apm would not be applicable for other archs ??
The question is actually about other PC sub-arches, not other (Big)
arch-es.
>
>>I agree that it should be fixed, one way or another.
>>--
--
~Randy
next prev parent reply other threads:[~2004-10-13 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 11:38 Build problems with APM/Subarch type Raj
2004-10-13 5:11 ` Randy.Dunlap
2004-10-13 5:21 ` Ricky lloyd
2004-10-13 5:21 ` Randy.Dunlap [this message]
2004-10-13 5:27 ` Raj
2004-10-13 5:26 ` Randy.Dunlap
2004-10-14 9:15 ` Andrey Panin
2004-10-14 22:34 ` [PATCH] VISWS: disable APM Randy.Dunlap
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=416CBB5E.7050803@osdl.org \
--to=rddunlap@osdl.org \
--cc=inguva@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ricky.lloyd@gmail.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 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.