From: David Lewin <[email protected]>
Reply-To: <[email protected]>
Date: Monday, February 10, 2014 at 5:43 AM
To: <[email protected]>
Subject: Re: [beagleboard] Xenomai master -> BBB RCNelson 3.13-bone5 kernel
patches
> John,
> from the KERNEL dir :
>> patch -p1 < cds_xenomai.patch
>
> outputs error on :
>
> Can't find file at
>
>> @@ -866,12 +866,40 @@ saucy () {
Did you checkout the am33x-v3.8 branch?
git checkout am33x-v3.8
Place the patch so that it is in the same folder as linux-dev, not in the
linux-dev folder.
patch -p1 < ../cds_xenomai.patch
Regards,
John
>
>
>
>
> 2014-02-09 18:51 GMT+01:00 David Lewin <[email protected]>:
>> OK will give it a try, thanks for the tip.
>>
>>
>> 2014-02-09 3:39 GMT+01:00 John Syn <[email protected]>:
>>
>>>
>>> From: David Lewin <[email protected]>
>>> Reply-To: <[email protected]>
>>> Date: Saturday, February 8, 2014 at 2:15 AM
>>> To: <[email protected]>
>>> Subject: Re: [beagleboard] Xenomai master -> BBB RCNelson 3.13-bone5 kernel
>>> patches
>>>
>>>> I 200% agree : that's why I was refering to it :
>>>>
>>>>> Is it possible to get a same instructions list for the official one
>>>>> <http://git.xenomai.org/xenomai-2.6.git/tree/ksrc/arch/arm/patches/README>
>>>>> ?
>>>>
>>>> anyway with a checkout from any branch, I'm not sure that xenomai will be
>>>> compiled as from docs, blog, forums, book
>>>> it's clearly precise that not all kernel version accept xenomai patches.
>>>> Therefore, from my understanding only 1 commit is currenlty guaranteed to
>>>> work :
>>>>
>>>>> ---- Beaglebone
>>>>>
>>>>> 1- Checkout the "am33x-v3.8" branch in the Robert Nelson repository [3],
>>>>> the patch has been tested with commit
>>>>> 3fc8a73d782231ab2750ff29793a760e8fa076bb
>>>>> 2- apply beaglebone/ipipe-core-3.8.13-beaglebone-pre.patch
>>>>> 3- apply ipipe-core-3.8.13-arm-1.patch
>>>>> 4- apply beaglebone/ipipe-core-3.8.13-beaglebone-post.patch
>>>>> 5- you can resume to generic installation instructions.
>>>>
>>>>
>>>> John: until now I've been just compiled vanilla kernels, -ie no xenomai
>>>> worked- could you please indicate what are these steps you have followed to
>>>> compile it ?
>>> Way to complicated. Simply clone Robert's linux-dev repo and apply the
>>> attached patch. Build the kernel as normal.
>>>
>>> Regards,
>>> John
>>>>
>>>>
>>>>
>>>> 2014-02-07 22:36 GMT+01:00 John Syn <[email protected]>:
>>>>>
>>>>> On 2/7/14, 8:38 AM, "Charles Steinkuehler" <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> >If you're wanting a Xenomai kernel, you should:
>>>>>> >
>>>>>> >git checkout --track 3.8.13-bone39-xenomai
>>>>>> >
>>>>>> >...then run the build-kernel.sh script.
>>>>>> >
>>>>>> >If you want a plain kernel, pull from Robert's repository and use one of
>>>>>> >the 3.8.13-bone* tags. It's not a branch so when you checkout the tag
>>>>>> >you'll get a "detatched head" warning. You can ignore this (until you
>>>>>> >have changes you want to push back upstream) and just build the kernel
>>>>>> >as usual.
>>>>> Why not checkout the am33x-v3.8 branch? That way you can track the changes
>>>>> Robert makes to his v3.8 branch. I find it easier to patch Robert¹s
>>>>> linux-dev repo with your xenomai changes and then I¹m always up to date
>>>>> with Robert¹s changes. It might be even easier to have Robert add a
>>>>> Xenomai branch.
>>>>>
>>>>> Regards,
>>>>> John
>>>>>> >
>>>>>> >On 2/7/2014 9:55 AM, David Lewin wrote:
>>>>>>> >> Therefore, this would need to
>>>>>>> >>
>>>>>>> >> - git checkout to branch /3.8.13-bone36 as the emmc flasher kernel
>>>>>>> use
>>>>>>> >>this
>>>>>>> >> one
>>>>>>> >> - build_kernel.sh anew
>>>>>>> >>
>>>>>>> >> is that right ?
>>>>>>> >> if yes, I couldn't retrieve where to set the branch to co.
>>>>>>> >>
>>>>>>> >> 2014-02-07 Charles Steinkuehler <[email protected]>:
>>>>>>> >>
>>>>>>>> >>> If you're using my linux-dev repository, you need to check out the
>>>>>>>> >>> appropriate branch, master is not intended for actual use.
>>>>>>>> >>>
>>>>>>>> >>> On 2/7/2014 8:48 AM, David Lewin wrote:
>>>>>>>>> >>>> I've followed :
>>>>>>>>> >>>>
>>>>>>>>>> >>>>> For the MachineKit Xenomai kernels it's very easy, and
>>>>>>>>>> identical to
>>>>>>>>>> >>>>> working with Robert Nelson's kernels. You just work from my
>>>>>>>>>> github
>>>>>>>>>> >>>>> repository instead of his (I've added the Xenomai patches to
the
>>>>>>>>>> >>>>> laundry-list of BeagleBone patches his scripts apply):
>>>>>>>>>> >>>>> https://github.com/cdsteinkuehler/linux-dev
>>>>>>>>>> >>>>> You run the ./build_kernel.sh script, so the BeagleBone and
>>>>>>>>>> Xenomai
>>>>>>>>>> >>>>> patches will be applied. You can then edit the configuration
as
>>>>>>>>>> >>>>>desired
>>>>>>>>>> >>>>> and rebuild the kernel using tools/rebuild.sh
>>>>>>>>> >>>>
>>>>>>>>> >>>>
>>>>>>>>> >>>> which may be wrong, but :
>>>>>>>>> >>>> *git branch *
>>>>>>>>> >>>> within linux-dev is correctly pointing to master.
>>>>>>>>> >>>>
>>>>>>>>> >>>> What did I've missed
>>>>>>>>> >>>>
>>>>>>>>> >>>>
>>>>>>>>> >>>> 2014-02-07 Robert Nelson <[email protected]>:
>>>>>>>>> >>>>
>>>>>>>>>> >>>>>
>>>>>>>>>> >>>>>
>>>>>>>>>> >>>>>
>>>>>>>>>> >>>>> On Fri, Feb 7, 2014 at 8:09 AM, David Lewin
>>>>>>>>>> <[email protected]>
>>>>>>>> >>> wrote:
>>>>>>>>>> >>>>>
>>>>>>>>>>> >>>>>> Charles,
>>>>>>>>>>> >>>>>> My tries didn't succeeded, but I'm sure I've missed the good
kernel
>>>>>>>>>>> >>>>>>:
>>>>>>>>>>> >>>>>> I've flashed the
>>>>>>>>>>> >>>>>>
>>>>>>>> >>>
>>>>>>>>
>>>http://rcn-ee.net/deb/testing/2014-02-05/BBB-eMMC-flasher-debian-7.3>>>>>>>>
-201
>>>>>>>> >>>4-02-05-2gb.img.xz
>>>>>>>>>>> >>>>>> which could boot and run.
>>>>>>>>>>> >>>>>> It use currently : 3.8.13-bone36
>>>>>>>>>>> >>>>>> I then build the linux-dev where
>>>>>>>>>>> /deploy/3.11.0-rc1-armv7-d1.zimage
>>>>>>>>>>> >>>>>>to
>>>>>>>>>>> >>>>>> overwrite the bbb /boot/uboot
>>>>>>>>>>> >>>>>> which lead me to a wrong boot : 4 leds fixed.
>>>>>>>>>>> >>>>>>
>>>>>>>>>>> >>>>>> Therefore, please where to get the correct kernel to swap
from ?
>>>>>>>>>>> >>>>>>
>>>>>>>>>> >>>>>
>>>>>>>>>> >>>>> If you built/installed "3.11.0-rc1-armv7-d1.zimage" then you
>>>>>>>>>> didn't
>>>>>>>> >>> follow
>>>>>>>>>> >>>>> the directions posted, as that would have been the "master"
>>>>>>>>>> branch of
>>>>>>>>>> >>>>> linux-dev..
>>>>>>>>>> >>>>>
>>>>>>>>>> >>>>> 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 a topic
in
>>>>>>>>>> >>>>>the
>>>>>>>>>> >>>>> Google Groups "BeagleBoard" group.
>>>>>>>>>> >>>>> To unsubscribe from this topic, visit
>>>>>>>>>> >>>>>
>>>>>>>>>>
>>>>>https://groups.google.com/d/topic/beagleboard/HqwuSu2tLe8/unsubs>>>>>>>>>>
cribe.
>>>>>>>>>> >>>>> To unsubscribe from this group and all its topics, send an
>>>>>>>>>> email to
>>>>>>>>>> >>>>> [email protected]
>>>>>>>>>> <mailto:beagleboard%[email protected]> .
>>>>>>>>>> >>>>> For more options, visit
>>>>>>>>>> https://groups.google.com/groups/opt_out.
>>>>>>>>>> >>>>>
>>>>>>>>> >>>>
>>>>>>>> >>>
>>>>>>>> >>>
>>>>>>>> >>> --
>>>>>>>> >>> Charles Steinkuehler
>>>>>>>> >>> [email protected]
>>>>>>>> >>>
>>>>>>>> >>> --
>>>>>>>> >>> For more options, visit http://beagleboard.org/discuss
>>>>>>>> >>> ---
>>>>>>>> >>> You received this message because you are subscribed to a topic in
the
>>>>>>>> >>> Google Groups "BeagleBoard" group.
>>>>>>>> >>> To unsubscribe from this topic, visit
>>>>>>>> >>>
>>>>>>>> https://groups.google.com/d/topic/beagleboard/HqwuSu2tLe8/unsubscribe.
>>>>>>>> >>> To unsubscribe from this group and all its topics, send an email to
>>>>>>>> >>> [email protected]
>>>>>>>> <mailto:beagleboard%[email protected]> .
>>>>>>>> >>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>>> >>>
>>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> >--
>>>>>> >Charles Steinkuehler
>>>>>> >[email protected]
>>>>>> >
>>>>>> >--
>>>>>> >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]
>>>>>> <mailto:beagleboard%[email protected]> .
>>>>>> >For more options, visit https://groups.google.com/groups/opt_out.
>>>>>
>>>>>
>>>>> --
>>>>> For more options, visit http://beagleboard.org/discuss
>>>>> ---
>>>>> You received this message because you are subscribed to a topic in the
>>>>> Google Groups "BeagleBoard" group.
>>>>> To unsubscribe from this topic, visit
>>>>> https://groups.google.com/d/topic/beagleboard/HqwuSu2tLe8/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>> [email protected]
>>>>> <mailto:beagleboard%[email protected]> .
>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>
>>>> --
>>>> 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/groups/opt_out.
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/HqwuSu2tLe8/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> [email protected]
>>> <mailto:beagleboard%[email protected]> .
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
> --
> 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/groups/opt_out.
--
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/groups/opt_out.