[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Peter Seiderer]

... sorry for the resend, file linux/linux-ext-fbtft.mk was missing.

First draft of a patch adding fbtft framebuffer drivers to buildroot.

My first attempt was using the out of tree kernel modules compile
(as suggested by Yann E. MORIN [1]) which is already (partly)
supported by the fbtft source, but I failed to enable some
needed kernel configurations e.g FB_DEFERRED_IO (did not survive
the oldconfig/silentoldconfig step when not referenced in tree,
workaround is to enable a built in feature with the same
preferences [2]).

The second attempt is the linux-ext approach (as presented here).

I am unsure if the enabling of CONFIG_SPI_BCM2708 belongs into
linux.mk or should go into raspberrypi_defconfig or belongs into
the appropriate Readme?

The second question is about the 25 submodules of fbtft
(at the moment only FB_TFT_ILI9340 and FB_TFT_ILI9341 are
enabled). Should every submodule be configurable or should all
submodules be enabled by default?

There is an adafruit fork of the fbtft repository [4] with some
adfruit specific enhancements...

Regards,
Peter

Tested with RaspberryPi B+ and PiTFT Mini Kit - 320x240 2.8" TFT
(see [5] and [6]) and the following configuration changes:

- cmdline.txt: add 'fbcon=map:10 fbcon=font:VGA8x8'
- add /etc/modules-load.d/fbtft.conf with 'fbtft_device'
- add /etc/modprobe.d/00-fbtft.conf with 'options fbtft_device name=adafruit28 rotate=90 gpios=dc:25'

[1] http://lists.busybox.net/pipermail/buildroot/2014-December/115770.html
[2] https://github.com/notro/fbtft/issues/209#issuecomment-68191514
[3] http://www.adafruit.com/products/1983
[4] https://github.com/adafruit/adafruit-rpi-fbtft
[5] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9893.jpg
[6] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9897.jpg

Peter Seiderer (1):
  linux: add fbtft kernel extension

 linux/Config.ext.in      | 10 ++++++++++
 linux/linux-ext-fbtft.mk | 25 +++++++++++++++++++++++++
 linux/linux.mk           |  9 +++++++++
 package/Config.in        |  1 +
 package/fbtft/Config.in  | 13 +++++++++++++
 package/fbtft/fbtft.mk   | 11 +++++++++++
 6 files changed, 69 insertions(+)
 create mode 100644 linux/linux-ext-fbtft.mk
 create mode 100644 package/fbtft/Config.in
 create mode 100644 package/fbtft/fbtft.mk

-- 
2.1.2

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Peter Seiderer]

Signed-off-by: Peter Seiderer <ps.report@gmx.net>
---
 linux/Config.ext.in      | 10 ++++++++++
 linux/linux-ext-fbtft.mk | 25 +++++++++++++++++++++++++
 linux/linux.mk           |  9 +++++++++
 package/Config.in        |  1 +
 package/fbtft/Config.in  | 13 +++++++++++++
 package/fbtft/fbtft.mk   | 11 +++++++++++
 6 files changed, 69 insertions(+)
 create mode 100644 linux/linux-ext-fbtft.mk
 create mode 100644 package/fbtft/Config.in
 create mode 100644 package/fbtft/fbtft.mk

diff --git a/linux/Config.ext.in b/linux/Config.ext.in
index 40c4684..583c250 100644
--- a/linux/Config.ext.in
+++ b/linux/Config.ext.in
@@ -42,4 +42,14 @@ config BR2_LINUX_KERNEL_EXT_RTAI_PATCH
 	help
 	  Optionally, explicitly specify the RTAI patch to use.
 
+# fbtft
+config BR2_LINUX_KERNEL_EXT_FBTFT
+	bool "fbtft patch"
+	select BR2_PACKAGE_FBTFT
+	help
+	  Linux Framebuffer drivers for small TFT LCD display modules,
+	  e.g. Adafruit PiTFT displays for Raspberry Pi.
+
+	  https://github.com/notro/fbtft
+
 endmenu
