Linux wireless drivers development
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: andrewl733@aol.com, linux-wireless@vger.kernel.org
Subject: Re: Updates to 3.8 kernel break b43 Wireless with 4331 chipset
Date: Mon, 21 Oct 2013 13:31:18 -0500	[thread overview]
Message-ID: <526572F6.7010807@lwfinger.net> (raw)
In-Reply-To: <8D09C98149E95D8-27D8-2CD34@Webmail-d105.sysops.aol.com>

It may just be me, but I kept getting a "deja vu" feeling when I read your 
report. Please minimize the repetition of material.

Unfortunately, I do not have a 4331 device, and I cannot duplicate your result. 
Ideally, the best approach would be for you to clone the Linux mainline git repo 
and verify that the latest 3.12-rc6 has the problem. If so, then you could 
bisect between that version and 3.8 to determine the commit that caused the 
failures. As I have no idea of your facility with kernel builds, that may be 
beyond your ability.

If you can locate an on-line list of the kernel changes between 3.8.13-1 and 
3.8.13.4-1 and post a URL, it might be possible for us to spot the faulty 
change. I do not even know how to interpret those versions. To me, it seems that 
both are based on 3.8.13. As 3.8 is EOL and not being updated by any of the 
kernel developers, all changes are now being done by Mageia. Thus, only they 
know what was done.

Larry


      reply	other threads:[~2013-10-21 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 17:14 Updates to 3.8 kernel break b43 Wireless with 4331 chipset andrewl733
2013-10-21 18:31 ` Larry Finger [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=526572F6.7010807@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=andrewl733@aol.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