Re: [PATCH 1/1] riscv: set fdtfile on VisionFive 2

2023-09-25 Thread Leo Liang
On Fri, Sep 22, 2023 at 09:54:23PM +0800, Shengyu Qu wrote: > Hello Leo, > > This patch seems only landed in next branch, not master. It is seriously > > needed to make visionfive 2 working properly. Could you merge it to > > master branch? > > Best regards, > > Shengyu > Hi Shengyu, Got i

Re: [PATCH 1/1] riscv: set fdtfile on VisionFive 2

2023-09-22 Thread Shengyu Qu
Hello Leo, This patch seems only landed in next branch, not master. It is seriously needed to make visionfive 2 working properly. Could you merge it to master branch? Best regards, Shengyu Multiple revisions of the StarFive VisionFive 2 board exist. They can be identified by reading their E

Re: [PATCH 1/1] riscv: set fdtfile on VisionFive 2

2023-09-21 Thread Milan P . Stanić
On Thu, 2023-09-07 at 13:21, Heinrich Schuchardt wrote: > Multiple revisions of the StarFive VisionFive 2 board exist. They can be > identified by reading their EEPROM. > > Linux uses two differently named device-tree files. To load the correct > device-tree we need to set $fdtfile to the device-t

Re: [PATCH 1/1] riscv: set fdtfile on VisionFive 2

2023-09-13 Thread Leo Liang
On Thu, Sep 07, 2023 at 01:21:28PM +0200, Heinrich Schuchardt wrote: > Multiple revisions of the StarFive VisionFive 2 board exist. They can be > identified by reading their EEPROM. > > Linux uses two differently named device-tree files. To load the correct > device-tree we need to set $fdtfile to

[PATCH 1/1] riscv: set fdtfile on VisionFive 2

2023-09-07 Thread Heinrich Schuchardt
Multiple revisions of the StarFive VisionFive 2 board exist. They can be identified by reading their EEPROM. Linux uses two differently named device-tree files. To load the correct device-tree we need to set $fdtfile to the device-tree file name that matches the board revision. Signed-off-by: Hei