public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Rockchip RK3288 u-boot with mainline kernel
Date: Tue, 29 Nov 2016 11:20:52 +0100	[thread overview]
Message-ID: <1790297.5MBZbjcMZN@diego> (raw)
In-Reply-To: <CAPnjgZ3-ugQ_tmYsvg_cpxwv-aHzcKncn0BXD_R8C=Y7qjySFw@mail.gmail.com>

Hi Rick,

Am Montag, 28. November 2016, 15:09:05 schrieb Simon Glass:
> + A few rockchip people and linux-rockchip
> 
> Hi Rick,
> 
> On 25 November 2016 at 11:20, Rick Bronson <rick@efn.org> wrote:
> > Hi All,
> > 
> >   I've got unsupported RK3288 hardware running the latest git u-boot to
> > 
> > SPL as explained in
> > http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.rockchip.  My goal
> > is to run the mainline (ie. not Android) Linux kernel on this hardware
> > 
> > and wondered:
> >  - Do I need to get the latest git u-boot to run before I can run the
> > 
> > mainline kernel?  Or can I use
> > github.com/linux-rockchip/u-boot-rockchip.git, which I have running
> > u-boot fully.
> 
> It's up to you - obviously mainline is where the development should
> be, but there is no requirement that I know of.

correct, the (mainline-)kernel runs just fine on both the vendor-fork of uboot 
as well as on mainline.


> Does mainline run on your board?
> 
> >  - The device tree seems to be in two places, once via:
> >         resource_tool --image=resource2.img --pack linux/logo.bmp
> >         ${DTS}.dtb
> >   
> >   that gets put into the resource file and then again at the end of the
> > 
> > kernel via CONFIG_ARM_APPENDED_DTB.  Do I need both?  When I do both
> > I get things like:
>
> > Unknow param: MACHINE_MODEL:rk30sdk!
> > Unknow param: MACHINE_ID:007!

ARM_APPEND_DTB is meant for boards where the bootloader cannot load the 
devicetree (to old or so) and also cannot be reasonably exchanged. So the 
append-mechanism was invented to allow bundling the devicetree with the actual 
kernel image, so that to the bootloader it looks like just any other kernel 
image.

So you essentially only need one or the other. Also at least mainline uboot 
also supports the FIT image type, where you can bundle the devicetree in a 
more generalized way.

For your message I would guess the kernel didn't find a usable devicetree 
somehow and was falling back to ATAGS-based board selection?

  reply	other threads:[~2016-11-29 10:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 18:20 [U-Boot] Rockchip RK3288 u-boot with mainline kernel Rick Bronson
2016-11-28 22:09 ` Simon Glass
2016-11-29 10:20   ` Heiko Stübner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-29 18:22 Rick Bronson
2016-11-29 21:40 ` Simon Glass
2016-11-29 22:11   ` Heiko Stübner
2016-11-29 22:50 Rick Bronson
2016-12-01 19:00 Rick Bronson
2016-12-01 21:01 ` Heiko Stuebner
2016-12-03 18:07 Rick Bronson
2016-12-03 21:24 ` Heiko Stuebner
2016-12-06  0:56 Rick Bronson
2016-12-07  3:48 ` Simon Glass

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=1790297.5MBZbjcMZN@diego \
    --to=heiko@sntech.de \
    --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