Op 24 sep 2010, om 22:00 heeft Luciano Coelho het volgende geschreven: > On Fri, 2010-09-24 at 21:42 +0200, ext Koen Kooi wrote: >> Op 24 sep 2010, om 21:11 heeft Tony Lindgren het volgende geschreven: >> >>> * Luciano Coelho <luciano.coelho@xxxxxxxxx> [100924 11:42]: >>>> On Fri, 2010-09-24 at 20:03 +0200, ext John W. Linville wrote: >>>>> On Thu, Sep 23, 2010 at 01:03:35PM +0300, Luciano Coelho wrote: >>>>>> Add board configuration for the wl1271 daughter board. This patch is based >>>>>> on Ohad Ben-Cohen's patches for Zoom boards. >>>>>> >>>>>> Cc: Ohad Ben-Cohen <ohad@xxxxxxxxxx> >>>>>> Signed-off-by: Luciano Coelho <luciano.coelho@xxxxxxxxx> >>>>>> --- >>>>>> from v2 to v3: removed accidental change to wl1271.h >>>>> >>>>> I presume that this should come through my tree as well (since it >>>>> contains the move of wl12xx.h)? >>>> >>>> Yes, this is based on your tree. But please hold on, because there were >>>> some comments (namely, the expansion board should be detected, not >>>> configured for wl1271 by default), which I still have to fix. I'm >>>> waiting for the manufacturer of the expansion board to provide me with >>>> some more info for proper detection. >>>> >>>> Also, I know that there are some other work being done in the beagle >>>> board file, so we may need to rethink how to sync this. >>>> >>>> So, for now, let's skip this patch and I'll provide another one when >>>> these issues are addressed. >>> >>> You could also do it based on some kernel cmdline option. Of course >>> detection during the runtime would be better. >> >> That's what we're currently doing in the beagle kernels: http://gitorious.org/beagleboard-validation/linux/commit/17c1b214b918c6f9efc5579134a7ff71d51b60bf >> >> That needs forward porting to .37 before I can submit is as RFC here :) > > Yes! I have seen that as pointed out by Robert. It would be nice if you > could port this soon(ish) so that others can start using it (ok, maybe > not many people, but at least me :P) > > What would you think about having the actual probing moved from u-boot > to the kernel? Do you think that would make sense or are there some > other reasons for having it in the bootloader? It would make a lot of sense, but when we did the code the in-kernel muxing was pretty much unusable for this goal. I'd prefer to get the uboot based detection way into the kernel first before embarking on the bigger fully in-kernel stuff. Note that on beagleboard-xM we have an additional problem with the camera modules, the different sensors use the same i2c address, which means it completely falls down with the current i2c implementation. Does anyone have any hints on how to read a register over i2c before registering the i2c platform data? regards, Koen-- 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
