All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John G. Heim" <jheim@math.wisc.edu>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: speakup bug
Date: Sat, 3 Mar 2012 18:01:07 -0600	[thread overview]
Message-ID: <FD8CB954D8084F998E24C4558E41C627@hinkle> (raw)
In-Reply-To: <20120303173916.7eca9391@pyramind.ukuu.org.uk>

From: Alan Cox
Sent: Saturday, March 03, 2012 11:39 AM
>> Can anyone tell me how to fix this so it can be patched in the official
>> kernel code?
>
>The proper fix is to make the drivers work via the serial layer properly.

Well, I am not the worlds greatest C programmer but many years ago I wrote 
unix
device drivers for a living. Could a reasonably competent person have a
chance of fixing that?

> The speakup people have been told this repeatedly for years and years
> which is why their drivers work on less and less systems and won't run
> with things PCI or USB serial ports, and why they are forever buried in
> staging.

Do you recall if they gave a reason for not wanting to use the serial layer?
I don't even know what the serial layer is (although the name is descriptive
enough and I can guess).But I would think they'd have had some reason for
not wanting to do that.


  parent reply	other threads:[~2012-03-04  0:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 17:18 speakup bug John G. Heim
2012-03-03 17:39 ` Alan Cox
2012-03-03 22:01   ` Ted Ts'o
2012-03-04  0:01   ` John G. Heim [this message]
2012-03-04  0:18     ` Samuel Thibault
2012-03-04  0:21       ` Samuel Thibault
2012-03-04  0:41         ` Ted Ts'o
2012-03-04  0:43           ` Samuel Thibault
2012-03-04  0:44             ` Samuel Thibault
2012-03-04  1:41             ` Ted Ts'o
2012-03-04  0:26     ` Ted Ts'o
2012-03-04  2:03   ` John G. Heim
2012-03-04 21:06     ` Alan Cox

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=FD8CB954D8084F998E24C4558E41C627@hinkle \
    --to=jheim@math.wisc.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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 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.