On 01/08/11 at 07:31pm, Denis 'GNUtoo' Carikli wrote: > hi, > Previously, by accident, having multiple plugins for handling one > resource worked. > It doesn't work anymore. > Instead Mickeyl told me that he will come up with something but he needs > usage scenario.
You mean the wifi part, right? What will we have than different to the current situation, as we now a have a power control plugin for each architecture we support. Which other way do you want to go? Implementing the steps mentioned below (module loading, rfkill, ifconfig, psm) in such a generic way that they apply's for every machine? > I'll leave the palm-pre, the nokia900 and the om-gta02 to other people to > describe them better than I could. For palmpre it's the following for wifi (as already implemented in a power control plugin): - load 'sirloin_wifi' module to take wifi chip out of reset - load 'libertas' module - load 'libertas_sdio' module - load firmware by udev or our firmware_loader - use wifi (even ifconfig eth1 power off/on works) For bluetooth there is currently no process as nobody has ever looked for it. But I think it should be something like this: - enable chip via sysfs - attach the hsuart responsible for bluetooth via hci_attach - let bluez handle the rest regards, Simon _______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
