linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: "Dan Williams" <dcbw@redhat.com>
Cc: "Nicolas Pitre" <nico@cam.org>, "Michael Buesch" <mb@bu3sch.de>,
	"Stefanik Gábor" <netrolller.3d@gmail.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008
Date: Tue, 15 Jul 2008 21:20:06 +0300	[thread overview]
Message-ID: <87bq0zau21.fsf@nokia.com> (raw)
In-Reply-To: <1216144711.13411.18.camel@localhost.localdomain> (ext Dan Williams's message of "Tue\, 15 Jul 2008 13\:58\:31 -0400")

"Dan Williams" <dcbw@redhat.com> writes:

> Some of the issues with the current Marvell 83xx GPL drivers that have
> gotten out are (a) code style, (b) lots of commented out stuff that's
> never used, (c) OS abstraction that's unnecessary on Linux, (d) doesn't
> use mac80211, and (e) uses private ioctls.  

I think you just listed exactly the problems with all vendor WLAN
drivers. 

I think Intel is the only expection here. Is there anyone else?

> So hopefully you're writing a new 83xx driver from scratch :)

And it always seems that this is the only viable way to solve it :)

(dropping lkml and netdev from CC)

-- 
Kalle Valo

  parent reply	other threads:[~2008-07-15 18:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 19:09 Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008 John W. Linville
2008-07-10  0:13 ` Tomas Winkler
2008-07-10  6:52   ` Ron Rindjunsky
2008-07-10 14:30   ` Kalle Valo
2008-07-11  1:41     ` Jouni Malinen
2008-07-11  4:46       ` Kalle Valo
2008-07-10  6:41 ` Mark Ryden
2008-07-10  7:21 ` Holger Schurig
2008-07-10  7:23   ` Johannes Berg
2008-07-10 10:22 ` Johannes Berg
2008-07-10 10:50   ` Tomas Winkler
2008-07-10 14:31 ` Johannes Berg
2008-07-10 15:15   ` Tomas Winkler
2008-07-10 15:52 ` Inaky Perez-Gonzalez
2008-07-10 16:12 ` Stefanik Gábor
2008-07-10 16:15   ` Michael Buesch
2008-07-15 17:16     ` Dan Williams
2008-07-15 17:31       ` Nicolas Pitre
2008-07-15 17:58         ` Dan Williams
2008-07-15 18:02           ` Dan Williams
2008-07-15 18:14           ` Nicolas Pitre
2008-07-15 18:38             ` Dan Williams
2008-07-21 14:23             ` Dan Williams
2008-07-21 16:46               ` Nicolas Pitre
2008-07-15 18:20           ` Kalle Valo [this message]
2008-07-14 15:05 ` Guy Cohen
2008-07-15 17:42   ` John W. Linville
2008-07-15 18:15     ` Dan Williams
2008-07-16  8:24       ` Johannes Berg
2008-07-16 16:27         ` Dan Williams
2008-07-14 15:43 ` Guy Cohen
2008-07-15 18:26 ` REVISED AGENDA -- " John W. Linville
2008-07-16  8:40   ` Johannes Berg
2008-07-16 11:29     ` Tomas Winkler
2008-07-16 18:48   ` 2nd " John W. Linville
2008-07-16 19:58     ` John W. Linville
2008-07-17 10:05     ` Luis R. Rodriguez
2008-07-17 10:16     ` Luis R. Rodriguez
2008-07-18 23:23     ` 3rd " John W. Linville
  -- strict thread matches above, loose matches on Subject: below --
2008-07-10  7:41 Joerg Pommnitz

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=87bq0zau21.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=netrolller.3d@gmail.com \
    --cc=nico@cam.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).