iwn 5100AGN for netbsd-5

[Chuck Zmudzinski]

I saw in the mailing list archives a few weeks back that iwn(4) for
5100/5300 AGN devices was working in netbsd-current but hasn't been
ported to netbsd-5 yet. I decided to try and get it working in
netbsd-5 with minimal changes to the netbsd-5 kernel sources.

I got it working to the point I could run 'dhcp iwn0' and get a
dhcp lease, but pinging the router gave me this error from arp:

arpresolve: can't allocate llinfo on iwn0 for 192.168.6.1

See the copy of my message to netbsd-users about how my patch to netbsd-5
kernel source was constructed.

If anyone can direct me about how to fix this error in arp, let me
know. Would it require a lot of work, or a simple fix?

-----Original Message-----

From: Chuck Zmudzinski<***@netscape.net>
To: netbsd-***@netbsd.org
Sent: Fri, Dec 10, 2010 11:55 am
Subject: iwn 5100AGN for netbsd-5 success

I saw in the mailing list archives a few weeks back that iwn(4) for
5100/5300 AGN devices was working in netbsd-current but hasn't been
ported to netbsd-5 yet. I decided to try and get it working in
netbsd-5 with minimal changes to the netbsd-5 kernel sources.

Seven files were patched in src/sys/dev/pci: if_iwn.c, if_iwnreg.h
if_iwnvar.h, pcidevs, pcidevs.h pcidevs_data.h, and pcireg.h.

The details:

1. Used the first of version of src/sys/dev/if_iwn.c that works with
the 5100/5300 iwn devices from the current branch (revision 1.33), but
removed the two lines associated with revision 1.25 of
src/sys/dev/if_iwn.c. The iwn(4) driver failed in netbsd-5 with that
revision included - that revision was part of a major commit to the
netbsd-current kernel networking code.

2. Used the first version of src/sys/dev/if_iwnreg.h that works with
the 5100/5300 iwn devices from the current branch (revision 1.6).

3. Used the first version of src/sys/dev/if_iwnvar.h that works with
the 5100/5300 iwn devices from the current branch (revision 1.6).)

4. Edited the src/sys/dev/pcidevs file to add the new iwn devices
(these changes were derived from additions to pcidevs between revision
1.967 and 1.968 of src/sys/dev/pcidevs, but I changed "Pro/Wireless" to
"PRO/Wireless" for consistency with the other devices):

5. Regenerated src/sys/dev/pcidevs.h and src/sys/dev/pcidevs_data.h
using 'make -f Makefile.pcidevs'

6. Edited the src/sys/dev/pcireg.h file to add the changes that were
included in the changes to pcireg.h when the support was added for the
new iwn(4) devices in netbsd-current. It is essentially revision 1.57
(the netbsd-5 version) of pcireg.h patched with the changes between
revision 1.60 and 1.61 of pcireg.h.

7. Added the updated firmware for the 5100 AGN to my filesystem.

The 5100 iwn(4) device in my Toshiba laptop successfully runs 'dhclient
iwn0' in my patched netbsd-5 kernel (I am using the 5.0.2 release)
where it listened for dhcp offers, but I haven't tested it with an
actual wireless network in range yet to see if it makes a connection -
I assume it will work with a network in range; if it doesn't when I try
it I'll post a followup message.

The actual patchfile against the netbsd-5 kernel is too big to post
here (about 300K) because the difference in if_iwn.c between the
netbsd-5 version (revision 1.22.4.3 I think) and revision 1.33 is
rather large.







--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Manuel Bouyer]

Post by Chuck Zmudzinski
I saw in the mailing list archives a few weeks back that iwn(4) for
5100/5300 AGN devices was working in netbsd-current but hasn't been
ported to netbsd-5 yet. I decided to try and get it working in
netbsd-5 with minimal changes to the netbsd-5 kernel sources.
I got it working to the point I could run 'dhcp iwn0' and get a
arpresolve: can't allocate llinfo on iwn0 for 192.168.6.1
See the copy of my message to netbsd-users about how my patch to netbsd-5
kernel source was constructed.
If anyone can direct me about how to fix this error in arp, let me
know. Would it require a lot of work, or a simple fix?

I think it's a difference in network stack between -current and netbsd-5,
most probably a difference in the way a network driver interfaces with
sys/net/if_ethersubr.c
You may be missing a call to a function which is not present anymore in
-current. You should probably compare what your driver is doing in
initialisation and ioctl functions with another, working ethernet driver.

[Chuck Zmudzinski]

Post by Manuel Bouyer

Post by Chuck Zmudzinski
I saw in the mailing list archives a few weeks back that iwn(4) for
5100/5300 AGN devices was working in netbsd-current but hasn't been
ported to netbsd-5 yet. I decided to try and get it working in
netbsd-5 with minimal changes to the netbsd-5 kernel sources.
I got it working to the point I could run 'dhcp iwn0' and get a
arpresolve: can't allocate llinfo on iwn0 for 192.168.6.1
See the copy of my message to netbsd-users about how my patch to netbsd-5
kernel source was constructed.
If anyone can direct me about how to fix this error in arp, let me
know. Would it require a lot of work, or a simple fix?

