Le 02/11/2019 à 20:54, Philippe Mathieu-Daudé a écrit :
> On 11/2/19 7:10 PM, Laurent Vivier wrote:
>> Paolo,
>>
>> the RFC was mainly for you:
>>
>> Is this the good way to replicate 256 times a memory chunk containing a
>> bunch of different MMIO spaces?
>
> I asked Richard about this and he sai
On 11/2/19 7:10 PM, Laurent Vivier wrote:
Paolo,
the RFC was mainly for you:
Is this the good way to replicate 256 times a memory chunk containing a
bunch of different MMIO spaces?
I asked Richard about this and he said this is OK because this is
the FlatView memory tree. It is then optimized
Paolo,
the RFC was mainly for you:
Is this the good way to replicate 256 times a memory chunk containing a
bunch of different MMIO spaces?
...
> +/*
> + * Memory from VIA_BASE to VIA_BASE + 0x4 is repeated
> + * from VIA_BASE + 0x4 to VIA_BASE + 0x400
> + */
> +fo
Le 01/11/2019 à 01:00, Philippe Mathieu-Daudé a écrit :
> On 10/31/19 11:03 AM, Laurent Vivier wrote:
>> Linux kernel 5.4 will introduce a new memory map for SWIM device.
>> (aee6bff1c325 ("m68k: mac: Revisit floppy disc controller base
>> addresses"))
>>
>> Until this release all MMIO are mapped b
On 10/31/19 11:03 AM, Laurent Vivier wrote:
Linux kernel 5.4 will introduce a new memory map for SWIM device.
(aee6bff1c325 ("m68k: mac: Revisit floppy disc controller base addresses"))
Until this release all MMIO are mapped between 0x50f0 and 0x50f4,
but it appears that for real hardwar
Linux kernel 5.4 will introduce a new memory map for SWIM device.
(aee6bff1c325 ("m68k: mac: Revisit floppy disc controller base addresses"))
Until this release all MMIO are mapped between 0x50f0 and 0x50f4,
but it appears that for real hardware 0x50f0 is not the base address:
the MMIO
