All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Schultz <eschultz@prplfoundation.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	<linux-wireless@vger.kernel.org>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: Re: New FCC requirements and Linux Wifi
Date: Wed, 3 Dec 2014 11:00:03 -0600	[thread overview]
Message-ID: <CAMkzgA64La8cwJcNNQ2i9GGksoWQNTcUAiva-7OW2b30eC3rCQ@mail.gmail.com> (raw)
In-Reply-To: <547ED33C.5020409@broadcom.com>

Arend,

Thanks, that is the publication!

I've tried to summarize the topic at
http://wiki.prplfoundation.org/wiki/Complying_with_FCC_rules_on_5ghz_wifi.
I hope that provides folks with enough background to understand what's
going on and the issues with fixing it. If you think you can add
additional information to clarify anything, don't hesitate to do so.

We do most of our discussions on our list at
openwrt@lists.prplfoundation.org so feel free to join the list and
share your thoughts on this with other members of the community. I'd
like to organize an online meeting this month (or early next) of all
the interested parties to discuss suggestions on how to handle this.

Thanks,

Eric

On Wed, Dec 3, 2014 at 3:09 AM, Arend van Spriel <arend@broadcom.com> wrote:
> On 12/02/14 20:35, Arend van Spriel wrote:
>>
>> On 12/02/14 01:31, John W. Linville wrote:
>>>
>>> On Mon, Dec 01, 2014 at 04:27:25PM -0600, Eric Schultz wrote:
>>>>
>>>> All,
>>>>
>>>> I work for the prpl Foundation, an open source foundation organized by
>>>> a number of companies, most related to MIPS. One project we work with
>>>> externally is the OpenWrt project. Recently one of our members
>>>> mentioned a new FCC requirement (described in FCC publication 594280)
>>>> which requires wifi hardware devices to restrict modifications in ways
>>>> that were not previously required. Some of the suggestions the company
>>>> had internally for complying would be to use features like Secure Boot
>>>> and other types of DRM-like mechanisms to prevent routers from being
>>>> modified. This obviously would be quite bad for the OpenWrt community
>>>> (and the embedded Linux community as a whole) so we agreed as a group
>>>> to try to provide hardware companies with a way of complying without
>>>> harming the community.
>
>
> The FCC publication can be found here:
>
> https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?switch=P&id=39498
>
> I had issues downloading the guidance document itself.
>
> Another fine read from 2010 is here:
>
> http://www.fcc.gov/oet/ea/presentations/files/oct10/FCC_Roundtable_General_Discussion_101910-Staff.pdf
>
> At page 13 of this document are draft updates that Eric is probably
> referring to.
>
> Regards,
> Arend
>
>>>> I'm looking to find individuals (and other companies!) interested in
>>>> working with myself and the foundation, companies, the OpenWrt
>>>> community and eventually regulators to provide guidance to hardware
>>>> companies on how to best comply with these rules. If you're interested
>>>> in getting involved or just would like to know more, please get in
>>>> touch with me. We want to make sure that routers and related embedded
>>>> Linux hardware is hackable and we could use all the help we could get.
>>>>
>>>> Thanks and I look forward to working with you,
>>>>
>>>> Eric
>>>
>>>
>>> Eric,
>>>
>>> Obviously, I would be interested in hearing more. I suspect there
>>> are others on the list that will be interested as well...
>>
>>
>> I think so too. Just not sure what "Linux hardware is hackable" really
>> means here. Well, I guess I mean to say: tell me more. I guess with
>> hardware companies you mean OEMs here, right?
>>
>> Regards,
>> Arend
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>



-- 
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschultz@prplfoundation.org
cell: 920-539-0404
skype: ericschultzwi
@EricPrpl

      reply	other threads:[~2014-12-03 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 22:27 New FCC requirements and Linux Wifi Eric Schultz
2014-12-02  0:31 ` John W. Linville
2014-12-02  6:23   ` Oleksij Rempel
2014-12-02 19:35   ` Arend van Spriel
2014-12-02 19:41     ` Eric Schultz
2014-12-03  9:09     ` Arend van Spriel
2014-12-03 17:00       ` Eric Schultz [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=CAMkzgA64La8cwJcNNQ2i9GGksoWQNTcUAiva-7OW2b30eC3rCQ@mail.gmail.com \
    --to=eschultz@prplfoundation.org \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.