public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: moving from amd to p3?
Date: Mon, 18 Jun 2007 09:34:25 -0600	[thread overview]
Message-ID: <013a01c7b1be$2a680070$6401a8c0@GRANDMA> (raw)
In-Reply-To: <001501c7b08a$1f274070$ab00a8c0@tenstac>

If you do a make oldconfig, with your distro's kernel, in debian the one 
found in /boot I believe, it will ask you questions about the kernel that 
aren't in the old config.
also, if speakup patches, I'd mrproper, then put the config in, and patch 
speakup in.

Thanks,
~~TheCreator~~
[My programs don't have bugs; just randomly added features]
msn:
compgeek13@gmail.com
aim: st8amnd2005
skype: st8amnd127
vertigo head coder
web: tysdomain.com
----- Original Message ----- 
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, June 16, 2007 8:49 PM
Subject: Re: moving from amd to p3?


>
>
>> Actually, as far as I know, and this is what I've always done, you're
>> supposed to untar the kernel, patch with speakup, run make mrproper
>> clean, then copy a .config file into place if any. Also, if you're just
>> building a freshly untared kernel from kernel.org without speakup, or
>> any other patches, you don't need to do make mrproper, I never did
>> that in those cases.
>
> If you read the kernel FAQ it states that even if a fresh kernel from
> source you should do mrproper because there is a chance that some
> old stuff gets left behind when they package it. Better safe than sorry,
> always do mrproper before building a kernel. It can't hurt anything
> and does make sure there are no old deps or object modules around.
> mrproper is a superset of clean so if you do that you don't need to
> also do clean.
>
> Also, it doesn't seem right to copy an existing  .config after doing the
> speakup patch. The speakup patch adds new items into .config after
> speakup is selected in menuconfig, the CONFIG_SPEAKUP and
> other related entries. If you copied in a .config from a kernel without
> speakup then it won't have the speakup stuff in .config. If you copy
> some existing .config then it may not match the kernel that you are
> compiling from source. If it's the same kernel version that you used
> before it will work, but if you now have a newer kernel it may or
> may not work, and you might be missing some new stuff that's in the
> newer kernel version.
>
> It is a pain to go through the config, but worthwhile to understand
> what you need and don't for your hardware. There is so much in
> the kernel that is not needed on most systems. If you set all those
> to not be included, then you have a whole lot less to compile.
>
>  -- Doug
>
>
>
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 



      parent reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Littlefield, Tyler
 ` Doug Sutherland
   ` Scott Berry
     ` Littlefield, Tyler
       ` Doug Sutherland
         ` Littlefield, Tyler
     ` Doug Sutherland
       ` Gregory Nowak
         ` Doug Sutherland
           ` Gregory Nowak
             ` Doug Sutherland
               ` Gregory Nowak
           ` Scott Berry
             ` Doug Sutherland
               ` Gregory Nowak
                 ` Doug Sutherland
           ` Littlefield, Tyler [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='013a01c7b1be$2a680070$6401a8c0@GRANDMA' \
    --to=compgeek13@gmail.com \
    --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).