From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68knommu: add missing make rule for Palm/Pilot bitmap boot logo
Date: Thu, 22 Dec 2011 17:27:06 +1000 [thread overview]
Message-ID: <4EF2DBCA.6020806@snapgear.com> (raw)
In-Reply-To: <CAMuHMdVjEn2cNvPCYegp3gweNp_98XjPvoBEf20J5jQ++UNLkA@mail.gmail.com>
Hi Geert,
On 22/12/11 17:18, Geert Uytterhoeven wrote:
> On Thu, Dec 22, 2011 at 08:03,<gerg@snapgear.com> wrote:
>> From: Greg Ungerer<gerg@uclinux.org>
>>
>> Compiling for the m68knommu/68328 Palm/Pilot target you get:
>>
>> áAS á á áarch/m68k/platform/68328/head-pilot.o
>> arch/m68k/platform/68328/head-pilot.S:37:23: fatal error: bootlogo.rh: No such file or directory
>>
>> The Makefile contains rules to make the bootlogo.rh file from the C source
>> bootlogo.h. But it is missing a dependency that compiling head-pilot.S needs
>> bootlogo.rh.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>> ---
>> áarch/m68k/platform/68328/Makefile | á á3 +++
>> á1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/m68k/platform/68328/Makefile b/arch/m68k/platform/68328/Makefile
>> index e4dfd8f..704e36d 100644
>> --- a/arch/m68k/platform/68328/Makefile
>> +++ b/arch/m68k/platform/68328/Makefile
>> @@ -16,6 +16,9 @@ obj-$(CONFIG_ROM) á á += romvec.o
>> áextra-y á á á á á á á á á á á á:= head.o
>> áextra-$(CONFIG_M68328) += bootlogo.rh head.o
>>
>> +$(obj)/head-pilot.o: $(obj)/bootlogo.rh
>> +$(obj)/head-rom.o: $(obj)/bootlogo.rh
>> +
>> á$(obj)/bootlogo.rh: $(src)/bootlogo.h
>> á á á áperl $(src)/bootlogo.pl< $(src)/bootlogo.h> $(obj)/bootlogo.rh
>
> Nothing serious, you just made me wondering:
> 1. Any chance bootlogo.h can be generated from a more edit-friendly format,
> cfr. drivers/video/logo/?
Probably. This is the way the code came to me originally, and I haven't
looked at it in quite a while.
> 2. Why do you include the *.rh file from an assembler source file, instead of
> including the *.h file from a C source file?
Good question. I am not sure why it was done this way. I'll see if we
can do this a little more cleanly.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2011-12-22 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 7:03 [PATCH] m68knommu: add missing make rule for Palm/Pilot bitmap boot logo gerg
2011-12-22 7:18 ` Geert Uytterhoeven
2011-12-22 7:27 ` Greg Ungerer [this message]
2011-12-30 0:30 ` Greg Ungerer
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=4EF2DBCA.6020806@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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