public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Okash Khawaja <okash.khawaja@gmail.com>
To: speakup@linux-speakup.org
Cc: William Hubbs <w.d.hubbs@gmail.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: TODO file
Date: Tue, 12 Mar 2019 20:26:52 +0000	[thread overview]
Message-ID: <20190312202652.1e386ddf@narunkot> (raw)

Hi,

I am going through drivers/staging/speakup/TODO file with the aim of
creating tasks on the github page[1]. I need some help in understanding
what the tasks in TODO file mean, so I will be posting my questions to
this thread.

For now, I wanted to ask how much of this part is still to be done:

"The first issue has to do with the way speakup communicates with serial
ports.  Currently, we communicate directly with the hardware ports.
This however conflicts with the standard serial port drivers, which
poses various problems. This is also not working for modern hardware
such as PCI-based serial ports.  Also, there is not a way we can
communicate with USB devices.  The current serial port handling code is
in serialio.c in this directory."

Thanks,
Okash

[1] https://github.com/bytefire/speakup/issues

             reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Okash Khawaja [this message]
 ` Samuel Thibault
   ` Okash Khawaja
     ` Samuel Thibault
       ` Okash Khawaja
         ` Samuel Thibault
           ` Okash Khawaja
             ` Samuel Thibault
               ` Okash Khawaja
               ` Gregory Nowak
                 ` Samuel Thibault
                   ` Gregory Nowak
                   ` Janina Sajka
                 ` Tom Fowle
                 ` Janina Sajka
                   ` doubletalks Tom Fowle
                     ` doubletalks Tom Fowle
                     ` doubletalks Janina Sajka
                       ` doubletalks Tom Fowle
               ` TODO file John Covici
                 ` John Covici
 Gregory Nowak
 ` Tom Fowle
 ` John Covici

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=20190312202652.1e386ddf@narunkot \
    --to=okash.khawaja@gmail.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).