On Wed, 21 Jan, at 11:06:33AM, Borislav Petkov wrote:
> On Wed, Jan 21, 2015 at 12:48:58AM -0500, Jon Masters wrote:
> > We have on a number of occasions found just this output useful in
> > debugging boot issues on ARM servers
>
> We can turn it on by default on ARM and off on x86...
Yeah,
On Wed, 21 Jan, at 11:06:33AM, Borislav Petkov wrote:
On Wed, Jan 21, 2015 at 12:48:58AM -0500, Jon Masters wrote:
We have on a number of occasions found just this output useful in
debugging boot issues on ARM servers
We can turn it on by default on ARM and off on x86...
Yeah, there's no
On Wed, Jan 21, 2015 at 12:48:58AM -0500, Jon Masters wrote:
> We have on a number of occasions found just this output useful in
> debugging boot issues on ARM servers
We can turn it on by default on ARM and off on x86...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you
On Wed, Jan 21, 2015 at 12:48:58AM -0500, Jon Masters wrote:
We have on a number of occasions found just this output useful in
debugging boot issues on ARM servers
We can turn it on by default on ARM and off on x86...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
On 1/5/15, 10:00 AM, Laszlo Ersek wrote:
On 01/05/15 15:03, Matt Fleming wrote:
On Wed, 10 Dec, at 11:46:28AM, Borislav Petkov wrote:
On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
I have same feeling with you, it is too long for most of people.
Since the printk code are for
On 1/5/15, 10:00 AM, Laszlo Ersek wrote:
On 01/05/15 15:03, Matt Fleming wrote:
On Wed, 10 Dec, at 11:46:28AM, Borislav Petkov wrote:
On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
I have same feeling with you, it is too long for most of people.
Since the printk code are for
On 01/05/15 15:03, Matt Fleming wrote:
> On Wed, 10 Dec, at 11:46:28AM, Borislav Petkov wrote:
>> On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
>>> I have same feeling with you, it is too long for most of people.
>>>
>>> Since the printk code are for EFI_DEBUG, they are around the
On Wed, 10 Dec, at 11:46:28AM, Borislav Petkov wrote:
> On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
> > I have same feeling with you, it is too long for most of people.
> >
> > Since the printk code are for EFI_DEBUG, they are around the #ifdef
> > so I would like to see a kernel
On Wed, 10 Dec, at 11:46:28AM, Borislav Petkov wrote:
On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
I have same feeling with you, it is too long for most of people.
Since the printk code are for EFI_DEBUG, they are around the #ifdef
so I would like to see a kernel param like
On 01/05/15 15:03, Matt Fleming wrote:
On Wed, 10 Dec, at 11:46:28AM, Borislav Petkov wrote:
On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
I have same feeling with you, it is too long for most of people.
Since the printk code are for EFI_DEBUG, they are around the #ifdef
so I
On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
> I have same feeling with you, it is too long for most of people.
>
> Since the printk code are for EFI_DEBUG, they are around the #ifdef
> so I would like to see a kernel param like efi_debug=on, so only
> efi_debug is specified then
On Wed, Dec 10, 2014 at 10:17:41AM +0800, Dave Young wrote:
I have same feeling with you, it is too long for most of people.
Since the printk code are for EFI_DEBUG, they are around the #ifdef
so I would like to see a kernel param like efi_debug=on, so only
efi_debug is specified then these
On 12/09/14 at 10:58am, Borislav Petkov wrote:
> Hi guys,
>
> so this decoded EFI regions output is nice but can we shorten it? It
> sticks too far out in the terminal more than anything else in dmesg and
> staring at it needs me to resize window and such. It probably is an even
> bigger problem
On Tue, Dec 09, 2014 at 04:35:33PM +0100, Laszlo Ersek wrote:
> I disagree with the patch in general, and I strongly disagree with this
> specific change in particular. This part:
>
> - breaks the alignment for the right side of the table
Well, we can start by removing the sizes - they're
On 12/09/14 10:58, Borislav Petkov wrote:
> Hi guys,
>
> so this decoded EFI regions output is nice but can we shorten it? It
> sticks too far out in the terminal more than anything else in dmesg and
> staring at it needs me to resize window and such. It probably is an even
> bigger problem if
On Tue, Dec 09, 2014 at 01:42:44PM +0100, Ard Biesheuvel wrote:
> The |] thing is easily fixed, though.
>
> [...]
> > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
> > index 8590099ac148..6734072980ee 100644
> > --- a/drivers/firmware/efi/efi.c
> > +++
On 9 December 2014 at 10:58, Borislav Petkov wrote:
> Hi guys,
>
> so this decoded EFI regions output is nice but can we shorten it? It
> sticks too far out in the terminal more than anything else in dmesg and
> staring at it needs me to resize window and such. It probably is an even
> bigger
Hi guys,
so this decoded EFI regions output is nice but can we shorten it? It
sticks too far out in the terminal more than anything else in dmesg and
staring at it needs me to resize window and such. It probably is an even
bigger problem if one's monitor hasn't switched to higher res early
during
Hi guys,
so this decoded EFI regions output is nice but can we shorten it? It
sticks too far out in the terminal more than anything else in dmesg and
staring at it needs me to resize window and such. It probably is an even
bigger problem if one's monitor hasn't switched to higher res early
during
On 9 December 2014 at 10:58, Borislav Petkov b...@alien8.de wrote:
Hi guys,
so this decoded EFI regions output is nice but can we shorten it? It
sticks too far out in the terminal more than anything else in dmesg and
staring at it needs me to resize window and such. It probably is an even
On Tue, Dec 09, 2014 at 01:42:44PM +0100, Ard Biesheuvel wrote:
The |] thing is easily fixed, though.
[...]
diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
index 8590099ac148..6734072980ee 100644
--- a/drivers/firmware/efi/efi.c
+++ b/drivers/firmware/efi/efi.c
On 12/09/14 10:58, Borislav Petkov wrote:
Hi guys,
so this decoded EFI regions output is nice but can we shorten it? It
sticks too far out in the terminal more than anything else in dmesg and
staring at it needs me to resize window and such. It probably is an even
bigger problem if one's
On Tue, Dec 09, 2014 at 04:35:33PM +0100, Laszlo Ersek wrote:
I disagree with the patch in general, and I strongly disagree with this
specific change in particular. This part:
- breaks the alignment for the right side of the table
Well, we can start by removing the sizes - they're useless
On 12/09/14 at 10:58am, Borislav Petkov wrote:
Hi guys,
so this decoded EFI regions output is nice but can we shorten it? It
sticks too far out in the terminal more than anything else in dmesg and
staring at it needs me to resize window and such. It probably is an even
bigger problem if
24 matches
Mail list logo
