linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Patrick Ziegler <patrick.ziegler@fh-kl.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Wimax
Date: Tue, 13 Nov 2007 10:29:37 -0500	[thread overview]
Message-ID: <1194967777.2955.31.camel@localhost.localdomain> (raw)
In-Reply-To: <47398FD8.6030409@fh-kl.de>

On Tue, 2007-11-13 at 12:51 +0100, Patrick Ziegler wrote:
> Hi,
> 
> is there any support for Wimax network cards in the kernel yet ?

No, unless those cards work like broadband cellular cards and just
present a USB serial interface to the kernel.  I haven't been able to
get a hold of WiMAX parts yet (preferably 802.16e-2005 mobile wimax
parts like the Airspan MiMAX USB) not that I've tried extremely hard.

> is this the right mailing list for this topic ?

Probably for now, yes.

> is someone working on a Wimax integration ?

I've been thinking about WiMAX for quite a while, but only recently have
real cards started to appear.  My fear is that with WiMAX, Linux will be
where it was with 802.11 3 years ago.  No hardware support, no vendor
support, nothing.

The problem with WiMAX is that many operators have _licensed_ spectrum
for WiMAX.  The software stack is more complicated, and vendors may put
more and more software on the host rather than in firmware.  However,
since software stack will deal with things like QoS in licensed spectrum
and whatnot, vendors may close the stack and do things like binary blobs
linked to the kernel module, or things like the old IPW regulatory
daemon.  Not sure how to avoid that.

Dan



  reply	other threads:[~2007-11-13 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 11:51 Wimax Patrick Ziegler
2007-11-13 15:29 ` Dan Williams [this message]
2007-11-14  9:24   ` Wimax Patrick Ziegler

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=1194967777.2955.31.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=patrick.ziegler@fh-kl.de \
    /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).