All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Pass through start.elf bootargs on Raspberry Pi
Date: Wed, 2 Dec 2015 09:49:50 -0500	[thread overview]
Message-ID: <20151202144950.GS9551@bill-the-cat> (raw)
In-Reply-To: <CAEhB=BudnB_Vjpvv7dv4k-M-2aSu-uutzP=xZGLJdMzAKZ48rA@mail.gmail.com>

On Sun, Nov 29, 2015 at 07:40:12PM +0100, Marco Schuster wrote:

> On Raspberry Pi, the primary bootloader start.elf uses the options in
> config.txt, as well as options hidden in the firmware itself, to tell
> the Linux kernel e.g. framebuffer sizes, memory regions, MAC addresses
> and more.

While Stephen has made some important and useful comments, I want to
poke at one other thing:

>> +        * To force start.elf to pass a processed, ready-to-go DT,
> +        * you have to use the mkknlimg tool on the u-boot image:
> +        * ./mkknlimg --dtok u-boot.bin /boot/u-boot.bin
> +        *
> +        * mkknlimg can be obtained from
> https://github.com/raspberrypi/tools/blob/master/mkimage/knlinfo

I think there is value in being able to support the Pi-official flow.
What I'd like to see (along with making sure that we don't break support
of using mainline kernels) is that knlinfo be updated with a more
complete license statement (it doesn't say what version of the GPL it's
licensed under) and then dropped into U-Boot so that we can generate the
correct binary for this case out of the box.  That's a much cleaner
experience for the users.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151202/32f6f17e/attachment.sig>

      parent reply	other threads:[~2015-12-02 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-29 18:40 [U-Boot] [PATCH 1/2] Pass through start.elf bootargs on Raspberry Pi Marco Schuster
2015-12-02  4:14 ` Stephen Warren
2015-12-02 14:49 ` Tom Rini [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=20151202144950.GS9551@bill-the-cat \
    --to=trini@konsulko.com \
    --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 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.