Hi Ludovic,
On Tue, May 22, 2012 at 3:51 PM, frq09524 ludovic.ba...@stericsson.com wrote:
In my previous patch, to find the correct subdevice that match with physical
memory, I used pa member of rproc_mem_entry.
I'm not sure we want to find these subdevices using the physical
memory of the
Hi Michal,
On Tue, May 22, 2012 at 8:51 AM, Michal Simek mon...@monstr.eu 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
Hi Ohad and Michal
yes I can share my patch, remoteproc has evolved and my patch is not
aligned on latest version of remote proc (especially since remoteproc:
remove the single rpmsg vdev limitation).
Ohad, for alignment I can take the latest branch of kernel.org
(remoteproc) branch
Hi Ludovic,
On Tue, May 22, 2012 at 12:14 PM, frq09524 ludovic.ba...@stericsson.com wrote:
Ohad, for alignment I can take the latest branch of kernel.org (remoteproc)
branch for-next?
Sure, it's pretty much updated sans a few simple changes.
Thanks,
Ohad.
--
To unsubscribe from this list:
hi Ohad
In my previous patch, to find the correct subdevice that match with
physical memory, I used pa member of rproc_mem_entry.
but today in these 2 resources: fw_rsc_trace, fw_rsc_vdev_vring, pa
menber has been removed.
for fw_rsc_trace it's not a problem, because use rproc_da_to_va and
Hi Michal,
On Mon, May 21, 2012 at 4:02 PM, Michal Simek mon...@monstr.eu wrote:
I have looked at it and tested on latest and greatest and the problem is
still there.
Ok, I see why this is happening.
We're now allocating the vrings' DMA in -find_vqs() just before we
boot the remote processor,
Hi Michal,
On Sat, Mar 17, 2012 at 8:39 AM, Ohad Ben-Cohen o...@wizery.com wrote:
IOW: you can probably just wait a bit until this patch is ready and
take it into your tree. It will most likely bring back the behavior you
need :)
Does something like the attached help ?
Thanks,
Ohad.
Hi Ohad,
On Fri, Mar 16, 2012 at 4:57 PM, Michal Simek mon...@monstr.eu wrote:
In previous version I had carverout first which means that code was copyied
to physical address 0x0 and then vrigns were allocated. Current code
allocate vring first and then RTOS is not able to run from zero
Hi Michal,
On Fri, Mar 16, 2012 at 4:57 PM, Michal Simek mon...@monstr.eu wrote:
In previous version I had carverout first which means that code was copyied
to physical address 0x0 and then vrigns were allocated. Current code
allocate vring first and then RTOS is not able to run from zero
Hi Ohad,
Ohad Ben-Cohen wrote:
The resource table is an array of 'struct fw_resource' members, where
each resource entry is expressed as a single member of that array.
This approach got us this far, but it has a few drawbacks:
1. Different resource entries end up overloading the same members
10 matches
Mail list logo
