netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "Michael Renzmann" <madwifi@nospam.otaku42.de>
Cc: "David Kimdon" <david.kimdon@devicescape.com>,
	"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 17:03:21 +0100	[thread overview]
Message-ID: <200611291703.21648.mb@bu3sch.de> (raw)
In-Reply-To: <1443.194.45.26.221.1164815926.squirrel@webmail.otaku42.de>

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.

  reply	other threads:[~2006-11-29 16:03 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
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 [this message]
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=200611291703.21648.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=david.kimdon@devicescape.com \
    --cc=ddrake@brontes3d.com \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=madwifi@nospam.otaku42.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).