From: Pavel Roskin <proski@gnu.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
"Michael Buesch" <mb@bu3sch.de>,
"John Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: Broadcom's Hybrid Driver
Date: Wed, 11 Jun 2008 17:53:48 -0400 [thread overview]
Message-ID: <1213221228.3649.15.camel@dv> (raw)
In-Reply-To: <48504417.7020803@lwfinger.net>
On Wed, 2008-06-11 at 16:31 -0500, Larry Finger wrote:
> I have two ideas about what Broadcom is doing.
>
> The b/g device with an ID of 0x4315 and an LP-PHY is the one that HP
> has been shipping in many laptops for the past few months. Perhaps HP
> wants to offer Linux on those computers, but doesn't want to use
> ndiswrapper for wireless access. HP might have enough clout to get
> Broadcom to budge a little on the subject of Linux.
That's sounds plausible.
> It is also possible that they want to stifle our RE efforts.
By releasing the driver? I don't think so. They don't think we are
such idiots to take their code and get in trouble, do they?
Besides, Broadcom contributes to the kernel. There are files with their
copyright, even in the SSB code. They just don't want to help with the
wireless driver.
> Given some of the other parts of the license relating to penalties,
> etc., anyone trying to RE this code could be in a heap of trouble.
Reverse engineering efforts should always be careful about the legal
aspects. Yet I see two possible loopholes.
1) The recipient is not necessarily bound by the license without having
signed it (in some jurisdictions).
2) Reverse engineering to the purpose of compatibility may not be
restricted (in some other jurisdictions).
Even if neither applies, it's not like we are losing anything. We
should just be careful, as always.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-11 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 17:44 Open source driver with binary HAL for BCM4313 from Broadcom Tim Gardner
2008-06-11 18:47 ` Michael Buesch
2008-06-11 19:47 ` Pavel Roskin
2008-06-11 20:26 ` Stefanik Gábor
2008-06-11 21:00 ` Larry Finger
2008-06-11 21:02 ` Pavel Roskin
2008-06-11 21:31 ` Broadcom's Hybrid Driver Larry Finger
2008-06-11 21:46 ` Stefanik Gábor
2008-06-11 21:53 ` Pavel Roskin [this message]
2008-06-11 21:55 ` Johannes Berg
2008-06-11 19:50 ` Open source driver with binary HAL for BCM4313 from Broadcom Stefanik Gábor
2008-06-11 20:02 ` Larry Finger
2008-06-11 19:46 ` Stephen Hemminger
2008-06-11 21:28 ` Johannes Berg
2008-06-11 21:12 ` Hauke Mehrtens
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=1213221228.3649.15.camel@dv \
--to=proski@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@gmail.com \
/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).