linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Womack <james.c.womack@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: r8187se panic
Date: Sun, 14 Nov 2010 12:22:16 +0000	[thread overview]
Message-ID: <ibokag$481$1@dough.gmane.org> (raw)
In-Reply-To: <4CDEEEE4.80801@lwfinger.net>

On 13/11/10 20:02, Larry Finger wrote:
> On 11/13/2010 01:27 PM, James Womack wrote:
>> If building a kernel is as simple as building other programs from source
>> (i.e. configure, make, make install), I could do that. I'm using Debian
>> at the moment. Presumably I'd need a compiler of some kind, which I
>> could obtain from the repos. I am not sure how one would apply patches
>> to the kernel, however. Would I be able to compile a modified kernel and
>> add this to grub whilst retaining the ability to boot in the unmodified
>> kernel?
>
> It is similar to the process used with other programs. My distro is openSUSE and
> the steps are to get the kernel source, the kernel development package, and the
> patch utility using YaST. Other distros use emerge, apt-get, or similar
> utilities. The easiest way to configure the kernel is to match the current one
> using the compressed version in /proc/config.gz. You should end up with an
> additional kernel in the GRUB menu that can be selected at boot time.
>
> Larry
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Okay, I've downloaded the necessary tools and extracted the kernel 
source. I have a tutorial on how to patch and build the kernel. Where 
should I apply your patches?

James


  reply	other threads:[~2010-11-14 12:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  0:41 r8187se panic Robie Basak
2010-11-12  2:00 ` Larry Finger
2010-11-12 11:06   ` Robie Basak
2010-11-12 13:06     ` Larry Finger
2010-11-12 15:55       ` Robie Basak
2010-11-12 16:09         ` Larry Finger
2010-11-12 17:00           ` Robie Basak
2010-11-12 17:28             ` Larry Finger
2010-11-12 17:40               ` Robie Basak
2010-11-13 18:18                 ` James Womack
2010-11-13 18:44                   ` Larry Finger
2010-11-13 19:27                     ` James Womack
2010-11-13 20:02                       ` Larry Finger
2010-11-14 12:22                         ` James Womack [this message]
2010-11-14 16:18                           ` Larry Finger
2010-11-14 18:49                             ` James Womack
2010-11-14 20:23                               ` Larry Finger
2010-11-15 21:05                                 ` James Womack
2010-11-15 23:44                                   ` Larry Finger
2010-11-16  9:55                                     ` James Womack
2010-11-16 14:24                                       ` Larry Finger
2010-11-16 14:46                                         ` James Womack
2010-11-16 15:00                                           ` Larry Finger
2010-11-16 15:08                                             ` Rafał Miłecki
2010-11-16 15:42                                               ` Larry Finger
2010-11-16 16:55                                             ` James Womack
2010-11-16 17:16                                               ` Larry Finger
2010-11-14 19:38       ` James Womack

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='ibokag$481$1@dough.gmane.org' \
    --to=james.c.womack@gmail.com \
    --cc=linux-wireless@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 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 NNTP newsgroup(s).