From: "André Draszik" <git@andred.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v8 3/3] kernel-devicetree.bbclass: Add support to generate append to kernel
Date: Thu, 14 Sep 2017 11:26:07 +0100 [thread overview]
Message-ID: <1505384767.19222.4.camel@andred.net> (raw)
In-Reply-To: <CAP9ODKoRrYs0SB1f6GCvFW6fStoEQNYkv7YbMfZdqbhLfGnXJw@mail.gmail.com>
On Wed, 2017-09-13 at 09:30 -0300, Otavio Salvador wrote:
> On Wed, Sep 13, 2017 at 5:15 AM, André Draszik <git@andred.net> wrote:
> > On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
>
> ...
> > AFAICS, zImage is specific to x86 and arm, all other arches, including
> > MIPS
> > have no zImage Makefile target, so we'll never get here.
>
> Do you know which types we can use here?
* for CONFIG_MIPS_RAW_APPENDED_DTB this can be either vmlinux.bin, or
vmlinuz.bin
* for for CONFIG_MIPS_ELF_APPENDED_DTB this should be vmlinux
see other mail :-)
A.
next prev parent reply other threads:[~2017-09-14 10:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 20:36 [PATCH v8 1/3] kernel: Move Device Tree support to kernel.bbclass Otavio Salvador
2017-09-12 20:36 ` [PATCH v8 2/3] kernel-devicetree.bbclass: Rework to use tasks Otavio Salvador
2017-09-12 20:36 ` [PATCH v8 3/3] kernel-devicetree.bbclass: Add support to generate append to kernel Otavio Salvador
2017-09-13 8:15 ` André Draszik
2017-09-13 12:30 ` Otavio Salvador
2017-09-14 10:26 ` André Draszik [this message]
2017-09-14 12:13 ` Otavio Salvador
2017-09-15 7:55 ` André Draszik
2017-09-14 10:19 ` André Draszik
2017-09-13 8:24 ` [PATCH v8 1/3] kernel: Move Device Tree support to kernel.bbclass Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2017-09-12 13:45 Otavio Salvador
2017-09-12 13:45 ` [PATCH v8 3/3] kernel-devicetree.bbclass: Add support to generate append to kernel Otavio Salvador
2017-09-12 14:45 ` Andreas Oberritter
2017-09-12 17:00 ` Otavio Salvador
2017-09-12 19:10 ` Andreas Oberritter
2017-09-12 20:26 ` Otavio Salvador
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=1505384767.19222.4.camel@andred.net \
--to=git@andred.net \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox