On Sat, Apr 30, 2016 at 11:35:14PM +0100, Matt Fleming wrote:
> (Adding Colin and Ricardo)
>
> On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote:
> >
> > How is an end user supposed to see such a message and report it to the
> > people that can fix it? They can't. So they report it in their
> >
On Sat, Apr 30, 2016 at 11:35:14PM +0100, Matt Fleming wrote:
> (Adding Colin and Ricardo)
>
> On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote:
> >
> > How is an end user supposed to see such a message and report it to the
> > people that can fix it? They can't. So they report it in their
> >
On 30/04/16 23:35, Matt Fleming wrote:
> (Adding Colin and Ricardo)
>
> On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote:
>>
>> How is an end user supposed to see such a message and report it to the
>> people that can fix it? They can't. So they report it in their
>> distributions bug tracker
On 30/04/16 23:35, Matt Fleming wrote:
> (Adding Colin and Ricardo)
>
> On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote:
>>
>> How is an end user supposed to see such a message and report it to the
>> people that can fix it? They can't. So they report it in their
>> distributions bug tracker
(Adding Colin and Ricardo)
On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote:
>
> How is an end user supposed to see such a message and report it to the
> people that can fix it? They can't. So they report it in their
> distributions bug tracker and it either gets closed as "yeah, firmware
>
(Adding Colin and Ricardo)
On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote:
>
> How is an end user supposed to see such a message and report it to the
> people that can fix it? They can't. So they report it in their
> distributions bug tracker and it either gets closed as "yeah, firmware
>
On Wed, Apr 27, 2016 at 1:05 PM, Josh Triplett wrote:
> On Wed, Apr 27, 2016 at 11:20:26AM -0400, Josh Boyer wrote:
>> On Wed, Apr 27, 2016 at 10:57 AM, Môshe van der Sterre wrote:
>> >
>> > On 04/27/2016 03:56 PM, Josh Boyer wrote:
>> >>
>> >> On Wed, Apr
On Wed, Apr 27, 2016 at 1:05 PM, Josh Triplett wrote:
> On Wed, Apr 27, 2016 at 11:20:26AM -0400, Josh Boyer wrote:
>> On Wed, Apr 27, 2016 at 10:57 AM, Môshe van der Sterre wrote:
>> >
>> > On 04/27/2016 03:56 PM, Josh Boyer wrote:
>> >>
>> >> On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der
On Wed, Apr 27, 2016 at 11:20:26AM -0400, Josh Boyer wrote:
> On Wed, Apr 27, 2016 at 10:57 AM, Môshe van der Sterre wrote:
> >
> > On 04/27/2016 03:56 PM, Josh Boyer wrote:
> >>
> >> On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre
> >> wrote:
> >>>
> >>>
On Wed, Apr 27, 2016 at 11:20:26AM -0400, Josh Boyer wrote:
> On Wed, Apr 27, 2016 at 10:57 AM, Môshe van der Sterre wrote:
> >
> > On 04/27/2016 03:56 PM, Josh Boyer wrote:
> >>
> >> On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre
> >> wrote:
> >>>
> >>> (additionally CC-ing Josh
On Wed, Apr 27, 2016 at 10:57 AM, Môshe van der Sterre wrote:
>
> On 04/27/2016 03:56 PM, Josh Boyer wrote:
>>
>> On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre wrote:
>>>
>>> (additionally CC-ing Josh Triplett)
>>
>> Thanks for doing so. I completely
On Wed, Apr 27, 2016 at 10:57 AM, Môshe van der Sterre wrote:
>
> On 04/27/2016 03:56 PM, Josh Boyer wrote:
>>
>> On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre wrote:
>>>
>>> (additionally CC-ing Josh Triplett)
>>
>> Thanks for doing so. I completely forgot.
>>
>>> On 04/27/2016 02:50
On 04/27/2016 03:56 PM, Josh Boyer wrote:
On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre wrote:
(additionally CC-ing Josh Triplett)
Thanks for doing so. I completely forgot.
On 04/27/2016 02:50 PM, Josh Boyer wrote:
The promise of pretty boot splashes from firmware
On 04/27/2016 03:56 PM, Josh Boyer wrote:
On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre wrote:
(additionally CC-ing Josh Triplett)
Thanks for doing so. I completely forgot.
On 04/27/2016 02:50 PM, Josh Boyer wrote:
The promise of pretty boot splashes from firmware via BGRT was at
On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre wrote:
> (additionally CC-ing Josh Triplett)
Thanks for doing so. I completely forgot.
> On 04/27/2016 02:50 PM, Josh Boyer wrote:
>>
>> The promise of pretty boot splashes from firmware via BGRT was at
>> best only that; a
On Wed, Apr 27, 2016 at 9:26 AM, Môshe van der Sterre wrote:
> (additionally CC-ing Josh Triplett)
Thanks for doing so. I completely forgot.
> On 04/27/2016 02:50 PM, Josh Boyer wrote:
>>
>> The promise of pretty boot splashes from firmware via BGRT was at
>> best only that; a promise. The
(additionally CC-ing Josh Triplett)
On 04/27/2016 02:50 PM, Josh Boyer wrote:
The promise of pretty boot splashes from firmware via BGRT was at
best only that; a promise. The kernel diligently checks to make
sure the BGRT data firmware gives it is valid, and dutifully warns
the user when it
(additionally CC-ing Josh Triplett)
On 04/27/2016 02:50 PM, Josh Boyer wrote:
The promise of pretty boot splashes from firmware via BGRT was at
best only that; a promise. The kernel diligently checks to make
sure the BGRT data firmware gives it is valid, and dutifully warns
the user when it
The promise of pretty boot splashes from firmware via BGRT was at
best only that; a promise. The kernel diligently checks to make
sure the BGRT data firmware gives it is valid, and dutifully warns
the user when it isn't. However, it does so via the pr_err log
level which seems unnecessary. The
The promise of pretty boot splashes from firmware via BGRT was at
best only that; a promise. The kernel diligently checks to make
sure the BGRT data firmware gives it is valid, and dutifully warns
the user when it isn't. However, it does so via the pr_err log
level which seems unnecessary. The
20 matches
Mail list logo