From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: lothar@denx.de
Cc: yocto@yoctoproject.org
Subject: Re: how to build external firmware for kernel
Date: Mon, 05 Aug 2013 11:05:43 +0100 [thread overview]
Message-ID: <7243158.LY4yQ1ssbD@helios> (raw)
In-Reply-To: <20130805114222.15220qh2lyd417dw@webmail.mnet-online.de>
Hi Lothar,
On Monday 05 August 2013 11:42:22 lothar@denx.de wrote:
> I have a linux kernel and a external firmware. Building manually,
> first I have to checkout and build the firmware "native" to obtain a
> firmware blob, then I need this firmware blob to build the kernel for
> the target.
>
> So far I tried to do this in yocto with separate recipes: a
> firmware.bb and a mylinux.bb. In firmware.bb, I check out the firmware
> via git and let it run "make" on native (this is necessary, since the
> Makefile builds a tool which then automatically gets called inside the
> Makefile to create the firmware blob).
>
> In the kernel recipe, I declare a DEPEND on firmware.bb. I set the
> .config options to load an extra firmware blob. But now, I have a
> problem: I need actually to have the firmware blob within the kernel's
> file hierarchy. Ideally I would copy/move it from the firmware's
> destination directory into the kernel's source directory.
Shouldn't firmware go into /lib/firmware?
> Questions:
> How can I achieve this kind of setup working out with yocto or
> bitbake, respectively? What might be the best approach in my situation?
You can get the kernel version name from ${STAGING_KERNEL_DIR}/kernel-
abiversion if that helps, but I wouldn't have thought you'd need it if the
firmware is installed to /lib/firmware instead.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-05 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 9:42 how to build external firmware for kernel lothar
2013-08-05 10:05 ` Paul Eggleton [this message]
2013-08-05 12:41 ` lothar
2013-08-05 14:38 ` Paul Eggleton
2013-08-05 22:42 ` lothar
2013-08-06 12:45 ` lothar
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=7243158.LY4yQ1ssbD@helios \
--to=paul.eggleton@linux.intel.com \
--cc=lothar@denx.de \
--cc=yocto@yoctoproject.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.