From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup List" <speakup@braille.uwo.ca>
Subject: patch for 2.4.21 and later
Date: Wed, 29 Oct 2003 01:14:35 -0700 [thread overview]
Message-ID: <000501c39df4$b272e0c0$6400a8c0@merlin> (raw)
Hi all,
I've noticed that there has been quite a bit of confusion reguarding the
failed patching of miscdevice.h on kernels 2.4.21 and later. (this is only
true in the 2.4 series) I don't know if this will be helpful to anyone, but
below is a patch that will cause speakup to install with no failed hunks on
these kernels. Simply apply this patch to speakup 1.5 before you run
./install. If you simply copy this entire message to the speakup 1.5
subdirectory on your system, then run patch -p1 < [name of file containing
patch] it should patch your speakup source just fine. Patch is smart enough
to skip the other text of this message and only process the patch. Note,
once you apply this patch, you can't use that copy of speakup to install to
any 2.4 series kernel earlier than 2.4.21. Only apply this patch if you have
2.4.21 or later.
diff -u -r speakup-1.5.old/speakup/patchlist-v24
speakup-1.5/speakup/patchlist-v24
--- speakup-1.5.old/speakup/patchlist-v24 2003-04-14
10:07:44.000000000 -0600
+++ speakup-1.5/speakup/patchlist-v24 2003-10-29 01:08:34.000000000 -0700
@@ -14,7 +14,6 @@
1,/usr/src/linux/drivers/char/selection.c
1,/usr/src/linux/fs/proc/root.c
1,/usr/src/linux/include/linux/keyboard.h
-1,/usr/src/linux/include/linux/miscdevice.h
1,/usr/src/linux/include/linux/proc_fs.h
1,/usr/src/linux/init/main.c
0,/usr/src/linux/Documentation/speakup/DefaultKeyAssignments
If this helps anyone, great. If not, sorry for the wasted bandwidth.
--
Joseph C. Lininger
jbahm@pcdesk.net
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000501c39df4$b272e0c0$6400a8c0@merlin' \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/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).