I think it's a difference in network stack between -current and netbsd-5,
most probably a difference in the way a network driver interfaces with
sys/net/if_ethersubr.c
You may be missing a call to a function which is not present anymore in
-current. You should probably compare what your driver is doing in
initialisation and ioctl functions with another, working ethernet driver.

When I examined the code a bit that's what I thought it might be; I
think I'll take a look
at the iwi netbsd-5 intel wifi driver as a start and see if it has any
functions that look like
they interface with if_ethersubr.c and are missing in mu patched iwn
from -current.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Chuck Zmudzinski]

Post by Manuel Bouyer

Post by Chuck Zmudzinski
I saw in the mailing list archives a few weeks back that iwn(4) for
5100/5300 AGN devices was working in netbsd-current but hasn't been
ported to netbsd-5 yet. I decided to try and get it working in
netbsd-5 with minimal changes to the netbsd-5 kernel sources.
I got it working to the point I could run 'dhcp iwn0' and get a
arpresolve: can't allocate llinfo on iwn0 for 192.168.6.1
See the copy of my message to netbsd-users about how my patch to netbsd-5
kernel source was constructed.
If anyone can direct me about how to fix this error in arp, let me
know. Would it require a lot of work, or a simple fix?

I think it's a difference in network stack between -current and netbsd-5,
most probably a difference in the way a network driver interfaces with
sys/net/if_ethersubr.c
You may be missing a call to a function which is not present anymore in
-current. You should probably compare what your driver is doing in
initialisation and ioctl functions with another, working ethernet driver.

It looks like the netbsd-5 arp routines cannot get information from the
driver about
the ethernet addresses of the devices on the wireless network but
-current can. From
my tests, the networking subsytem can figure out what the gateway's IP
address is,
but not its ethernet address.

Well so far I noticed some functions missing in the -current driver I am
using as compared
to the netbsd-5 driver - notably a function called iwn_alloc_shared was
missing, so I added
it but still had the same error from arpresolve and also from arplookup
in if_arp.c.
I also tried renaming two functions function whose names were changed
between -5 and
-current but no success - always the arpresolve and an arplookup error.
I can't figure out
which call(s) might be missing in the -current driver that netbsd-5
needs for resolving IP
addresses to ethernet addresses. Any hints on this? Thanks.



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[FUKAUMI Naoki]

Post by Chuck Zmudzinski

Post by Manuel Bouyer
I think it's a difference in network stack between -current and netbsd-5,
most probably a difference in the way a network driver interfaces with
sys/net/if_ethersubr.c
You may be missing a call to a function which is not present anymore in
-current. You should probably compare what your driver is doing in
initialisation and ioctl functions with another, working ethernet driver.

It looks like the netbsd-5 arp routines cannot get information from the

(snip)

did you compare ioctl() which already mentioned by Manuel Bouyer?

...and you should read "#ifdef INET" as "#if 0" unless you added
necessary "#include".

--
FUKAUMI Naoki

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Chuck Zmudzinski]

Post by FUKAUMI Naoki

Post by Chuck Zmudzinski

Post by Manuel Bouyer
I think it's a difference in network stack between -current and netbsd-5,
most probably a difference in the way a network driver interfaces with
sys/net/if_ethersubr.c
You may be missing a call to a function which is not present anymore in
-current. You should probably compare what your driver is doing in
initialisation and ioctl functions with another, working ethernet driver.

It looks like the netbsd-5 arp routines cannot get information from the

(snip)
did you compare ioctl() which already mentioned by Manuel Bouyer?
...and you should read "#ifdef INET" as "#if 0" unless you added
necessary "#include".
--
FUKAUMI Naoki

Thanks for the tips!

I got it working by removing the the case SIOCSIFADDR: statement
from iwn_ioctl in if_iwn.c revision 1.33 - then it worked with netbsd-5.

So, to summarize, to get the newer iwn devices working in netbsd-5, I used
revision 1.6 of if_iwnvar.h and if_iwnreg.h, and I patched revision 1.33
of if_iwn.c
as follows (I also edited pcidevs with the new devices and included the
patch to
pcireg.h that went with the first commit that got the new iwn devices
working in
-current and added the firmware for the 5100 to the filesystem):

--- if_iwn.c 2009-09-10 20:28:20.000000000 -0500
+++ if_iwn.c 2010-12-17 11:31:52.000000000 -0600
@@ -1,6 +1,10 @@
/* $NetBSD: if_iwn.c,v 1.33 2009/09/11 01:28:20 christos Exp $ */
/* $OpenBSD: if_iwn.c,v 1.49 2009/03/29 21:53:52 sthen Exp $ */
-
+/*-
+ * This file is modified for use with netbsd-5 release kernels
+ * The changes in revision 1.25 of iwn.c have been removed
+ * The iwn_ioctl routine was modified to remove case SIOCSIFADDR:
+ */
/*-
* Copyright (c) 2007, 2008
* Damien Bergamini <***@free.fr>
@@ -3194,11 +3198,7 @@
s = splnet();

switch (cmd) {
- case SIOCSIFADDR:
- /* FALLTHROUGH */
case SIOCSIFFLAGS:
- if ((error = ifioctl_common(ifp, cmd, data)) != 0)
- break;
if (ifp->if_flags & IFF_UP) {
/*
* resync the radio state just in case we missed




--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de