On Mon, May 2, 2016 at 8:39 AM, Riku Voipio wrote:
>> #1 is not strictly needed, as the driver would default to using a
>> random MAC. and I don't think what we do is nice enough to be
>> upstream... we can discuss more..
>
> The problem is common, no-one can bother an extra chip to store a
> mac
On 29 April 2016 at 17:05, Nicolas Dechesne wrote:
> On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salveti
> wrote:
>>
>>> wcnss-config: 1.8
>>> optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1
>>> glshim: 0.41+git20150911.42a7739-0.linarojessie.1
>>
>> We should be able to get these in debian.
May
On 30 April 2016 at 08:25, Fathi Boudra wrote:
> Hi Riku,
>
> On 29 April 2016 at 16:06, Riku Voipio wrote:
>> One of the goals of RPB is to follow that our changes go back
>> upstream. For the next RPB release, a more polished report is planned.
>> But to get things started, here's a sample - an
Hi Riku,
On 29 April 2016 at 16:06, Riku Voipio wrote:
> One of the goals of RPB is to follow that our changes go back
> upstream. For the next RPB release, a more polished report is planned.
> But to get things started, here's a sample - and to use as baseline to
> compare progress for the 16.06
On 04/29/2016 07:06 AM, Riku Voipio wrote:
> One of the goals of RPB is to follow that our changes go back
> upstream. For the next RPB release, a more polished report is planned.
> But to get things started, here's a sample - and to use as baseline to
> compare progress for the 16.06 release. The
On Fri, Apr 29, 2016 at 11:05 AM, Nicolas Dechesne
wrote:
> On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salveti
> wrote:
>>
>>> wcnss-config: 1.8
>>> optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1
>>> glshim: 0.41+git20150911.42a7739-0.linarojessie.1
>>
>> We should be able to get these in debia
On Fri, Apr 29, 2016 at 3:56 PM, Ricardo Salveti
wrote:
>
>> wcnss-config: 1.8
>> optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1
>> glshim: 0.41+git20150911.42a7739-0.linarojessie.1
>
> We should be able to get these in debian.
wcnss-config shouldn't go upstream, imho. at least not in its cur
On Fri, Apr 29, 2016 at 10:21 AM, Nicolas Dechesne
wrote:
> On Fri, Apr 29, 2016 at 3:06 PM, Riku Voipio wrote:
>> One of the goals of RPB is to follow that our changes go back
>> upstream. For the next RPB release, a more polished report is planned.
>> But to get things started, here's a sample
On Fri, Apr 29, 2016 at 10:06 AM, Riku Voipio wrote:
> One of the goals of RPB is to follow that our changes go back
> upstream. For the next RPB release, a more polished report is planned.
> But to get things started, here's a sample - and to use as baseline to
> compare progress for the 16.06 re
On Fri, Apr 29, 2016 at 3:06 PM, Riku Voipio wrote:
> One of the goals of RPB is to follow that our changes go back
> upstream. For the next RPB release, a more polished report is planned.
> But to get things started, here's a sample - and to use as baseline to
> compare progress for the 16.06 rel
One of the goals of RPB is to follow that our changes go back
upstream. For the next RPB release, a more polished report is planned.
But to get things started, here's a sample - and to use as baseline to
compare progress for the 16.06 release. The list of packages is
collected from db410/alip image
11 matches
Mail list logo
