Avoid the kernel loading the Cadence MAC driver by
disabling it in the kernel configuration. Remains the
Xilinx emacps driver, the one we need.
Signed-off-by: David Andrey david.and...@netmodule.com
---
.../microzed/microzed-disable-net-cadence.cfg | 23
conf/machine
Increase the RAM device block size to allow bigger
RamDisk FS image
Signed-off-by: David Andrey david.and...@netmodule.com
---
conf/machine/boards/microzed/microzed-blk-dev-ram.cfg | 11 +++
conf/machine/microzed-zynq7.conf |4
2 files changed, 15
Use Xilinx kernel 3.14 for the Microzed board
instead of the 3.10
Signed-off-by: David Andrey david.and...@netmodule.com
---
conf/machine/microzed-zynq7.conf |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/conf/machine/microzed-zynq7.conf b/conf/machine/microzed-zynq7
Machine specific interfaces file
Signed-off-by: David Andrey david.and...@netmodule.com
---
recipes-core/init-ifupdown/init-ifupdown-1.0/interfaces | 9 -
.../init-ifupdown/init-ifupdown-1.0/microzed-zynq7/interfaces| 9 +
2 files changed, 9 insertions(+), 9
Machine specific interfaces file
Signed-off-by: David Andrey david.and...@netmodule.com
---
.../init-ifupdown-1.0/virtex-4-ml405-powerpc-405/interfaces | 9 +
1 file changed, 9 insertions(+)
create mode 100644
recipes-core/init-ifupdown/init-ifupdown-1.0/virtex-4-ml405-powerpc-405
Machine specific interfaces file
Signed-off-by: David Andrey david.and...@netmodule.com
---
.../init-ifupdown-1.0/virtex-5-ml507-powerpc-440/interfaces | 12
1 file changed, 12 insertions(+)
create mode 100644
recipes-core/init-ifupdown/init-ifupdown-1.0/virtex-5-ml507-powerpc
Hi,
There are lot of threads floating around, and a FAQ without answer.
https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_change_the_root_p
assword
So what is the official way to set a default root password ?
Using a sed command on /etc/passwd through ROOTFS_POSTPROCESS_COMMAND or
is there
Hi everyone !
I tried to share the shared-state folder on a build server for several
people working on the same project. But I meet some unexpected problems,
like errors callings the native dpkg tool.
So I'm back to the basic question :-) Is it possible to share this cache
between developers or