[PATCH v10 00/14] riscv: Add support for xtheadvector

[Yangyu Chen]

On 11/9/24 06:16, Jesse T wrote:
> Hey Palmer there are a bunch of merge artifacts in for-next from this
> set. Just letting you know.
> https://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git/commit/?h=for-next&id=95437f8c02b5907b5f2d7dc6c03e3c73523c5cd6
> 

I think these can be merged with keep both merge option except for the 
line "#define RISCV_HWPROBE_KEY_VENDOR_EXT_THEAD_0	9". The 9 here should 
be changed to 11.

> On Mon, Sep 30, 2024 at 11:52 AM Aoba K <nExp_0x17 at outlook.com> wrote:
>>
>> The devicetree name shown in OpenSBI is
>> the one packed with U-Boot SPL.
>> As the image builder didn't put the kernel
>> devicetree with the image under boot partition,
>> The whole boot process only uses the U-Boot device tree.
>>
>> The reason why the log shows "Nezha"
>> but not "Lichee RV" is that this log is produced
>> which U-Boot revision is d1-2022-10-31 from samuel's repo.
>> Build from d1-wip can show "Lichee RV" correctly
>> (manually edit config to specify LicheeRV dtb should have same effect though),
>> while the issue persists when kernel load to
>> the procedure same as the dmesg mentioned above.
>>
>>
>> Cheers,
>> Aoba K
>>
>> 2024年9月30日 下午10:53:40 Conor Dooley <conor at kernel.org>:
>>
>>> On Sun, Sep 29, 2024 at 12:44:07PM +0000, Aoba K wrote:
>>>> Hello Charlie,
>>>>
>>>> I've been working on bringing up the Sipeed Lichee RV Dock
>>>> (which also uses the D1 SoC) with the kernel patches you provided.
>>>> The patches applied cleanly to Palmer's for-next branch,
>>>> but I've encountered a couple of issues:
>>>>
>>>> 1. Skiffos Compilation Error during the compilation process of `cgo`:
>>>> `unknown relocation type 17; compiled without -fpic?`
>>>> Unfortunately, I closed the terminal before saving the full log,
>>>> so I don't have the complete details, but the result should be reproducible.
>>>> While this should be a SkiffOS issue, mention it in case SkiffOS is the method
>>>> that you mentioned for bringing up the device.
>>>>
>>>> 2. Image Building with sehraf/riscv-arch-image-builder:
>>>> After building the image, the device failed to start at an early stage.
>>>> I suspect this may be related to incorrect RAM size detection,
>>>> as the board only has 512MB of RAM.
>>>> Interestingly, the vendor image reports 1GB, and the Sipeed website also states
>>>> that the Dock has 1GB, despite there being no extra memory bank present.
>>>>
>>>> You can find the boot log here: https://fars.ee/bdYk.log
>>>>
>>>> Any help would be appreciated, and big thanks to your work
>>>> to make the efficient part of this board to work (again)!
>>>
>>> The log you posted at https://fars.ee/XFzR appears to be using the
>>> devicetree of a Nezha not the Lichee RV Dock. Why are you doing that,
>>> when the Lichee RV Dock is supported in the kernel already?
>>>
>>> Cheers,
>>> Conor.
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv