From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: phcoder@gmail.com
Subject: Re: Grub & accessibility
Date: Fri, 10 Jul 2009 19:22:48 +0200 [thread overview]
Message-ID: <20090710172248.GD17114@thorin> (raw)
In-Reply-To: <20090707135023.GS4727@const.eduroam-ext.univ-nantes.prive>
On Tue, Jul 07, 2009 at 03:50:23PM +0200, Samuel Thibault wrote:
> Hello,
>
> (Cc-ing the grub-devel mailing list for the record)
>
> Just a few short points:
>
> - brltty GPL2+ and has a _lot_ of drivers for braille devices, it would
> be sad to not reuse them :)
> - speakup is also GPL2+ and has drivers for hardware speech syntheses.
> - qemu can emulate a Baum braille device through the -usbserial braille
> or -serial braille options. The output needs to be done through
> brltty, thanks to its virtual braille device for instance. I had
> written some howto on http://brl.thefreecat.org/text-apps-a11y-test.html
> - I had already developed something to make grub accessible through
> braille devices, in GRUB1, as a prototype, I've attached it. I've
> never had the time to develop it more.
Hi Samuel,
We've made some exceptions, but in general, we'd like to keep the GRUB
codebase made entirely of FSF-copyrighted code, or at least code we
have disclaimers for.
OTOH, we don't want to discard valuable work that wasn't written specifically
for GRUB. Perhaps Marco or Okuji will allow an exception for this case.
Another possibility is integrating those drivers in the grub-extras
repository. grub-extras is a collection of 3rd party add-ons for GRUB.
It's not officially part of GRUB, but distributions (e.g. debian) can
integrate it into their builds.
About your patch:
> diff -urN grub-debian-patched/configure.ac grub-0.95+cvs20040624/configure.ac
> --- grub-debian-patched/configure.ac 2005-09-05 03:57:02.000000000 +0200
> +++ grub-0.95+cvs20040624/configure.ac 2005-09-05 03:56:54.000000000 +0200
Only GRUB 2 is in development. New features won't be added to GRUB Legacy
anymore.
> +static unsigned char latin1_2_dots_vs[256] = {
> +0X00, 0X81, 0X83, 0X89, 0X99, 0X91, 0X8B, 0X9B,
> +[...]
This needs some clarification. Opaque blobs are not acceptable, but arrays
whose content is documented/understandable should be ok.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-07-10 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 13:50 Grub & accessibility Samuel Thibault
2009-07-10 17:22 ` Robert Millan [this message]
[not found] ` <20090710174321.GB5471@const.bordeaux.inria.fr>
2009-07-10 18:13 ` Samuel Thibault
2009-07-12 14:51 ` Pavel Roskin
2009-07-13 21:44 ` Vladimir 'phcoder' Serbinenko
2009-07-18 20:03 ` Robert Millan
2009-07-18 20:08 ` 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=20090710172248.GD17114@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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.