From: Andrew Morton <akpm@linux-foundation.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: linux-kernel@vger.kernel.org, Dmitry Torokhov <dtor@mail.ru>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH2] Basic braille screen reader support
Date: Sat, 23 Feb 2008 00:04:10 -0800 [thread overview]
Message-ID: <20080223000410.674ce674.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080222002822.GB32480@implementation>
On Fri, 22 Feb 2008 01:28:22 +0100 Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> Samuel Thibault, le Wed 06 Feb 2008 02:04:23 +0000, a __crit :
> > Andrew Morton, le Tue 05 Feb 2008 16:58:53 -0800, a __crit :
> > > On Tue, 5 Feb 2008 22:00:54 +0000
> > > Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> > > > + serial8250_console.write(braille_co, data, c - data);
> > >
> > > hm. Is it appropriate that this driver wire itself directly into
> > > serial8250?
> > > What if the screen reader is attached to some other sort of
> > > uart, or a terminal server, or...
> >
> > Indeed that's an issue. For now, there is no clean way to attach to the
> > early serial drivers, that's why I chose 8250,
>
> In the patch below, I hook into kernel/printk.c's console= parser, which
> now gives me attachment to any kind of console.
>
>
>
>
> This adds a minimalistic braille screen reader support.
> This is meant to be used by blind people e.g. on boot failures or when /
> cannot be mounted etc and thus the userland screen readers can not work.
>
Sorry, but I can't say that this is my favoritest ever patch. But I can't
immediately think of any way of significantly improving it :( Jiri and
Dmitry appear to be hiding.
> +++ linux-2.6.24.1-perso/kernel/printk.c 2008-02-21 12:09:06.000000000 +0100
> @@ -105,6 +105,7 @@
Please use `diff -p'
> char name[8]; /* Name of the driver */
> int index; /* Minor dev. to use */
> char *options; /* Options for the driver */
> + char *brl_options; /* Options for braille driver */
> };
Should this depend on CONFIG_A11Y_BRAILLE_CONSOLE or whatever?
> #define MAX_CMDLINECONSOLES 8
> @@ -766,15 +767,59 @@
>
> #endif
>
> +static int __add_preferred_console(char *name, int idx, char *options,
> + char *brl_options)
> +{
> + struct console_cmdline *c;
> + int i;
> +
> + /*
> + * See if this tty is not yet registered, and
> + * if we have a slot free.
> + */
> + for (i = 0; i < MAX_CMDLINECONSOLES && console_cmdline[i].name[0]; i++)
> + if (strcmp(console_cmdline[i].name, name) == 0 &&
> + console_cmdline[i].index == idx) {
> + if (!brl_options)
> + selected_console = i;
> + return 0;
> + }
> + if (i == MAX_CMDLINECONSOLES)
> + return -E2BIG;
Does the array of consles have any locking here?
> + if (!brl_options)
> + selected_console = i;
> + c = &console_cmdline[i];
> + memcpy(c->name, name, sizeof(c->name));
> + c->name[sizeof(c->name) - 1] = 0;
strlcpy()?
> + c->options = options;
> + c->brl_options = brl_options;
> + c->index = idx;
> + return 0;
> +}
> /*
> * Set up a list of consoles. Called from init/main.c
> */
> static int __init console_setup(char *str)
> {
> char buf[sizeof(console_cmdline[0].name) + 4]; /* 4 for index */
> - char *s, *options;
> + char *s, *options, *brl_options = NULL;
> int idx;
>
> +#ifdef CONFIG_A11Y_BRAILLE_CONSOLE
> + if (!memcmp(str, "brl,", 4)) {
> + brl_options = "";
> + str += 4;
> + } else if (!memcmp(str, "brl=", 4)) {
> + brl_options = str + 4;
> + str = strchr(brl_options, ',');
> + if (!str) {
> + printk(KERN_ERR "need port name after brl=\n");
> + return 1;
> + }
> + *(str++) = 0;
> + }
> +#endif
Update Documentation/kernel-parameters.txt, please. And additional
documentation would be nice, if justified?
> /*
> * Decode str into name, index, options.
> */
> @@ -799,7 +844,7 @@
> idx = simple_strtoul(s, NULL, 10);
> *s = 0;
>
> - add_preferred_console(buf, idx, options);
> + __add_preferred_console(buf, idx, options, brl_options);
> return 1;
> }
>
> ...
>
> +static void beep(unsigned int freq)
> +{
> + if (sound)
> + kd_mksound(freq, HZ/10);
> +}
hm, do we have enough Kconfig dependencies here to ensure that kd_mksound()
is always available?
next prev parent reply other threads:[~2008-02-23 8:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 3:18 [PATCH] " Samuel Thibault
2008-02-04 3:22 ` Samuel Thibault
2008-02-04 17:10 ` Greg KH
2008-02-04 17:24 ` Samuel Thibault
2008-02-04 18:06 ` Greg KH
2008-02-04 18:15 ` Samuel Thibault
2008-02-04 18:27 ` Greg KH
2008-02-05 22:00 ` [PATCH,RESEND] " Samuel Thibault
2008-02-06 0:58 ` Andrew Morton
2008-02-06 2:04 ` Samuel Thibault
2008-02-22 0:28 ` [PATCH2] " Samuel Thibault
2008-02-23 8:04 ` Andrew Morton [this message]
2008-02-23 13:10 ` Samuel Thibault
2008-02-23 13:15 ` [PATCH] Braille screen reader fixes Samuel Thibault
2008-02-23 13:17 ` [PATCH] Braille screen reader documentation Samuel Thibault
2008-04-24 0:39 ` [PATCH2] Basic braille screen reader support Samuel Thibault
2008-04-24 4:46 ` Andrew Morton
2008-04-24 10:21 ` Alan Cox
2008-04-24 11:09 ` Samuel Thibault
2008-03-19 18:57 ` [mmotm build error] Re: [PATCH,RESEND] " Randy Dunlap
2008-03-20 2:07 ` Samuel Thibault
2008-03-20 4:19 ` Randy Dunlap
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=20080223000410.674ce674.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dtor@mail.ru \
--cc=jkosina@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome