From: Dan Williams <dcbw@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev <b43-dev@lists.infradead.org>,
linux-wireless@vger.kernel.org,
"Henry Ptasinski" <henryp@broadcom.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Nohee Ko" <noheek@broadcom.com>
Subject: Re: Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs)
Date: Thu, 14 Oct 2010 17:12:40 -0500 [thread overview]
Message-ID: <1287094360.22636.6.camel@dcbw.foobar.com> (raw)
In-Reply-To: <20101014171739.GA28522@suse.de>
On Thu, 2010-10-14 at 10:17 -0700, Greg KH wrote:
> On Thu, Oct 14, 2010 at 07:06:00PM +0200, Rafał Miłecki wrote:
> > 2010/10/14 Greg KH <gregkh@suse.de>:
> > > On Thu, Oct 14, 2010 at 06:40:14PM +0200, Rafał Miłecki wrote:
> > >> W dniu 11 października 2010 18:24 użytkownik Gábor Stefanik
> > >> <netrolller.3d@gmail.com> napisał:
> > >> > Doesn't brcm80211 contain register names for B2055?
> > >>
> > >> I've checked brcm80211 and noticed defines in
> > >> drivers/staging/brcm80211/phy/wlc_phy_radio.h.
> > >>
> > >> Whole brcm80211 driver is licensed as:
> > >> MODULE_LICENSE("Dual BSD/GPL");
> > >>
> > >> Mentioned file contains following comments:
> > >> +/*
> > >> + * Copyright (c) 2010 Broadcom Corporation
> > >> + *
> > >> + * Permission to use, copy, modify, and/or distribute this software for any
> > >> + * purpose with or without fee is hereby granted, provided that the above
> > >> + * copyright notice and this permission notice appear in all copies.
> > >>
> > >> Our b43 driver is licensed as:
> > >> MODULE_LICENSE("GPL");
> > >> and I am not sure if permission above is actually GPL-compatible. The
> > >> best option would be to add defines from wlc_phy_radio.h and include
> > >> Broadcom's copyright. However comment above wants us to include info
> > >> about free copying/modifying/using which is not GPL-compatible.
> > >>
> > >> Is there any way to solve this issue?
> > >
> > > I don't understand, are you just wanting to use the names in the .h file
> > > for the registers?
> >
> > Yes. I want to put lines like:
> > #define RADIO_2056_RX0 (0x6 << 12)
> > in my radio_2056.h
>
> I don't think that bitfields are copyrightable :)
Right. If you're just looking to include constants then you can copy
and paste them all over the place. It might be nice give Broadcom a
shout-out in the header, but pure numbers like this (command
definitions, register values, bitfields, constants, etc) simply aren't
copyrightable, just like you can't copyright a telephone book.
Dan
prev parent reply other threads:[~2010-10-14 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 16:40 Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs) Rafał Miłecki
2010-10-14 16:51 ` Greg KH
2010-10-14 17:06 ` Rafał Miłecki
2010-10-14 17:17 ` Greg KH
2010-10-14 17:24 ` Michael Büsch
2010-10-14 17:38 ` Rafał Miłecki
2010-10-14 18:14 ` John W. Linville
2010-10-14 18:18 ` Luis R. Rodriguez
2010-10-14 22:12 ` Dan Williams [this message]
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=1287094360.22636.6.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=b43-dev@lists.infradead.org \
--cc=brudley@broadcom.com \
--cc=gregkh@suse.de \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.com \
--cc=noheek@broadcom.com \
--cc=zajec5@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).