netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Kimdon <david.kimdon@devicescape.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Michael Buesch <mb@bu3sch.de>,
	Nick Kossifidis <mickflemm@gmail.com>,
	Daniel Drake <ddrake@brontes3d.com>,
	netdev@vger.kernel.org, madwifi-devel@lists.sourceforge.net
Subject: Re: [Madwifi-devel] ar5k and Atheros AR5005G
Date: Wed, 29 Nov 2006 07:30:38 -0800	[thread overview]
Message-ID: <20061129153038.GC5412@devicescape.com> (raw)
In-Reply-To: <1164813669.2752.31.camel@localhost.localdomain>

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
> > > 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 won't be merged mainline either.
> 
> I thought dadwifi was supposed to replace net80211 with d80211 (but not
> replace the binary HAL). 

yes

>  Aren't the two things complementary, 

yes

> or did
> you just decide that starting from scratch would produce a less crufty,
> better understood, better-d80211 integrated driver?

well, dadwifi will be (is) well integrated with d80211.  As far as
cruft goes, I'd rather call it historical artifacts :-)  We are doing
our best to minimize cruft while standing on the shoulders of madwifi.

-David

> 
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-11-29 15:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 20:39 ar5k and Atheros AR5005G Daniel Drake
2006-11-28 20:45 ` Michael Buesch
2006-11-29 13:55   ` [Madwifi-devel] " Nick Kossifidis
2006-11-29 14:05     ` Michael Buesch
2006-11-29 14:34       ` Nick Kossifidis
2006-11-29 15:12         ` Michael Buesch
2006-11-29 15:21           ` Dan Williams
2006-11-29 15:30             ` David Kimdon [this message]
2006-11-29 15:24           ` David Kimdon
2006-11-29 15:38             ` Michael Buesch
2006-11-29 15:58               ` Michael Renzmann
2006-11-29 16:03                 ` Michael Buesch
2006-11-30  5:33                   ` Michael Renzmann
2006-11-29 16:03               ` [Madwifi-devel] " David Kimdon
2006-11-29 20:13                 ` Stephen Hemminger
2006-12-01 18:35                   ` [Madwifi-devel] " Luis R. Rodriguez
2006-12-01 18:37                     ` Luis R. Rodriguez
2006-12-05 14:39                     ` Michael Renzmann
2006-12-05 15:15                       ` Luis R. Rodriguez
2006-12-05 17:18                         ` Stephen Hemminger
2006-12-05 18:57                           ` Luis R. Rodriguez
2006-11-29 15:47             ` Michael Buesch
2006-11-29 15:56     ` Daniel Drake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061129153038.GC5412@devicescape.com \
    --to=david.kimdon@devicescape.com \
    --cc=dcbw@redhat.com \
    --cc=ddrake@brontes3d.com \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=mb@bu3sch.de \
    --cc=mickflemm@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).