| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
remoteproc: remove remoteproc drivers Move remoteproc drivers implementation to applications' platform implementation. Signed-off-by: Wendy Liang <jliang@xilinx.com> | 7 年前 | |
remoteproc: Fix management of non loadable program segments The elf loader assumes that the last ELF program segment will always be a LOAD type segment. I deduce this from the fact that the elf_load() function, when loading the remote ELF sections during the RPROC_LOADER_READY_TO_LOAD stage, compares the last load segment num to the total ELF sections to determine if the loading is complete and it can move to the next stage RPROC_LOADER_POST_DATA_LOAD. If the last program segment in the ELF is not of type LOAD, the last loaded LOAD segment never equals total ELF sections. This creates an error condition and the firmware loading fails. This patch fixes this issue by comparing the last loaded LOAD segment number with the max LOAD segment number in the ELF. Signed-off-by: Umair Khan <umair_khan@mentor.com> | 3 个月前 | |
lib/remoteproc: seperate the vdev and vring bitmap Linux do not alloc the notifyid for the virtio device and use one idr alloc notifyid for the vring. OpenAMP use one bitmap alloc the notifyid for both the virtio device and the vring. Both the Linux and OpenAMP will assgin back the alloced notifyid to the resource table and check this notifyid is used before. This may cause the notifyid is different to the linux alloced and cause remoteproc init error in OpenAMP. For example, Linux alloc the vring notifyid: 0, 1 and assgin back to the resource table, OpenAMP must alloc the same notifyid for vring, but the notifyid 0 already be used by the virtio device, so OpenAMP will init failed at the handle_vdev_rsc() with error code: -RPROC_ERR_RSC_TAB_NP. Signed-off-by: Bowen Wang <wangbowen6@xiaomi.com> | 3 个月前 | |
lib/remoteproc: Don't need to check vdev->notifyid and vring->notifyid vdev->notifid may be equal to vring->notifyid because https://gerrit.pt.mioffice.cn/c/vela/nuttx/openamp/open-amp/+/6522276 Signed-off-by: yintao <yintao@xiaomi.com> | 3 个月前 | |
lib/remoteproc: seperate the vdev and vring bitmap Linux do not alloc the notifyid for the virtio device and use one idr alloc notifyid for the vring. OpenAMP use one bitmap alloc the notifyid for both the virtio device and the vring. Both the Linux and OpenAMP will assgin back the alloced notifyid to the resource table and check this notifyid is used before. This may cause the notifyid is different to the linux alloced and cause remoteproc init error in OpenAMP. For example, Linux alloc the vring notifyid: 0, 1 and assgin back to the resource table, OpenAMP must alloc the same notifyid for vring, but the notifyid 0 already be used by the virtio device, so OpenAMP will init failed at the handle_vdev_rsc() with error code: -RPROC_ERR_RSC_TAB_NP. Signed-off-by: Bowen Wang <wangbowen6@xiaomi.com> | 3 个月前 | |
rsc_table_parser: Move header to make internal functions internal only The files in include/openamp are deployed on install and can be used by applications using the OpenAMP API. The functions in rsc_table_parser are all internal use only. Move this header out of that location. Signed-off-by: Andrew Davis <afd@ti.com> | 3 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 7 年前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 3 个月前 |