The following changes since commit f82f5f2754dd2d41db8d62f455dd380c26635ee1:
update: add option to stop immediately on parse errors (2018-08-24 16:41:59
+1200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes7
I created a custom meta-layer to build libfmt 4.1.0 (
https://github.com/fmtlib/fmt).
Since this library uses cmake, I created this receipe:
*SUMMARY = "fmt"*
*SECTION = "base"*
*SRC_URI = "https://github.com/fmtlib/fmt/archive/${PV}.tar.gz
On 9/4/18 10:39 PM, Ravikiran J wrote:
> Dear Yocto team,
>
> We have developed some recipe file to install the firmware binary in
> the file system of Yocto.
> Recipe file is working fine in *Yocto morty* version but when we tried
> the same in the *Yocto sumo* version we got the following
On Wed, Sep 05, 2018 at 01:21:18PM +, Amol Lad wrote:
> Hi,
>
> I want to build two initramfs images when building core-image-minimal. First
> initramfs gets bundled with kernel and available after build. This is all
> good.
>
> Now, how to include second initramfs image also in
Hi,
I want to build two initramfs images when building core-image-minimal. First
initramfs gets bundled with kernel and available after build. This is all good.
Now, how to include second initramfs image also in core-image-minimal? It will
be standalone initramfs image i.e. it won't be bundled
On Thursday, 30 August 2018 11:44:10 AM NZST Paul Eggleton wrote:
> On Wednesday, 29 August 2018 10:46:27 PM NZST Paul Eggleton wrote:
> > I know Konrad promised to update the docker-compose setup to be closer
> > to what we'd done recently with the docker setup, but I needed something
> >
Please also merge it to yocto-4.18, because linux-yocto-rt_4.18 also
faces with
the same problem.
Thanks,
--Hongzhi
On 2018年09月05日 14:15, Hongzhi.Song wrote:
According to the changes before linux-4.18-rc6, we must add new
dependency for some config option or modify them value.
1. If
Hi all,
I'm writing to this mailing list to try to collect some advice about a
situation that I'm involved and that could be quite common.
I have a physical machine, and I have my own meta-layers to support it:
a BSP layer containing a machine configuration and some customizations
on kernel and
The preempt-rt config explicitly disables aufs which can result in
config warnings for kernels where the aufs patches aren't applied.
Since default state of aufs is 'n', there's no need to disable it
explicitly here.
For BSPs relying on aufs, they should enable it by including
Please merge to master.
--Hongzhi
On 2018年09月05日 14:15, Hongzhi.Song wrote:
According to the changes before linux-4.18-rc6, we must add new
dependency for some config option or modify them value.
1. If "CONFIG_PINCTRL_SUNRISEPOINT=m", CONFIG_PINCTRL_INTEL cann't
be set y, because
According to the changes before linux-4.18-rc6, we must add new
dependency for some config option or modify them value.
1. If "CONFIG_PINCTRL_SUNRISEPOINT=m", CONFIG_PINCTRL_INTEL cann't
be set y, because CONFIG_PINCTRL_INTEL is selected by
CONFIG_PINCTRL_SUNRISEPOINT.
2. The dependency of
11 matches
Mail list logo
