Bug 173898 - [iwn] [patch] iwn(4) DOES support 6235 chip.
Summary: [iwn] [patch] iwn(4) DOES support 6235 chip.
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 10.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-24 22:00 UTC by Johannes Meixner
Modified: 2016-01-02 06:14 UTC (History)
0 users

See Also:

Attachments
file.diff (982 bytes, patch)
2012-11-24 22:00 UTC, Johannes Meixner 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Meixner 2012-11-24 22:00:00 UTC 
As a follow-up to 

kern/169433: iwn(4) doesn't support 6235 chip.

and

http://forums.freebsd.org/showthread.php?t=35467 

I managed to get WiFi running on my Intel Centrino Advanced-N 6235 chip 
on the newest firmware downloaded from http://intellinuxwireless.org/ . After finding out the chip's numbers with pciconf -lbcev I added one line to if_iwn.c, recompiled the module and it worked. 

Please find attached the output from `svn diff` in /usr/src.

Required steps in order to get it working are documented in the forum post mentioned above.

Fix: Patch attached with submission follows:
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-11-24 22:21:03 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-wireless

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2012-11-30 23:25:59 UTC 
Responsible Changed
From-To: freebsd-wireless->eadler

I'll take it.
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2012-12-01 04:59:22 UTC 
On 30 November 2012 20:28, Adrian Chadd <adrian@freebsd.org> wrote:
> It's not that simple. Speak to bernhard.


Davide, You mention some issues and I asked you to follow up to the
PR.  Can you please explain them?

> There are other issues that he knows about. I don't know if he's
> replied to the email or not; poke him on irc.

IRC doesn't help as the record does not go into the PR


-- 
Eitan Adler
Source, Ports, Doc committer
Bugmeister, Ports Security teams
Comment 4 Bernhard Schmidt freebsd_committer freebsd_triage 2012-12-12 21:38:59 UTC 
On Saturday 01 December 2012 05:59:22 Eitan Adler wrote:
> On 30 November 2012 20:28, Adrian Chadd <adrian@freebsd.org> wrote:
> > It's not that simple. Speak to bernhard.
> 
> 
> Davide, You mention some issues and I asked you to follow up to the
> PR.  Can you please explain them?
> 
> > There are other issues that he knows about. I don't know if he's
> > replied to the email or not; poke him on irc.
> 
> IRC doesn't help as the record does not go into the PR

For the record.. I thought I mentioned this in another PR already.

Using the new firmware and adding the PCI IDs is enough to detect
the cards and get some basic stuff working. The major part of the
features is not though. At least on 11n HT40 you will definitely
get a firmware crash. Also, the throughput sucks, even in legacy
mode.

I'm not able to pin the cause, working on it. Johannes is also
looking into it.

-- 
Bernhard
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2013-01-31 13:58:15 UTC 
Responsible Changed
From-To: eadler->freebsd-wireless

sorry I held on to this for so long;   at the moment I have no time to 
look at this PR so return to the pool
Comment 6 ahmedcharles 2013-02-11 19:22:05 UTC 
Note: There is also a reference to the firmware in sys/conf/files.

-- 
Ahmed Charles
Comment 7 Adrian Chadd freebsd_committer freebsd_triage 2014-02-11 05:26:58 UTC 
State Changed
From-To: open->closed

Fixed in- HEAD