All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Console keyboard events and accessibility
Date: Sat, 1 Sep 2007 18:18:45 +0000	[thread overview]
Message-ID: <20070901181845.GA4839@ucw.cz> (raw)
In-Reply-To: <20070901173329.GB12644@implementation>

Hi!

> > > Very early is not so early, and loading initrd itself may actually fail.
> > > The kernel may indeed hang, but there are more chances to get some
> > > messages before the hang.  Don't _you_ have a VGA screen for getting
> > > earliest failure messages from the kernel?
> > 
> > No. I'm using framebuffer, that's initialized quite late in boot
> > process. Plus many users just use bootsplash. I do use vga mode for
> > heavy debugging, but that's quite unusual.
> 
> But that's what some people do for their work, so they need it.

How many such users are out there?

> > So... you actually have speech-enabled grub/lilo/something?
> 
> That's in project too (and there's no reason it shouldn't be done).

I'd say kernel debugging is hard without accessible bootloader, so I'd
hope number of such users is very low.
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	dtor@mail.ru
Subject: Re: [PATCH] Console keyboard events and accessibility
Date: Sat, 1 Sep 2007 18:18:45 +0000	[thread overview]
Message-ID: <20070901181845.GA4839@ucw.cz> (raw)
In-Reply-To: <20070901173329.GB12644@implementation>

Hi!

> > > Very early is not so early, and loading initrd itself may actually fail.
> > > The kernel may indeed hang, but there are more chances to get some
> > > messages before the hang.  Don't _you_ have a VGA screen for getting
> > > earliest failure messages from the kernel?
> > 
> > No. I'm using framebuffer, that's initialized quite late in boot
> > process. Plus many users just use bootsplash. I do use vga mode for
> > heavy debugging, but that's quite unusual.
> 
> But that's what some people do for their work, so they need it.

How many such users are out there?

> > So... you actually have speech-enabled grub/lilo/something?
> 
> That's in project too (and there's no reason it shouldn't be done).

I'd say kernel debugging is hard without accessible bootloader, so I'd
hope number of such users is very low.
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-09-01 18:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21  0:57 [PATCH] Console keyboard events and accessibility Samuel Thibault
2007-08-21 20:02 ` Andrew Morton
2007-08-21 20:22   ` Samuel Thibault
2007-08-25  1:07     ` Adrian Bunk
2007-08-25  1:07       ` Adrian Bunk
2007-08-27 14:59       ` Samuel Thibault
2007-08-21 20:42 ` Jan Engelhardt
2007-08-21 20:49   ` Samuel Thibault
2007-07-12 19:19     ` Pavel Machek
2007-07-12 19:19       ` Pavel Machek
2007-09-01 12:26       ` Samuel Thibault
2007-09-01 12:32         ` Pavel Machek
2007-09-01 12:32           ` Pavel Machek
2007-09-01 12:51           ` Samuel Thibault
2007-09-01 17:23             ` Pavel Machek
2007-09-01 17:23               ` Pavel Machek
2007-09-01 17:33               ` Samuel Thibault
2007-09-01 18:18                 ` Pavel Machek [this message]
2007-09-01 18:18                   ` Pavel Machek
2007-09-01 19:36                   ` Samuel Thibault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070901181845.GA4839@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.