<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/wireless/b43/phy_lp.c, branch linux-4.0.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2014-08-25T20:00:42Z</updated>
<entry>
<title>b43: flush some writes on Broadcom MIPS SoCs</title>
<updated>2014-08-25T20:00:42Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2014-08-07T05:45:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=25c15566635fef86e87f762f73a19f24598e45fa'/>
<id>urn:sha1:25c15566635fef86e87f762f73a19f24598e45fa</id>
<content type='text'>
Access to PHY and radio registers is indirect on Broadcom hardware and
it seems that addressing on some MIPS SoCs may require flushing. So far
this problem was noticed on 0x4716 SoC only (marketing names: BCM4717,
BCM4718).

Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>b43: don't duplicate common PHY read/write ops</title>
<updated>2014-08-25T20:00:42Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2014-07-31T19:59:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d342b95dd735014a590f9051b1ba227eb54ca8f6'/>
<id>urn:sha1:d342b95dd735014a590f9051b1ba227eb54ca8f6</id>
<content type='text'>
Most of the PHYs use the same way of accessing registers, so move that
code to the shared place. An exception is G-PHY which sometimes access
A-PHY regs and requires special handling.

Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>b43: use defines for board_type</title>
<updated>2013-04-23T10:27:57Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2013-03-28T21:25:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fb3bc67ed8e2ec6e18078e047e9e72254d1526d1'/>
<id>urn:sha1:fb3bc67ed8e2ec6e18078e047e9e72254d1526d1</id>
<content type='text'>
Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
</content>
</entry>
<entry>
<title>b43: remove warning for LP-PHY with sprom &lt; 8</title>
<updated>2013-03-25T20:47:06Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2013-03-21T19:28:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=64513ef449e3beaacb801d41467f47642683e35a'/>
<id>urn:sha1:64513ef449e3beaacb801d41467f47642683e35a</id>
<content type='text'>
The BCM5354 SoC has a build in ieee80211 core rev 13 with a LP-PHY on
it. This devices has a sprom version 3 stored in the nvram. This patch
removes the warning and uses the opo values from the sprom as mentioned
in the specs.

Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>net: fix assignment of 0/1 to bool variables.</title>
<updated>2011-12-20T03:27:29Z</updated>
<author>
<name>Rusty Russell</name>
</author>
<published>2011-12-19T13:56:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3db1cd5c05f35fb43eb134df6f321de4e63141f2'/>
<id>urn:sha1:3db1cd5c05f35fb43eb134df6f321de4e63141f2</id>
<content type='text'>
DaveM said:
   Please, this kind of stuff rots forever and not using bool properly
   drives me crazy.

Joe Perches &lt;joe@perches.com&gt; gave me the spatch script:

	@@
	bool b;
	@@
	-b = 0
	+b = false
	@@
	bool b;
	@@
	-b = 1
	+b = true

I merely installed coccinelle, read the documentation and took credit.

Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial</title>
<updated>2011-07-25T20:56:39Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2011-07-25T20:56:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d3ec4844d449cf7af9e749f73ba2052fb7b72fc2'/>
<id>urn:sha1:d3ec4844d449cf7af9e749f73ba2052fb7b72fc2</id>
<content type='text'>
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial: (43 commits)
  fs: Merge split strings
  treewide: fix potentially dangerous trailing ';' in #defined values/expressions
  uwb: Fix misspelling of neighbourhood in comment
  net, netfilter: Remove redundant goto in ebt_ulog_packet
  trivial: don't touch files that are removed in the staging tree
  lib/vsprintf: replace link to Draft by final RFC number
  doc: Kconfig: `to be' -&gt; `be'
  doc: Kconfig: Typo: square -&gt; squared
  doc: Konfig: Documentation/power/{pm =&gt; apm-acpi}.txt
  drivers/net: static should be at beginning of declaration
  drivers/media: static should be at beginning of declaration
  drivers/i2c: static should be at beginning of declaration
  XTENSA: static should be at beginning of declaration
  SH: static should be at beginning of declaration
  MIPS: static should be at beginning of declaration
  ARM: static should be at beginning of declaration
  rcu: treewide: Do not use rcu_read_lock_held when calling rcu_dereference_check
  Update my e-mail address
  PCIe ASPM: forcedly -&gt; forcibly
  gma500: push through device driver tree
  ...

Fix up trivial conflicts:
 - arch/arm/mach-ep93xx/dma-m2p.c (deleted)
 - drivers/gpio/gpio-ep93xx.c (renamed and context nearby)
 - drivers/net/r8169.c (just context changes)
</content>
</entry>
<entry>
<title>Update my e-mail address</title>
<updated>2011-07-07T13:18:01Z</updated>
<author>
<name>Michael Büsch</name>
</author>
<published>2011-07-04T18:50:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eb032b9837a958e21ca000358a5bde5e17192ddb'/>
<id>urn:sha1:eb032b9837a958e21ca000358a5bde5e17192ddb</id>
<content type='text'>
Signed-off-by: Michael Buesch &lt;m@bues.ch&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>b43: LP-PHY: use new pointers path to access ssb_device</title>
<updated>2011-06-01T19:12:27Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2011-05-19T13:11:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6ac53692179da165b2cb1e2a122b0ed9dad9b9ad'/>
<id>urn:sha1:6ac53692179da165b2cb1e2a122b0ed9dad9b9ad</id>
<content type='text'>
LP-PHY code is SSB specific, add check for bus type.

Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>b43: bus: abstract board info</title>
<updated>2011-06-01T19:10:57Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2011-05-18T00:06:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=79d2232fed23e8e0d1b11abe2f9b78fb09084506'/>
<id>urn:sha1:79d2232fed23e8e0d1b11abe2f9b78fb09084506</id>
<content type='text'>
Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>b43: bus: abstract chip info</title>
<updated>2011-06-01T19:10:57Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2011-05-18T00:06:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c244e08c7aa30abea3c29ff17a40f4b0a58a7913'/>
<id>urn:sha1:c244e08c7aa30abea3c29ff17a40f4b0a58a7913</id>
<content type='text'>
Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
</feed>
