Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] axfs: add new filesystem type
Date: Wed, 14 Oct 2015 12:50:13 -0300	[thread overview]
Message-ID: <561E79B5.8070509@vanguardiasur.com.ar> (raw)
In-Reply-To: <20151013205313.GB4161@free.fr>

Yann,

El 13/10/15 a las 17:53, Yann E. MORIN escribi?:
> Arnout, Ariel, All,
> 
> On 2015-10-05 19:53 +0100, Arnout Vandecappelle spake thusly:
>> On 05-10-15 17:55, Ariel D'Alessandro wrote:
>>> The Advanced XIP File System is a Linux kernel filesystem driver that enables
>>> files to be executed directly from flash or ROM memory rather than being copied
>>> into RAM.
> [--SNIP--]
>>  It would be nice to add the axfs kernel side as a kernel extension as well. But
>> that looks heavily non-trivial.
> 
> I had a quick and cursory look at the axfs sources, and I think this
> could be quite easily achievable. Non-trivial, granted, but not too
> complex either.
> 
> Ariel, are you interested in adding this as a kernel extension?
> (Hint: it would be really great! ;-) )

Yes, I'll make some room and take a look at this!

> 
> Kernel extensions are a way to "modify" the kernel source tree with
> patches provided by another package:
>     http://buildroot.org/downloads/manual/manual.html#linux-kernel-ext
> 
> Basically, here's what you'd have to do in the axfs extension:
> 
>   - get the 'raw' version of the kernel with (but see notes below):
>         AXFSUTILS_KVER = $(MAKE) -C $(LINUX_DIR) kernelversion
> 
>   - check that there is a patch directory for that kernel version:
>         kernel/patches/v$(AXFSUTILS_KVER)/
>     => if not, bail out
>     => if yes, continue
> 
>   - copy $(@D)/kernel/fs/axfs to $(LINUX_DIR)/fs/axfs
> 
>   - copy $(@D)/include/linux/* to $(LINUX_DIR)/include/linux/
> 
>   - modify $(LINUX_DIR)/fs/Kconfig with (before last line):
>         source "fs/axfs/Kconfig"
> 
>   - modify $(LINUX_DIR)/fs/Makefile with (as last line):
>         obj-$(CONFIG_AXFS) += axfs
> 
> Obviously, entirely untested; adapt to Real Life (TM). ;-)
> 
> Notes: ideally, the kernel 'raw' version should be provided by
> linux/linux.mk but we currently do not have it yet; we only have
> 'kernelrelease', not 'kernelversion'. It would be interesting if you
> provided an initial patch that adds this.
> 
> Currently, 'kernelrelease' is in $(LINUX_VERSION_PROBED), so maybe you
> could introduce LINUX_VERSION_RAW filled with the output of
> 'kernelversion' (see how it's done for 'kernelrelease').

That's pretty clarifying! Thank you very much for this Yann, it will
help me a lot. I'll try to submit patches for this ASAP.

Thanks,

-- 
Ariel D'Alessandro, VanguardiaSur
www.vanguardiasur.com.ar

  reply	other threads:[~2015-10-14 15:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 16:55 [Buildroot] [PATCH v2 0/2] Add support for AXFS filesystem type Ariel D'Alessandro
2015-10-05 16:55 ` [Buildroot] [PATCH v2 1/2] axfsutils: add new package Ariel D'Alessandro
2015-10-05 18:39   ` Arnout Vandecappelle
2015-10-13 12:06     ` Ariel D'Alessandro
2015-10-05 16:55 ` [Buildroot] [PATCH v2 2/2] axfs: add new filesystem type Ariel D'Alessandro
2015-10-05 18:53   ` Arnout Vandecappelle
2015-10-05 18:59     ` Ezequiel Garcia
2015-10-05 19:09       ` Arnout Vandecappelle
2015-10-13 12:12     ` Ariel D'Alessandro
2015-10-13 20:24       ` Yann E. MORIN
2015-10-13 21:14         ` Arnout Vandecappelle
2015-10-13 20:53     ` Yann E. MORIN
2015-10-14 15:50       ` Ariel D'Alessandro [this message]
2015-10-13 21:14 ` [Buildroot] [PATCH v2 0/2] Add support for AXFS " Thomas Petazzoni
2015-10-14 16:05   ` Ariel D'Alessandro
2015-10-14 17:06     ` Thomas Petazzoni

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=561E79B5.8070509@vanguardiasur.com.ar \
    --to=ariel@vanguardiasur.com.ar \
    --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