[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Yves Deweerdt]

added a new config file for the Raspberry Pi Zero W
- added new folder for raspberrypi0w
- included the overlays in the genimage config
- add pi3-miniuart-bt overlay to the config
- add enable_uart to the config

Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>
---
 board/raspberrypi/genimage-raspberrypi0w.cfg | 32 +++++++++++++++++++++++++
 board/raspberrypi/post-image.sh              |  9 +++++++
 board/raspberrypi0w                          |  1 +
 configs/raspberrypi0w_defconfig              | 35 ++++++++++++++++++++++++++++
 4 files changed, 77 insertions(+)
 create mode 100644 board/raspberrypi/genimage-raspberrypi0w.cfg
 create mode 120000 board/raspberrypi0w
 create mode 100644 configs/raspberrypi0w_defconfig

diff --git a/board/raspberrypi/genimage-raspberrypi0w.cfg b/board/raspberrypi/genimage-raspberrypi0w.cfg
new file mode 100644
index 0000000..9fab44f
--- /dev/null
+++ b/board/raspberrypi/genimage-raspberrypi0w.cfg
@@ -0,0 +1,32 @@
+image boot.vfat {
+  vfat {
+    files = {
+      "bcm2708-rpi-b-plus.dtb",
+      "bcm2708-rpi-0-w.dtb",
+      "rpi-firmware/bootcode.bin",
+      "rpi-firmware/cmdline.txt",
+      "rpi-firmware/config.txt",
+      "rpi-firmware/fixup.dat",
+      "rpi-firmware/start.elf",
+      "rpi-firmware/overlays",
+      "zImage"
+    }
+  }
+  size = 32M
+}
+
+image sdcard.img {
+  hdimage {
+  }
+
+  partition boot {
+    partition-type = 0xC
+    bootable = "true"
+    image = "boot.vfat"
+  }
+
+  partition rootfs {
+    partition-type = 0x83
+    image = "rootfs.ext4"
+  }
+}
diff --git a/board/raspberrypi/post-image.sh b/board/raspberrypi/post-image.sh
index de97299..4ae199a 100755
--- a/board/raspberrypi/post-image.sh
+++ b/board/raspberrypi/post-image.sh
@@ -15,6 +15,15 @@ case "${2}" in
 dtoverlay=pi3-miniuart-bt
 __EOF__
 	fi
+
+	# Enable uart console
+	if ! grep -qE '^enable_uart=1' "${BINARIES_DIR}/rpi-firmware/config.txt"; then
+		cat << __EOF__ >> "${BINARIES_DIR}/rpi-firmware/config.txt"
+
+# enable rpi3 ttyS0 serial console
+enable_uart=1
+__EOF__
+	fi
 	;;
 	--aarch64)
 	# Run a 64bits kernel (armv8)
diff --git a/board/raspberrypi0w b/board/raspberrypi0w
new file mode 120000
index 0000000..fcdafc8
--- /dev/null
+++ b/board/raspberrypi0w
@@ -0,0 +1 @@
+raspberrypi
\ No newline at end of file
diff --git a/configs/raspberrypi0w_defconfig b/configs/raspberrypi0w_defconfig
new file mode 100644
index 0000000..20e792d
--- /dev/null
+++ b/configs/raspberrypi0w_defconfig
@@ -0,0 +1,35 @@
+BR2_arm=y
+BR2_arm1176jzf_s=y
+BR2_ARM_EABIHF=y
+
+# Linux headers same as kernel, a 4.9 series
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_9=y
+
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_GIT=y
+BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="5e4ee836560d4c0371e109bf469e1ad808ae7a44"
+BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi"
+
+# Build the DTBs for A/B from the kernel sources: the zero is the same
+# as the A+ model, just in a different form-factor
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2708-rpi-b-plus bcm2708-rpi-0-w"
+
+BR2_PACKAGE_RPI_FIRMWARE=y
+BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y
+
+# Required tools to create the SD image
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y
+
+# Filesystem / image
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+# BR2_TARGET_ROOTFS_TAR is not set
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi0w/post-build.sh"
+BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi0w/post-image.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"
-- 
2.7.4

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Thomas Petazzoni]

Hello,

