On Mar 02 2010, at 13:02, Holger Schurig was caught saying: > > support is an option our community would be happy with. However, I also > > don't want to end up with a libertas fork (all our mesh patches are > > currently upstream and not forkd off) > > Oh, sorry for being misinformed and spreading this misinformation. I had some > read-only variables in the mainline libertas driver (for example > mesh_autostart_enabled get's never written to) and heard that this is a > remnant, and that the real implementation in in the OLPC tree. That is definitely a remnant of old work and our tree seems to have the same read-only issues. > Therefore I thought that you're sticking to some older kernel, and not > following mainline linux at all. We're currently on 2.6.31, which I guess is somewhat pre-historic by kernel development standards. We do have some patches to Libertas which were co-developed along with Marvell to fix some bugs we've discovered during the XO-1.5 ramp up process and unfortunately we were on a really tight release schedule and not all of those have been pushed upstream, including some changes to the SDIO stack that were needed for proper suspend/resume support on the gen 2 laptops. I'll be working on moving our kernel up to a newer version and will send up any patches that we need merged and will also work with our users to figure out what to do about mesh testing. ~Deepak -- "People think all we need to fix our predicament is a free source of energy, but I think we need to change out behaviour. More energy would just deplete the Earth's lifeblood faster." - Janine Benyius -- 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
