I've been working trying to build a kernel package "the Debian way" by tweaking the debian dir, making some minors edits to the config, and applying patches from:
git://git.openpandora.org/pyra-kernel.git branch: 3.17-rc6 commit: 02766ba0d8fd95af3e30625682f8fed7ff211874
I've finally managed to get it to successfully build, no idea if it works.
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
The config differs a bit from gta04_defconfig. It's based on Debian's armmp kernel config with a few additions to try and make it more similar to gta04_defconfig:
CONFIG_SOC_OMAP5=y CONFIG_SOC_AM43XX=y CONFIG_SOC_DRA7XX=y CONFIG_CHARGER_TWL4030=y CONFIG_SENSORS_TWL4030_MADC=m CONFIG_TWL4030_MADC=m CONFIG_BATTERY_TWL4030_MADC=m CONFIG_CHARGER_BQ2429X=m CONFIG_OMAP5_DSS_HDMI=y # CONFIG_TWL4030_USB is not set CONFIG_GPIO_TWL4030=m CONFIG_GPIO_TWL6040=m CONFIG_RTC_DRV_TWL4030=m
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
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 set to get it to work as a built-in; something else in the debian config was built as a module which forced it to also build as a module. With CONFIG_TWL4030_USB=m, it fails to build:
ERROR: "twl4030_charger_enable_usb_ext" [drivers/phy/phy-twl4030-usb.ko] undefined! make[6]: *** [__modpost] Error 1 /«PKGBUILDDIR»/scripts/Makefile.modpost:90: recipe for target '__modpost' failed make[5]: *** [modules] Error 2 /«PKGBUILDDIR»/Makefile:1107: recipe for target 'modules' failed make[5]: *** Waiting for unfinished jobs....
Full build log:
http://cascadia.debian.net/~vagrant/pyra/linux_3.17~rc6-1~exp1~20140924~3_ar...
Not sure how important the TWL4030 is for the pyra, specifically...
live well, vagrant
Hi,
Am 25.09.2014 um 18:18 schrieb Vagrant Cascadian:
I've been working trying to build a kernel package "the Debian way" by tweaking the debian dir, making some minors edits to the config, and applying patches from:
git://git.openpandora.org/pyra-kernel.git branch: 3.17-rc6 commit: 02766ba0d8fd95af3e30625682f8fed7ff211874
I've finally managed to get it to successfully build, no idea if it works.
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.
The config differs a bit from gta04_defconfig. It's based on Debian's armmp kernel config with a few additions to try and make it more similar to gta04_defconfig:
CONFIG_SOC_OMAP5=y CONFIG_SOC_AM43XX=y CONFIG_SOC_DRA7XX=y CONFIG_CHARGER_TWL4030=y CONFIG_SENSORS_TWL4030_MADC=m CONFIG_TWL4030_MADC=m CONFIG_BATTERY_TWL4030_MADC=m CONFIG_CHARGER_BQ2429X=m CONFIG_OMAP5_DSS_HDMI=y # CONFIG_TWL4030_USB is not set CONFIG_GPIO_TWL4030=m CONFIG_GPIO_TWL6040=m CONFIG_RTC_DRV_TWL4030=m
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...
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 set to get it to work as a built-in; something else in the debian config was built as a module which forced it to also build as a module. With CONFIG_TWL4030_USB=m, it fails to build:
ERROR: "twl4030_charger_enable_usb_ext" [drivers/phy/phy-twl4030-usb.ko] undefined! make[6]: *** [__modpost] Error 1 /«PKGBUILDDIR»/scripts/Makefile.modpost:90: recipe for target '__modpost' failed make[5]: *** [modules] Error 2 /«PKGBUILDDIR»/Makefile:1107: recipe for target 'modules' failed make[5]: *** Waiting for unfinished jobs....
Full build log:
http://cascadia.debian.net/~vagrant/pyra/linux_3.17~rc6-1~exp1~20140924~3_ar...
Not sure how important the TWL4030 is for the pyra, specifically...
Not at all. The TWL4030 is for OMAP3 devices.
The current tree is to support multiple platforms, i.e. OMAP3, OMAP4 and OMAP5 devices by a single kernel and just different device trees.
Unfortunately this is not always successful.
Anyways it is a good start!
And you can check if your results are similar to mine:
http://download.goldelico.com/gta04/unstable/quantumstep-linux-gta04-kernel_...
live well, vagrant
same to you!
BR, Nikolaus
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
Hi, I have checked with the latest -rc6 but for me all .dtb compile fine.
Which branch / commit did you try? Maybe it was only temporarily broken (wrong order of checking in some diffs). Or please can you share the error log?
And with CONFIG_TWL4030_USB=y it also compiles fine.
As module it is indeed broken. See:
http://projects.goldelico.com/p/gta04-kernel/issues/659/
BR, Nikolaus
Am 25.09.2014 um 18:18 schrieb Vagrant Cascadian:
I've been working trying to build a kernel package "the Debian way" by tweaking the debian dir, making some minors edits to the config, and applying patches from:
git://git.openpandora.org/pyra-kernel.git branch: 3.17-rc6 commit: 02766ba0d8fd95af3e30625682f8fed7ff211874
I've finally managed to get it to successfully build, no idea if it works.
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
The config differs a bit from gta04_defconfig. It's based on Debian's armmp kernel config with a few additions to try and make it more similar to gta04_defconfig:
CONFIG_SOC_OMAP5=y CONFIG_SOC_AM43XX=y CONFIG_SOC_DRA7XX=y CONFIG_CHARGER_TWL4030=y CONFIG_SENSORS_TWL4030_MADC=m CONFIG_TWL4030_MADC=m CONFIG_BATTERY_TWL4030_MADC=m CONFIG_CHARGER_BQ2429X=m CONFIG_OMAP5_DSS_HDMI=y # CONFIG_TWL4030_USB is not set CONFIG_GPIO_TWL4030=m CONFIG_GPIO_TWL6040=m CONFIG_RTC_DRV_TWL4030=m
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
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 set to get it to work as a built-in; something else in the debian config was built as a module which forced it to also build as a module. With CONFIG_TWL4030_USB=m, it fails to build:
ERROR: "twl4030_charger_enable_usb_ext" [drivers/phy/phy-twl4030-usb.ko] undefined! make[6]: *** [__modpost] Error 1 /«PKGBUILDDIR»/scripts/Makefile.modpost:90: recipe for target '__modpost' failed make[5]: *** [modules] Error 2 /«PKGBUILDDIR»/Makefile:1107: recipe for target 'modules' failed make[5]: *** Waiting for unfinished jobs....
Full build log:
http://cascadia.debian.net/~vagrant/pyra/linux_3.17~rc6-1~exp1~20140924~3_ar...
Not sure how important the TWL4030 is for the pyra, specifically...
live well, vagrant _______________________________________________ Firmware mailing list Firmware@pyra-handheld.com http://pyra-handheld.com/cgi-bin/mailman/listinfo/firmware
Hello,
On 09/29/2014 10:09 AM, Dr. H. Nikolaus Schaller wrote:
Hi, I have checked with the latest -rc6 but for me all .dtb compile fine.
Which branch / commit did you try? Maybe it was only temporarily broken (wrong order of checking in some diffs). Or please can you share the error log?
I have the same problem, maybe you forgot to commit some files? branch 3.17-rc6, commit 02766ba0d8fd95af3e30625682f8fed7ff211874
You should try clean a clone, or at least: # cause a dtb rebuild $ rm arch/arm/boot/dts/*.dtb $ make
Grazvydas