b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: b43-dev@lists.infradead.org
Subject: [PATCH] b43/b43legacy - Credit Broadcom with enabling the development of the drivers
Date: Wed, 22 Sep 2010 12:14:38 +0100	[thread overview]
Message-ID: <1285154078.4498.78.camel@i7.infradead.org> (raw)
In-Reply-To: <1285131914.14456.17.camel@maggie>

On Wed, 2010-09-22 at 07:05 +0200, Michael B?sch wrote:
> 
> +  Broadcom enabled the development of this driver, by providing all required
> +  hardware information in the form of binary software drivers.
> 
> Let me rephrase the comment a little bit. I will not change the
> meaning :)
> 
> +  Certain lawyers are wrong, and this driver proves it.
> +  http://tinyurl.com/ybl83uw
> 
> That's basically all it says. No more, no less. 

Fairly close :)

But it's a little more than that. It's more like:

 + I know you're scared that the world will end if you 'enable' this
 + driver in any way... but *look* -- you've actually been 'enabling'
 + if from the very beginning, and you haven't been eaten by a grue
 + yet. So please get over your stupid paranoia, and work with us
 + sensibly for once. Which would include:
 +  - letting us have permission to distribute the firmware.
 +  - giving us the odd hint about how to fix/improve the driver.
 +  - merging your new driver with the existing one, if appropriate.
 +  - etc.

It does us no harm to make it explicitly clear that the driver
development was 'enabled' by what Broadcom published. And if it has
*any* chance of showing the paranoid factions in Broadcom that their
fears are baseless, it has the potential to be helpful.

-- 
dwmw2

  reply	other threads:[~2010-09-22 11:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19 18:40 [PATCH] b43/b43legacy - Credit Broadcom with enabling the development of the drivers David Woodhouse
2010-09-20 16:36 ` Gábor Stefanik
2010-09-20 16:56   ` Luis R. Rodriguez
2010-09-20 19:02     ` Ehud Gavron
2010-09-20 19:09       ` Luis R. Rodriguez
2010-09-20 21:22         ` Ehud Gavron
2010-09-20 21:33           ` Luis R. Rodriguez
2010-09-20 21:51             ` Ehud Gavron
2010-09-21  4:01               ` Peter Stuge
2010-09-21  4:24                 ` Baybal Ni
2010-09-21  4:44                   ` Peter Stuge
2010-09-21 22:38                   ` Larry Finger
2010-09-22  5:05                     ` Michael Büsch
2010-09-22 11:14                       ` David Woodhouse [this message]
2010-09-22 17:26                         ` Luis R. Rodriguez
2010-09-22 11:07                     ` David Woodhouse
2010-09-20 21:42   ` David Woodhouse

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=1285154078.4498.78.camel@i7.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=b43-dev@lists.infradead.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).