All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>, "Ted Ts'o" <tytso@mit.edu>,
	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 14:12:25 -0800	[thread overview]
Message-ID: <AANLkTi=PQmAfNPFj9pytgP0yMX+B8eZ6Bg3KYwyZZsO3@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi==VRvn2XjNf3EWZf8jAXwFTrRz8uyFSnnYVi8c@mail.gmail.com>

On Sun, Nov 21, 2010 at 1:47 PM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> On Sun, Nov 21, 2010 at 12:31 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>>> Right -- which is why ideally I think it'd be nice to have an open
>>> permissive stack people shared. My preference would be to just pick up
>>
>> Which we know in practice they won't. They'll sit on fixes (often
>> security fixes) and tweak and add private copies of features. In turn the
>> Linux one could then only keep up by adding features itself - which would
>> have to be GPL to stop the same abuse continuing.
>>
>> It's a nice idea but the corporations exist to make money and adding
>> proprietary custom stack add-ons is clearly a good move on their part to
>> do that.
>
> I agree completely with you. Its up to companies to decide whether or
> not they want to do that and ultimately traditionally companies have
> preferred not to. I actually think there is more to it than not
> wanting though... As I see it without people upstream working for some
> of these companies its really hard for them to get these ideas and
> actually believe in the possibility of it and the benefits. I'm
> voicing this publicly to our own managers and lkml because I'd like to
> see that companies get the message because realistically I really
> don't expect anything like this has been *seriously* considered
> before. When I ask people about it, I often hear people say they think
> it'd be nice, but that's about it. Nothing more. No push, no action.
> Its to the industry's best interest IMHO. Even if a common 802.11
> stack was shared, if it was permissive licensed companies could still
> go on and hack their own proprietary crap on top if they so wish, so
> that would still be an option.
>
> My point with all this thread is this: companies tend to not think out
> of the proprietary box they have been put in by old driver development
> habits, and driver development should not be so hard and tedious. They
> should start considering working on more open solutions even for
> proprietary operating systems, under a permissive license. I suspect
> this will help out with resources considerations, bug fix propagation
> and coordination between supporting different Operating Systems. We
> also stand to gain from this on Linux too, after all a driver bug fix
> for hardware sensitive code will need to be propagated to other OSes
> anyway.
>
> I can surely ignore the other OSes and their IMHO their terrible
> software practices but I can't because although it only affects Linux
> in a tedious way I think we can do better and strive for that. If
> sharing an 802.11 stack seems like a pipe dream oh well, at least I
> think we should consider opening up the code for the other OSes and
> let communities help with that crap for our company. Let it evolve
> naturally. The benefits of FOSS cannot just only benefit Linux.

Maybe what we need is a BSD guy at Atheros :)

  Luis

  reply	other threads:[~2010-11-21 22:12 UTC|newest]

Thread overview: 32+ 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
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-12-29 21:35                 ` Enrico Weigelt
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 [this message]
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='AANLkTi=PQmAfNPFj9pytgP0yMX+B8eZ6Bg3KYwyZZsO3@mail.gmail.com' \
    --to=lrodriguez@atheros.com \
    --cc=Charles.Marker@atheros.com \
    --cc=Don.Breslin@atheros.com \
    --cc=Doug.Dahlby@atheros.com \
    --cc=Jouni.Malinen@atheros.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --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=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 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.