From: Don Raikes <don.raikes@oracle.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: RE: ot memory allocation question
Date: Mon, 22 Jul 2013 09:53:02 -0700 (PDT) [thread overview]
Message-ID: <c050ecd5-3e7b-4955-868e-680a03da1524@default> (raw)
In-Reply-To: <87bo5ywpb4.fsf@mushroom.PK5001Z>
Hi Chris and all those who were of such great help last week.
Just wanted to let you all know that with your help and support, plus a link from a fellow classmate I was able to get the assignment finished and turned in 3 hours early.
Of course after spending over 60 hours on this assignment, my prof sent out a note this morning saying that he wasn't expecting for the students to spend more than 10 hours on an assignment :-)
-----Original Message-----
From: Chris Brannon [mailto:chris@the-brannons.com]
Sent: Friday, July 19, 2013 8:19 AM
To: Speakup is a screen review system for Linux.
Subject: Re: ot memory allocation question
covici@ccs.covici.com writes:
> So could we use this inspeakup to write and read from a serial device
> -- thus circumventing most of our serial problems?
No. We discussed this several years ago, and we concluded that it won't work. It's pretty much infeasible to use the tty devices (/dev/ttyS*) from kernel space. That discussion might be available in the list archives. I've been told that the solution to our serial problems in Speakup is to write a tty line discipline. I don't really understand how to do it.
-- Chris
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Don Raikes
` Chris Brannon
` covici
` Chris Brannon
` covici
` Brian Buhrow
` Don Raikes [this message]
` Don Raikes
` Don Raikes
` Chris Brannon
` Don Raikes
` Jason White
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=c050ecd5-3e7b-4955-868e-680a03da1524@default \
--to=don.raikes@oracle.com \
--cc=speakup@linux-speakup.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).