From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Charles Steinkuehler <charles@steinkuehler.net>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Pre/Post patches
Date: Mon, 21 Apr 2014 21:33:35 +0200 [thread overview]
Message-ID: <5355728F.80507@xenomai.org> (raw)
In-Reply-To: <5355705B.5010604@steinkuehler.net>
On 04/21/2014 09:24 PM, Charles Steinkuehler wrote:
> On 4/19/2014 1:02 PM, Gilles Chanteperdrix wrote:
>>
>> I am currently validating the I-pipe patch for Linux 3.14 on armv4 and
>> armv5, but it should already work for armv6 and armv7 processors, it is
>> available as a branch for-ipipe-3.14.0 in ipipe-gch git. Could you have
>> a look at it on BeagleBone, Raspberry and Zynq? For the SOCs supported
>> by mainline, please simply send patches to the for-ipipe-3.14.0 branch.
>
> I'm still working on building a kernel for the BeagleBone Black.
>
> I tried the standard method of generating the ipipe patch and applying
> it to the BeagleBone patched kernel source. The first problem I
> encountered was an unknown architecture error for the
> net/ethernet/cadence/at91_ether.c driver. I edited the genpatches.sh
> script and forced this to x86 (since I'm pretty sure I don't need this
> driver for the BeagleBone).
Well, at91 are arms, will fix.
> Note the patch set for the 3.14 BeagleBone
> kernel is mostly device-tree changes and about four fairly simple
> back-ported fixes.
>
> The next problem comes when building the kernel, I get an undefined
> warning from the raid456.ko module (see below). I'll keep plugging
> away, but any advice would be appreciated.
probably something wrong with the configuration. Why do you need raid 4,
5, 6 anyway? In a first step, you should work with a standard
configuraiton, such as omap2plus_defconfig, or better, if you have it,
with a minimal configuration suited for your board, which will avoid:
> (...)
> MODPOST 1950 modules
and build a kernel in just a few minutes.
--
Gilles.
next prev parent reply other threads:[~2014-04-21 19:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 18:02 [Xenomai] Pre/Post patches Gilles Chanteperdrix
2014-04-20 18:22 ` Matthew Fornero
2014-04-20 23:00 ` Gilles Chanteperdrix
2014-04-21 12:35 ` Matthew Fornero
2014-04-21 12:37 ` Matthew Fornero
2014-04-21 23:11 ` Gilles Chanteperdrix
2014-04-21 6:28 ` Huub Van Niekerk
2014-04-21 8:15 ` Gilles Chanteperdrix
2014-04-21 12:38 ` Huub Van Niekerk
2014-04-21 15:31 ` Gilles Chanteperdrix
2014-04-21 19:24 ` Charles Steinkuehler
2014-04-21 19:33 ` Gilles Chanteperdrix [this message]
2014-04-21 19:39 ` Charles Steinkuehler
2014-04-21 21:08 ` Gilles Chanteperdrix
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=5355728F.80507@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=charles@steinkuehler.net \
--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.