All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Renzmann <madwifi@nospam.otaku42.de>
To: Michael Buesch <mb@bu3sch.de>
Cc: netdev@vger.kernel.org, madwifi-devel@lists.sourceforge.net,
	Nick Kossifidis <mickflemm@gmail.com>
Subject: Re: ar5k and Atheros AR5005G
Date: Thu, 30 Nov 2006 06:33:36 +0100	[thread overview]
Message-ID: <456E6D30.9030904@otaku42.de> (raw)
In-Reply-To: <200611291703.21648.mb@bu3sch.de>

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 as there is source available
>> to dissolve, at least.
> Ok, so who actually does the work?

The MadWifi team? It won't happen today or tomorrow, but I'm confident 
that it will happen. Any contribution to that effort is highly welcome - 
the more people help, the faster will the goal be reached.

>> 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.

You referred to the archives where that exact "issue"(s) (binary-only, 
non-free, no sources, unwanted level of abstraction) has/have been 
discussed in lenght, but you claim you didn't have a clue what David was 
talking about? Come on.

Bye, Mike

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-11-30  5:33 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
2006-11-30  5:33                   ` Michael Renzmann [this message]
2006-11-29 16:03               ` 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=456E6D30.9030904@otaku42.de \
    --to=madwifi@nospam.otaku42.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.