From: fachkar.datawind@gmail.com (f. achkar)
To: linux-arm-kernel@lists.infradead.org
Subject: defining ARM machine type properly
Date: Thu, 27 May 2010 10:29:04 -0400 [thread overview]
Message-ID: <4BFE81B0.4010003@gmail.com> (raw)
In-Reply-To: <20100527010742.GH7248@trinity.fluff.org>
On 05/26/2010 09:07 PM, Ben Dooks wrote:
> On Wed, May 26, 2010 at 05:11:22PM -0400, f. achkar wrote:
>
>> hi,
>> I'm trying to port smdk2450 arch to the a new kernel 2.6.32-9, I did the
>>
> I suspect what you are doing is trying to port it to a machine that
> was loosley based on the SMDK2450 and that whoever did the uboot port
> failed to understand that when the hardware changes then the machine
> number needs to change too.
>
u-boot came with the evaluation board so it is samsung's doing! however,
the u-boot correctly reports the machine type of 0x648 (corresponding to
1608 ), I suspect me wrong doing :( in setting the correct mach_type in
the linux-2.6.32-9.
>
>> 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
>>
> you probably wanted to enable the debugging in the head code.
>
>
>> #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
>>
> How about downloading the latest kernel, with nice fresh S3C2450 support
> in it?
>
excellent, I'll check that ... thaks
next prev parent reply other threads:[~2010-05-27 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 21:11 defining ARM machine type properly f. achkar
2010-05-27 1:07 ` Ben Dooks
2010-05-27 14:29 ` f. achkar [this message]
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=4BFE81B0.4010003@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).