On Sun, 18 Jun 2017 21:44:04 +0200, Yves Deweerdt wrote:
> added a new config file for the Raspberry Pi Zero W
> - added new folder for raspberrypi0w
> - included the overlays in the genimage config
> - add pi3-miniuart-bt overlay to the config
> - add enable_uart to the config
> 
> Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>

I am a bit confused: what do you need in this defconfig, that the
existing raspberrypi0_defconfig doesn't provide?

Your proposed defconfig is using the exact same kernel version and list
of Device Trees. The only differences are:

+BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y

and:

+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"

Is this the motivation for this separate defconfig? Could the existing
raspberrypi0_defconfig be extended to also work for your use case,
while keeping compatibility for the RPi Zero ?

If not, we should remove the RPi Zero W support from
raspberrypi0_defconfig, because otherwise things are pretty confusing.

Thanks!

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

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Peter Seiderer]

Hello Thomas, Yves,

On Mon, 19 Jun 2017 22:27:53 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
> 
> On Sun, 18 Jun 2017 21:44:04 +0200, Yves Deweerdt wrote:
> > added a new config file for the Raspberry Pi Zero W
> > - added new folder for raspberrypi0w
> > - included the overlays in the genimage config
> > - add pi3-miniuart-bt overlay to the config
> > - add enable_uart to the config
> > 
> > Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>
> 
> I am a bit confused: what do you need in this defconfig, that the
> existing raspberrypi0_defconfig doesn't provide?
> 
> Your proposed defconfig is using the exact same kernel version and list
> of Device Trees. The only differences are:
> 
> +BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y
> 
> and:
> 
> +BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"
> 

And the additional genimage line:

+      "rpi-firmware/overlays",

And the 'enable_uart=1' in the config.txt (Is this really needed? For the Pi3 the
overlay solution is enough).

See [1], [2] and [3] for the old suggestion/discussion...

> Is this the motivation for this separate defconfig? Could the existing
> raspberrypi0_defconfig be extended to also work for your use case,
> while keeping compatibility for the RPi Zero ?
> 
> If not, we should remove the RPi Zero W support from
> raspberrypi0_defconfig, because otherwise things are pretty confusing.
> 

Regards,
Peter

[1] http://lists.busybox.net/pipermail/buildroot/2017-March/187206.html
[2] http://lists.busybox.net/pipermail/buildroot/2017-March/187377.html
[3] http://lists.busybox.net/pipermail/buildroot/2017-March/187403.html

> Thanks!
> 
> Thomas

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Yves Deweerdt]

Hello Peter, Thomas,


On Mon, Jun 19, 2017 at 10:54 PM Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Thomas, Yves,
>
> On Mon, 19 Jun 2017 22:27:53 +0200, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
>
> > Hello,
> >
> > On Sun, 18 Jun 2017 21:44:04 +0200, Yves Deweerdt wrote:
> > > added a new config file for the Raspberry Pi Zero W
> > > - added new folder for raspberrypi0w
> > > - included the overlays in the genimage config
> > > - add pi3-miniuart-bt overlay to the config
> > > - add enable_uart to the config
> > >
> > > Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>
> >
> > I am a bit confused: what do you need in this defconfig, that the
> > existing raspberrypi0_defconfig doesn't provide?
> >
>
The raspberrypi0_defconfig was not working for me because:
- it does not install the overlay files on the vfat partition
- it does not add the pi3-miniuart-bt overlay in the configuration
- it does not put enable_uart=1 in the configuration

> Your proposed defconfig is using the exact same kernel version and list
> > of Device Trees. The only differences are:
> >
> > +BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y
> >
> > and:
> >
> > +BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"
> >
>
> And the additional genimage line:
>
> +      "rpi-firmware/overlays",
>
> And the 'enable_uart=1' in the config.txt (Is this really needed? For the
> Pi3 the
> overlay solution is enough).
>

I've tried running rpi0w without the enable_uart=1 and then I don't have
serial, with the enable_uart=1 the console is working fine.
 I didn't try running on rpi3 though.
For rpi3, is it correct that it seems that when running in 64bit mode you
should add enable_uart=1 and for 32 bit mode you don't need to add it?

See [1], [2] and [3] for the old suggestion/discussion...
>
> > Is this the motivation for this separate defconfig? Could the existing
> > raspberrypi0_defconfig be extended to also work for your use case,
> > while keeping compatibility for the RPi Zero ?
>

