From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: New kernel for etch
Date: Sun, 3 Jun 2007 15:37:46 +0800 [thread overview]
Message-ID: <000801c7a5b2$163f5700$2518a8c0@bouncy> (raw)
Looking for some guidance preparing a new kernel for Debian etch with
speakup in it.
I have downloaded 2.6.18 vanilla sources and investigated applying Debian
specific patches to the tree but it all looks rather messy.
Does anyone have sample configs for 2.6.21.4 with or without speakup in them
or an idea where to get something suitable for Debian?
There are so many questions these days it would take quite awhile to answer
all the questions with make config and make menuconfig is a little clunky.
I have tried grabbing the .config from 2.6.18 and doing a make menuconfig
however some of the variables have disappeared and this does not look like a
clean solution.
I usually build the kernels with kernel-package and I am using an initramfs
with customizations to support evms. Basically I need a recent kernel with
speakup, the bd-claim patch and the bad-block relocation applied to it.
I can apply these patches and speakup to Vanilla sources; however defaults
for the .config have me a little stumped and i'd rather not do the whole
config myself without guidance unless I absolutely have to.
In the sarge days i'd grab 2.6.15, apply Marvell ethernet patches and
speakup then build 2 or 3 different images with speakup and vmware features
in them.
Looks like kernels have gotten a little trickier since then.
Regards, Kerry.
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='000801c7a5b2$163f5700$2518a8c0@bouncy' \
--to=kerry@gotss.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).