On Mon, Oct 01, 2007 at 10:18:10AM -0400, Dan Williams wrote: > On Thu, 2007-09-20 at 13:56 -0700, Jean Tourrilhes wrote: > > > > Well, as it happens, 0.6.5 uses wpa_supplicant for the scan if > > it's available (more below). > > This is mainly to ensure that wpa_supplicant and NM scan in a > coordinated manner. Otherwise you get into a situation where > wpa_supplicant scans, and NM's scan timer happens to fall right after > wpa_supplicant's, and the driver gets two back-to-back scan requests > (maybe the second one even overlaps the first). Makes drivers confused. Yes, I fully agree with this decision, it look to me the right way to do it. > > I'm currently stuck because I don't have a box handy to try > > NetworkManager on, most of my boxes are without all the Gnome > > overhead. I'll try to fix that, but it may take a few days. > > Meanwhile, I made a few patch just for you for NetworkManager > > 0.6.5. I could not even try to compile it (./configure dependancy), so > > beware. > > I think you already did the patch and sent it, and it was committed on > March 2, 2007 to NM CVS. Unfortunately, I don't think we've cut a > release of NM "stable" (which would be 0.6.5) for a long time, which is > probably quite overdue. Most distros should be shipping a 0.6.5 > snapshot at least. The patch last march was for the "scanning" code. The new patch is for the "event" code. Yes, last march, I totally forgot about the event code, sorry about that. From my casual glance around, most distro ship what they call "0.6.5". The fact that it's not a release means that all those "0.6.5" are probably not the exact same version, as they are most likely at different CVS time. This looks to me like the receipe for some confusion. I personally don't know which "0.6.5" are good and which are not, I assume most are good, but without looking at the actual code, who knows... In other words, if you eventually do a release, you may want to call it "0.6.6". > Dan Have fun... Jean - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
