mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Michael Buesch <mb@bu3sch.de>,
	madwifi-devel@lists.sourceforge.net, lwn@lwn.net,
	mcgrof@gmail.com, david.kimdon@devicescape.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: ANNOUNCE: SFLC helps developers assess ar5k (enabling free Atheros HAL)
Date: Wed, 15 Nov 2006 20:26:29 +0100	[thread overview]
Message-ID: <1163618789.31358.152.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061115192054.GA10009@tuxdriver.com>

On Wed, 2006-11-15 at 14:21 -0500, John W. Linville wrote:
> On Wed, Nov 15, 2006 at 07:42:14PM +0100, Michael Buesch wrote:
> 
> > Now that it seems to be ok to use these openbsd sources, should I port
> > them to my driver framework?
> > I looked over the ar5k code and, well, I don't like it. ;)
> > I don't really like having a HAL. I'd rather prefer a "real" driver
> > without that HAL obfuscation.
> 
> I don't think anyone likes the HAL-based architecture.  I don't think
> we will accept a HAL-based driver into the upstream kernel.
> 
> The point is that the ar5k is now safe to be used as a reference and
> source of information (and code, as appropriate) without copyright FUD.
> Distilling that information into a proper Linux driver is work that
> remains to be done.

there have been several efforts on this before; is it worth revitalizing
one of them?

Also I suspect that if you merge a provisional driver early, lots of
folks will switch to it and start beating on it and fixing the style etc
issues...


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org


  parent reply	other threads:[~2006-11-15 19:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  3:10 John W. Linville
2006-11-15 18:42 ` Michael Buesch
2006-11-15 19:21   ` John W. Linville
2006-11-15 19:26     ` Michael Buesch
2006-11-15 19:35       ` [Madwifi-devel] " Ben Greear
2006-11-16 14:18       ` Jochen Friedrich
2006-11-16 14:56         ` [Madwifi-devel] " Michael Renzmann
2006-11-15 19:26     ` Arjan van de Ven [this message]
2006-11-15 19:39     ` Pavel Roskin
2006-11-15 20:02       ` Michael Buesch
2006-11-16  5:37         ` Michael Renzmann
2006-11-16 10:07           ` Nick Kossifidis
2006-11-16 11:55             ` Michael Renzmann
2006-11-15 23:28       ` [Madwifi-devel] ANNOUNCE: SFLC helps developers assessar5k " David Kimdon
2006-11-16 14:50       ` [Madwifi-devel] ANNOUNCE: SFLC helps developers assess ar5k " Dan Williams

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=1163618789.31358.152.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=david.kimdon@devicescape.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lwn@lwn.net \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=mb@bu3sch.de \
    --cc=mcgrof@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

all inboxes | Powered by JetHome®