Re: MadWifi HAL now open source

"Ken Caruso" <[email protected]> Wed, 10 Dec 2008 16:47:50 -0800
Newsgroups gmane.network.wireless.seattle.general
Message-ID <[email protected]>
------=_Part_77938_14311967.1228956470066
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Dec 10, 2008 at 10:25 AM, <[email protected]> wrote:

>
> Have you tried digging through the ubnt forums or contacting ubiquiti
> support yet?


They also have their own HAL and madwifi distro:

http://ubnt.com/support/


-Ken


>
>
> On Dec 9, 5:55 pm, macker <[email protected]> wrote:
> > All this means, is that the ubiquiti SRX expresscard will still not
> > work for months, going on 8 months later?
> >
> > On Tue, Dec 9, 2008 at 4:31 PM, Daevid Vincent <[email protected]>
> wrote:
> > > So does this mean I'll be able to use one of those newer 802.11g or n
> cards
> > > as my AP on my linux box?
> >
> > > Currently I'm stuck at 802.11b with my Engenius Senao NL-2511 PCMCIA
> card
> > > and hostap. I'm dying.
> > > ________________________________
> > > MadWifi HAL now open source
> >
> > > Sam Leffler, maintainer of the binary HAL used in MadWifi releases,
> > > announced last weekend that he was releasing the source code for the
> > > hardware abstraction layer (HAL) of the MadWifi Linux Wifi driver. It
> is now
> > > available under an ISC license via a subversion repository (svn web
> > > interface).
> >
> > > For a long time, MadWifi was the only Linux driver able to handle
> Atheros
> > > Wifi cards. A few weeks ago, Atheros released a HAL under the same
> license,
> > > to help develop the ath5k, IEEE 802.11a/b/g, Wifi driver, which some
> > > developers, including Atheros employee Luis R. Rodriguez, had ported
> from
> > > OpenBSD to Linux last year. Ath5k and the ath9k Draft-N WLAN driver,
> which
> > > dispense entirely with proprietary parts in favour of OpenHAL, have
> been
> > > part of the Linux kernel since versions 2.6.25 and 2.6.27 respectively.
> > > Before now, MadWifi used the manufacturer's proprietary HAL, which
> prevented
> > > direct access to the Wifi hardware. The developers of the MadWifi
> driver had
> > > tolerated this situation, although it meant that parts of the software
> > > project resembled a black box and could not be incorporated in the
> Linux
> > > kernel.
> >
> > > The release of the MadWifi HAL concludes the agreement between Leffler
> and
> > > Atheros which gave him access to information on the manufacturer's
> devices.
> > > All fixes and updates for new chips will be carried out by the
> developer
> > > community from now on. The published source code uses the Linux
> operating
> > > system as its reference platform. Potential developers can find out
> more on
> > > the ath5k-devel and ath9k-devel mailing lists; note that these lists
> are SSL
> > > secured with an unverifiable certificate and will require an exception
> be
> > > made in your browser.
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the SeattleWireless Talk list, hosted by Google Groups
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/swn-talk?hl=en

For more about the SeattleWireless.NET project, see http://seattlewireless.net/
-~----------~----~----~----~------~----~------~--~---


