On Mon, 2016-06-27 at 20:45 +0200, Patrik Jakobsson wrote:
> On Mon, Jun 27, 2016 at 7:12 PM, Vivi, Rodrigo m> wrote:
> >
> > On Mon, 2016-06-27 at 19:51 +0300, Imre Deak wrote:
> > >
> > > On Mon, 2016-06-27 at 19:32 +0300, Vivi, Rodrigo wrote:
> > > >
> > > >
> > > > On Mon, 2016-06-27 at 14
On Mon, Jun 27, 2016 at 7:12 PM, Vivi, Rodrigo wrote:
> On Mon, 2016-06-27 at 19:51 +0300, Imre Deak wrote:
>> On Mon, 2016-06-27 at 19:32 +0300, Vivi, Rodrigo wrote:
>> >
>> > On Mon, 2016-06-27 at 14:20 +0300, Imre Deak wrote:
>> > >
>> > > Adding Christophe, he was supposed to make the release
On Mon, 2016-06-27 at 19:51 +0300, Imre Deak wrote:
> On Mon, 2016-06-27 at 19:32 +0300, Vivi, Rodrigo wrote:
> >
> > On Mon, 2016-06-27 at 14:20 +0300, Imre Deak wrote:
> > >
> > > Adding Christophe, he was supposed to make the release after
> > > validation.
> > Apparently we are almost ready t
On Mon, 2016-06-27 at 19:32 +0300, Vivi, Rodrigo wrote:
> On Mon, 2016-06-27 at 14:20 +0300, Imre Deak wrote:
> > Adding Christophe, he was supposed to make the release after
> > validation.
>
> Apparently we are almost ready to release and one latest round of
> final
> validation was pending.
>
On Mon, 2016-06-27 at 14:20 +0300, Imre Deak wrote:
> Adding Christophe, he was supposed to make the release after
> validation.
Apparently we are almost ready to release and one latest round of final
validation was pending.
Christophe, any news on this front?
> I don't think it prevents mergin
Adding Christophe, he was supposed to make the release after
validation. I don't think it prevents merging this patch though, the
result is failure to load the firmware in either case.
--Imre
On ma, 2016-06-27 at 12:57 +0200, Patrik Jakobsson wrote:
> On Wed, Jun 15, 2016 at 12:11:55AM +, Viv
On Wed, Jun 15, 2016 at 12:11:55AM +, Vivi, Rodrigo wrote:
> On Mon, 2016-05-23 at 10:57 +0200, Patrik Jakobsson wrote:
> > On Wed, May 18, 2016 at 01:24:12PM +0300, Mika Kuoppala wrote:
> > > Patrik Jakobsson writes:
> > >
> > > > [ text/plain ]
> > > > Load specific firmware versions for th
On Mon, 2016-05-23 at 10:57 +0200, Patrik Jakobsson wrote:
> On Wed, May 18, 2016 at 01:24:12PM +0300, Mika Kuoppala wrote:
> > Patrik Jakobsson writes:
> >
> > > [ text/plain ]
> > > Load specific firmware versions for the DMC instead of using
> > > symbolic
> > > links. The currently recommende
On Wed, May 18, 2016 at 01:24:12PM +0300, Mika Kuoppala wrote:
> Patrik Jakobsson writes:
>
> > [ text/plain ]
> > Load specific firmware versions for the DMC instead of using symbolic
> > links. The currently recommended versions are: SKL 1.26, KBL 1.01 and
> > BXT 1.07.
> >
> > Certain DMC vers
Patrik Jakobsson writes:
> [ text/plain ]
> Load specific firmware versions for the DMC instead of using symbolic
> links. The currently recommended versions are: SKL 1.26, KBL 1.01 and
> BXT 1.07.
>
> Certain DMC versions need workarounds in the driver which forces us to
> have a tight dependenc
On Mon, 16 May 2016, Patrik Jakobsson wrote:
> Load specific firmware versions for the DMC instead of using symbolic
> links. The currently recommended versions are: SKL 1.26, KBL 1.01 and
> BXT 1.07.
>
> Certain DMC versions need workarounds in the driver which forces us to
> have a tight depende
Load specific firmware versions for the DMC instead of using symbolic
links. The currently recommended versions are: SKL 1.26, KBL 1.01 and
BXT 1.07.
Certain DMC versions need workarounds in the driver which forces us to
have a tight dependency between firmware and driver. In order to be able
to p
12 matches
Mail list logo
