All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Budhee Jamaich <budheej@gmail.com>
Cc: Dan Williams <dcbw@redhat.com>,
	linux-wireless@vger.kernel.org, Kalle Valo <kalle.valo@nokia.com>
Subject: Re: madwifi is not fully open source
Date: Tue, 12 Feb 2008 08:58:57 -0500	[thread overview]
Message-ID: <20080212135857.GA3051@tuxdriver.com> (raw)
In-Reply-To: <57314e840802120045h6e6960d8jde5657da8aff0e3e@mail.gmail.com>

On Tue, Feb 12, 2008 at 10:45:40AM +0200, Budhee Jamaich wrote:

> First - thank you for the detailed response!

Yes, thanks Dan!

> So even if a vendor is willng to completely Open Source it's code,
> having FCC troubles
> is a serious problem.

The answer of course is "it depends".  For example, depending on the
device it might be possible to provide code to configure the device
in "good" ways without necessarily revealing how to configure it in
"bad" ways...YMMV.  This may be more or less difficult depending on
the exact details of your hardware design.

> Is there any vendor who walked this path ? complete Open Source RF code ?
> If yes, has it's chip got FCC certified ?

The rtl8180 driver does not use any firmware and is completely open
source.  The driver code contains lots of "magic number" tables related
to initializing and configuring the device.  I don't know enough
about the hardware to tell you if the hardware is flexible enough
to be easily forced into non-compliant power or frequency settings,
so I can't really characterize the risk to Realtek.

I do know that Realtek supported rtl8180 driver development with
datasheets and access to developers.  Presumably they feel that
whatever risk there is is acceptable to their business.

Hth!

John
-- 
John W. Linville
linville@tuxdriver.com

      parent reply	other threads:[~2008-02-12 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 22:27 madwifi is not fully open source Budhee Jamaich
2008-02-11 22:48 ` Dan Williams
2008-02-12  5:24   ` Kalle Valo
2008-02-12  7:53   ` Nick Kossifidis
2008-02-12  8:45   ` Budhee Jamaich
2008-02-12  9:13     ` Holger Schurig
2008-02-12 12:18       ` Eddy Petrișor
2008-02-12 14:17       ` John W. Linville
2008-02-14 15:45         ` Luis R. Rodriguez
2008-02-12 13:58     ` John W. Linville [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=20080212135857.GA3051@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=budheej@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=kalle.valo@nokia.com \
    --cc=linux-wireless@vger.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.