On 2014-09-25 12:04:35 -0500, Dr. H. Nikolaus Schaller wrote:
Am 25.09.2014 um 18:18 schrieb Vagrant Cascadian:
Had to remove numerous dtbs that failed to build, largely the ones with +gta04; I'm not sure if these will be needed for the pyra or not, but I get the impression this kernel tree is actually intended to support several platforms. Patch available:
http://cascadia.debian.net/~vagrant/pyra/remove-broken-dtbs.patch
ok, those with +gta04 are indeed partially broken. Just ignore them. I have to check why my build system does not complain. Maybe, because I don't build all .dts files but just a subset.
The pyra+something are definitions for different panels and also work-in-progress.
Ok, should we update the git tree accordingly, or use the issue reporting at:
http://dev.pyra-handheld.com/index.php/p/pyra-kernel/issues/
no idea if it boots on anything usefully, as I don't have hardware to test. Full config available:
http://cascadia.debian.net/~vagrant/pyra/config-3.17-rc6-pyra.gz
That has to be tested on a real EVM/device to see if it has all the useful things. My experience is that standard defconfigs usually lack 5% of what is needed to develop or test hardware...
At aTc's request, i've also uploaded the .dsc (debian source package) and .deb (debian binary package) files:
http://cascadia.debian.net/~vagrant/pyra/
It's got quite a few more things enabled as modules, being based on the Debian armmp kernel, hopefully it's the right things...
Let me know how it works for you!
Notably had to disable CONFIG_TWL4030_USB, as it didn't build as a module, and I couldn't figure out which depending options needed to be
...
Not sure how important the TWL4030 is for the pyra, specifically...
Not at all. The TWL4030 is for OMAP3 devices.
Ok, for now I'll leave it disabled.
The current tree is to support multiple platforms, i.e. OMAP3, OMAP4 and OMAP5 devices by a single kernel and just different device trees.
That's pretty much how it's done in Debian, too.
live well, vagrant