From: Pavel Machek <pavel@ucw.cz>
To: rpurdie@rpsys.net, kernel list <linux-kernel@vger.kernel.org>
Subject: sharp zaurus: prevent killing spitz-en
Date: Tue, 25 Oct 2005 21:08:29 +0200 [thread overview]
Message-ID: <20051025190829.GA1788@elf.ucw.cz> (raw)
Hi!
This is wrong solution, but it prevents breaking flashing mechanism on
spitz with too big kernel. It may be handy to someone...
Pavel
--- clean-rp/arch/arm/boot/Makefile 2004-12-25 13:34:57.000000000 +0100
+++ linux-rp/arch/arm/boot/Makefile 2005-10-25 20:43:58.000000000 +0200
@@ -53,6 +53,12 @@
$(obj)/zImage: $(obj)/compressed/vmlinux FORCE
$(call if_changed,objcopy)
@echo ' Kernel: $@ is ready'
+ @ls -al $@
+ @wc -c $@ | ( read SIZE Y; \
+ if [ $$SIZE -gt 1294336 ]; then \
+ echo ' Kernel is too big, would kill spitz'; \
+ rm $@; \
+ fi )
endif
--
Thanks, Sharp!
next reply other threads:[~2005-10-25 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 19:08 Pavel Machek [this message]
2005-10-25 22:58 ` sharp zaurus: prevent killing spitz-en Ben Dooks
2005-10-25 23:14 ` Pavel Machek
2005-10-25 23:18 ` David Vrabel
2005-10-26 0:10 ` Russell King
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=20051025190829.GA1788@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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