linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Clark <Stephen.Clark@seclark.us>
To: David Miller <davem@davemloft.net>
Cc: jeff@garzik.org, jketreno@linux.intel.com,
	axjslack@bluebottle.com, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] Request for help...
Date: Tue, 24 Jul 2007 20:43:13 -0400	[thread overview]
Message-ID: <46A69CA1.5020706@seclark.us> (raw)
In-Reply-To: <20070724.173529.48529759.davem@davemloft.net>

David Miller wrote:

>From: Stephen Clark <Stephen.Clark@seclark.us>
>Date: Tue, 24 Jul 2007 20:30:16 -0400
>
>  
>
>>I find it really sad that a hardware vendor that is willing to write
>>and develope drivers for Linux for their hardware aren't helped more
>>by "the community" or is the "the community" only interested in
>>hacking drivers where the manufacturer give no or minimal support?
>>    
>>
>
>This is a massive mischaracterization of reality.
>
>I agree with every statement Jeff has made, Intel really is a problem
>child in this area, and consistently so.
>
>The only way we could "help them" more is to take over the code base
>and do the development for them.
>
>The thing you should find truly sad is how Intel handles these
>situations time and time again, rather than the tireless attempts of
>Jeff and others to education them on how to improve the situation.
>
>  
>
So if someone in "the community" really wanted to help  Intel why don't 
they take the
code Intel posts to  the ipw3945 ml and put it into where ever it is 
really supposed to go?
Instead of whining how Intel doesn't do it right.



-- 

"They that give up essential liberty to obtain temporary safety, 
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty 
decreases."  (Thomas Jefferson)




  reply	other threads:[~2007-07-25  0:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 15:02 Request for help Axj
2007-07-24 16:12 ` John W. Linville
2007-07-24 18:29   ` [ipw3945-devel] " Stephen Clark
2007-07-24 20:30     ` John W. Linville
2007-07-24 21:13       ` Jeff Garzik
2007-07-25  1:15         ` James Ketrenos
2007-07-25  0:03           ` Jeff Garzik
2007-07-25  0:30             ` Stephen Clark
2007-07-25  0:35               ` David Miller
2007-07-25  0:43                 ` Stephen Clark [this message]
2007-07-25  0:46                   ` David Miller
2007-07-25  1:05                     ` Stephen Clark
2007-07-25  1:18                       ` David Miller
2007-07-25  1:23                       ` Jeff Garzik
2007-07-25  1:29                         ` Stephen Clark
2007-07-25  1:40                     ` Jeff Garzik
2007-07-25  1:40                   ` Jeff Garzik
2007-07-25  0:45               ` Maurizio Monge
2007-07-25  1:35               ` Jeff Garzik
2007-07-25  8:01             ` James Ketrenos
2007-07-25 14:50               ` John W. Linville
2007-07-27 12:36               ` Jeff Garzik
2007-07-25 14:46             ` John W. Linville
2007-07-25 15:19               ` Jeff Garzik
2007-07-25  9:32 ` Zhu Yi
2007-07-26 15:10   ` Axj
2007-07-26 16:22     ` Pavel Roskin
2007-07-27  6:34       ` Axj
2007-07-27  7:44         ` Zhu Yi
2007-07-27  8:48           ` Axj
     [not found]           ` <200707270848.l6R8mqkh004526@mi1.bluebottle.com>
2007-07-27  8:56             ` Zhu Yi
2007-07-27  9:10               ` Axj
2007-07-30  0:58                 ` Zhu Yi
2007-08-01  6:40                   ` Axj

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=46A69CA1.5020706@seclark.us \
    --to=stephen.clark@seclark.us \
    --cc=axjslack@bluebottle.com \
    --cc=davem@davemloft.net \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=jeff@garzik.org \
    --cc=jketreno@linux.intel.com \
    --cc=linux-wireless@vger.kernel.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).