Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: VizaH9XDHOx1qaqN8ofkC3RA7qta1UewHmFAl9H+US3zqyXJYPt/KcnKdR8QFItlQuvLw2epbP
 axygVI6+VMnT4hl9mz0l9dLrjtS7ljd3SATUJxPBAOyA4OiKrsJ3Pe6CmfLchYEdmfGEkDPmNb
 ZBs3nNBpWv2bjSuxWNUnnF5YScCf15aJlR1BQ7VN5MGJSxJaHxID8keADTDU93kR6gVuSbHsxo
 +LHNK2gFcLGxoH5R1NcktchM+CYHy94aoGidzveCRGyyytg/IxPmKzmQzbDvwHFm9I3DOKgmGo
 N2zQE2kH9FlsvGEzY9F7KLlw
IronPort-SDR: mZPVRNCcrQg0GSMxctVrj1B5CpZbH7XSaburiAROp35ljKYTcDnD7YqZpudMdcVzJPjHEtlf/S
 1uqeXAJnPE0UZ/3c6R2Pk7j78VC8oOs9gLqyg2q7YyrLKBhiVvcLgIW11IsXT5PINBLUpXfcSm
 IENFtq8Mek+1AmrB9IWraE/UF6lpzk4Oxn8wNXx/5XBFpfVEO1id3M5kgHGhPqgJS+EmG9TpiU
 LF7dd2EnHy+L3E2P+xnmU6TwO0HI6C/SVbZVHOpY7WDi59NFAs7L8c+b4jOYTHDGKvSMXbLwEw
 Jw0=
WDCIronportException: Internal
Message-ID: <730eae0f-6d79-f84b-fe63-a1c4223d7379@opensource.wdc.com>
Date:   Fri, 21 Jan 2022 08:29:50 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.5.0
Subject: Re:
Content-Language: en-US
To:     Vitaly Wool <vitaly.wool@konsulko.com>,
        Myrtle Shah <gatecat@ds0.me>
Cc:     linux-riscv <linux-riscv@lists.infradead.org>,
        Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        LKML <linux-kernel@vger.kernel.org>
References: <20220120152828.4089364-1-gatecat@ds0.me>
 <CAM4kBBJqHVX_Q2C0VO7qKNZywRiWbHK9t0G076ov6u+_gwO2=A@mail.gmail.com>
From:   Damien Le Moal <damien.lemoal@opensource.wdc.com>
Organization: Western Digital
In-Reply-To: <CAM4kBBJqHVX_Q2C0VO7qKNZywRiWbHK9t0G076ov6u+_gwO2=A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2022/01/21 0:37, Vitaly Wool wrote:
> Hey,
> 
> On Thu, Jan 20, 2022 at 4:30 PM Myrtle Shah <gatecat@ds0.me> wrote:
>>
>> These are some initial patches to bugs I found attempting to
>> get a XIP kernel working on hardware:
>>  - 32-bit VexRiscv processor
>>  - kernel in SPI flash, at 0x00200000
>>  - 16MB of RAM at 0x10000000
>>  - MMU enabled
>>
>> I still have some more debugging to do, but these at least
>> get the kernel as far as initialising the MMU, and I would
>> appreciate feedback if anyone else is working on RISC-V XIP.
> 
> I'll try to support you as much as I can, unfortunately I don't have
> any 32-bit RISC-V around so I was rather thinking of extending the
> RISC-V XIP support to 64-bit non-MMU targets.

That would be great ! I am completing the buildroot patches for the K210. Got
u-boot almost working for SD card boot too (fighting a problem with rootfs
kernel mount on boot when using u-boot though).

> For now just please keep in mind that there might be some inherent
> assumptions that a target is 64 bit.
> 
> Best regards,
> Vitaly
> 
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv


-- 
Damien Le Moal
Western Digital Research