From: Shawn Kirkpatrick <shawn@shawnk.ca>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: script to make patched ubuntu kernel
Date: Wed, 15 Apr 2015 16:26:22 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1504151615180.22332@odyssey> (raw)
In-Reply-To: <552D8B85.10806@math.wisc.edu>
Since Ubuntu has a speakup-source package wouldn't it be easier to make this
script patch that rather than recompiling the whole kernel? This way
module-assistant could be used to install the speakup modules and then the
patch would stay in place accross kernel upgrades.
To take this a step further, it might be a good idea to have a script that
could bring the speakup sources up to the latest version and compile that.
I'm currently having this problem myself, the speakup modules that come with
ubuntu have some major problems but I'm not sure what sources they're using
or what is the latest speakup source. Is it the one in the kernel tree or
the one from the git repository? The problem is made worse by the speakup
version number not being updated and no change log seeming to be available.
On Tue, 14 Apr 2015, John G Heim wrote:
> I've written a bash script to make it easier to create a ubuntukernel patched
> for serial hardware synths. Instructions for downloading and using the script
> are at http://www.iavit.org/~john/ubuntu/.
>
> The script itself is at
> http://www.iavit.org/~john/ubuntu/make-speakup-kernel.
>
> All you need to do is to download the script and run it. The script installs
> the ubuntu kernel source package, comments out the line of code that keeps
> hardware synths from working, and compiles the kernel.
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
John G Heim
` Shawn Kirkpatrick [this message]
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=alpine.DEB.2.10.1504151615180.22332@odyssey \
--to=shawn@shawnk.ca \
--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).