We could also add the device tree overlays in the raspberrypi0 config by
default, then there is only one difference left between rpi0 and rpi0w:
that is that for rpi0w you need this:enable_uart=1,
dtoverlay=pi3-miniuart-bt in the configuration.

>
> > If not, we should remove the RPi Zero W support from
> > raspberrypi0_defconfig, because otherwise things are pretty confusing.
> >
>
right, if we choose to make a seperate rpi0w defconfig, reference to 0w
needs to be removed from rpi0 defconfig.


> Regards,
> Peter
>
> [1] http://lists.busybox.net/pipermail/buildroot/2017-March/187206.html
> [2] http://lists.busybox.net/pipermail/buildroot/2017-March/187377.html
> [3] http://lists.busybox.net/pipermail/buildroot/2017-March/187403.html
>
> > Thanks!
> >
> > Thomas
>
> Kind regards,

Yves
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170620/1ed35380/attachment.html>

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Peter Seiderer]

Hello Yves, Thomas,

On Tue, 20 Jun 2017 09:39:11 +0000, Yves Deweerdt <yves.deweerdt.linux@gmail.com> wrote:

> Hello Peter, Thomas,
> 
> 
> On Mon, Jun 19, 2017 at 10:54 PM Peter Seiderer <ps.report@gmx.net> wrote:
> 
> > Hello Thomas, Yves,
> >
> > On Mon, 19 Jun 2017 22:27:53 +0200, Thomas Petazzoni <
> > thomas.petazzoni at free-electrons.com> wrote:
> >
> > > Hello,
> > >
> > > On Sun, 18 Jun 2017 21:44:04 +0200, Yves Deweerdt wrote:
> > > > added a new config file for the Raspberry Pi Zero W
> > > > - added new folder for raspberrypi0w
> > > > - included the overlays in the genimage config
> > > > - add pi3-miniuart-bt overlay to the config
> > > > - add enable_uart to the config
> > > >
> > > > Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>
> > >
> > > I am a bit confused: what do you need in this defconfig, that the
> > > existing raspberrypi0_defconfig doesn't provide?
> > >
> >
> The raspberrypi0_defconfig was not working for me because:
> - it does not install the overlay files on the vfat partition
> - it does not add the pi3-miniuart-bt overlay in the configuration
> - it does not put enable_uart=1 in the configuration
> 
> > Your proposed defconfig is using the exact same kernel version and list
> > > of Device Trees. The only differences are:
> > >
> > > +BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y
> > >
> > > and:
> > >
> > > +BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"
> > >
> >
> > And the additional genimage line:
> >
> > +      "rpi-firmware/overlays",
> >
> > And the 'enable_uart=1' in the config.txt (Is this really needed? For the
> > Pi3 the
> > overlay solution is enough).
> >
> 
> I've tried running rpi0w without the enable_uart=1 and then I don't have
> serial, with the enable_uart=1 the console is working fine.
>  I didn't try running on rpi3 though.
> For rpi3, is it correct that it seems that when running in 64bit mode you
> should add enable_uart=1 and for 32 bit mode you don't need to add it?

Never tried the 64bit mode (yet), any reference for this?

If I remember right enable_uart and pi3-miniuart-bt overlay are
orthogonal approaches to (re-)enable the serial console? If
the overlay does not work for pi0w maybe the enable_uart=1 is
enough (care to test it?)...

Did you test it with the defconfig otherwise unchanged or with
additional changes (maybe systemd)?

Some information about it can be found at [4]...

Regards,
Peter

[4] https://www.raspberrypi.org/documentation/configuration/uart.md

