From: "Andrey Panin" <pazke@donpac.ru>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: "Raj" <inguva@gmail.com>, "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Build problems with APM/Subarch type
Date: Thu, 14 Oct 2004 13:15:58 +0400 (MSD) [thread overview]
Message-ID: <21579.80.80.111.240.1097745358.squirrel@80.80.111.240> (raw)
In-Reply-To: <416CBC9C.8010905@osdl.org>
> Raj wrote:
>>>Using an editor or make *config? which *config?
>>>
>>
>> xconfig
>>
>>
>>>>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?
>>>
>>>I agree that it should be fixed, one way or another.
>>
>>
>> i am not aware much about the apm dependencies. maintainers might answer
>> this more correctly.
>
> True. I should have copied Andrey on it earlier.
>
> Andrey, any thoughts about how to keep VISWS from building APM
> support? use Kconfig? or does VISWS support APM?
IMHO Kconfig is the best choise. VISWS has no PC compatible BIOS at all,
it uses ARC compilant firmware for startup and configuration. Even though
this firmware does limited BIOS emulation for running ROMs on PCI cards, i
dont think it has working APM BIOS implementation.
next prev parent reply other threads:[~2004-10-14 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 11:38 Raj
2004-10-13 5:11 ` Randy.Dunlap
2004-10-13 5:21 ` Ricky lloyd
2004-10-13 5:21 ` Randy.Dunlap
2004-10-13 5:27 ` Raj
2004-10-13 5:26 ` Randy.Dunlap
2004-10-14 9:15 ` Andrey Panin [this message]
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=21579.80.80.111.240.1097745358.squirrel@80.80.111.240 \
--to=pazke@donpac.ru \
--cc=inguva@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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®