<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ath5k on Insignificant Bits</title>
    <link>https://bobcopeland.com/blog/tags/ath5k/</link>
    <description>Recent content in Ath5k on Insignificant Bits</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 18 Jul 2010 00:39:27 +0000</lastBuildDate>
    <atom:link href="https://bobcopeland.com/blog/tags/ath5k/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kernel updates</title>
      <link>https://bobcopeland.com/blog/2010/07/kernel-updates/</link>
      <pubDate>Sun, 18 Jul 2010 00:39:27 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1506</guid> 
      <description>&lt;p&gt;During baby naps I actually did some Rio Karma work this week. First, I &lt;a href=&#34;http://marc.info/?l=linux-usb&amp;amp;m=127894796224563&amp;amp;w=2&#34;&gt;found and fixed&lt;/a&gt; a recent bug in usb storage that makes the Karma not work at all in 2.6.35. Then I finally set up my &lt;a href=&#34;http://git.kernel.org/?p=linux/kernel/git/bcopeland/omfs.git;a=shortlog;h=refs/heads/for-next&#34;&gt;omfs git tree&lt;/a&gt; on kernel.org, with a few patches I wrote almost two years ago, plus a recently found memory leak. I&amp;rsquo;ll try to get Linus to pull it in 2.6.36. Then, I made a new release of &lt;a href=&#34;https://bobcopeland.com/blog/karma/&#34;&gt;omfsprogs&lt;/a&gt; rewritten to use libomfs from the FUSE version of omfs (I also did this work two years ago). Now all is right in the Karma world again; time to ignore it for another 6 months.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ath5k AP Mode</title>
      <link>https://bobcopeland.com/blog/2009/11/ath5k-ap-mode/</link>
      <pubDate>Sun, 01 Nov 2009 18:29:22 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1399</guid> 
      <description>&lt;p&gt;People seem to keep asking about this, despite there being a &lt;a href=&#34;http://wireless.kernel.org/en/users/Documentation/hostapd&#34;&gt;quality page on kernel.org&lt;/a&gt; on how to run an AP with any mac80211 driver. So for what it&amp;rsquo;s worth, here&amp;rsquo;s how my setup works. Note if you are seeing flakiness with certain clients, e.g. it works fine with a computer but not with your cell phone, it is likely there is some bug with the power saving handling. I&amp;rsquo;m currently working on a few such issues, so it may be fixed soon enough.&lt;/p&gt;</description>
    </item>
    <item>
      <title>wl1251_sdio merged</title>
      <link>https://bobcopeland.com/blog/2009/08/wl1251_sdio-merged/</link>
      <pubDate>Tue, 11 Aug 2009 03:27:23 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1378</guid> 
      <description>&lt;p&gt;The SDIO patches for TI 1251 (Android wifi chipset) are finally merged into wireless-testing, so they should be a lot easier to hack on now. That means the driver should make it into 2.6.32, though at a rather experimental stage. I did fix some crashes on ifup/ifdown since last posting, but there&amp;rsquo;s always more work to do. Current todo list includes better behavior for non-polling controllers (make the irq have a top-half), tracking down a device hang on reinitialization, pushing the msm_wifi.ko module, and on and on.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ath5k performance history</title>
      <link>https://bobcopeland.com/blog/2009/07/ath5k-performance-history/</link>
      <pubDate>Fri, 03 Jul 2009 17:35:04 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1351</guid> 
      <description>&lt;p&gt;I was curious how well ath5k has been improving since its release, so I hacked up a little script to associate and do five minute iperf runs from /etc/rc.local. Looks pretty good so far (w-t is wireless-testing plus 5 or 6 extra patches I have brewing). The script is pretty kludgy, but may form the basis for some automatic build/regression testing in the future.
&lt;img alt=&#34;ath5k iperf chart&#34; loading=&#34;lazy&#34; src=&#34;https://bobcopeland.com/blog/images/lj/ath5k_iperf.png&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kernel 2.6.30</title>
      <link>https://bobcopeland.com/blog/2009/06/kernel-2630/</link>
      <pubDate>Tue, 16 Jun 2009 15:54:57 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1335</guid> 
      <description>&lt;p&gt;Linux kernel 2.6.30 is out, featuring the best mainline support for ath5k yet. I recommend if you do use wireless with 2.6.30 (or .29), that you also grab &lt;a href=&#34;http://lkml.org/lkml/2009/6/5/269&#34;&gt;this patch&lt;/a&gt; which fixes a nasty memory corruption issue. That one haunted me for months but it was a great feeling to finally nail it down. Of course the fix turned out to be quite simple. It should be hitting stable in short order.&lt;/p&gt;</description>
    </item>
    <item>
      <title>2.6.30 preview</title>
      <link>https://bobcopeland.com/blog/2009/03/2630-preview/</link>
      <pubDate>Wed, 01 Apr 2009 03:39:42 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1277</guid> 
      <description>&lt;p&gt;Now that Linux 2.6.29 just went out the door, here&amp;rsquo;s what I have prepared for 2.6.30 in the wireless arena. Of note, mac80211 now has suspend/resume support so a lot of nasty hacks in the drivers can go away. Most of the rest is just bug fixes, some of them for panics and soft lockups.&lt;/p&gt;
&lt;p&gt;The work I&amp;rsquo;m excited about this week is scheduled for 2.6.31 &amp;ndash; we extracted a bunch of ath9k regulatory infrastructure into a common module that all of the Atheros drivers (including the new ar9170) will use. This is the first step in getting a lot of that common code into a library. Hooray! Also Nick has some great improvements to the RF stuff queued up, so the driver is behaving much better.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
