All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Green <andy@warmcat.com>
To: Benjamin Bryant <blbryant@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: problem installing mac80211 on Fedora Core 7
Date: Sat, 07 Jul 2007 07:56:15 +0100	[thread overview]
Message-ID: <468F390F.9090206@warmcat.com> (raw)
In-Reply-To: <45b4f7d90707062023i25dfb913s3e22b404490f245c@mail.gmail.com>

Benjamin Bryant wrote:

> I'm getting the following output:
> 
> # make patch_kernel
> Patching from compatible/ to /lib/modules/2.6.21-1.3228.fc7/source/:
> + Replaced 57 files.
> Checking for required kernel build updates...
> - checking net/Kconfig and net/Makefile...
> - checking net/core/Makefile for old 'wireless'...
> - checking net/core/dev.c for wireless_proc_init vs. wext_proc_init...
> grep: /lib/modules/2.6.21-1.3228.fc7/source/net/core/dev.c: No such

Hi -

The kernel-devel package doesn't include all the kernel sources, just
include files and so on.  You need the kernel SRPM installed to get all
the c source files.

Since Fedora kernels already have a recent mac80211 in them, depending
on what you want to achieve you may be better off either

 - skipping trying to cook mac80211 at all (I guess this is from iwlwifi)

 - using the latest Fedora development kernel with

     yum --enablerepo development update kernel

 - or using the wireless-dev git with

git clone
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git

and copying over /boot/config-<something> as .config in there so you
will be working with the most recent mac80211 all the time.

-Andy

      reply	other threads:[~2007-07-07  6:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45b4f7d90707062022j384934a1neb431bad641ef5b1@mail.gmail.com>
2007-07-07  3:23 ` problem installing mac80211 on Fedora Core 7 Benjamin Bryant
2007-07-07  6:56   ` Andy Green [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=468F390F.9090206@warmcat.com \
    --to=andy@warmcat.com \
    --cc=blbryant@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.