On Thu, Mar 30, 2023 at 5:54 PM Chris Johns wrote:
>
> On 31/3/2023 2:55 am, Alex White wrote:
> > On Wed, Mar 29, 2023 at 11:04 PM Chris Johns wrote:
> >>
> >> On 30/3/2023 12:26 pm, Sam Price wrote:
> >>> Same IP as the regular KCU105.
> >>> The current uart ip is dependent on the fpga.
> >>> I
On 31/3/2023 2:55 am, Alex White wrote:
> On Wed, Mar 29, 2023 at 11:04 PM Chris Johns wrote:
>>
>> On 30/3/2023 12:26 pm, Sam Price wrote:
>>> Same IP as the regular KCU105.
>>> The current uart ip is dependent on the fpga.
>>> I don't believe this modifies the kcu105 bsp, but allows other bsps t
On Wed, Mar 29, 2023 at 11:04 PM Chris Johns wrote:
>
> On 30/3/2023 12:26 pm, Sam Price wrote:
> > Same IP as the regular KCU105.
> > The current uart ip is dependent on the fpga.
> > I don't believe this modifies the kcu105 bsp, but allows other bsps to
> > support up to 4 uarts.
>
> I am not su
On 30/3/2023 12:26 pm, Sam Price wrote:
> Same IP as the regular KCU105.
> The current uart ip is dependent on the fpga.
> I don't believe this modifies the kcu105 bsp, but allows other bsps to
> support up to 4 uarts.
I am not sure if this patch is OK. If the UART driver is needed for a console
d
Same IP as the regular KCU105.
The current uart ip is dependent on the fpga.
I don't believe this modifies the kcu105 bsp, but allows other bsps to
support up to 4 uarts.
On Wed, Mar 29, 2023 at 5:21 PM Chris Johns wrote:
>
> On 30/3/2023 6:22 am, Alex White wrote:
> > From: "Maldonado, Sergio E.
On 30/3/2023 6:22 am, Alex White wrote:
> From: "Maldonado, Sergio E. (GSFC-580.0)" .../microblaze/microblaze_fpga/optuartirq.yml | 20 ++
> .../microblaze/microblaze_fpga/optuseuart.yml | 17 ++
> .../microblaze_fpga/optuseuart1.yml | 17 ++
> .../microblaze_fpga/optuseuart2.yml
From: "Maldonado, Sergio E. (GSFC-580.0)"
---
bsps/microblaze/include/dev/serial/uartlite.h | 2 +
.../microblaze_fpga/console/console-io.c | 229 --
bsps/microblaze/shared/dev/serial/uartlite.c | 8 +-
.../bsps/microblaze/microblaze_fpga/grp.yml | 32 +++
.../bsps/m