> 
> See [1], [2] and [3] for the old suggestion/discussion...
> >
> > > Is this the motivation for this separate defconfig? Could the existing
> > > raspberrypi0_defconfig be extended to also work for your use case,
> > > while keeping compatibility for the RPi Zero ?
> >
> 
> We could also add the device tree overlays in the raspberrypi0 config by
> default, then there is only one difference left between rpi0 and rpi0w:
> that is that for rpi0w you need this:enable_uart=1,
> dtoverlay=pi3-miniuart-bt in the configuration.
> 
> >
> > > If not, we should remove the RPi Zero W support from
> > > raspberrypi0_defconfig, because otherwise things are pretty confusing.
> > >
> >
> right, if we choose to make a seperate rpi0w defconfig, reference to 0w
> needs to be removed from rpi0 defconfig.
> 
> 
> > Regards,
> > Peter
> >
> > [1] http://lists.busybox.net/pipermail/buildroot/2017-March/187206.html
> > [2] http://lists.busybox.net/pipermail/buildroot/2017-March/187377.html
> > [3] http://lists.busybox.net/pipermail/buildroot/2017-March/187403.html
> >
> > > Thanks!
> > >
> > > Thomas
> >
> > Kind regards,
> 
> Yves

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Yves Deweerdt]

Hello Peter,

Probably I tried adding the dtoverlay, without adding the overlay files on
the fat partition, and then added both the files and the enable_uart in one
go, which was working, and I jumped directly to the conclusion that both
were needed.
I have retested with dtoverlay only on rpi0w and I can confirm that this is
working as it should.

So what do I do now? Rework the patch to create the raspberrypi0w_defconfig
with the dtoverlay only, remove the 0w device tree from
raspberrypi0_defconfig?

Kind regards,

Yves

On Tue, Jun 20, 2017 at 9:19 PM Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Yves, Thomas,
>
> On Tue, 20 Jun 2017 09:39:11 +0000, Yves Deweerdt <
> yves.deweerdt.linux at gmail.com> wrote:
>
> > Hello Peter, Thomas,
> >
> >
> > On Mon, Jun 19, 2017 at 10:54 PM Peter Seiderer <ps.report@gmx.net>
> wrote:
> >
> > > Hello Thomas, Yves,
> > >
> > > On Mon, 19 Jun 2017 22:27:53 +0200, Thomas Petazzoni <
> > > thomas.petazzoni at free-electrons.com> wrote:
> > >
> > > > Hello,
> > > >
> > > > On Sun, 18 Jun 2017 21:44:04 +0200, Yves Deweerdt wrote:
> > > > > added a new config file for the Raspberry Pi Zero W
> > > > > - added new folder for raspberrypi0w
> > > > > - included the overlays in the genimage config
> > > > > - add pi3-miniuart-bt overlay to the config
> > > > > - add enable_uart to the config
> > > > >
> > > > > Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>
> > > >
> > > > I am a bit confused: what do you need in this defconfig, that the
> > > > existing raspberrypi0_defconfig doesn't provide?
> > > >
> > >
> > The raspberrypi0_defconfig was not working for me because:
> > - it does not install the overlay files on the vfat partition
> > - it does not add the pi3-miniuart-bt overlay in the configuration
> > - it does not put enable_uart=1 in the configuration
> >
> > > Your proposed defconfig is using the exact same kernel version and list
> > > > of Device Trees. The only differences are:
> > > >
> > > > +BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y
> > > >
> > > > and:
> > > >
> > > > +BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"
> > > >
> > >
> > > And the additional genimage line:
> > >
> > > +      "rpi-firmware/overlays",
> > >
> > > And the 'enable_uart=1' in the config.txt (Is this really needed? For
> the
> > > Pi3 the
> > > overlay solution is enough).
> > >
> >
> > I've tried running rpi0w without the enable_uart=1 and then I don't have
> > serial, with the enable_uart=1 the console is working fine.
> >  I didn't try running on rpi3 though.
> > For rpi3, is it correct that it seems that when running in 64bit mode you
> > should add enable_uart=1 and for 32 bit mode you don't need to add it?
>
> Never tried the 64bit mode (yet), any reference for this?
>
> If I remember right enable_uart and pi3-miniuart-bt overlay are
> orthogonal approaches to (re-)enable the serial console? If
> the overlay does not work for pi0w maybe the enable_uart=1 is
> enough (care to test it?)...
>
> Did you test it with the defconfig otherwise unchanged or with
> additional changes (maybe systemd)?
>
> Some information about it can be found at [4]...
>
> Regards,
> Peter
>
> [4] https://www.raspberrypi.org/documentation/configuration/uart.md
>
> >
> > See [1], [2] and [3] for the old suggestion/discussion...
> > >
> > > > Is this the motivation for this separate defconfig? Could the
> existing
> > > > raspberrypi0_defconfig be extended to also work for your use case,
> > > > while keeping compatibility for the RPi Zero ?
> > >
> >
> > We could also add the device tree overlays in the raspberrypi0 config by
> > default, then there is only one difference left between rpi0 and rpi0w:
> > that is that for rpi0w you need this:enable_uart=1,
> > dtoverlay=pi3-miniuart-bt in the configuration.
> >
> > >
> > > > If not, we should remove the RPi Zero W support from
> > > > raspberrypi0_defconfig, because otherwise things are pretty
> confusing.
> > > >
> > >
> > right, if we choose to make a seperate rpi0w defconfig, reference to 0w
> > needs to be removed from rpi0 defconfig.
> >
> >
> > > Regards,
> > > Peter
> > >
> > > [1]
> http://lists.busybox.net/pipermail/buildroot/2017-March/187206.html
> > > [2]
> http://lists.busybox.net/pipermail/buildroot/2017-March/187377.html
> > > [3]
> http://lists.busybox.net/pipermail/buildroot/2017-March/187403.html
> > >
> > > > Thanks!
> > > >
> > > > Thomas
> > >
> > > Kind regards,
> >
> > Yves
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170621/bf59d923/attachment.html>

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Yves Deweerdt]

