From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] spidev_test: use the one from the kernel we build
Date: Mon, 19 Jan 2015 22:32:58 +0100 [thread overview]
Message-ID: <20150119213258.GD4217@free.fr> (raw)
In-Reply-To: <20150119211348.GC4217@free.fr>
Vincent, All,
On 2015-01-19 22:13 +0100, Yann E. MORIN spake thusly:
> Vincent, All,
> On 2015-01-19 20:35 +0100, Vincent Stehl? spake thusly:
> > Add a configuration option to use the spidev_test.c from the Linux kernel we
> > build. This allows to be perfectly consistent between spidev_test and the
> > kernel in use.
>
> So, let me try to summarise: [...]
After discussing on IRC with Gustavo, I decided to further reply with
some clarifications.
I'll use a table, that should much easier to understand (hopefully).
We need to have spidev_test buildable, so it needs to be aligned with
the kernel headers from the toolchain.
toolchain headers: 3.14- 3.15+
spidev_test:
3.14- OK OK*
3.15+ KO OK
* builds but is missing new features.
Ten at runtime we need a similar table:
spidev_test: 3.14- 3.15+
kernel:
3.14- OK KO
3.15+ OK* OK
[*] builds and runs, but missing extra features.
The only broken case is when using toolchain headers 3.15+ with a 3.14-
kernel, becuse currently, we'd build a 3.15+ spidev_test, and that would
break at runtime.
Al other cases are supposed to build and run, albeit with restricted
features in one cae: using 3.14- toolchain headers with a 3.15+ Linux
kernel.
(Note: by "toolchain headers X.Y", I really mean "toolchain with kernel
headers version X.Y").
So, we're currently screwed with a too-recent toolchain that builds an
ancient kernel.
Is that all correct?
So, if we want to be bullet-proof, we can *not* build spidev_test if we
do not know both the toolchain headers version *and* the running kernel
version. Otherwise, all we can do is build the largest common
denominator, which is a spidev_test 3.14- (that is, a 3.0 in our current
code).
Anything I missed?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-01-19 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 19:35 [Buildroot] [PATCH] spidev_test: use the one from the kernel we build Vincent Stehlé
2015-01-19 21:13 ` Yann E. MORIN
2015-01-19 21:32 ` Yann E. MORIN [this message]
2015-01-20 9:02 ` Vincent Stehlé
2015-07-12 23:31 ` Arnout Vandecappelle
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=20150119213258.GD4217@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.