On 12/5/06, Stephen Hemminger <[EMAIL PROTECTED]> wrote:
On Tue, 5 Dec 2006 10:15:33 -0500
"Luis R. Rodriguez" <[EMAIL PROTECTED]> wrote:
> On 12/5/06, Michael Renzmann <[EMAIL PROTECTED]> wrote:
> openhal here.
> >
> > I've set up the suggested branches, with slight changing to the proposed
>
On Tue, 5 Dec 2006 10:15:33 -0500
"Luis R. Rodriguez" <[EMAIL PROTECTED]> wrote:
> On 12/5/06, Michael Renzmann <[EMAIL PROTECTED]> wrote:
> openhal here.
> >
> > I've set up the suggested branches, with slight changing to the proposed
> > names:
> >
> > * http://svn.madwifi.org/branches/madwifi-
On 12/5/06, Michael Renzmann <[EMAIL PROTECTED]> wrote:
openhal here.
I've set up the suggested branches, with slight changing to the proposed
names:
* http://svn.madwifi.org/branches/madwifi-old-openhal (based on r1142)
* http://svn.madwifi.org/branches/dadwifi-openhal (based on r1827)
Neithe
Hi all.
> To make things easier for development I'd like to suggest a few madwif
> ibranches created:
>
> * madwifi-1152-openhal: based on madwifi-1152, patched with my patch,
> added openhal, old hal removed. Working free solution. Should exist
> just as a reference and to allow users to checkout
On 12/1/06, Luis R. Rodriguez <[EMAIL PROTECTED]> wrote:
* madwifi-1152-openhal: based on madwifi-1152, patched with my patch,
added openhal, old hal removed. Working free solution. Should exist
just as a reference and to allow users to checkout a working free
alternative in the mean time.
typ
On 11/29/06, Stephen Hemminger <[EMAIL PROTECTED]> wrote:
On Wed, 29 Nov 2006 08:03:28 -0800
David Kimdon <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 29, 2006 at 04:38:56PM +0100, Michael Buesch wrote:
> > On Wednesday 29 November 2006 16:24, David Kimdon wrote:
> > > On Wed, Nov 29, 2006 at 04:12:
Hi.
Michael Buesch wrote:
IIRC Pavel already explained that getting rid of the HAL per se should be
no problem - it could easily be dissolved into the driver, if that is one
of the requirements to be fulfilled before the driver (MadWifi or DadWifi)
is considered for mainline inclusion. As soon a
On Wed, 29 Nov 2006 08:03:28 -0800
David Kimdon <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 29, 2006 at 04:38:56PM +0100, Michael Buesch wrote:
> > On Wednesday 29 November 2006 16:24, David Kimdon wrote:
> > > On Wed, Nov 29, 2006 at 04:12:33PM +0100, Michael Buesch wrote:
> > > > On Wednesday 29 No
On Wednesday 29 November 2006 16:58, Michael Renzmann wrote:
> Hi.
>
> > On Wednesday 29 November 2006 16:24, David Kimdon wrote:
> >> There is absolutely no reason why dadwifi can't be merged into the
> >> mainline once the hal issue is resolved.
> > Last time we talked about that stuff, it was d
On Wed, Nov 29, 2006 at 04:38:56PM +0100, Michael Buesch wrote:
> On Wednesday 29 November 2006 16:24, David Kimdon wrote:
> > On Wed, Nov 29, 2006 at 04:12:33PM +0100, Michael Buesch wrote:
> > > On Wednesday 29 November 2006 15:34, Nick Kossifidis wrote:
> > Why do you say that?
> >
> > There is
Hi.
> On Wednesday 29 November 2006 16:24, David Kimdon wrote:
>> There is absolutely no reason why dadwifi can't be merged into the
>> mainline once the hal issue is resolved.
> Last time we talked about that stuff, it was decided that
> we don't want a HAL... See archives.
IIRC Pavel already ex
On Wed, 2006-11-29 at 15:55 +0200, Nick Kossifidis wrote:
> I 've already ported ar5k to linux and it works with madwifi versions
> before the bsd-head merge, you can see more infos here ->
> http://madwifi.org/wiki/OpenHAL
>
> If i can help in any way feel free to mail ;-)
Thanks, I'm trying it
On Wednesday 29 November 2006 16:24, David Kimdon wrote:
> On Wed, Nov 29, 2006 at 04:12:33PM +0100, Michael Buesch wrote:
> > On Wednesday 29 November 2006 15:34, Nick Kossifidis wrote:
> > > Good luck then ;-)
> > >
> > > If anyone wants to help on making ar5k work with newer madwifi
> > > versi
On Wednesday 29 November 2006 16:24, David Kimdon wrote:
> On Wed, Nov 29, 2006 at 04:12:33PM +0100, Michael Buesch wrote:
> > On Wednesday 29 November 2006 15:34, Nick Kossifidis wrote:
> > > Good luck then ;-)
> > >
> > > If anyone wants to help on making ar5k work with newer madwifi
> > > versi
On Wed, Nov 29, 2006 at 10:21:09AM -0500, Dan Williams wrote:
> On Wed, 2006-11-29 at 16:12 +0100, Michael Buesch wrote:
> > On Wednesday 29 November 2006 15:34, Nick Kossifidis wrote:
> > > Good luck then ;-)
> > >
> > > If anyone wants to help on making ar5k work with newer madwifi
> > > version
On Wed, Nov 29, 2006 at 04:12:33PM +0100, Michael Buesch wrote:
> On Wednesday 29 November 2006 15:34, Nick Kossifidis wrote:
> > Good luck then ;-)
> >
> > If anyone wants to help on making ar5k work with newer madwifi
> > versions and fix bugs etc (that 'll also help bsd ppl) plzz mail me.
> > W
On Wed, 2006-11-29 at 16:12 +0100, Michael Buesch wrote:
> On Wednesday 29 November 2006 15:34, Nick Kossifidis wrote:
> > Good luck then ;-)
> >
> > If anyone wants to help on making ar5k work with newer madwifi
> > versions and fix bugs etc (that 'll also help bsd ppl) plzz mail me.
> > We can m
On Wednesday 29 November 2006 15:34, Nick Kossifidis wrote:
> Good luck then ;-)
>
> If anyone wants to help on making ar5k work with newer madwifi
> versions and fix bugs etc (that 'll also help bsd ppl) plzz mail me.
> We can make it better.
>
> Nick
> P.S. Why not work on dawifi ?
Because it
Good luck then ;-)
If anyone wants to help on making ar5k work with newer madwifi
versions and fix bugs etc (that 'll also help bsd ppl) plzz mail me.
We can make it better.
Nick
P.S. Why not work on dawifi ?
2006/11/29, Michael Buesch <[EMAIL PROTECTED]>:
On Wednesday 29 November 2006 14:55,
On Wednesday 29 November 2006 14:55, Nick Kossifidis wrote:
> I 've already ported ar5k to linux and it works with madwifi versions
No, you misunderstood me.
Madwifi is not a native driver and will never be accepted into
mainline. My attempt is to write a native d80211 driver based
on the ar5k sou
I 've already ported ar5k to linux and it works with madwifi versions
before the bsd-head merge, you can see more infos here ->
http://madwifi.org/wiki/OpenHAL
If i can help in any way feel free to mail ;-)
Nick
2006/11/28, Michael Buesch <[EMAIL PROTECTED]>:
On Tuesday 28 November 2006 21:39,
On Tuesday 28 November 2006 21:39, Daniel Drake wrote:
> Hi,
>
> I'm interested in porting the ar5k driver to Linux after the recent SFLC
> conclusions on the legal status. However, the hardware I have here
> appears to be unsupported by ar5k:
>
> 01:04.0 0200: 168c:001a (rev 01)
> Subsys
Hi,
I'm interested in porting the ar5k driver to Linux after the recent SFLC
conclusions on the legal status. However, the hardware I have here
appears to be unsupported by ar5k:
01:04.0 0200: 168c:001a (rev 01)
Subsystem: 168c:2052
01:04.0 Ethernet controller: Atheros Communications, In
23 matches
Mail list logo
