linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Kyle McMartin <kyle@infradead.org>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Paul Hickey <paul@christianpatriot.us>,
	"stable@kernel.org" <stable@kernel.org>,
	Kyle McMartin <kyle@mcmartin.ca>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Failed Build of modules for 2.6.27.9-159
Date: Tue, 20 Jan 2009 13:21:56 -0800	[thread overview]
Message-ID: <20090120212156.GK19581@tesla> (raw)
In-Reply-To: <20090120211246.GD17452@bombadil.infradead.org>

On Tue, Jan 20, 2009 at 01:12:46PM -0800, Kyle McMartin wrote:
> On Tue, Jan 20, 2009 at 11:42:43AM -0800, Luis R. Rodriguez wrote:
> > On Mon, Jan 19, 2009 at 10:42:18PM -0800, Paul Hickey wrote:
> > > Hi Luis,
> > >
> > > 2.6.27.9-159.fc10.x86_64 is the kernel. I burned the distro right=
 from
> > > Fedora.
> >
> > I am =FCber-surprised to hear that FC10 2.6.27 kernels have added
> > pci_ioremap_bar() in their kernel header include/linux/pci.h. I
> > have verified this by checking:
> >
> > http://download.fedora.redhat.com/pub/fedora/linux/updates/10/x86_6=
4/kernel-devel-2.6.27.9-159.fc10.x86_64.rpm
> >
> > I have checked upstrea 2.6.27.9 and even 2.6.27.12 and they do not =
have this. This breaks
> > compatibility projects like compat-wireless :(
> >
> > Kyle?
> >
>=20
> F10 will be going to 2.6.28 within a few days... but honestly, if peo=
ple
> are going to using out of tree wireless (which is what they're doing,
> even if it's going upstream, it's not there now)=20

This stuff just pulls directly from wireless-testing BTW, the rest is j=
ust compat crap
to get it to work on older kernels.

> why can't they just
> build their own kernel too?

Because it involves a lot more work, just getting initrds to work prope=
rly these
days in distributions tends to be a real big pain in the ass for the no=
vice user.
Upgrading a user's wireless subsystem by simply typing in

make
sudo make install

Is a lot easier than trying to get them to wrap their brain around how =
to compile
and successfully install a new kernel. Additionally some project like o=
penwrt seem
to find it a lot more useful than bumping their entire kernel. 16 GB wo=
rth of
downloads of compat-wireless seems to indicate some people find it a re=
asonable
alternative. Its the only reason why I still maintain it.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-01-20 21:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 23:04 Failed Build of modules for 2.6.27.9-159 Paul Hickey
2009-01-19 19:11 ` Luis R. Rodriguez
     [not found]   ` <1232404986.3641.2.camel@localhost.localdomain>
     [not found]     ` <20090120000336.GB4018@tesla>
     [not found]       ` <1232433738.3696.3.camel@localhost.localdomain>
2009-01-20 19:42         ` Luis R. Rodriguez
2009-01-20 20:05           ` [stable] " Greg KH
2009-01-20 20:13             ` Luis R. Rodriguez
2009-01-20 20:16               ` Greg KH
     [not found]                 ` <20090120211630.GJ19581@tesla>
2009-01-20 22:08                   ` Kyle McMartin
2009-01-20 22:37                     ` Greg KH
2009-01-20 22:55                       ` Luis R. Rodriguez
2009-01-20 23:23                       ` Kyle McMartin
2009-01-21  0:07                     ` Luis R. Rodriguez
2009-01-21  0:12                       ` Kyle McMartin
2009-01-21  0:20                         ` Luis R. Rodriguez
2009-01-20 20:15             ` Michael Buesch
2009-01-20 21:12           ` Kyle McMartin
2009-01-20 21:21             ` Luis R. Rodriguez [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=20090120212156.GK19581@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=kyle@infradead.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-wireless@vger.kernel.org \
    --cc=paul@christianpatriot.us \
    --cc=stable@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).