From: Mario Lang <mlang@delysid.org>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>, BRLTTY@mielke.cc
Subject: Re: Fwd: [RFC] GRUB2 and braille support
Date: Wed, 28 Jul 2010 22:50:02 +0200 [thread overview]
Message-ID: <87iq3zqqkl.fsf@x4.delysid.org> (raw)
In-Reply-To: <4C4774BF.9060009@gmail.com> ("Vladimir 'φ-coder/phcoder' Serbinenko"'s message of "Thu, 22 Jul 2010 00:29:19 +0200")
"Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com> writes:
> Now I'm working on braille support. I already coded 40x1 menu selector
> and menuentry editor. For 40x1 console I need to add scrolling first.
> it's in branches/a11y
> I also coded FTDI and PL3203 usbserial drivers. It's in branches/usb.
Some of our existing drivers implement well-known serial adaptors,
others need more low-level USB access which we provide through our
own internal USB stack impementation.
> Now we need the braille drivers to go in-between. I thought of importing
> Linux braille drivers since they seem to be under GPLv2+. I hope that I
> CC the right list for it. My plan is to have an import similar to what
> we have with libgcrypt: we copy the patches verbatim and try to emulate
> the environment similar to native one. If any preprocessing is needed we
> have 2 directories: one with files as they are imported and another with
> the files to compile. The second one is generated from the first one
> with python script at autogen phase. This way we avoid forking and can
> easily resync
That sounds like a nice plan.
> What do you think?
The drivers you want to import are at
svn://mielke.cc/main/brltty in subdirectory Drivers/Braille minus
a few like Skeleton, Libbraille and possibly BrlAPI.
As mentioned, these drivers use IO functions provides in
Programs/io_{serial,usb,bluetooth}.h which are implemented
for several platforms (Linux, BSDs, Windows and a few others).
The way the drivers work is currently a bit of a mixture. These
days, most of the drivers enqueue driver-specific keycodes
which are mapped to commands in so-called keytables.
However, a few drivers still return commands, hardcoding
the mapping from keycodes to commands in the driver itself.
That said, there is probably quite some infrastructure code
which you will need to copy as well to get the drivers to work.
I guess another approach could be to treat GRUB2 as a platform
supported by brltty, but I really dont know anything about
GRUBs support for plugins or externally compiled code...
--
CYa,
⡍⠁⠗⠊⠕
next prev parent reply other threads:[~2010-07-29 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 22:29 Fwd: [RFC] GRUB2 and braille support Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-28 20:50 ` Mario Lang [this message]
2010-07-28 20:58 ` [BRLTTY] " Samuel Thibault
2010-07-28 22:12 ` Samuel Thibault
2010-07-28 23:19 ` Samuel Thibault
2010-07-30 12:21 ` 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=87iq3zqqkl.fsf@x4.delysid.org \
--to=mlang@delysid.org \
--cc=BRLTTY@mielke.cc \
--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.