On 28.03.24 16:48, Kinsey Moore wrote:
This patch set looks good to me. I'd suggest a different file for the
versal unless there's a good name that can easily cover both.
The versal BSP doesn't use this driver and seems to have a different
hardware UART interface. It uses a BSP-specific driver
Hello,
I am Purva Yeshi, I applied for the project "Add BSP for Polarfire based
Beagle" for GSoC 2024. I proposed a project to create a BSP for the
Beagle-V fire board from scratch. The primary objective of the project is
to run a "Hello World" code and a ticker on the board. After that, I will
fo
Hi Purva,
On Thu, Apr 4, 2024 at 6:05 AM Purva Yeshi wrote:
> Hello,
>
> I am Purva Yeshi, I applied for the project "Add BSP for Polarfire based
> Beagle" for GSoC 2024. I proposed a project to create a BSP for the
> Beagle-V fire board from scratch. The primary objective of the project is
>
On 4/4/2024 8:19 pm, Sebastian Huber wrote:
> On 28.03.24 16:48, Kinsey Moore wrote:
>> This patch set looks good to me. I'd suggest a different file for the versal
>> unless there's a good name that can easily cover both.
>
> The versal BSP doesn't use this driver and seems to have a different
Just a late note to say thanks for the direction Sebastien. What you suggest
makes sense to me, requiring (and enforcing) that vector registers not be used
within _RISCV_Interrupt_dispatch() while preserving the vector state across
_Thread_Do_dispatch(). (ref: cpukit/score/cpu/riscv/riscv-exce