diff --git a/linux/linux-ext-fbtft.mk b/linux/linux-ext-fbtft.mk
new file mode 100644
index 0000000..30b9ab4
--- /dev/null
+++ b/linux/linux-ext-fbtft.mk
@@ -0,0 +1,25 @@
+################################################################################
+# Linux fbtft extensions
+#
+# Patch the linux kernel with fbtft extension
+################################################################################
+
+ifeq ($(BR2_LINUX_KERNEL_EXT_FBTFT),y)
+# Add dependency to fbtft package (download helper for the fbtft source)
+LINUX_DEPENDENCIES += fbtft
+
+define FBTFT_PREPARE_KERNEL
+	mkdir $(LINUX_DIR)/drivers/video/fbtft
+	$(INSTALL) $(FBTFT_DIR)/*.h \
+		$(FBTFT_DIR)/*.c \
+		$(FBTFT_DIR)/Makefile \
+		$(FBTFT_DIR)/Kconfig \
+		$(FBTFT_DIR)/README \
+		$(LINUX_DIR)/drivers/video/fbtft
+	echo 'source "drivers/video/fbtft/Kconfig"' >>  $(LINUX_DIR)/drivers/video/Kconfig
+	echo 'obj-y += fbtft/' >> $(LINUX_DIR)/drivers/video/Makefile
+endef
+
+LINUX_PRE_PATCH_HOOKS += FBTFT_PREPARE_KERNEL
+
+endif #BR2_LINUX_KERNEL_EXT_FBTFT
diff --git a/linux/linux.mk b/linux/linux.mk
index 8256641..1fc0159 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -196,6 +196,15 @@ define LINUX_CONFIGURE_CMDS
 		$(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS_MOUNT,$(@D)/.config))
 	$(if $(BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV),
 		$(call KCONFIG_ENABLE_OPT,CONFIG_INOTIFY_USER,$(@D)/.config))
+	$(if $(BR2_LINUX_KERNEL_EXT_FBTFT),
+		$(call KCONFIG_ENABLE_OPT,CONFIG_FB,$(@D)/.config)
+		$(call KCONFIG_SET_OPT,CONFIG_FB_TFT,m,$(@D)/.config)
+		$(call KCONFIG_SET_OPT,CONFIG_FB_TFT_ILI9340,m,$(@D)/.config)
+		$(call KCONFIG_SET_OPT,CONFIG_FB_TFT_ILI9341,m,$(@D)/.config)
+		$(call KCONFIG_SET_OPT,CONFIG_FB_TFT_FBTFT_DEVICE,m,$(@D)/.config)
+		$(call KCONFIG_ENABLE_OPT,CONFIG_SPI,$(@D)/.config)
+		$(call KCONFIG_ENABLE_OPT,CONFIG_SPI_BCM2708,$(@D)/.config)
+		$(call KCONFIG_ENABLE_OPT,CONFIG_GPIOLIB,$(@D)/.config))
 	$(if $(BR2_PACKAGE_KTAP),
 		$(call KCONFIG_ENABLE_OPT,CONFIG_DEBUG_FS,$(@D)/.config)
 		$(call KCONFIG_ENABLE_OPT,CONFIG_EVENT_TRACING,$(@D)/.config)
diff --git a/package/Config.in b/package/Config.in
index 3b37bb2..c658a28 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -311,6 +311,7 @@ endif
 	source "package/evemu/Config.in"
 	source "package/evtest/Config.in"
 	source "package/fan-ctrl/Config.in"
+	source "package/fbtft/Config.in"
 	source "package/fconfig/Config.in"
 	source "package/fis/Config.in"
 	source "package/flashrom/Config.in"
diff --git a/package/fbtft/Config.in b/package/fbtft/Config.in
new file mode 100644
index 0000000..eceea85
--- /dev/null
+++ b/package/fbtft/Config.in
@@ -0,0 +1,13 @@
+config BR2_PACKAGE_FBTFT
+	bool "fbtft"
+	depends on BR2_LINUX_KERNEL
+	help
+	  Linux Framebuffer drivers for small TFT LCD display modules,
+	  e.g. Adafruit PiTFT displays for Raspberry Pi.
+
+	  This is only the download helper for the kernel patch.
+
+	  https://github.com/notro/fbtft
+
+comment "fbtft needs a Linux kernel to be built"
+	depends on !BR2_LINUX_KERNEL
diff --git a/package/fbtft/fbtft.mk b/package/fbtft/fbtft.mk
new file mode 100644
index 0000000..9f46bdb
--- /dev/null
+++ b/package/fbtft/fbtft.mk
@@ -0,0 +1,11 @@
+################################################################################
+#
+# fbtft
+#
+################################################################################
+
+FBTFT_VERSION = 274035404701245e7491c0c6471c5b72ade4d491
+FBTFT_SITE = $(call github,notro,fbtft,$(FBTFT_VERSION))
+FBTFT_LICENSE = GPLv2+
+
+$(eval $(generic-package))
-- 
2.1.2

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Yann E. MORIN]

Peter, All,

On 2014-12-30 20:58 +0100, Peter Seiderer spake thusly:
> ... sorry for the resend, file linux/linux-ext-fbtft.mk was missing.

No problem, I've marked the first iteration as "Syuperseded" in our
Patchwork.

> First draft of a patch adding fbtft framebuffer drivers to buildroot.

Thanks! :-)

> My first attempt was using the out of tree kernel modules compile
> (as suggested by Yann E. MORIN [1]) which is already (partly)
> supported by the fbtft source, but I failed to enable some
> needed kernel configurations e.g FB_DEFERRED_IO (did not survive
> the oldconfig/silentoldconfig step when not referenced in tree,
> workaround is to enable a built in feature with the same
> preferences [2]).

OK, I'll be looking at it, to see why it fails. Don't expect much before
next week-end (actually, that will be next year, too! :-) ) because,
well, New Year celebrations, boring stuff like that, which I'm socially
obliged to attend... ;-)

Regards,
Yann E. MORIN.

> The second attempt is the linux-ext approach (as presented here).
> 
> I am unsure if the enabling of CONFIG_SPI_BCM2708 belongs into
> linux.mk or should go into raspberrypi_defconfig or belongs into
> the appropriate Readme?
> 
> The second question is about the 25 submodules of fbtft
> (at the moment only FB_TFT_ILI9340 and FB_TFT_ILI9341 are
> enabled). Should every submodule be configurable or should all
> submodules be enabled by default?
> 
> There is an adafruit fork of the fbtft repository [4] with some
> adfruit specific enhancements...
> 
> Regards,
> Peter
> 
> Tested with RaspberryPi B+ and PiTFT Mini Kit - 320x240 2.8" TFT
> (see [5] and [6]) and the following configuration changes:
> 
> - cmdline.txt: add 'fbcon=map:10 fbcon=font:VGA8x8'
> - add /etc/modules-load.d/fbtft.conf with 'fbtft_device'
> - add /etc/modprobe.d/00-fbtft.conf with 'options fbtft_device name=adafruit28 rotate=90 gpios=dc:25'
> 
> [1] http://lists.busybox.net/pipermail/buildroot/2014-December/115770.html
> [2] https://github.com/notro/fbtft/issues/209#issuecomment-68191514
> [3] http://www.adafruit.com/products/1983
> [4] https://github.com/adafruit/adafruit-rpi-fbtft
> [5] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9893.jpg
> [6] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9897.jpg
> 
> Peter Seiderer (1):
>   linux: add fbtft kernel extension
> 
>  linux/Config.ext.in      | 10 ++++++++++
>  linux/linux-ext-fbtft.mk | 25 +++++++++++++++++++++++++
>  linux/linux.mk           |  9 +++++++++
>  package/Config.in        |  1 +
>  package/fbtft/Config.in  | 13 +++++++++++++
>  package/fbtft/fbtft.mk   | 11 +++++++++++
>  6 files changed, 69 insertions(+)
>  create mode 100644 linux/linux-ext-fbtft.mk
>  create mode 100644 package/fbtft/Config.in
>  create mode 100644 package/fbtft/fbtft.mk
> 
> -- 
> 2.1.2
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Peter Seiderer]

Hello Yann,

> Gesendet: Dienstag, 30. Dezember 2014 um 23:36 Uhr
> Von: "Yann E. MORIN" <yann.morin.1998@free.fr>
> An: "Peter Seiderer" <ps.report@gmx.net>
> Cc: buildroot at busybox.net, loucrittenden63 at gmail.com, "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> Betreff: Re: [RFC v2] linux: add fbtft kernel extension
>
> Peter, All,
> 
> On 2014-12-30 20:58 +0100, Peter Seiderer spake thusly:
> > ... sorry for the resend, file linux/linux-ext-fbtft.mk was missing.
> 
> No problem, I've marked the first iteration as "Syuperseded" in our
> Patchwork.
> 
> > First draft of a patch adding fbtft framebuffer drivers to buildroot.
> 
> Thanks! :-)
> 
> > My first attempt was using the out of tree kernel modules compile
> > (as suggested by Yann E. MORIN [1]) which is already (partly)
> > supported by the fbtft source, but I failed to enable some
> > needed kernel configurations e.g FB_DEFERRED_IO (did not survive
> > the oldconfig/silentoldconfig step when not referenced in tree,
> > workaround is to enable a built in feature with the same
> > preferences [2]).
> 
> OK, I'll be looking at it, to see why it fails. Don't expect much before
> next week-end (actually, that will be next year, too! :-) ) because,
> well, New Year celebrations, boring stuff like that, which I'm socially
> obliged to attend... ;-)
> 

...as a little help my patch file for the first attempt (after the duplication
of the KCONFIG_ENABLE_OPT calls after the call to oldconfig I gave up and tried the
second approach)...

Regards,
Peter

> Regards,
> Yann E. MORIN.
> 
> > The second attempt is the linux-ext approach (as presented here).
> > 
> > I am unsure if the enabling of CONFIG_SPI_BCM2708 belongs into
> > linux.mk or should go into raspberrypi_defconfig or belongs into
> > the appropriate Readme?
> > 
> > The second question is about the 25 submodules of fbtft
> > (at the moment only FB_TFT_ILI9340 and FB_TFT_ILI9341 are
> > enabled). Should every submodule be configurable or should all
> > submodules be enabled by default?
> > 
> > There is an adafruit fork of the fbtft repository [4] with some
> > adfruit specific enhancements...
> > 
> > Regards,
> > Peter
> > 
> > Tested with RaspberryPi B+ and PiTFT Mini Kit - 320x240 2.8" TFT
> > (see [5] and [6]) and the following configuration changes:
> > 
> > - cmdline.txt: add 'fbcon=map:10 fbcon=font:VGA8x8'
> > - add /etc/modules-load.d/fbtft.conf with 'fbtft_device'
> > - add /etc/modprobe.d/00-fbtft.conf with 'options fbtft_device name=adafruit28 rotate=90 gpios=dc:25'
> > 
> > [1] http://lists.busybox.net/pipermail/buildroot/2014-December/115770.html
> > [2] https://github.com/notro/fbtft/issues/209#issuecomment-68191514
> > [3] http://www.adafruit.com/products/1983
> > [4] https://github.com/adafruit/adafruit-rpi-fbtft
> > [5] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9893.jpg
> > [6] http://h65951.serverkompetenz.net/PeterSeiderer/upload/PiTFT_2_8_ct/Image9897.jpg
> > 
> > Peter Seiderer (1):
> >   linux: add fbtft kernel extension
> > 
> >  linux/Config.ext.in      | 10 ++++++++++
> >  linux/linux-ext-fbtft.mk | 25 +++++++++++++++++++++++++
> >  linux/linux.mk           |  9 +++++++++
> >  package/Config.in        |  1 +
> >  package/fbtft/Config.in  | 13 +++++++++++++
> >  package/fbtft/fbtft.mk   | 11 +++++++++++
> >  6 files changed, 69 insertions(+)
> >  create mode 100644 linux/linux-ext-fbtft.mk
> >  create mode 100644 package/fbtft/Config.in
> >  create mode 100644 package/fbtft/fbtft.mk
> > 
> > -- 
> > 2.1.2
> > 
> 
> -- 
> .-----------------.--------------------.------------------.--------------------.
> |  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 part --------------
An embedded and charset-unspecified text was scrubbed...
Name: commit-a3501eb.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141231/854c2fe5/attachment.ksh>

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Yann E. MORIN]

Peter, All,

On 2014-12-30 23:36 +0100, Yann E. MORIN spake thusly:
> On 2014-12-30 20:58 +0100, Peter Seiderer spake thusly:
> > My first attempt was using the out of tree kernel modules compile
> > (as suggested by Yann E. MORIN [1]) which is already (partly)
> > supported by the fbtft source, but I failed to enable some
> > needed kernel configurations e.g FB_DEFERRED_IO (did not survive
> > the oldconfig/silentoldconfig step when not referenced in tree,
> > workaround is to enable a built in feature with the same
> > preferences [2]).
> 
> OK, I'll be looking at it, to see why it fails. Don't expect much before
> next week-end (actually, that will be next year, too! :-) ) because,
> well, New Year celebrations, boring stuff like that, which I'm socially
> obliged to attend... ;-)

OK, so it seems it will not be possible to biuld it as an out-of-tree
module, after all. DAmn, that's really, really bad... :-(

So, here's why: the code uses FB-related functions that are built from
separate source files, most of them conditionalised to a Kconfig symbol.
But those symbols are promptless, and can only be selected.

Thus, unless another frambuffer implementation is enabled, that selects
them, they wonlt be enabled, and thus the corresponding source files
will not be built, and the needed functions will not be in the Kernel
(neither built-in, nor in a module).

Moreover, one of the symbol, CONFIG_FB_BACKLIGHT, can only be selected
by PCI-dependent symbols (DRM stuff, like radeon or nouvea), or SuperH
dependent symbols (for some SuperH framebuffers).

Almost all needed symbols can be selected by cheating, and selecting the
virtual framebuffer, but that's not a real sane option. And we'd still
miss two symbols anyway.

So, for now, I'd say we can only use it as a linux-extension.

That's sad, real sad... :-(

The proper solution would be to patch the kernel to add a kind of
"framebuffer library for external FB drivers" (a bit like we have in the
"Library routines" sub-menu for CRC and a few other functions, that
would select all the hidden knobs for helper functions, and build them
(built-in or module), and send that patch upstream.

But I'll have a deeper look later this week-end.

Happy New Year, have nice celebrations in the coming days! :-)

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.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Thomas Petazzoni]

Dear Yann E. MORIN,

On Wed, 31 Dec 2014 00:28:07 +0100, Yann E. MORIN wrote:

> OK, so it seems it will not be possible to biuld it as an out-of-tree
> module, after all. DAmn, that's really, really bad... :-(
> 
> So, here's why: the code uses FB-related functions that are built from
> separate source files, most of them conditionalised to a Kconfig symbol.
> But those symbols are promptless, and can only be selected.
> 
> Thus, unless another frambuffer implementation is enabled, that selects
> them, they wonlt be enabled, and thus the corresponding source files
> will not be built, and the needed functions will not be in the Kernel
> (neither built-in, nor in a module).
> 
> Moreover, one of the symbol, CONFIG_FB_BACKLIGHT, can only be selected
> by PCI-dependent symbols (DRM stuff, like radeon or nouvea), or SuperH
> dependent symbols (for some SuperH framebuffers).
> 
> Almost all needed symbols can be selected by cheating, and selecting the
> virtual framebuffer, but that's not a real sane option. And we'd still
> miss two symbols anyway.

Hum, indeed, that is a very good reason why external modules cannot
work. Thanks for the analysis.

> The proper solution would be to patch the kernel to add a kind of
> "framebuffer library for external FB drivers" (a bit like we have in the
> "Library routines" sub-menu for CRC and a few other functions, that
> would select all the hidden knobs for helper functions, and build them
> (built-in or module), and send that patch upstream.

No the proper solution would be for those fbtft people to submit their
drivers to the upstream kernel. But of course, since those drivers are
developed by RasberryPi folks, they cannot play with the normal
open-source rules of contributing things upstream: they *have* to do
some utter crap and do everything in their own fork.

Sigh. RasberryPi is definitely the worst platform ever when it comes to
learning embedded Linux.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Thomas Petazzoni]

Hello,

On Wed, 31 Dec 2014 09:20:41 +0100, Thomas Petazzoni wrote:

> No the proper solution would be for those fbtft people to submit their
> drivers to the upstream kernel. But of course, since those drivers are
> developed by RasberryPi folks, they cannot play with the normal
> open-source rules of contributing things upstream: they *have* to do
> some utter crap and do everything in their own fork.

So, I've just submitted a proposal to include those drivers to the
staging tree of the Linux kernel:

  http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2014-December/063195.html

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [RFC v2] linux: add fbtft kernel extension

[Angelo Compagnucci]

Hi Thomas:

FYI, Notro started a rewrite of fbtft aiming at kernel inclusion here:

https://github.com/notro/fbdbi/wiki

Sincerely, Angelo

2014-12-31 10:14 GMT+01:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
> Hello,
>
> On Wed, 31 Dec 2014 09:20:41 +0100, Thomas Petazzoni wrote:
>
>> No the proper solution would be for those fbtft people to submit their
>> drivers to the upstream kernel. But of course, since those drivers are
>> developed by RasberryPi folks, they cannot play with the normal
>> open-source rules of contributing things upstream: they *have* to do
>> some utter crap and do everything in their own fork.
>
> So, I've just submitted a proposal to include those drivers to the
> staging tree of the Linux kernel:
>
>   http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2014-December/063195.html
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot



-- 
Profile: http://it.linkedin.com/in/compagnucciangelo