Hello Peter, Thomas,


> > For rpi3, is it correct that it seems that when running in 64bit mode you
> > should add enable_uart=1 and for 32 bit mode you don't need to add it?
>
> Never tried the 64bit mode (yet), any reference for this?
>
>
> Hello Peter, Thomas,

I just had a closer look to the raspberrypi3 and raspberrypi3_64 story.
It seems that on the 32 bit version the overlay is being used, which means
that the console is being put on /dev/ttyS0 in stead of /dev/ttyAMA0, which
means that /dev/ttyAMA0 is available already if you plan to use bluetooth.
On the 64 bit version, the console is put on /dev/ttyAMA0, so that means
that if you want to enable bluetooth, you need to do the same modifications
again to move console over to /dev/ttyS0 and free up /dev/ttyAMA0 for
bluetooth.

I don't know if there are any drawbacks in using the /dev/ttyS0 on the 64
bit version. If not, I would recommend making the 32 bit version and the 64
bit version do the same thing, and at that moment the --aarch64 option in
the post-image.sh script could be completely removed.

Kind regards,

Yves

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170621/b72cb84d/attachment.html>

[Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W

[Peter Seiderer]

Hello Yves, Thomas,

On Wed, 21 Jun 2017 20:35:21 +0000, Yves Deweerdt <yves.deweerdt.linux@gmail.com> wrote:

> Hello Peter, Thomas,
> 
> 
> > > For rpi3, is it correct that it seems that when running in 64bit mode you
> > > should add enable_uart=1 and for 32 bit mode you don't need to add it?
> >
> > Never tried the 64bit mode (yet), any reference for this?
> >
> >
> > Hello Peter, Thomas,
> 
> I just had a closer look to the raspberrypi3 and raspberrypi3_64 story.
> It seems that on the 32 bit version the overlay is being used, which means
> that the console is being put on /dev/ttyS0 in stead of /dev/ttyAMA0, which
> means that /dev/ttyAMA0 is available already if you plan to use bluetooth.
> On the 64 bit version, the console is put on /dev/ttyAMA0, so that means
> that if you want to enable bluetooth, you need to do the same modifications
> again to move console over to /dev/ttyS0 and free up /dev/ttyAMA0 for
> bluetooth.
> 
> I don't know if there are any drawbacks in using the /dev/ttyS0 on the 64
> bit version. If not, I would recommend making the 32 bit version and the 64
> bit version do the same thing, and at that moment the --aarch64 option in
> the post-image.sh script could be completely removed.

The --aarch64 options sets the important 'arm_control=0x200' to enable to
boot the 64bit kernel, this needs to be kept (maybe change the post-image.sh
script to support multiple cmdl options and separate overlay and aarch64)...

But I had no success to enable the serial console for raspberrypi3_64 using
only the overlay, only 'enable_uart=1' worked for me...

Regards,
Peter


> 
> Kind regards,
> 
> Yves
> 
> >
> >