<feed xmlns='http://www.w3.org/2005/Atom'>
<title>network-manager/debian/patches/14-use-same-kernel-API-as-wpa_supplicant.patch, branch debian/latest</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.equa.space/network-manager/atom?h=debian%2Flatest</id>
<link rel='self' href='https://git.equa.space/network-manager/atom?h=debian%2Flatest'/>
<link rel='alternate' type='text/html' href='https://git.equa.space/network-manager/'/>
<updated>2012-06-29T18:23:49+00:00</updated>
<entry>
<title>Update patches.</title>
<updated>2012-06-29T18:23:49+00:00</updated>
<author>
<name>Michael Biebl</name>
<email>biebl@debian.org</email>
</author>
<published>2012-06-29T18:23:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.equa.space/network-manager/commit/?id=038b9f5fcfedd9c117fc69f164e5b1c04efb0aca'/>
<id>urn:sha1:038b9f5fcfedd9c117fc69f164e5b1c04efb0aca</id>
<content type='text'>
* debian/patches/02-dbus_access_network_manager.patch: Updated.
* Remove patches which have been merged upstream.
</content>
</entry>
<entry>
<title>wifi: attempt to use same kernel API wpa_supplicant does</title>
<updated>2012-05-29T10:28:20+00:00</updated>
<author>
<name>Michael Biebl</name>
<email>biebl@debian.org</email>
</author>
<published>2012-05-29T10:28:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.equa.space/network-manager/commit/?id=41dfe5011b55b35f53f6ce2fe9bc2375f37039f1'/>
<id>urn:sha1:41dfe5011b55b35f53f6ce2fe9bc2375f37039f1</id>
<content type='text'>
  * debian/patches/14-use-same-kernel-API-as-wpa_supplicant.patch: Some
    drivers (ipw2x00) have an incomplete nl80211 implementation and only
    report capabilities which made NM chose the wrong API to talk to the
    device. Instead, match the logic that wpa_supplicant uses to determine
    whether to stick with nl80211 or fall back to WEXT. (Closes: #673705)
</content>
</entry>
</feed>
