Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: kd4e <doc@kd4e.com>
To: Jeff Laughlin <jeff.laughlin@gmail.com>
Cc: "Curt, WE7U" <archer@eskimo.com>,
	Linux Hams <linux-hams@vger.kernel.org>,
	ChristianHams@yahoogroups.com,
	ham-computers <ham-computers@mailman.qth.net>,
	Ham-Linux <ham-linux@mailman.qth.net>
Subject: Re: Take ACER Off your Linux-Friendly List
Date: Wed, 29 Jul 2009 23:02:32 -0500	[thread overview]
Message-ID: <4A711B58.2060605@kd4e.com> (raw)
In-Reply-To: <8ea83f40907291943v41f90ab3h9cea4f07c2ef0cb2@mail.gmail.com>

Acer chooses with whom they sign contracts for sub-devices 
like wireless
nics.  If they had insisted on nics with Linux drivers they 
would have
received them.  Other companies have.  I already own 
Linux-friendly
b/g/n devices, so it is nothing bleeding-edge to do so.

There are drivers out there for Atheros b/g/n nics but I 
don't have the
time to chase them down and fuss with Alpha drivers - this 
laptop was
to be a productivity tool - right now it's a defective piece 
of hardware.

Since I told the salesman it was for Linux and was not 
warned it was
non-Linux compatible they will get it back.

Manufactures need to stop wasting the time of customers and 
give
us what we want - in this economy customers are getting 
harder to
find - and Linux use is growing like crazy.

 > Jeff Laughlin wrote:
> Vendors don't hate Linux, they just don't like it enough.
> 
> Usually wireless or other devices are unsupported by Linux because
> 1. Vendor doesn't care
> 2. Driver loads firmware or VHDL code or something at initialization 
> which the vendor has licensed from a 3rd party under restrictive terms
> 3. Vendor intentionally locks out FOSS drivers because of silly FCC 
> rules about frequency agility
> 
> It can be neigh on impossible to create clean room drivers based on 
> reverse engineering for stuff like that.
> 
> Anyway, while Acer is complicit, they are really just a middle man. It's 
> really the device vendor that is ultimately to blame.

-- 

Thanks! & 73, doc, KD4E
FS/Swap/Wanted: http://kd4e.com/swapn.html
Free OS : http://www.PuppyLinux.com
Personal: http://kd4e.com
             |_|___|_|
             | | & | |
        /\      {|
       /  \     {|
      /    \    {|
     /   @  \   {|
     |   |~_|~~~~|
     |   -| |    |
============\ # KD4E
Have an http://ultrafidian.com day!

  parent reply	other threads:[~2009-07-30  4:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30  3:00 Take ACER Off your Linux-Friendly List kd4e
2009-07-30  2:35 ` Curt, WE7U
2009-07-30  3:55   ` kd4e
2009-07-30 14:48     ` [Ham-Linux] " match
2009-07-30 15:23       ` Robert Eliassen
2009-07-30 16:19         ` F8arr
2009-08-02  4:06     ` Stef Daniels VK5HSX
     [not found]   ` <8ea83f40907291943v41f90ab3h9cea4f07c2ef0cb2@mail.gmail.com>
2009-07-30  4:02     ` kd4e [this message]
2009-07-30  9:55       ` walter harms
2009-07-30 10:41         ` richard.bown
2009-07-30 21:37           ` Nate Bargmann
2009-07-30 17:10         ` kd4e
2009-07-30 16:38           ` walter harms
2009-07-30 10:55       ` Nate Bargmann
2009-07-31  3:42 ` [Ham-Linux] " dtx
2009-07-30 19:48   ` Mike McCarthy, W1NR
2009-07-30 20:46   ` kd4e
2009-07-31 21:14   ` kd4e

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=4A711B58.2060605@kd4e.com \
    --to=doc@kd4e.com \
    --cc=ChristianHams@yahoogroups.com \
    --cc=archer@eskimo.com \
    --cc=ham-computers@mailman.qth.net \
    --cc=ham-linux@mailman.qth.net \
    --cc=jeff.laughlin@gmail.com \
    --cc=linux-hams@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