<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://purl.org/rss/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

  <channel rdf:about="http://lwn.net/headlines/278132/">
    <title>LWN: Comments on "Atheros hires ath5k developer"</title>
    <link>http://lwn.net/Articles/278132/</link>
    <description>
This is a special feed containing comments posted
to the individual LWN article titled &quot;Atheros hires ath5k developer&quot;.

    </description>

    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>2</syn:updateFrequency>
    <items>
      <rdf:Seq>
	<rdf:li resource="http://lwn.net/Articles/283401/rss" />
	<rdf:li resource="http://lwn.net/Articles/282840/rss" />
	<rdf:li resource="http://lwn.net/Articles/279061/rss" />
	<rdf:li resource="http://lwn.net/Articles/278727/rss" />
	<rdf:li resource="http://lwn.net/Articles/278629/rss" />
	<rdf:li resource="http://lwn.net/Articles/278603/rss" />
	<rdf:li resource="http://lwn.net/Articles/278589/rss" />
	<rdf:li resource="http://lwn.net/Articles/278403/rss" />
	<rdf:li resource="http://lwn.net/Articles/278383/rss" />
	<rdf:li resource="http://lwn.net/Articles/278297/rss" />
	<rdf:li resource="http://lwn.net/Articles/278293/rss" />
	<rdf:li resource="http://lwn.net/Articles/278289/rss" />
	<rdf:li resource="http://lwn.net/Articles/278290/rss" />
	<rdf:li resource="http://lwn.net/Articles/278283/rss" />
	<rdf:li resource="http://lwn.net/Articles/278270/rss" />
	<rdf:li resource="http://lwn.net/Articles/278264/rss" />
	<rdf:li resource="http://lwn.net/Articles/278255/rss" />
	<rdf:li resource="http://lwn.net/Articles/278229/rss" />
	<rdf:li resource="http://lwn.net/Articles/278224/rss" />
	<rdf:li resource="http://lwn.net/Articles/278214/rss" />
	<rdf:li resource="http://lwn.net/Articles/278207/rss" />
	<rdf:li resource="http://lwn.net/Articles/278191/rss" />
	<rdf:li resource="http://lwn.net/Articles/278187/rss" />
	<rdf:li resource="http://lwn.net/Articles/278182/rss" />
	<rdf:li resource="http://lwn.net/Articles/278181/rss" />
	<rdf:li resource="http://lwn.net/Articles/278166/rss" />
	<rdf:li resource="http://lwn.net/Articles/278160/rss" />
	<rdf:li resource="http://lwn.net/Articles/278157/rss" />
	<rdf:li resource="http://lwn.net/Articles/278155/rss" />
      
      </rdf:Seq>
    </items>

  </channel>
    <item rdf:about="http://lwn.net/Articles/283401/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/283401/rss</link>
      <dc:date>2008-05-21T20:52:26+00:00</dc:date>
      <dc:creator>opheriper</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
congratulations, Luis!

I've got a job offer from Ahteros too, and another offer from Cisco, both are ASIC design
position. Now I'm confusing which company I should join, could you guys give me some advice,
thanks very much!
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/282840/rss">
      <title>I wonder if it is market pressure</title>
      <link>http://lwn.net/Articles/282840/rss</link>
      <dc:date>2008-05-17T11:07:24+00:00</dc:date>
      <dc:creator>muwlgr</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
S*it, how wrong I was. Asus Z99Le uses A8LE motherboard with Atheros 5006EG (or 5007EG?) card
: PCI ven:dev 168c:001c, subsystem 1a3b:1026 . Never ever buy it in your life. There will be
neither working madwifi/ath5k driver, nor anything working opensource from Atheros. Trust me
:&amp;gt;
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/279061/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/279061/rss</link>
      <dc:date>2008-04-22T14:04:24+00:00</dc:date>
      <dc:creator>MisterIO</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
I wasn't talking about that.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278727/rss">
      <title>I wonder if it is market pressure</title>
      <link>http://lwn.net/Articles/278727/rss</link>
      <dc:date>2008-04-19T15:30:19+00:00</dc:date>
      <dc:creator>muwlgr</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
