From: jayant@linux.intel.com
To: stephen.hemminger@vyatta.com
Cc: wimax@linuxwimax.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANN] WiMAX stack and drivers for Intel WiMAX Link 5050
Date: Tue, 8 Apr 2008 11:57:49 -0700 (PDT) [thread overview]
Message-ID: <4602.134.134.163.87.1207681069.squirrel@linux.intel.com> (raw)
>From: Stephen Hemminger [mailto:stephen.hemminger@vyatta.com]
>I notice that there is a binary supplicant required. After the
>experience with the ipw3945 driver lack of acceptance, I would
>hope that Intel would have learned that dependence on binary
>userspace components would limit acceptance especially
> with other more hostile projects (OpenBSD).
This is a temporary situation with supplicant while we resolve some
licensing issues. You should soon see us link with the opensource
supplicant. Our intention is to use all open source components whenever
available.
rgds
Jayant
next reply other threads:[~2008-04-08 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 18:57 jayant [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-01 18:07 [ANN] WiMAX stack and drivers for Intel WiMAX Link 5050 Inaky Perez-Gonzalez
[not found] ` <200804011107.38563.inaky-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2008-04-01 18:18 ` Stephen Hemminger
2008-04-01 18:33 ` Inaky Perez-Gonzalez
2008-04-08 15:13 ` Stephen Hemminger
2008-04-08 19:04 ` Stephen Hemminger
2008-04-08 18:56 ` Stephen Hemminger
2008-04-08 19:44 ` Marcel Holtmann
2008-04-08 20:59 ` Inaky Perez-Gonzalez
2008-04-09 6:10 ` Andi Kleen
[not found] ` <871w5fpnhs.fsf@basil.nowhere.org>
[not found] ` <200804091109.25265.inaky@linux.intel.com>
2008-04-09 20:31 ` Andi Kleen
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=4602.134.134.163.87.1207681069.squirrel@linux.intel.com \
--to=jayant@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen.hemminger@vyatta.com \
--cc=wimax@linuxwimax.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;
as well as URLs for NNTP newsgroup(s).