Hi Michal,
On Tue, May 22, 2012 at 8:51 AM, Michal Simek <[email protected]> wrote:
> Simple enabling RSC_VDEV in rproc_handle_rsc doesn't work.
Sure - you'll need to actually plug the vrings allocation code there,
too (i.e. this requires some coding, it's not a 1-liner).
> BTW: I am using kernel modules and there is no dependency for
> virtio_rpmsg_bus in remoteproc module
> in sense if you load remoteproc module you also need to load
> virtio_rpmsg_bus to get firmware to work.
This is expected: remoteproc only provides means for booting and
controlling remote processors and it doesn't boot them upfront.
To actually boot a remote processor, and do something useful with it,
one needs to load a module which utilizes remoteproc's API (e.g.
virtio_rpmsg_bus, but YMMV).
> ~ # lsmod
> ~ # modprobe zynq_remoteproc
> zynq_remoteproc: Unknown symbol rproc_register (err 0)
> zynq_remoteproc: Unknown symbol rproc_alloc (err 0)
> zynq_remoteproc: Unknown symbol rproc_vq_interrupt (err 0)
> zynq_remoteproc: Unknown symbol rproc_free (err 0)
> zynq_remoteproc: Unknown symbol rproc_unregister (err 0)
We don't have these errors - have you tried looking into them ?
Btw do you plan on submitting the code for zynq_remoteproc ?
> Can you see the same behavior on omap?
Except the "Unknown symbol" errors, everything else looks good.
Thanks,
Ohad.