| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
A new device tree for USDPAA support has been added for p3041ds platform. This
was necessary to allow the usage of an ethernet interface as a normal one, that
interfaces with the Linux kernel network stack. In the beginning all the
interfaces were allocated to USDPAA, so they were not visible to the Linux
kernel. For the development process this would mean the impossibility to boot
using a nfs or to connect via ssh.
Signen-off-by: Mihaela Martinas <Mihaela.Martinas@enea.com>
Signed-off-by: Huimin She <huimin.she@enea.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
A new device tree for USDPAA support has been added for p2041rdb platform. This
was necessary to allow the usage of an ethernet interface as a normal one, that
interfaces with the Linux kernel network stack. In the beginning all the
interfaces were allocated to USDPAA, so they were not visible to the Linux
kernel. For the development process this would mean the impossibility to boot
using a nfs or to connect via ssh.
Signed-off-by: Mihaela Martinas <Mihaela.Martinas@enea.com>
Signed-off-by: Huimin She <huimin.she@enea.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
A device tree (dts) is added for USDPAA support on t4240rdb. In the
default USDPAA dts, all the ethernet interfaces are dedicated to
USDPAA, so that they are not visible to Linux kernel. This brings
difficulty for development, such as nfs booting and ssh login.
In the new dts, one ethernet interface is reserved for Linux kernel
network stack, and the others are for USDPAA.
Signed-off-by: Huimin She <huimin.she@enea.com>
Signed-off-by: Nora Björklund <nora.bjorklund@enea.com>
|
| |
|
|
|
|
|
|
|
| |
When printing from a recipe it should be used the printing
functions provided by yocto. Used bb.note for info printing
and bb.error for error exception printing.
Signed-off-by: Andrei Varvara <andrei.varvara@enea.com>
Signed-off-by: George Nita <george.nita@enea.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Freescale linux-qoriq.inc is expecting that cfg folder
is present in the source directory. Our recipes regarding cfg
copies the cfg folder in the working directory. A patch was made
to the Freescale's original recipe to look for cfg patches inside workdir,
but this was not accepted by Freescale.
A new fix was proposed that basically copies the cfg folder from the
working directory to source directory where original FSL recipe expects
to find it. This way we do not have to modify the original FSL recipe.
In order to implement this fix python code that copies the cfg folder
from working directory to source directory has been added in the
do_unpack task.
Signed-off-by: Andrei Varvara <andrei.varvara@enea.com>
Signed-off-by: George Nita <george.nita@enea.com>
|
| |
|
|
|
|
|
|
| |
relocated config fragment path fix for linux-qoriq kernel
from meta-fsl-ppc to meta-enea-bsp-ppc
Signed-off-by: Andrei Varvara <andrei.varvara@enea.com>
Signed-off-by: George Nita <george.nita@enea.com>
|
| |
|
|
|
|
|
|
| |
New kernel recipes are defined in the meta-enea-bsp-<arch> layers now.
Movin the recipe together with patches from meta-fsl-ppc.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Tudor Florea <tudor.florea@enea.com>
|
| |
|
|
| |
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
| |
|
|
| |
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
| |
|
|
|
|
|
|
| |
We give up building the so-called "staging kernel". From now on we'll
use the native kernel configuration mechanism and issue two kernel build
commands if needed.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
| |
|
|
|
|
|
| |
To keep it in synch with the one defined in enea.common.inc in
meta-enea-base.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
|
|
result of splitting up meta-enea
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
