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 23:08:02 +0200 [thread overview]
Message-ID: <535588B2.90205@xenomai.org> (raw)
In-Reply-To: <535573FD.6050308@steinkuehler.net>
On 04/21/2014 09:39 PM, Charles Steinkuehler wrote:
> On 4/21/2014 2:33 PM, Gilles Chanteperdrix wrote:
>> On 04/21/2014 09:24 PM, Charles Steinkuehler wrote:
>>>>
>>> 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?
>
> I don't, of course, it's just what the config from RCN's build
> scripts has setup for by default.
>
>> 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.
>
> As mentioned, I'm still plugging along, and mostly learning as I
> go.
>
> Thanks for the breadcrumbs! :)
Our users have evolved. Somewhere along the road, Linux users stopped
being used to configuring their kernel, and we did not notice. I hope
to be able to propose something soon to help this situation.
Anyway, start with an unpatched kernel, tune the configuration until
you get a kernel which compiles and runs.
Then merge with the I-pipe tree. If the same configuration (minus the
usual forbidden options) does not compile, then there may be a problem
in the I-pipe tree.
Something to definitely disable for the time being is context tracking
(and so CONFIG_NOHZ_FULL).
--
Gilles.
prev parent reply other threads:[~2014-04-21 21:08 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
2014-04-21 19:39 ` Charles Steinkuehler
2014-04-21 21:08 ` Gilles Chanteperdrix [this message]
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=535588B2.90205@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.