March 30th, 2009
So we had a wonderfully successful Nouveau test day on Thursday. The turnout was great and we got really high-quality feedback, which is already allowing Ben to fix several bugs in Rawhide updates. A huge thanks to everyone who came out and helped test. Remember, if you couldn’t make it to the test day, you can still do the testing and report your results following the instructions on the Wiki page.
This week’s regular Thursday test day is on power management, but we are also again having a special off-schedule test day. This one will be on Wednesday April 1st (yes, really!), and is on the radeon driver. This isn’t a new driver like nouveau, but it has seen substantial changes since Fedora 10 – especially in the 3D layer. It also supports a wide range of very different cards, from the ancient to the brand new, so we need broad-based testing to see where it stands across as much of the range as possible. Just like the Nouveau test day there will be a live CD to make testing easy, and the test cases are simple to follow and carry out, so if you have an ATI graphics adapter, please come along to help with testing!
To post a quick update on other things I’ve been working on lately – as discussed on -devel-list, I’ve been working with the opensync maintainer, Andreas Bierfert, to get Fedora’s opensync package stack into shape. Well, mostly, I’ve been telling him what he ought to do and he’s been doing all the actual work! We now have the 0.22 package set in Rawhide, which is a good start. There’s still a few more tweaks that would be useful. Concomitant to that, I’ve also been poking at NetworkManager’s behaviour with regards to Windows Mobile devices, with the invaluable assistance of the super-awesome Dan Williams. I went after a few red herrings, but in the end we’ve determined that NetworkManager can handle Windows Mobile devices connected via USB in internet connection sharing mode perfectly correctly, but should butt out and ignore Windows Mobile devices connected via USB in synchronization mode entirely, and let the scripts in synce-hal handle them. synce-hal should be doing the exact opposite – handling devices in synchronization mode and ignoring ones in ICS mode. The synce developers are aware of this now, so hopefully future versions of NM and synce will work harmoniously together and you won’t need to work around them to do what you need to do. That just leaves Bluetooth to sort out…