Re: brcmsmac: Unknown symbol backport_cordic_calc_iq (err 0)

[Camaleón <noelamac@gmail.com>]

El 2013-03-28 a las 03:23 -0700, Luis R. Rodriguez escribió:

> On Thu, Mar 28, 2013 at 2:56 AM, Camaleón <noelamac@gmail.com> wrote:

(...)

> > Now, what happens is that the compat-driver freezes with kernel 3.9
> > and I get this message with kernel 3.2:
> >
> > [  684.589268] Compat-drivers backport release: compat-drivers-2013-03-26-u
> > [  684.589279] Backport based on linux-next.git next-20130326
> > [  684.589285] compat.git: linux-next.git
> > [  684.609187] cfg80211: Unknown symbol
> > backport_netdev_set_default_ethtool_ops (err 0)
> >
> > This driver is "driving" me nuts :-)
> 
> I have a fix for this, mind you, this is a Debian thing, that is --
> debian cherry picked some code from a future kernel on their own
> kernel. The new LINUX_BACKPORT() macro will rescue these. I'll post a
> new release tomorrow, but I'm working on backporting some other
> collateral evolutions right now.

Okay, no problem and thanks for caring about this.
 
> >> We have yet to require any backport work between 3.9 and what we assume will be
> >> 3.10. My bet is this is a real driver bug, not backport bug.
> >
> > Curious is that brcmsmac module loads fine from the common kernel
> > module, I mean, the stock one.
> 
> What do you mean? Have you tried the stock driver from 3.9-rc2?

Sure! (full report is on the kernel wireless mailing list)

In fact, the only reason I compiled the kernel is to test the latest brcmsmac 
driver because being this a netbook, having to use an external usb card 
to be "online" when I'm out of home is a bit annoying.

Now you say... can you please tell me -in user's parlance terms so I can 
understand it- what's the difference between "brcmsmac" from the stock 
kernel modules and this one from "compat-drivers"? I mean, what's the 
difference from a user's POV and from kernel hacker POV. Are they 
related? Are they going to me merged somehow? What's the goal of having 
both?

> >> Can you
> >>
> >> git clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
> >>
> >> and use your .config, and build and test that kernel ? If it fails to
> >> boot / crash then you know its the driver.
> >
> > I'm not using git (don't even have it installed in my system), I'm
> > used to compile kernels/modules in the old fashion way. Sorry, I don't
> > know how git works.
> 
> make localmodconfig
> make
> make install

(...)

Will try and report back. Thanks, Luis.
 
Greetings,

-- 
Camaleón