linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Noel Milton Vega <nmvega@nyceyes.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Julian Calaby <julian.calaby@gmail.com>,
	ozan@pardus.org.tr, linux-wireless@vger.kernel.org
Subject: Re: UPDATE -- Need Linux driver (preferably 64 bit) for "Intel Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card ...
Date: Thu, 10 Feb 2011 17:17:56 -0600	[thread overview]
Message-ID: <4D547224.4020306@lwfinger.net> (raw)
In-Reply-To: <937938.34583.qm@web36102.mail.mud.yahoo.com>

On 02/10/2011 05:08 PM, Noel Milton Vega wrote:
> 
>   > > In working with the kernel.org linux-wireless  developers, the conclusion
>   > > from one developer was that, though generally  speaking the
>   > > "Centrino Advanced-N 6230 AGN" card is supported by the  "iwlagn" kernel
>   > > module, it seems that the stock kernel module provided  in the
>   > > Fedora 14 kernel package (circa 2.6.35.10-74.fc14.x86_64), does  not
>   > > support the this card.
>   > > 
>   > > In other words, though code  in the main kernel.org git repository does
>   > > show support for the card  (via iwlagn kernel module), Fedora 14's
>   > > rendition/distribution of that  does not.
>   > 
>   > The point you seem to be missing is that your hardware is very  new,
>   > and the current Fedora 14 kernel is an "ancient" 6+ months  old.
>   >
> The point wasn't missed. In fact I highlighted the Fedora kernel
> version, and my card model to expressly make the point. Moreover,
> one of my suggested work-arounds was to try a newer kernel module
> (via compat-wireless) so as to bridge bridge that gap for this issue.
> 
>   > > Command  output during my debugging session with the developers is
>   > > shown below  for completeness, and in case the Fedora folks are
>   > >  monitoring.
>   > 
>   > I'm sorry, but your acquisition of bleeding-edge hardware  does not
>   > merit a change in the normal Fedora release  policy.
>   >
> Nothing in my email asked or expected them to. Still, the community
> in general should know what's going on. And, I did suggest two
> work-arounds in my email, neither of which asks anything of Fedora. 
> 
>   > P.S. I apologize if this seems rude -- that is  not my intent.
>   >
> Ah... This postscript repairs everything.

As an interested reader, he was not being rude. Usually, anyone that writes to
this list using the tone that you did, and continue to do, get blasted. You,
however, did not, but I predict that the gloves will soon come off!

Larry


  reply	other threads:[~2011-02-10 23:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 20:31 UPDATE -- Need Linux driver (preferably 64 bit) for "Intel Corporation Centrino Advanced-N 6230 (rev 34)" WiFI & Bluetooth card Noel Milton Vega
2011-02-10 21:25 ` John W. Linville
2011-02-10 23:08   ` Noel Milton Vega
2011-02-10 23:17     ` Larry Finger [this message]
2011-02-11  0:05 ` compat-wireless trial :: " Noel Milton Vega
2011-02-11  0:19   ` Julian Calaby
2011-02-11  0:30     ` Noel Milton Vega
2011-02-11  1:14     ` Noel Milton Vega
2011-02-12 18:43 ` SOLVED -- " Noel Milton Vega

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=4D547224.4020306@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nmvega@nyceyes.com \
    --cc=ozan@pardus.org.tr \
    /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).