From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Buesch Subject: Re: [Madwifi-devel] ar5k and Atheros AR5005G Date: Wed, 29 Nov 2006 17:03:21 +0100 Message-ID: <200611291703.21648.mb@bu3sch.de> References: <1164746352.31456.22.camel@systems03.lan.brontes3d.com> <200611291638.56759.mb@bu3sch.de> <1443.194.45.26.221.1164815926.squirrel@webmail.otaku42.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: "David Kimdon" , "Nick Kossifidis" , "Daniel Drake" , netdev@vger.kernel.org, madwifi-devel@lists.sourceforge.net Return-path: Received: from static-ip-62-75-166-246.inaddr.intergenia.de ([62.75.166.246]:2232 "EHLO vs166246.vserver.de") by vger.kernel.org with ESMTP id S967455AbWK2QDf (ORCPT ); Wed, 29 Nov 2006 11:03:35 -0500 To: "Michael Renzmann" In-Reply-To: <1443.194.45.26.221.1164815926.squirrel@webmail.otaku42.de> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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.