From: Manish D <manish2312@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: [newbie] uboot relevant !
Date: Thu, 19 Mar 2009 11:44:54 +0530 [thread overview]
Message-ID: <d7ca49770903182314j6849decbhaa1039dbb5276f86@mail.gmail.com> (raw)
In-Reply-To: <d7ca49770903181013h20368741t7cd4653a83286006@mail.gmail.com>
Hi all,
please bear these probably newbie questions.
I am trying to port a BSP from 2.4 to 2.6 for a mpc834x based platform.
I am building and working on the device tree now.
Is there a way build this bsp, without taking the device tree route ?
I guess not.
The uboot version i am using is old and not sure how this uboot can
pass the device tree details while booting the kernel.
Is there a way to load 2.6 kernel from this older bootloader (cuImage
?) or will i have to upgrade to a newer uboot ?
Any relevant pointers for this would be appreciated.
TIA,
Manish
next parent reply other threads:[~2009-03-19 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d7ca49770903181013h20368741t7cd4653a83286006@mail.gmail.com>
2009-03-19 6:14 ` Manish D [this message]
2009-03-19 11:35 ` [newbie] uboot relevant ! Josh Boyer
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=d7ca49770903182314j6849decbhaa1039dbb5276f86@mail.gmail.com \
--to=manish2312@gmail.com \
--cc=linuxppc-dev@ozlabs.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