From: George G. Davis <gdavis@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Setup correct bi_arch_number for OMAP1610 boards
Date: Wed, 7 Jul 2004 08:45:01 -0400 [thread overview]
Message-ID: <20040707124501.GK6115@mvista.com> (raw)
Greetings,
The attached patch fixes OMAP1610 board builds so that the correct machine
number is setup based on the board target config file. This allows recent
OMAP linux-2.6 kernels to boot on OMAP1610 based boards since recent OMAP
Linux-2.6 kernels now expect the correct and official machine number to be
passed in for these OMAP1610 based boards. If the correct machine number is
not passed in to recent OMAP Linux-2.6 kernels, then the Linux kernel will
either malfunction or hang due to selection of the wrong machine specific
support code due to wrong machine number passed into the kernel by U-Boot.
I've tested U-boot on an OMAP1610 H2 board with recent OMAP Linux-2.6 kernel
with this patch applied - it works ok for me.
There is in fact one build failure for this MAKEALL test case:
CROSS_COMPILE=/opt/montavista/pro/devkit/arm/v4t_le/bin/arm_v4t_le- ./MAKEALL arm
Here's the build failure for the above test case:
Configuring for xsengine board...
cc1: error: unrecognized option `-fdisassemble-all'
cc1: error: unrecognized option `-fdisassemble-all'
cc1: error: unrecognized option `-fdisassemble-all'
make[1]: *** [.depend] Error 1
make: *** [board/xsengine/libxsengine.a] Error 2
/opt/montavista/pro/devkit/arm/v4t_le/bin/arm_v4t_le-size: u-boot: No such file or directory
I did not perform a test build prior to applying this fix. But I'm confident
the above build failure is not a regression due to this patch. Perhaps this
is merely a problem with my tool chain? However I'm indifferent about that
failure and do not know or really much care (at the moment : ) if it exists
for other tool chains or not.
--
Regards,
George
-------------- next part --------------
* Patch by George G. Davis, 06 Jul 2004:
- update mach-types.h to latest arm.linux.org.uk master list
- Set correct OMAP1610 bi_arch_number for build target
-------------- next part --------------
A non-text attachment was scrubbed...
Name: u-boot-HEAD040706-omap1610_mach_types.patch.bz2
Type: application/x-bzip2
Size: 7261 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040707/55df0429/attachment.bin
reply other threads:[~2004-07-07 12:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040707124501.GK6115@mvista.com \
--to=gdavis@mvista.com \
--cc=u-boot@lists.denx.de \
/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