On Wed, 27 Jul 2022 at 15:11, Daniel Henrique Barboza
wrote:
>
>
>
> On 7/26/22 15:24, Peter Maydell wrote:
> > On Tue, 26 Jul 2022 at 19:23, Peter Maydell
> > wrote:
> >>
> >> In dcr_write_dma(), there is code that uses cpu_physical_memory_map()
> >> to implement a DMA transfer. That function
On 7/26/22 15:24, Peter Maydell wrote:
On Tue, 26 Jul 2022 at 19:23, Peter Maydell wrote:
In dcr_write_dma(), there is code that uses cpu_physical_memory_map()
to implement a DMA transfer. That function takes a 'plen' argument,
which points to a hwaddr which is used for both input and
On 7/26/22 11:23, Peter Maydell wrote:
In dcr_write_dma(), there is code that uses cpu_physical_memory_map()
to implement a DMA transfer. That function takes a 'plen' argument,
which points to a hwaddr which is used for both input and output: the
caller must set it to the size of the range it
On Tue, 26 Jul 2022 at 19:23, Peter Maydell wrote:
>
> In dcr_write_dma(), there is code that uses cpu_physical_memory_map()
> to implement a DMA transfer. That function takes a 'plen' argument,
> which points to a hwaddr which is used for both input and output: the
> caller must set it to the
In dcr_write_dma(), there is code that uses cpu_physical_memory_map()
to implement a DMA transfer. That function takes a 'plen' argument,
which points to a hwaddr which is used for both input and output: the
caller must set it to the size of the range it wants to map, and on
return it is updated
