From: fachkar.datawind@gmail.com (f. achkar)
To: linux-arm-kernel@lists.infradead.org
Subject: defining ARM machine type properly
Date: Wed, 26 May 2010 17:11:22 -0400 [thread overview]
Message-ID: <4BFD8E7A.6050103@gmail.com> (raw)
hi,
I'm trying to port smdk2450 arch to the a new kernel 2.6.32-9, I did the
initial work as per various googled documents, but somehow the current
initial Image is failing at arch/arm/kernel/head-common.S :
'__lookup_processor_type', and eventually goes to '__error_a' of the
same file! this seems to be related to the definition of machine_type as
defined in :
include/asm-arm/mach-types.h and arch/arm/tools/mach-types*
I checked where the definition goes in include/asm-arm/mach-types.h by
inserting
#error 2223XX
into various parts of that header and seems fine at the point.
nevertheless I'm not 100 sure
I wonder if the is a definitive reference to guide in this matter,
better yet a check-list like procedure??
thanks,
ferar
next reply other threads:[~2010-05-26 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 21:11 f. achkar [this message]
2010-05-27 1:07 ` defining ARM machine type properly Ben Dooks
2010-05-27 14:29 ` f. achkar
2010-05-27 15:08 ` f. achkar
2010-05-28 1:08 ` Ben Dooks
2010-05-27 3:14 ` Wan ZongShun
2010-05-27 14:53 ` f. achkar
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=4BFD8E7A.6050103@gmail.com \
--to=fachkar.datawind@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).