linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ted Ts'o <tytso@mit.edu>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
	Charles Marker <Charles.Marker@atheros.com>,
	Jouni Malinen <Jouni.Malinen@atheros.com>,
	Kevin Hayes <kevin@atheros.com>,
	Zhifeng Cai <zhifeng.cai@atheros.com>,
	Don Breslin <Don.Breslin@atheros.com>,
	Doug Dahlby <Doug.Dahlby@atheros.com>,
	Julia Lawall <julia@diku.dk>
Subject: Re: Challenges with doing hardware bring up with Linux first
Date: Sun, 21 Nov 2010 09:29:06 -0800	[thread overview]
Message-ID: <20101121172906.GD3703@kroah.com> (raw)
In-Reply-To: <20101121130236.GE23423@thunk.org>

On Sun, Nov 21, 2010 at 08:02:36AM -0500, Ted Ts'o wrote:
> On Thu, Nov 18, 2010 at 08:46:11AM -0800, Luis R. Rodriguez wrote:
> > > What this provides for is a wonderful leverage for hardware
> > > vendors. ? If they provide GPL'ed code for their core hardware
> > > drivers that link against the Linux 802.11 layer, at one fell
> > > swoop they also get Windows 7 and Mac OS X drivers for free!
> > 
> > Yes, indeed ! That would be ideal indeed, but we'd need then an 802.11
> > stack which is also permissive licensed and then make APIs for that
> > 802.11 stack to match mac80211's or cfg80211's or bridges between
> > then. Because ultimately you will still need some 802.11 stack for
> > some OSes that don't have one.
> 
> I wonder how much this is true.  Yes, at the moment we still need to
> worry about those OS's that don't have one; but how much longer will
> hardware vendors need to support Windows XP?  If Linux, Windows 7, and
> Mac OS X all have an 802.11 stack, what other OS's do the hardware
> vendors need to support?

After visiting with a number of hardware companies that make wireless
chips, they mentioned that they still need to support, and they still
get new design wins for both eCos and vxworks, as well as some even
more obscure embedded operating systems that their customers use.

So unfortunatly, I don't see the ability for some of these vendors to
drop their own internal wifi stacks any year soon, if they still wish to
sell into some very large markets.

sorry,

greg k-h

  reply	other threads:[~2010-11-21 17:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  8:46 Challenges with doing hardware bring up with Linux first Luis R. Rodriguez
2010-11-18 11:11 ` Theodore Tso
2010-11-18 16:46   ` Luis R. Rodriguez
2010-11-21 13:02     ` Ted Ts'o
2010-11-21 17:29       ` Greg KH [this message]
2010-11-21 19:51         ` Luis R. Rodriguez
2010-11-21 20:31           ` Alan Cox
2010-11-21 21:44             ` Ted Ts'o
2010-11-21 21:47               ` Gábor Stefanik
2010-11-21 21:50                 ` Luis R. Rodriguez
2010-11-22  1:00                   ` Greg KH
2010-11-21 23:35                 ` Ted Ts'o
2010-11-21 21:49               ` Luis R. Rodriguez
2010-12-03 14:13               ` Pavel Machek
2010-11-21 21:47             ` Luis R. Rodriguez
2010-11-21 22:12               ` Luis R. Rodriguez
2010-11-18 11:34 ` Alan Cox
2010-11-18 16:51   ` Luis R. Rodriguez
2010-11-30 19:26     ` Pavel Machek
2010-11-30 19:30       ` Luis R. Rodriguez
2010-11-30 19:41         ` Luis R. Rodriguez
2010-11-30 20:00         ` Pavel Machek
2010-11-30 20:09           ` Luis R. Rodriguez
2010-11-30 20:13           ` david
2010-12-01 16:02             ` Bradley M. Kuhn
2010-11-18 16:45 ` Greg KH
2010-11-18 16:53   ` Luis R. Rodriguez
2010-11-18 17:23     ` Stephen Hemminger
2010-11-21  0:32     ` Adrian Chadd
2010-11-21  5:53       ` Luis R. Rodriguez
2010-11-21  7:11         ` Adrian Chadd

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=20101121172906.GD3703@kroah.com \
    --to=greg@kroah.com \
    --cc=Charles.Marker@atheros.com \
    --cc=Don.Breslin@atheros.com \
    --cc=Doug.Dahlby@atheros.com \
    --cc=Jouni.Malinen@atheros.com \
    --cc=davem@davemloft.net \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=julia@diku.dk \
    --cc=kevin@atheros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=shemminger@vyatta.com \
    --cc=tytso@mit.edu \
    --cc=zhifeng.cai@atheros.com \
    /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).