public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <bas.mevissen@hetnet.nl>
To: "Stuffed Crust" <pizza@shaftnet.org>,
	"David S. Miller" <davem@redhat.com>
Cc: <bas.mevissen@hetnet.nl>, <linux-kernel@vger.kernel.org>
Subject: RE: Broadcom BCM4306/BCM2050  support
Date: Thu, 1 May 2003 15:22:37 +0200	[thread overview]
Message-ID: <7dac01c30fe4$bbfebd60$db6897c2@hetnet.local> (raw)


> (..) And as Alan and myself have been
> talking to upper management entities at various wireless card
> companies we know the real reason has to do with making regulation
> agencies happy.  They do have drivers, and they do want to publish
> them and yes they recognize that this will expose a lot of their
> IP and they accept that.

OK. So at least they are open to it. Maybe they should drop a binary somewhere to get a start. It's not what you want in the long term, but I think good enough for now. Then we should work something out for the frequency settings.

What about the access points? There is nothing dangerous to set, so that information (or drivers and applications) can be given free. Does anyone know more about this?

I tried to get some info from an Edimax AP, but no success (yet). They used a PRISM chipset, but their own microcontroller and stuff for the USB instead of the chip from Intersil. So I guess that that will become difficult.

Regards,

Bas.




             reply	other threads:[~2003-05-01 13:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 13:22 bas.mevissen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01 13:35 Broadcom BCM4306/BCM2050 support Martin List-Petersen
2003-04-29 16:58 harry
2003-04-29 21:19 ` Oliver Neukum
2003-04-29 15:22 Nicholas Berry
2003-04-29 12:51 bas.mevissen
2003-04-29 14:40 ` Stuffed Crust
2003-05-01 11:01   ` David S. Miller
2003-04-29 12:28 bas.mevissen
2003-04-29 12:58 ` Martin List-Petersen
2003-04-29  6:16 Martin List-Petersen
2003-04-29 11:06 ` David S. Miller
2003-04-29 11:38   ` Carl-Daniel Hailfinger
2003-04-29 12:12     ` Martin List-Petersen
2003-04-29 12:27       ` Grzegorz Jaskiewicz
2003-04-29 13:26       ` Richard B. Johnson
2003-04-29 13:18         ` Alan Cox
2003-04-29 14:45           ` Stuffed Crust
2003-04-29 13:48         ` Carl-Daniel Hailfinger
2003-04-29 13:28   ` Alan Cox
2003-04-28 15:53 bas.mevissen

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='7dac01c30fe4$bbfebd60$db6897c2@hetnet.local' \
    --to=bas.mevissen@hetnet.nl \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pizza@shaftnet.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