b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bu3sch.de>
To: b43-dev@lists.infradead.org
Subject: [PATCH] b43/b43legacy - Credit Broadcom with enabling the development of the drivers
Date: Wed, 22 Sep 2010 07:05:14 +0200	[thread overview]
Message-ID: <1285131914.14456.17.camel@maggie> (raw)
In-Reply-To: <AANLkTikMZQ6G0=hLAdehinM1LNo7NzVVEE4xbK6fU0yP@mail.gmail.com> (sfid-20100921_183849_107489_3B5237EC)

On Tue, 2010-09-21 at 15:38 -0700, Larry Finger wrote: 
> 
> NACK on the patch that started this thread. Broadcom got caught
> violating the GPL and had to provide the binary drivers to compensate
> for that. They did not provide anything voluntarily.

Hm, I actually planned to not reply to this thread, but I think
I do have to comment on that one. :)

I'm not speaking for Broadcom or anybody else. However, I think first
of all Broadcom wasn't caught of anything. (I guess you are talking
about the WRT issue, right?). It's the _vendors_ who violated the GPL.

Second thing is that I do not think it's possible at all to compensate
for a GPL violation by providing binary object code. I don't
have to explain why this is the case. It's obvious.

Back to the original patch. I do think that David is misunderstood here.
I also misunderstood him when we talked about that earlier.
Here's the original comment again:

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

In the end, I am not interested in these legal fights at all. So I do not
have an opinion on whether the patch should be applied or not. I am only
interested in technical issues and I'll leave the rest to others who might
know better (or not).

-- 
Greetings Michael.

  reply	other threads:[~2010-09-22  5:05 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 [this message]
2010-09-22 11:14                       ` David Woodhouse
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=1285131914.14456.17.camel@maggie \
    --to=mb@bu3sch.de \
    --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).