Re: libertas private ioctls
On Fri, Jun 12, 2009 at 08:01:13PM +, Deepak Saxena wrote: > I'm a little aprehensive about that option. Where would the command go? > I'm wondering if this would be a good place for using platform device > data? Would it not go well in the initialisation of the wireless device driver, such that operation of the LEDs becomes the perceived responsibility of this driver? It would check if it is an XO. -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: libertas private ioctls
On Jun 11 2009, at 14:49, Daniel Drake was caught saying: > On Thu, 2009-06-11 at 08:42 +, Deepak Saxena wrote: > > My quick answer is to move these forward from our old kernel. We can try > > pushing them upstream too but I would like to understand why we need them > > and if there are alternatives such as sysfs that we could use. > > Would it be appropriate to include that specific command (ledgpio 1 1 2 > 12 3 16, whatever it is) in the kernel so that no userspace intervention > is needed to turn the LEDs on? I'm a little aprehensive about that option. Where would the command go? I'm wondering if this would be a good place for using platform device data? ~Deepak ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: libertas private ioctls
On Thu, 2009-06-11 at 08:42 +, Deepak Saxena wrote: > My quick answer is to move these forward from our old kernel. We can try > pushing them upstream too but I would like to understand why we need them > and if there are alternatives such as sysfs that we could use. Would it be appropriate to include that specific command (ledgpio 1 1 2 12 3 16, whatever it is) in the kernel so that no userspace intervention is needed to turn the LEDs on? Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: libertas private ioctls
On Jun 10 2009, at 11:48, Daniel Drake was caught saying: > Hi Deepak, > > In OLPC OS 8.2, libertas had private ioctls > which /etc/init.d/olpc-configure used to configure the LEDs: > iwpriv eth0 ledgpio 1 1 2 12 3 16 > > These aren't present in the 2.6.30-rc5 kernel I am running on my XO-1, > and presumably neither on the xo-1.5 kernel. > > I think the ledgpio command is needed for correct behavior of the LEDs > on the mesh. I have mesh working with NM-0.7/F11 but the LEDs are > silent. How should we solve this? My quick answer is to move these forward from our old kernel. We can try pushing them upstream too but I would like to understand why we need them and if there are alternatives such as sysfs that we could use. ~Deepak ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
libertas private ioctls
Hi Deepak, In OLPC OS 8.2, libertas had private ioctls which /etc/init.d/olpc-configure used to configure the LEDs: iwpriv eth0 ledgpio 1 1 2 12 3 16 These aren't present in the 2.6.30-rc5 kernel I am running on my XO-1, and presumably neither on the xo-1.5 kernel. I think the ledgpio command is needed for correct behavior of the LEDs on the mesh. I have mesh working with NM-0.7/F11 but the LEDs are silent. How should we solve this? Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
