On Fri, 24 Aug 2018, Julien Grall wrote:
> > > > +
> > > > +bool zynqmp_eemi(struct cpu_user_regs *regs)
> > > > +{
> > > > +return false;
> > > > +}
> > > > +
> > > > +/*
> > > > + * Local variables:
> > > > + * mode: C
> > > > + * c-file-style: "BSD"
> > > > + * c-basic-offset: 4
> > > > + *
Hi,
On 24/08/18 00:56, Stefano Stabellini wrote:
On Thu, 23 Aug 2018, Julien Grall wrote:
Hi Stefano,
2018 01:01 AM, Stefano Stabellini wrote:
From: "Edgar E. Iglesias"
From: Edgar E. Iglesias
Introduce zynqmp_eemi: a function resposible for implementing access
On Thu, 23 Aug 2018, Julien Grall wrote:
> Hi Stefano,
>
> 2018 01:01 AM, Stefano Stabellini wrote:
> > From: "Edgar E. Iglesias"
> >
> > From: Edgar E. Iglesias
> >
> > Introduce zynqmp_eemi: a function resposible for implementing access
>
> s/resposible/responsible/
I'll fix
> >
Hi Stefano,
2018 01:01 AM, Stefano Stabellini wrote:
From: "Edgar E. Iglesias"
From: Edgar E. Iglesias
Introduce zynqmp_eemi: a function resposible for implementing access
s/resposible/responsible/
controls over the firmware calls. Only calls that are allowed are
forwarded to the
From: "Edgar E. Iglesias"
From: Edgar E. Iglesias
Introduce zynqmp_eemi: a function resposible for implementing access
controls over the firmware calls. Only calls that are allowed are
forwarded to the firmware.
Signed-off-by: Edgar E. Iglesias
Signed-off-by: Stefano Stabellini
---
