Hi Bin,
On Tue, 30 Jul 2019 at 21:03, Bin Meng wrote:
>
> Hi Simon,
>
> On Wed, Jul 31, 2019 at 10:55 AM Simon Glass wrote:
> >
> > Hi Bin,
> >
> > On Thu, 23 May 2019 at 08:04, Bin Meng wrote:
> > >
> > > Hi Simon,
> > >
> > > On Thu, May 23, 2019 at 8:20 PM Simon Glass wrote:
> > > >
> > >
Hi Simon,
On Wed, Jul 31, 2019 at 10:55 AM Simon Glass wrote:
>
> Hi Bin,
>
> On Thu, 23 May 2019 at 08:04, Bin Meng wrote:
> >
> > Hi Simon,
> >
> > On Thu, May 23, 2019 at 8:20 PM Simon Glass wrote:
> > >
> > > Hi Bin,
> > >
> > > I'm looking at Apollo Lake and it seems to use a newer FSP
Hi Bin,
On Thu, 23 May 2019 at 08:04, Bin Meng wrote:
>
> Hi Simon,
>
> On Thu, May 23, 2019 at 8:20 PM Simon Glass wrote:
> >
> > Hi Bin,
> >
> > I'm looking at Apollo Lake and it seems to use a newer FSP version
> > (2.0). The API differences seem to be fairly minor but the packaging
> >
Hi Simon,
On Thu, May 23, 2019 at 8:20 PM Simon Glass wrote:
>
> Hi Bin,
>
> I'm looking at Apollo Lake and it seems to use a newer FSP version
> (2.0). The API differences seem to be fairly minor but the packaging
> seems a little more complicated.
>
I have investigated FSP 2.0 architecture
Hi Bin,
I'm looking at Apollo Lake and it seems to use a newer FSP version
(2.0). The API differences seem to be fairly minor but the packaging
seems a little more complicated.
I'm thinking of introducing a Kconfig for this and moving the existing
fsp implementation into an arch/x86/lib/fsp1
5 matches
Mail list logo