From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Porting OE to new hardware
Date: Tue, 30 Mar 2010 12:18:18 -0600 [thread overview]
Message-ID: <4BB2406A.10602@mlbassoc.com> (raw)
In-Reply-To: <a25fc1971003301114k3b1e53bch8d22ea79c26a41a0@mail.gmail.com>
On 03/30/2010 12:14 PM, Bernard Mentink wrote:
> Thanks Khem,
>
> That helps a lot. On the kernel config issue there is one thing I don't
> understand.
>
> I have set up to do an ARM i.mx31 build, but when I did a "make menuconfig"
> in the /build/tmp/.../kernelxxxxx directory, it only shows x86 options, I
> don't know where all the i.mx31 kernel options are.
You didn't tell it - the default architecture is the one you build on (probably
x86). Try this instead:
% make ARCH=arm menuconfig
> On Wed, Mar 31, 2010 at 7:03 AM, Khem Raj<raj.khem@gmail.com> wrote:
>
>> On Mon, Mar 29, 2010 at 12:29 PM, Bernard Mentink<bmentink@gmail.com>
>> wrote:
>>> Hi All,
>>>
>>> I am jumping across to this email list as the user one has very little
>>> traffic.
>>>
>>> I have just found OE and would like to use it to get Linux up and running
>> on
>>> some custom hardware. The hardware is currently running the logicloader
>>> bootloader from LogicPD and a YAFFS2 filesystem.
>>>
>>> I have found very little info on the steps necessary to port to new
>>> hardware. As far as OE is concerned, I have built an image after altering
>>> the MACHINE and DISTRO to something close to what I need.
>>> I now have a zimage (kernel) and a rootFS.
>>>
>>> However I have a number of questions:
>>>
>>> 1. To boot with zimage with logicloader, I have to load the image into
>>> memory at an address, and then execute it at the start code which I
>> presume
>>> is an offset the start of the image. Can anyone tell me how I can find
>>> the relevant map file to work out
>>> what offset I need to apply? I did a search for *.map files in the
>> build/tmp
>>> direcory and found nada ..
>>
>> this post tells how to load linux kernel using logicloader. It might help
>> you.
>>
>> http://forums.freescale.com/t5/Other-Microcontrollers/load-zImage-or-vmlinux-using-LogicLoader/td-p/32749;jsessionid=F6F40E5BF81249CFF86028A7AB86DE29
>>
>>>
>>> 2. How do I do a kernel config? Is there an option to pass to bitbake to
>> do
>>> that, or do I have to find the kernel source and do it manually, then
>>> rebuild with bitbake?
>>
>> You can copy the .config you want into
>> recipes/linux/<chosen-kernel-version>/<machine>/defconfig file and it
>> will use
>> it to build the kernel for you machine. You can also edit the .config
>> on fly search the ml on how to do it.
>>
>>>
>>> 3. What src files in the kernel do I need to to maybe alter to get the
>>> serial port and memory map right for my target hardware ..
>>>
>>
>> you can specify serial port in kernel commandline too unless your board
>> needs
>> a special handling of serial port.
>>
>>> 4. Once I get the kernel booting, I need it to load the rootfs, initially
>> I
>>> can boot that from NFS, but I would like to eventually load it from my
>> YAFFS
>>> NAND partition, how do I do that?
>>
>> you can do that thru kernel commandline.
>>
>>>
>>>
>>> Hope someone can give me some pointers in the right direction ... I would
>>> love to kick off WinCE from this hardware ;-)
>>>
>>> Cheers,
>>> Bernie
>>>
>>> --
>>> You always have believers and scepticts.. A True inventor is always a
>>> believer..
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
>
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2010-03-30 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 19:29 Porting OE to new hardware Bernard Mentink
2010-03-29 19:33 ` Izak Burger
2010-03-29 22:39 ` Bernard Mentink
2010-03-30 18:03 ` Khem Raj
2010-03-30 18:14 ` Bernard Mentink
2010-03-30 18:18 ` Gary Thomas [this message]
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=4BB2406A.10602@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.