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

Okash Khawaja, le mar. 12 mars 2019 20:26:52 +0000, a ecrit:
> 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."

You have done it all :)

(even if, as you mentioned, the USB auto-probing would now be great)

Samuel

  reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Okash Khawaja
 ` Samuel Thibault [this message]
   ` 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=20190312220915.qgtag5vezpaouoxp@function \
    --to=samuel.thibault@ens-lyon.org \
    --cc=okash.khawaja@gmail.com \
    --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).