Please inform us once you have pushed the code. Also, if you could inform the BeagleBoard community regarding the status on some on-going basis, you might solicit some community contributions to the effort. Robert Nelson in particular has done some useful work for his Ubuntu/Debian kernels and Koen on the Angstrom kernels. Folks looking for 1-wire, DT, PWM, pin ctrl and other support might also provide some useful contributions now that they are aware of this contribution path.

Thanks very much for volunteering to take on this important work while you are also focused on improving support for Sitara devices in the Linux mainline. I hope it is very synergistic work.

All,

The code pushed to this tree should be also submitted to subsystem maintainer trees and followed-through on individually, so don't use this as a dumping grounds. That said, for people making add-on daughterboards (ie. "capes"), this is a place for us to collaborate together to clean-up support to push all cape support to mainline, especially cleaning up device tree and enabling device tree fragments in EEPROMs such that kernel modifications are not required for new capes where drivers for the various components already exist.

As this tree comes on-line, I'll either eliminate the github.com/beagleboard kernel, clone this tree into it or give vaibhav commit rights to it to keep it in sync. I'm open to community feedback on that.

BeagleBoard/BeagleBoard-xM cannot be abandoned, so we still need to solve any gaps in supporting staging of patches for that platform if mainline isn't there yet. It would be nice to have some feedback on the status of BeagleBoard/BeagleBoard-xM support in the mainline kernel today.

> Also, if you could> inform the BeagleBoard community regarding the status on some on-going> basis, you might solicit some community contributions to the effort.> Robert Nelson in particular has done some useful work for his> Ubuntu/Debian kernels and Koen on the Angstrom kernels. Folks looking> for 1-wire, DT, PWM, pin ctrl and other support might also provide some> useful contributions now that they are aware of this contribution path.>

Any contribution to get our code to mainline would be really helpful and Appreciated. Currently the only focus I have is,

- Baseport: Clock and HWMOD Big code, so will take some time to make it its way to mainline. - Device Tree: For AM335x (handling of different boards, etc...) Basic DT support is already queued up for v3.4

> Thanks very much for volunteering to take on this important work while> you are also focused on improving support for Sitara devices in the> Linux mainline. I hope it is very synergistic work.>

Lets see how it works and shapes up in the future. My main focus still would be to get all our code into mainline, and without everybody's help it would be very hard for me.

Thanks,Vaibhav

> All,> > The code pushed to this tree should be also submitted to subsystem> maintainer trees and followed-through on individually, so don't use this> as a dumping grounds. That said, for people making add-on> daughterboards (ie. "capes"), this is a place for us to collaborate> together to clean-up support to push all cape support to mainline,> especially cleaning up device tree and enabling device tree fragments in> EEPROMs such that kernel modifications are not required for new capes> where drivers for the various components already exist.> > As this tree comes on-line, I'll either eliminate the> github.com/beagleboard kernel, clone this tree into it or give vaibhav> commit rights to it to keep it in sync. I'm open to community feedback> on that.> > BeagleBoard/BeagleBoard-xM cannot be abandoned, so we still need to> solve any gaps in supporting staging of patches for that platform if> mainline isn't there yet. It would be nice to have some feedback on the> status of BeagleBoard/BeagleBoard-xM support in the mainline kernel> today.> > Regards,> Jason>