ASUS Z99 is a great serie. They are all-Intel models (chipset, video, wireless), they are
light, and they are sold without Windows. ASUS definitely has to compete with itself.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278629/rss">
      <title>I wonder if it is market pressure</title>
      <link>http://lwn.net/Articles/278629/rss</link>
      <dc:date>2008-04-18T16:11:48+00:00</dc:date>
      <dc:creator>ofeeley</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
I know that when I read your posts about it I decided to hold off on getting one.  I purchased
another machine instead (which has an intel3945 wireless chipset and as a result works
wonderfully with Fedora 8 and Fedora 9 Preview's version of NetworkManager.) I think a lot of
other people that are interested in using GNU/Linux are at the stage where they realize that
it's easier to buy hardware that's supportable by the community AND that hardware actually
exists -- mainly from Intel.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278603/rss">
      <title>I wonder if it is market pressure</title>
      <link>http://lwn.net/Articles/278603/rss</link>
      <dc:date>2008-04-18T12:29:23+00:00</dc:date>
      <dc:creator>drag</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt; What I am wondering about, is if this is happening because Atheros is losing business to
Intel on a scale that makes it worthwhile to hire a developer. &lt;/font&gt;



I know that with my EEE I ended up with a Atheros wifi. It wasn't even supported under
Madwifi, Xandros used these special 'swan' drivers I haven't heard of before. 

So I know that lots of Linux people were upset about that and it required the use of
ndiswrapper for a while till Atheros released a special patch specifically to allow Madwifi
driverrs to work. I told other people before the EEE came out that I was dissapointed that
Asus choose Atheros over Ralink or Intel, of course they all thought Madwifi was cool... until
after the EEE came out the Madwifi folks were completely powerless to support the hardware
until that HAL hack was released by Atheros.

Keep in mind that a angy customer making a support call is enough for Asus to loose
profitability on that EEE sale...

So they defenately were paying attention and it was a big enough issue that they (Atheros) had
to do a abnormal release.

I expect that other manufacturers were paying close attention to the EEE and they would of
noticed the problems with having to support a single-kernel-specific proprietary module and
the problems it caused OEMs and customers. 

Where as if they used Intel (or a handful of other manufacturer's cards) then it would of been
a complete non-issue. I expect that this has caused Atheros to loose out on a couple big
potential customers.


&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278589/rss">
      <title>I wonder if it is market pressure</title>
      <link>http://lwn.net/Articles/278589/rss</link>
      <dc:date>2008-04-18T07:47:24+00:00</dc:date>
      <dc:creator>tarjei</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
This is good news. 

What I am wondering about, is if this is happening because Atheros is losing business to Intel
on a scale that makes it worthwhile to hire a developer. 

One developer may cost somewhere around $200 000. You do not have to loose a lot of sales
before that becomes the cheapest option. 

With big OEMs like Dell and IBM focusing a lot more on Linux support on desktop machines than
they used to combined with Intel providing a very good alternative we might be seeing a
turning point when it comes to support for wireless cards. 

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278403/rss">
      <title>Broadcom</title>
      <link>http://lwn.net/Articles/278403/rss</link>
      <dc:date>2008-04-17T16:26:38+00:00</dc:date>
      <dc:creator>mb</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt; In my personal view, broadcom provide a more stable driver than atheros, &lt;/font&gt;

Am I missing something? Where does broadcom provide _any_ driver? (aside from binary MIPS
drivers and such stuff for embedded devices).
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278383/rss">
      <title>Broadcom</title>
      <link>http://lwn.net/Articles/278383/rss</link>
      <dc:date>2008-04-17T15:47:39+00:00</dc:date>
      <dc:creator>mjdcl</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
In my personal view, broadcom provide a more stable driver than atheros, I got atheros src
code, there even has a bug on Makefile...  it can't work on my board, reset always.


&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278297/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278297/rss</link>
      <dc:date>2008-04-17T07:07:51+00:00</dc:date>
      <dc:creator>johoho</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
it was never a secret that showing a company of how good you understand their own products
puts you in a good hiring position.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278293/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278293/rss</link>
      <dc:date>2008-04-17T06:22:48+00:00</dc:date>
      <dc:creator>pabs</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Found this link after googling for the crda thing:

&lt;a href=&quot;http://lwn.net/Articles/271037/&quot;&gt;http://lwn.net/Articles/271037/&lt;/a&gt;
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278289/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278289/rss</link>
      <dc:date>2008-04-17T05:59:46+00:00</dc:date>
      <dc:creator>pabs</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Isn't Atheros HAL/OpenHAL something that runs on the host CPU?

The folks at prism54.org are developing FreeMAC, free (GPLed with source code) firmware for
Conexant wireless chips. Seems they have it easy though, since the Prism54 wireless cards have
an ARM CPU on them.

So, as long as wireless devices don't require firmware images to be signed before running them
(like bitfrost), we'll likely be able to try to write free firmware - and violate the
regulations :)

Anyways, I don't see how one firmware image can know which country it is in and which
regulations to comply with, nor if the user has a special licence to do software
radio/hamradio or the like. Even a kernel driver probably wouldn't be able to know that
without some kind of configuration info passed to it.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278290/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278290/rss</link>
      <dc:date>2008-04-17T05:49:19+00:00</dc:date>
      <dc:creator>MisterIO</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
So, does that mean that reverse engineering is even more useful than what was supposed to be?

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278283/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278283/rss</link>
      <dc:date>2008-04-17T05:09:58+00:00</dc:date>
      <dc:creator>muwlgr</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
You mean, like &quot;Creative hires Daniel_K to stop him hurting their business strategy&quot; ? :&amp;gt;
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278270/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278270/rss</link>
      <dc:date>2008-04-17T03:05:32+00:00</dc:date>
      <dc:creator>ikm</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
My thoughts as well
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278264/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278264/rss</link>
      <dc:date>2008-04-17T01:46:20+00:00</dc:date>
      <dc:creator>BenHutchings</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
&quot;Intel are NOT that great, their wireless drivers still require binary-blob non-free
firmware.&quot;

So far as I know, all wireless Ethernet controllers require firmware. Some of them load it
from flash, but since no-one expects to boot over wireless Ethernet, that's an unnecessary
expense. The last controller I know of that booted from flash was the Ralink RT2560, which has
been superceded.

I don't whether the firmware fundamentally has to be non-free. Radio regulations in some
countries might require that. Even so, it will tend to be so interdependent with the hardware
as to be practically unalterable by outsiders.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278255/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278255/rss</link>
      <dc:date>2008-04-17T00:59:05+00:00</dc:date>
      <dc:creator>pabs</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Intel are NOT that great, their wireless drivers still require binary-blob non-free firmware.
At least their binary blob doesn't run on the host system any more, but fixing this issue
isn't something we will see without any reverse engineering by people outside of Intel:

&lt;a href=&quot;http://bughost.org/bugzilla/show_bug.cgi?id=1594&quot;&gt;http://bughost.org/bugzilla/show_bug.cgi?id=1594&lt;/a&gt;

I'd dearly like to see something like ath5k's OpenHAL or prism54's FreeMAC for Intel wireless
cards, but I wouldn't have the foggiest idea about were to find information about the
hardware.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278229/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278229/rss</link>
      <dc:date>2008-04-16T22:20:50+00:00</dc:date>
      <dc:creator>okeydoke</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
The OpenBSD Atheros driver could use some work too. It doesn't support 802.11g or WPA.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278224/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278224/rss</link>
      <dc:date>2008-04-16T21:54:38+00:00</dc:date>
      <dc:creator>nowster</dc:creator>
      <description>
      It appears to be tweakable via debugfs. 
&lt;a href=&quot;http://linuxwireless.org/en/developers/Documentation/mac80211/RateControl/PID&quot;&gt;Linux Wireless Wiki&lt;/a&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278214/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278214/rss</link>
      <dc:date>2008-04-16T20:43:22+00:00</dc:date>
      <dc:creator>drag</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt; Hopefully Luis will be allowed to release his efforts in a form that can be incorporated
into the stock kernel source.&lt;/font&gt;


That's what the man said in the article, that Atheros is trying to get driver support into the
vanilla kernel.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278207/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278207/rss</link>
      <dc:date>2008-04-16T19:57:45+00:00</dc:date>
      <dc:creator>k3ninho</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Ah.  An explanation for my rt2500pci mac80211-based driver falling back to low speeds and
requiring a 'iwconfig' at the command to get the device back to full speed.  Thank you!
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278191/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278191/rss</link>
      <dc:date>2008-04-16T19:05:28+00:00</dc:date>
      <dc:creator>nowster</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Hopefully Luis will be allowed to release his efforts in a form that can be incorporated into
the stock kernel source.

At the moment the semi-free madwifi is more reliable than ath5k with 2.6.25-rc kernels[*], due
(I suspect) to problems with the mac80211 layer being rather too aggressive in reducing the
link speed in face of less than ideal signal conditions. Signal quality/level monitoring
(using wavemon) suggests that unsmoothed values are causing the rate algorithms to believe
that conditions are worse than they actually are. I see similar problems with the in-kernel
rt2500 driver.

[*] Incidentally, the 2.6.25-rc8 ath5k driver doesn't install, due to symbol mismatches.
compat-wireless does work.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278187/rss">
      <title>Broadcom</title>
      <link>http://lwn.net/Articles/278187/rss</link>
      <dc:date>2008-04-16T18:42:08+00:00</dc:date>
      <dc:creator>mb</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt; O Broadcom, where art thou?&lt;/font&gt;

Yeah, come on. I also need a job. :P
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278182/rss">
      <title>Broadcom</title>
      <link>http://lwn.net/Articles/278182/rss</link>
      <dc:date>2008-04-16T18:29:45+00:00</dc:date>
      <dc:creator>elanthis</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
O Broadcom, where art thou?
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278181/rss">
      <title>April 1</title>
      <link>http://lwn.net/Articles/278181/rss</link>
      <dc:date>2008-04-16T18:22:42+00:00</dc:date>
      <dc:creator>corbet</dc:creator>
      <description>
      Sorry for the hedging there - for some reason, something about the message set off my hoax alarms, to the point that I held it for a while to see what followups came.  I've removed the &quot;April&amp;nbsp;1&quot; reference from the blurb.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278166/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278166/rss</link>
      <dc:date>2008-04-16T17:41:47+00:00</dc:date>
      <dc:creator>JoeBuck</dc:creator>
      <description>
      If a company releases even a buggy driver, it still helps, because it provides information that the reimplementers need to know.
&lt;p&gt;
Ideally, of course, a good driver would be produced by effective two-way feedback between the experts on the hardware, and Linux kernel experts. One way is to get the company producing the product to hire an experienced Linux kernel developer to bridge the gaps, so good for Atheros.


      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278160/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278160/rss</link>
      <dc:date>2008-04-16T17:26:06+00:00</dc:date>
      <dc:creator>BenHutchings</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Ralink did release source for their Linux drivers, but that showed just how buggy they were.
The drivers that have made it into Linux upstream have been reimplemented by others.
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278157/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278157/rss</link>
      <dc:date>2008-04-16T17:16:04+00:00</dc:date>
      <dc:creator>drag</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Wow.

Go Atheros!

With them joining the ranks of companies like Ralink or Intel (sorry those are the ones that I
use, if there are others with good open drivers I want to know about it!) for providing good
open source drivers for Linux this is a very cool thing.

And special thanks for OBSD for providing the open source 'HAL' for Atheros.


Now this along with open source video driver support from Intel, AMD, and Via (hopefully..)
then things are looking up for these two traditionally sore spots on with open source drivers.

Amazing.

&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/278155/rss">
      <title>Atheros hires ath5k developer</title>
      <link>http://lwn.net/Articles/278155/rss</link>
      <dc:date>2008-04-16T17:10:47+00:00</dc:date>
      <dc:creator>mcgrof</dc:creator>
      <description>
      &lt;div class=&quot;FormattedComment&quot;&gt;&lt;pre&gt;
Certainly not an April 1st joke :)
&lt;/pre&gt;&lt;/div&gt;

      
      </description>
    </item>
</rdf:RDF>

