From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added linux drivers backports project
Date: Fri, 17 Apr 2015 21:44:01 +0200 [thread overview]
Message-ID: <55316281.6080506@mind.be> (raw)
In-Reply-To: <1429263209-13127-1-git-send-email-vorel@jablocom.com>
On 17/04/15 11:33, Petr Vorel wrote:
> From: Petr Vorel <petr.vorel@gmail.com>
>
> I fixed things which were reported and keep it as a package. This is for first start.
>
>> # FOO_KCONFIG_FILE is required
>> ifndef $(2)_KCONFIG_FILE
>> $$(error Internal error: no value specified for $(2)_KCONFIG_FILE)
>> endif
>
>> Oh, now I see that Yann's patch to convert this to ifeq hasn't been applied
>> yet... So yes in that case the custom check should stay.
> Ok. Could you send me a link to the patch?
http://patchwork.ozlabs.org/patch/459378/
[snip]
>> I plan further improvements:
>> * Allow to use different versions
>> There are stable releases, snapshot based on current linux-next and some
>> archived versions based on linux-next. Although it's recommended to use the
>> latest stable version, some people prefer / need different version.
I don't know if that is so important. If you really need that, you can still
use OVERRIDE_SRCDIR or copy it to BR2_EXTERNAL under a different name or add a
patch in BR2_GLOBAL_PATCH_DIR.
>
>> * Version check
>> For kernel versions older than 3.0 version backports-3.14 is needed,
>> kernels < 2.6.26 aren't supported.
Ah, that is a reason to allow versions! But then I'd limit it to three
versions, selectable with a choice: stable (default), next, and old (3.14).
I don't think a check of the kernel version is needed. There are also
dependencies in a bunch of other modules packages and those don't do a
dependency check either. You can anyway only do that check while building
(because you need to have the kernel source to extract the version), and usually
the modules package already does a check itself.
>
>> * Custom patches
>> Ekvivalent of BR2_LINUX_KERNEL_PATCH.
That's kind of superseded by BR2_GLOBAL_PATCH_DIR.
>
>> * Custom repository version
>> Ekvivalent of BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION.
That one would be useful, so a fourth version in the choice.
Regards,
Arnout
> Any comments?
>
> Kind regards,
> Petr
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-17 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 9:33 [Buildroot] [PATCH 1/1] Added linux drivers backports project Petr Vorel
2015-04-17 9:33 ` Petr Vorel
2015-04-17 19:44 ` Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-17 9:40 Petr Vorel
2015-04-17 9:40 ` Petr Vorel
2015-04-17 19:35 ` Arnout Vandecappelle
2015-04-17 23:02 ` Petr Vorel
2015-04-15 21:55 [Buildroot] [PATCH 0/1] " Petr Vorel
2015-04-15 21:55 ` [Buildroot] [PATCH 1/1] " Petr Vorel
2015-04-16 20:29 ` Arnout Vandecappelle
2015-04-17 8:01 ` Thomas Petazzoni
2015-04-17 9:03 ` Petr Vorel
2015-04-17 9:14 ` 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=55316281.6080506@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox