On 18/03/2022 14:20, Kinsey Moore wrote:
These changes look good other than the nit in the first patch.
Thanks for the review. I will check it in once I am able to build an up
to date tool chain. Currently, if one tool chain bug is fixed another
one shows up.
--
embedded brains GmbH
Herr Se
These changes look good other than the nit in the first patch.
On 3/18/2022 02:19, Sebastian Huber wrote:
Separate the Interrupt Manager implementation from the generic Arm GICv3
support. Move parts of the Arm GICv3 support into a new header file. This
helps to support systems with a
Separate the Interrupt Manager implementation from the generic Arm GICv3
support. Move parts of the Arm GICv3 support into a new header file. This
helps to support systems with a clustered structure in which multiple GICv3
instances are present. For example, two clusters of two Cortex-R52 cores
Great, thanks! That will make initial bringup a little bit easier while
deciding whether I need to write a full GICv3 driver.
William
On Wed, Oct 24, 2018 at 6:16 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Will,
>
> On 23/10/2018 20:28, Will wrote:
> > Hi,
> > I'm cu
Hello Will,
On 23/10/2018 20:28, Will wrote:
Hi,
I'm currently doing some evaluations for an ARMv8 BSP which would
necessarily include a GIC that implements the GICv3 spec[1]. I see
that there is a shared GIC driver for ARM that seems to implement the
ARM GICv1 spec based on the BSPs in which
Hi,
I'm currently doing some evaluations for an ARMv8 BSP which would
necessarily include a GIC that implements the GICv3 spec[1]. I see that
there is a shared GIC driver for ARM that seems to implement the ARM GICv1
spec based on the BSPs in which it is used.
Is anyone aware of whether the shared
