It should.Mike1010 wrote: Will it also work with make NAME=red_pitaya_0_92 all ?
No. The zynq_remoteproc driver stops and starts CPU cores when needed.Mike1010 wrote: Did you figure out why linux starts with both cores? I try to update to kernel 4.0.
Have you read this article that you and I referenced several times? It contains all the answers. I've even seen your comments at the end of this articleMike1010 wrote: The structs in file app_cpu1.c resource_table, fw_resource_type, fw_rsc_carveout, rproc_resource and the ams_vectors.S, boot.S, xtime_1.c patch file are all for the remoteproc driver?
I don't know.Mike1010 wrote:what will happen if cpu1_app.elf should be started on core1 but its blocked by linux (without your remoteproc approach)...it will not start and return no error?
Code: Select all
root@red-pitaya:/home# tar --directory=/lib/modules/3.18.0-xilinx/kernel/drivers -zxf drivers.tgz
root@red-pitaya:/home# depmod
depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.builtin: No such file or directory
I don't think that these warnings are critical. modules.builtin and modules.order can be copied fromMike1010 wrote: Just a note, what about the following warning?Code: Select all
root@red-pitaya:/home# tar --directory=/lib/modules/3.18.0-xilinx/kernel/drivers -zxf drivers.tgz root@red-pitaya:/home# depmod depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.builtin: No such file or directory
Code: Select all
tmp/linux-xlnx-xilinx-v2015.1/modules.order
tmp/linux-xlnx-xilinx-v2015.1/modules.builtinI'll try to make zynq_remoteproc, remoteproc, virtio and virtio_ring as builtin and then install only modules.builtin and modules.order.modules.builtin
--------------------------------------------------
This file lists all modules that are built into the kernel. This is used
by modprobe to not fail when trying to load something builtin.
I tried but it didn't work. I've just added instructions on how to install the modules.builtin and modules.order files.pavel wrote:I'll try to make zynq_remoteproc, remoteproc, virtio and virtio_ring as builtin and then install only modules.builtin and modules.order.
Code: Select all
@$(CC) $(LDFLAGS) $(LIBRARIES) -o $@ $^
Code: Select all
@$(CC) $(LDFLAGS) -o $@ $^ $(LIBRARIES)