Re: remoteproc open issues (was [RFC 1/4] remoteproc: Bugfix assign device address to carveout (noiommu)

2012-10-19 Thread Ohad Ben-Cohen
On Fri, Oct 19, 2012 at 3:45 PM, Sjur Brændeland wrote: > Has anyone started looking into any of the open issues mentioned above? No - feel free to take a stab at it. Thanks, Ohad. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

remoteproc open issues (was [RFC 1/4] remoteproc: Bugfix assign device address to carveout (noiommu)

2012-10-19 Thread Sjur Brændeland
Hi, On Fri, Aug 10, 2012 at 5:30 PM, Ohad Ben-Cohen wrote: > The general direction I have in mind is to put the resource table in > its final location while we do the first pass of fw parsing. > > This will solve all sort of open issues we have (or going to have soon): > > 1.

remoteproc open issues (was [RFC 1/4] remoteproc: Bugfix assign device address to carveout (noiommu)

2012-10-19 Thread Sjur Brændeland
Hi, On Fri, Aug 10, 2012 at 5:30 PM, Ohad Ben-Cohen o...@wizery.com wrote: The general direction I have in mind is to put the resource table in its final location while we do the first pass of fw parsing. This will solve all sort of open issues we have (or going to have soon): 1.

Re: remoteproc open issues (was [RFC 1/4] remoteproc: Bugfix assign device address to carveout (noiommu)

2012-10-19 Thread Ohad Ben-Cohen
On Fri, Oct 19, 2012 at 3:45 PM, Sjur Brændeland sjurb...@gmail.com wrote: Has anyone started looking into any of the open issues mentioned above? No - feel free to take a stab at it. Thanks, Ohad. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message