From: Jerome Glisse <j.glisse@gmail.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linuxppc64-dev@ozlabs.org
Subject: Re: Classic PPC specific ASM (CONFIG_6XX)
Date: Mon, 10 Jan 2005 19:14:28 +0100 [thread overview]
Message-ID: <4240b9160501101014317b8d85@mail.gmail.com> (raw)
In-Reply-To: <20050110145219.GB2226@smtp.west.cox.net>
> Signed-off-by: Tom Rini <trini@kernel.crashing.org>
>
> --- 1.40/arch/ppc/boot/simple/Makefile 2005-01-03 16:49:19 -07:00
> +++ edited/arch/ppc/boot/simple/Makefile 2005-01-10 07:51:34 -07:00
> @@ -112,11 +112,15 @@
> end-$(pcore) := pcore
> cacheflag-$(pcore) := -include $(clear_L2_L3)
>
> +# PPC_PREP can be set to y on a PPC970 configuration, which isn't a real
> +# machine.
> +ifeq ($(CONFIG_6xx),y)
> zimage-$(CONFIG_PPC_PREP) := zImage-PPLUS
> zimageinitrd-$(CONFIG_PPC_PREP) := zImage.initrd-PPLUS
> extra.o-$(CONFIG_PPC_PREP) := prepmap.o
> misc-$(CONFIG_PPC_PREP) += misc-prep.o mpc10x_memory.o
> end-$(CONFIG_PPC_PREP) := prep
> +endif
>
> end-$(CONFIG_SANDPOINT) := sandpoint
> cacheflag-$(CONFIG_SANDPOINT) := -include $(clear_L2_L3)
>
This do not compile with this patch maybe need also to define
CONFIG_6xx if PPC970 is selected as processor ?
The errors are:
undefined reference for cols, lines, vidmems, scroll, orig_x, orig_y
in functions puts, ClearVideoMemory, putc
Jerome Glisse
next prev parent reply other threads:[~2005-01-10 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 15:40 Classic PPC specific ASM (CONFIG_6XX) Jerome Glisse
2005-01-09 21:03 ` Paul Mackerras
2005-01-10 14:52 ` Tom Rini
2005-01-10 16:39 ` Christoph Hellwig
2005-01-10 16:44 ` Tom Rini
2005-01-10 18:14 ` Jerome Glisse [this message]
2005-01-10 18:29 ` Tom Rini
2005-01-10 18:59 ` Jerome Glisse
2005-01-10 19:12 ` Tom Rini
2005-01-10 19:31 ` Jerome Glisse
[not found] ` <4240b91605011211101ed322a8@mail.gmail.com>
[not found] ` <20050120231442.GE2626@smtp.west.cox.net>
2005-01-21 11:22 ` Jerome Glisse
2005-01-21 12:36 ` Geert Uytterhoeven
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=4240b9160501101014317b8d85@mail.gmail.com \
--to=j.glisse@gmail.com \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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.