From: Charles Steinkuehler <charles@steinkuehler.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [PATCH] BeagleBone 3.8.13 pre/post patches
Date: Tue, 27 Aug 2013 16:57:03 -0500 [thread overview]
Message-ID: <521D20AF.2040604@steinkuehler.net> (raw)
In-Reply-To: <521D167C.7070801@xenomai.org>
On 8/27/2013 4:13 PM, Gilles Chanteperdrix wrote:
> On 08/27/2013 11:12 PM, Gilles Chanteperdrix wrote:
>> On 08/27/2013 09:59 PM, Charles Steinkuehler wrote:
>>> I made a pre/post patch set for the BeagleBone 3.8.13 kernel and added
>>> the files to my xenomai 2.6 repository (patch attached).
>>>
>>> Note that I just added the files...I didn't do anything to try and
>>> integrate these with the prepare_kernel.sh script (since I'm applying
>>> the ipipe patch from git manually) or add documentation. With this, the
>>> patch generated from the current git ipipe-3.8 branch applies cleanly.
>>>
>>> Anyway, the patch turned out to be quite simple and will hopefully roll
>>> forward fairly well.
>>
>> Hi, thanks for the patch. The prepare-kernel script does not apply pre
>> and post patches automatically, but this could be arranged. The key
>> information to add to the documentation is the I-pipe repository/branch
>> and commit hash to which the patch applies.
>
> I mean the git repository/branch and commit hash.
Details below.
Let me know if I need to do anything else, or if this isn't the data you
were wanting. There isn't really a specific kernel source git commit
this applies to, since I'm building the BeagleBone kernel by applying a
fairly large set of patches to the mainline kernel source (handled
automatically by a build script from Robert C Nelson).
The pre/post patches apply to what is currently the most recent
ipipe-3.8 version from git and the latest BeagleBone kernel:
ipipe details:
==============
Repository: git://git.xenomai.org/ipipe.git
Branch: ipipe-3.8
commit 54e4874873e9bc6c65c30ee36ac0278020ad4854
Author: Philippe Gerum <rpm@xenomai.org>
Date: Wed Aug 21 19:02:42 2013 +0200
ipipe: pass migration data along with SETAFFINITY event
Kernel source details:
======================
3.8.13-bone26.1 as generated by RCN's patch scripts:
Repositroy: https://github.com/RobertCNelson/linux-dev
Branch: am33x-v3.8
commit 3fc8a73d782231ab2750ff29793a760e8fa076bb
Author: Robert Nelson <robertcnelson@gmail.com>
Date: Mon Aug 26 14:58:46 2013 -0500
config: HID, these should have been enabled by default over a month
ago...
--
Charles Steinkuehler
charles@steinkuehler.net
next prev parent reply other threads:[~2013-08-27 21:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 14:58 [Xenomai] Building BeagleBone kernel from git Charles Steinkuehler
2013-08-20 18:39 ` Gilles Chanteperdrix
2013-08-20 18:45 ` Sagar Behere
2013-08-21 5:53 ` Michael Haberler
2013-08-21 8:45 ` Jan Kiszka
2013-08-20 19:49 ` Charles Steinkuehler
2013-08-20 19:55 ` Gilles Chanteperdrix
2013-08-20 20:25 ` Charles Steinkuehler
2013-08-20 22:37 ` Charles Steinkuehler
2013-08-20 23:12 ` Gilles Chanteperdrix
2013-08-21 22:15 ` [Xenomai] [PATCH] Fix for awk vs. gawk Charles Steinkuehler
2013-08-25 23:54 ` Gilles Chanteperdrix
2013-08-21 13:16 ` [Xenomai] Building BeagleBone kernel from git Charles Steinkuehler
2013-08-21 18:25 ` Gilles Chanteperdrix
2013-08-24 17:10 ` Ralf Roesch
2013-08-24 17:54 ` Michael Haberler
2013-08-25 0:59 ` Charles Steinkuehler
2013-08-25 7:24 ` Ralf Roesch
2013-08-27 19:59 ` [Xenomai] [PATCH] BeagleBone 3.8.13 pre/post patches Charles Steinkuehler
2013-08-27 21:12 ` Gilles Chanteperdrix
2013-08-27 21:13 ` Gilles Chanteperdrix
2013-08-27 21:57 ` Charles Steinkuehler [this message]
2013-09-10 18:48 ` Gilles Chanteperdrix
2013-09-10 21:20 ` Charles Steinkuehler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521D20AF.2040604@steinkuehler.net \
--to=charles@steinkuehler.net \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.