[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200611291703.21648.mb@bu3sch.de>
Date: Wed, 29 Nov 2006 17:03:21 +0100
From: Michael Buesch <mb@...sch.de>
To: "Michael Renzmann" <madwifi@...pam.otaku42.de>
Cc: "David Kimdon" <david.kimdon@...icescape.com>,
"Nick Kossifidis" <mickflemm@...il.com>,
"Daniel Drake" <ddrake@...ntes3d.com>, netdev@...r.kernel.org,
madwifi-devel@...ts.sourceforge.net
Subject: Re: [Madwifi-devel] ar5k and Atheros AR5005G
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 decided that
> > we don't want a HAL... See archives.
>
> 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 as there is source available
> to dissolve, at least.
Ok, so who actually does the work?
It has been talked a lot about what could and what should be done.
But who does it?
> From what I understood the "... once the hal issue is resolved" part of
> David's mail refered to exactly that question.
Ok, I don't know what "The HAL Issue" (tm) is.
Sounds like a hollywood movie theme to me. ;)
--
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists