On Sun, 7 Mar 2004, David Young wrote:

> Sam, I *strongly* suggest that you cooperate with the person who is
> integrating the acx driver into FreeBSD, because they are making full
> use of the 802.11 layer.  If getting your work into NetBSD is your goal,
> then 802.11 integration is really quite important: if N months from now
> there is a driver in FreeBSD that uses the full power of the 802.11 layer,
> and a NetBSD driver that does not, then I will prefer for NetBSD to adopt
> the former driver, which will be more featureful and easier to maintain.

Okay, right now I just see:

<#prefix>/sys/net/if_ieee80211.h
<#prefix>/sys/net/if_ieee80211subr.c

So all the structures definied in these files should be used in the new
acx(4) driver / ~template where applicable.

there are more links and references in:

<#prefix>/sys/net/if.c
<#prefix>/sys/net/if_media.h
<#prefix>/sys/net/if_types

and more specifics in:
<#prefix>/sys/dev/pci/if_wi_pci.c
<#prefix>/sys/dev/ic/awi.c, awireg.h
<#prefix>/sys/dev/ic/wi.c, wi_ieee.h, wireg.h, wivar.h

I continue to traverse the source tree for more.

Concerning the authors: One of my tech-kern posts was forwarded to Darron
Broad, but I have not heard back.

I will try to directly contact Darron Broad, Simon Brown, or Marc P
Summers (acx111), and at least show them the code once it starts
"working".

> > Anything more on the mtx functions?
>
> In NetBSD, look at src/sys/dev/ic/athcompat.h to see how I have abstracted
> critical section code. It is usually sufficient to do splnet()/splx()
> wherever a mutex is acquired/released.

Thanks, that should save me some searching.

Sam.

--------------------------------------------------
SA Thigpen * KL1FE * http://sthigpen.freeshell.org
--------------------------------------------------