> I've been running a kernel based on the Ubuntu 12.04 setup
> *repo: git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git*
> *tag: ti-ubuntu-3.4-1485.7*
> I'm running *gst-ducati* so I need the Ducati processors running,
> using *libdce*
> This was all working great, including the *gst-ducati* stuff.
> Here's what it looks like when I boot:
> *[ 5.593658] rproc remoteproc1: powering up ipu_c0*
> *[ 5.615020] rproc remoteproc0: Booting fw image
> tesla-dsp.xe64T, size 481512*
> *[ 5.622650] omap-iommu omap-iommu.0: dsp: version 2.0*
> *[ 5.714447] rproc remoteproc0: remote processor dsp_c0 is now up*
> *[ 5.721343] rproc remoteproc1: Booting fw image
> ducati-m3-core0.xem3, size 3134213*
> *[ 5.729888] omap-iommu omap-iommu.1: ipu: version 2.1*
> *[ 5.739105] virtio_rpmsg_bus virtio0: rpmsg host is online*
> *[ 5.745361] rproc remoteproc0: registered virtio0 (type 7)*
> *[ 5.902709] omap-rproc omap-rproc.0: received echo reply from
> dsp_c0*
> *[ 5.919799] virtio_rpmsg_bus virtio0: creating channel
> rpmsg-client-sample addr 0x32*
> *[ 5.928710] virtio_rpmsg_bus virtio0: creating channel
> rpmsg-client-sample addr 0x33*
> *[ 5.941802] virtio_rpmsg_bus virtio0: creating channel
> rpmsg-omx2 addr 0x3c*
> *[ 5.949981] rpmsg_omx rpmsg-omx2: new OMX connection srv
> channel: 1024 -> 60!*
> *[ 6.088287] rproc remoteproc1: remote processor ipu_c0 is now up*
> *[ 6.100219] virtio_rpmsg_bus virtio1: rpmsg host is online*
> *[ 6.107269] rproc remoteproc1: registered virtio1 (type 7)*
> *[ 6.261962] EXT4-fs (mmcblk0p2): mounted filesystem with
> ordered data mode. Opts: (null)*
> *[ 6.555572] omap-rproc omap-rproc.1: received echo reply from
> ipu_c0*
> *[ 6.562408] virtio_rpmsg_bus virtio1: creating channel
> rpmsg-dce addr 0x2a*
> *[ 6.570587] virtio_rpmsg_bus virtio1: creating channel
> rpmsg-client-sample addr 0x32*
> *[ 6.579559] virtio_rpmsg_bus virtio1: creating channel
> rpmsg-client-sample addr 0x33*
> *
> *
> Today, I tried upgrading to a newer kernel version. I merged my
> kernel with
> *ti-ubuntu-3.4-1486.10* and now the Ducati processors no longer come up.
> Now, when I boot, I get these messages when bringing up the DSP
> processors:
> *[ 5.976135] rproc remoteproc0: powering up dsp_c0*
> *[ 5.989074] rproc remoteproc0: Booting fw image
> tesla-dsp.xe64T, size 481512*
> *[ 5.997436] omap-iommu omap-iommu.0: dsp: version 2.0*
> *[ 6.026794] rproc remoteproc0: remote processor dsp_c0 is now up*
> *[ 6.035705] virtio_rpmsg_bus virtio0: rpmsg host is online*
> *[ 6.041534] rproc remoteproc0: registered virtio0 (type 7)*
> *[ 6.071075] omap-rproc omap-rproc.0: received echo reply from
> dsp_c0*
> *[ 6.687103] rproc remoteproc1: powering up ipu_c0*
> *[ 6.723724] rproc remoteproc1: Booting fw image
> ducati-m3-core0.xem3, size 3134213*
> *[ 6.732482] omap-iommu omap-iommu.1: ipu: version 2.1*
> *[ 7.033416] rproc remoteproc1: remote processor ipu_c0 is now up*
> *[ 7.042785] virtio_rpmsg_bus virtio1: rpmsg host is online*
> *[ 7.048614] rproc remoteproc1: registered virtio1 (type 7)*
> *[ 7.498840] omap-rproc omap-rproc.1: received echo reply from
> ipu_c0*
> *[ 11.034973] omap_iommu_update_latency Requested latency -1 but
> limiting DSP latency to 300 due to buggy firmware*
> Notice, no virtual channels created. When I try to run the
> *gst-ducati* code, I now
> get this error:
> *libdce.c:459: init error: could not get plugin ioctl base: -22*
> My kernel config contains these [relevant] settings:
> *CONFIG_DRM_OMAP=y*
> *CONFIG_DRM_OMAP_NUM_CRTCS=2*
> *CONFIG_RPC_OMAP=y*
> *CONFIG_DRM_OMAP_DCE=y*
> *# CONFIG_OMAP_RPMSG_RDAEMON is not set*
> *CONFIG_REMOTEPROC=y*
> *CONFIG_OMAP_REMOTEPROC=y*
> *CONFIG_OMAP_REMOTEPROC_IPU=y*
> *CONFIG_OMAP_REMOTEPROC_DSP=y*
> *# CONFIG_OMAP_REMOTEPROC_WATCHDOG is not set*
> *CONFIG_OMAP4_IPU_CMA_SIZE=0x6500000*
> *CONFIG_OMAP5_IPU_CMA_SIZE=0xA100000*
> *CONFIG_OMAP_DSP_CMA_SIZE=0x400000*
> *CONFIG_RPMSG=y*
> *CONFIG_RPMSG_RESMGR_FWK=y*
> *CONFIG_RPMSG_RESMGR=y*
> *CONFIG_OMAP_RPMSG_RESMGR=y*
> *CONFIG_RPMSG_OMX=y*
> Only the two commented out options are different between the two
> kernel versions (these options are new).
> Any ideas what I'm missing? Why don't the virtual channels get created?
> Note: I did change my bootargs to remove the hole in this latest
> version, so I'm booting with *mem=1G@0x80000000*
> *
> *