On Sun, Sep 27, 2015 at 11:01 AM, Max Filippov wrote:
> On Sun, Sep 27, 2015 at 8:42 PM, Peter Crosthwaite
> wrote:
>> On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wrote:
>>> XTFPGA FLASH is tied to XTFPGA system IO block. It's not very important
>>> for systems with MMU where system IO block
On Sun, Sep 27, 2015 at 8:42 PM, Peter Crosthwaite
wrote:
> On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wrote:
>> XTFPGA FLASH is tied to XTFPGA system IO block. It's not very important
>> for systems with MMU where system IO block is visible at single
>> location,
>
> Are your relying on a ma
On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wrote:
> XTFPGA FLASH is tied to XTFPGA system IO block. It's not very important
> for systems with MMU where system IO block is visible at single
> location,
Are your relying on a matching change in the guest for MMU setup here?
Can you explain a li
XTFPGA FLASH is tied to XTFPGA system IO block. It's not very important
for systems with MMU where system IO block is visible at single
location, but it's important for noMMU systems, where system IO block is
accessible through two separate physical address ranges.
Map XTFPGA FLASH to system IO bl
