On 08/31/2016 11:37 AM, Bjorn Andersson wrote:
> On Tue 30 Aug 16:13 PDT 2016, Suman Anna wrote:
>
> +if (rsc->vring[i].da != 0 && rsc->vring[i].da != FW_RSC_ADDR_ANY) {
> [..]
@Suman, do you have any input on this?
>>
>
> Thanks Suman
>
>> I was thinking about this as well, and the
On Tue 30 Aug 16:13 PDT 2016, Suman Anna wrote:
> >>> +if (rsc->vring[i].da != 0 && rsc->vring[i].da != FW_RSC_ADDR_ANY) {
[..]
> >> @Suman, do you have any input on this?
>
Thanks Suman
> I was thinking about this as well, and the way I actually envisioned
> this is to add additional rproc
On 08/31/2016 01:13 AM, Suman Anna wrote:
Hi Suman,
Hi Loic, Bjorn,
On 08/29/2016 03:09 AM, loic pallardy wrote:
On 08/27/2016 02:32 AM, Bjorn Andersson wrote:
On Fri 26 Aug 13:19 PDT 2016, Loic Pallardy wrote:
Some coprocessors request fixed memory mapping for firmware execution
and
Hi Loic, Bjorn,
On 08/29/2016 03:09 AM, loic pallardy wrote:
>
>
> On 08/27/2016 02:32 AM, Bjorn Andersson wrote:
>> On Fri 26 Aug 13:19 PDT 2016, Loic Pallardy wrote:
>>
>>> Some coprocessors request fixed memory mapping for firmware execution
>>> and associated communication linked.
>>> Memory
On 08/27/2016 02:32 AM, Bjorn Andersson wrote:
On Fri 26 Aug 13:19 PDT 2016, Loic Pallardy wrote:
Some coprocessors request fixed memory mapping for firmware execution
and associated communication linked.
Memory resources are defined in firmware resource table.
Resource address different from
On Fri 26 Aug 13:19 PDT 2016, Loic Pallardy wrote:
> Some coprocessors request fixed memory mapping for firmware execution
> and associated communication linked.
> Memory resources are defined in firmware resource table.
> Resource address different from 0x0 and 0x is considered as predefi
6 matches
Mail list logo