------=_Part_77938_14311967.1228956470066
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Wed, Dec 10, 2008 at 10:25 AM,  <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">mattw@seattle=
wireless.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Have you tried digging through the ubnt forums or contacting ubiquiti<br>
support yet?</blockquote><div><br></div><div>They also have their own HAL a=
nd madwifi distro:</div><div><br></div><div><a href=3D"http://ubnt.com/supp=
ort/">http://ubnt.com/support/</a></div><div><br></div><div><br></div><div>
-Ken</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<div class=3D"Ih2E3d"><br>
On Dec 9, 5:55&nbsp;pm, macker &lt;<a href=3D"mailto:[email protected]">mac.=
[email protected]</a>&gt; wrote:<br>
&gt; All this means, is that the ubiquiti SRX expresscard will still not<br=
>
&gt; work for months, going on 8 months later?<br>
&gt;<br>
</div><div><div></div><div class=3D"Wj3C7c">&gt; On Tue, Dec 9, 2008 at 4:3=
1 PM, Daevid Vincent &lt;<a href=3D"mailto:[email protected]">dae...@daevid=
.com</a>&gt; wrote:<br>
&gt; &gt; So does this mean I&#39;ll be able to use one of those newer 802.=
11g or n cards<br>
&gt; &gt; as my AP on my linux box?<br>
&gt;<br>
&gt; &gt; Currently I&#39;m stuck at 802.11b with my Engenius Senao NL-2511=
 PCMCIA card<br>
&gt; &gt; and hostap. I&#39;m dying.<br>
&gt; &gt; ________________________________<br>
&gt; &gt; MadWifi HAL now open source<br>
&gt;<br>
&gt; &gt; Sam Leffler, maintainer of the binary HAL used in MadWifi release=
s,<br>
&gt; &gt; announced last weekend that he was releasing the source code for =
the<br>
&gt; &gt; hardware abstraction layer (HAL) of the MadWifi Linux Wifi driver=
. It is now<br>
&gt; &gt; available under an ISC license via a subversion repository (svn w=
eb<br>
&gt; &gt; interface).<br>
&gt;<br>
&gt; &gt; For a long time, MadWifi was the only Linux driver able to handle=
 Atheros<br>
&gt; &gt; Wifi cards. A few weeks ago, Atheros released a HAL under the sam=
e license,<br>
&gt; &gt; to help develop the ath5k, IEEE 802.11a/b/g, Wifi driver, which s=
ome<br>
&gt; &gt; developers, including Atheros employee Luis R. Rodriguez, had por=
ted from<br>
&gt; &gt; OpenBSD to Linux last year. Ath5k and the ath9k Draft-N WLAN driv=
er, which<br>
&gt; &gt; dispense entirely with proprietary parts in favour of OpenHAL, ha=
ve been<br>
&gt; &gt; part of the Linux kernel since versions 2.6.25 and 2.6.27 respect=
ively.<br>
&gt; &gt; Before now, MadWifi used the manufacturer&#39;s proprietary HAL, =
which prevented<br>
&gt; &gt; direct access to the Wifi hardware. The developers of the MadWifi=
 driver had<br>
&gt; &gt; tolerated this situation, although it meant that parts of the sof=
tware<br>
&gt; &gt; project resembled a black box and could not be incorporated in th=
e Linux<br>
&gt; &gt; kernel.<br>
&gt;<br>
&gt; &gt; The release of the MadWifi HAL concludes the agreement between Le=
ffler and<br>
&gt; &gt; Atheros which gave him access to information on the manufacturer&=
#39;s devices.<br>
&gt; &gt; All fixes and updates for new chips will be carried out by the de=
veloper<br>
&gt; &gt; community from now on. The published source code uses the Linux o=
perating<br>
&gt; &gt; system as its reference platform. Potential developers can find o=
ut more on<br>
&gt; &gt; the ath5k-devel and ath9k-devel mailing lists; note that these li=
sts are SSL<br>
&gt; &gt; secured with an unverifiable certificate and will require an exce=
ption be<br>
&gt; &gt; made in your browser.<br>
<br>
</div></div></blockquote></div><br>
<br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the SeattleWireless=
 Talk list, hosted by Google Groups
 <br> To post to this group, send email to [email protected]
 <br> To unsubscribe from this group, send email to
 <br> [email protected]
 <br> For more options, visit this group at
 <br> http://groups.google.com/group/swn-talk?hl=3Den
 <br> <p>For more about the SeattleWireless.NET project, see http://seattle=
wireless.net/<br>
-~----------~----~----~----~------~----~------~--~---<br>
<br>

------=_Part_77938_14311967.1228956470066--