On Mon, Sep 15, 2014 at 3:54 PM, Charles Steinkuehler
<[email protected]> wrote:
> On 9/15/2014 3:43 PM, Robert Nelson wrote:
>> On Mon, Sep 15, 2014 at 3:30 PM, Charles Steinkuehler
>> <[email protected]> wrote:
>>>
>>> What's the "right' way to build a -ti-19 kernel as a baseline so I can
>>> start playing with updating the pinmux helper and universal device tree?
>>
>> For your sanity you have to use the tags, from this tree:
>>
>> https://github.com/beagleboard/linux/tree/3.14.17-ti-r19
>>
>> Since our base is always a moving target ( ti's 3.14 bsp ) branch,
>> it's going to be painful working from my git tree directly.
>
> I tried that, using the configuration from:
> arch/arm/configs/bb.org_defconfig
>
> ...but the kernel version was 3.14.17+ (I was expecting 3.14.17-ti-r19)
> and when I did "make deb_pkg", I got armel instead of armhf packages.
>
> ...that's why I fell back to ti-linux-kernel-dev.
>
> I'm apparently missing some sort of secret sauce (a.k.a. "clues"). :-/
"deb_pkg" still hasn't learned to autodetect "armhf", so we do some
deb voodoo around that.. ;)
otherwise, the ti-r19 comes from LOCALVERSION
So:
make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-ti-r19
CROSS_COMPILE=${CC} KDEB_PKGVERSION=1wheezy deb-pkg
will generate:
linux-image-3.14.17-ti-r19_1wheezy_armhf.deb
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
