Re: [PATCH 0/12] EFI: drop arch efi

Hi, On Thu, Feb 16, 2017 at 08:38:11AM +0100, Michael Olbrich wrote: > On Wed, Feb 15, 2017 at 08:29:32PM +0100, Jean-Christophe PLAGNIOL-VILLARD > wrote: > > Today the EFI is build as an other ARCH when in fact it's just a boot mode > > > > so move it back to arch/x86 for the spicific x86 part

Re: [PATCH 0/12] EFI: drop arch efi

Hi, On Wed, Feb 15, 2017 at 08:29:32PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: > Today the EFI is build as an other ARCH when in fact it's just a boot mode > > so move it back to arch/x86 for the spicific x86 part and the common > to common and driver > > The last 3 patches allow to debu

Re: [RFC 0/2] sandbox: add gpio support with libftdi1

Hi Antony, On Wed, Feb 15, 2017 at 10:12:25AM +0300, Antony Pavlov wrote: > This patch series makes it possible to use FT2232H ACBUS[7:0] > pins as gpio pins from sandbox barebox. > > I have tested output gpio functionality by connecting > a LED to ACBUS[0] and lightening it with gpio_direction_o

Re: Using LVDS in a iMX6Q/D from Barebox

On Wed, Feb 15, 2017 at 03:34:55PM +0100, gianluca wrote: > On 02/15/2017 12:51 PM, Sascha Hauer wrote: > > On Tue, Feb 14, 2017 at 11:32:44AM +0100, gianluca wrote: > > > On 02/10/2017 08:35 AM, Sascha Hauer wrote: > > > > Hi Gianluca, > > > > > > > > On Thu, Feb 09, 2017 at 03:37:41PM +0100, gia

Re: [PATCH 07/12] efi: move x86 efi boot support to x86 arch

On Wed, Feb 15, 2017 at 08:34:15PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: > prepare to drop the efi arch as efi boot up is not arch sepecific > > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD > --- > Documentation/boards/efi.rst | 2 +- > arch/x86/Kconfig

Re: [PATCH] arm: imx: don't let MACH_SABRELITE select HAVE_PBL_MULTI_IMAGES

On Tue, Feb 14, 2017 at 12:03:12PM +0100, Uwe Kleine-König wrote: > MACH_SABRELITE is only selectable if IMX_MULTI_BOARDS is enabled. The latter > already selects HAVE_PBL_MULTI_IMAGES. > > Signed-off-by: Uwe Kleine-König > --- > arch/arm/mach-imx/Kconfig | 1 - > 1 file changed, 1 deletion(-)

Re: [PATCH 6/3] mvebu: kirkwood: simplify soc init code flow

On Wed, Feb 15, 2017 at 05:42:48PM +0100, Uwe Kleine-König wrote: > Similar to the two previous commits, this gets rid of a of-fixup which > is strange because the soc init stuff is rerun then when a new dt for > booting into Linux is loaded. It also only calls mvebu_mbus_add_range if > we're runni

[PATCH 08/12] ARCH: efi: Finally drop it as now we can build efi bootup from x86

Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- arch/efi/Kconfig | 53 --- arch/efi/Makefile | 43 --- arch/efi/configs/efi_defconfig | 79 --- arch/efi/include/asm/barebox.h | 1 - arch/efi/in

[PATCH 07/12] efi: move x86 efi boot support to x86 arch

prepare to drop the efi arch as efi boot up is not arch sepecific Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- Documentation/boards/efi.rst | 2 +- arch/x86/Kconfig | 53 -- arch/x86/Makefile| 74 +

[PATCH 09/12] efi: bus: add firmware vendor and resision and tables info

This alllow us to known where we boot from Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- drivers/efi/efi-device.c | 23 +++ include/efi.h| 7 ++- 2 files changed, 29 insertions(+), 1 deletion(-) diff --git a/drivers/efi/efi-device.c b/drivers/efi/efi-d

[PATCH 05/12] efi: move startup and payload to common/efi

Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- arch/efi/Makefile | 2 +- common/Makefile| 1 + {arch/efi => common}/efi/Makefile | 0 {arch/efi => common}/efi/efi-image.c | 0

[PATCH 01/12] efi: move block io driver to driver/block

so it can be reused on any ARCH Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- arch/efi/efi/Makefile | 5 - drivers/Makefile | 1 + drivers/block/Makefile | 1 + {arch/efi/efi => drivers/block}/efi-block-io.c

[PATCH 06/12] x86: move bios bootup code to arch/x86/bios

Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- arch/x86/Makefile | 1 + arch/x86/bios/Makefile | 3 +++ arch/x86/{lib => bios}/bios_disk.S | 0 arch/x86/{lib => bios}/memory16.S | 0 arch/x86/{lib => bios}/traveler.S | 0 arch/x86/lib/Makefile | 3

[PATCH 03/12] efi: move bus driver to driver/efi

Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- arch/efi/Kconfig| 1 + arch/efi/efi/Makefile | 1 - arch/efi/efi/efi-image.c| 4 ++-- arch/efi/efi/efi.c | 4 ++-- arc

[PATCH 02/12] efi: move clocksource out of arch

as efi is not an arch but a boot mode from where barebox is started Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- arch/efi/Kconfig| 1 + arch/efi/efi/Makefile | 1 - drivers/clocksource/Kconfig

[PATCH 04/12] efi: move debug_ll.h to include/efi

so other arch could include it too Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- arch/efi/include/mach/debug_ll.h | 21 + {arch/efi/include/mach => include/efi}/debug_ll.h | 0 2 files changed, 1 insertion(+), 20 deletions(-) copy {arch/efi/include/ma

[PATCH 0/12] EFI: drop arch efi

Today the EFI is build as an other ARCH when in fact it's just a boot mode so move it back to arch/x86 for the spicific x86 part and the common to common and driver The last 3 patches allow to debug EFI and prepare for more efi support The following changes since commit b225bbf295c92263adbcec2c3

Re: [PATCH 0/9] EFI: drop arch efi

On 14:04 Wed 15 Feb , Sascha Hauer wrote: > Hi Jean-Christophe, > > On Fri, Feb 10, 2017 at 10:56:55AM +0100, Jean-Christophe PLAGNIOL-VILLARD > wrote: > > Today the EFI is build as an other ARCH when in fact it's just a boot mode > > > > so move it back to arch/x86 for the spicific x86 part

[PATCH 6/3] mvebu: kirkwood: simplify soc init code flow

Similar to the two previous commits, this gets rid of a of-fixup which is strange because the soc init stuff is rerun then when a new dt for booting into Linux is loaded. It also only calls mvebu_mbus_add_range if we're running on a Kirkwood. The initcall must be postponed to post-core to ensure o

[PATCH 5/3] mvebu: dove: simplify soc init code flow

Similar to the previous commit, this gets rid of a of-fixup which is strange because the soc init stuff is rerun then when a new dt for booting into Linux is loaded. It also only calls mvebu_mbus_add_range if we're running on a Dove. The initcall must be postponed to post-core to ensure of_machine

[PATCH 4/3] mvebu: armada-370-xp: simplify soc init code flow

This gets rid of a of-fixup which is strange because the soc init stuff is rerun then when a new dt for booting into Linux is loaded. It also only calls mvebu_mbus_add_range if we're running on an Armada 370 or XP and inlines a simple function. The initcall must be postponed to post-core to ensure

[PATCH 3/3] fixup! mvebu: rework how memory is detected

--- arch/arm/mach-mvebu/dove.c | 2 -- arch/arm/mach-mvebu/kirkwood.c | 2 -- 2 files changed, 4 deletions(-) diff --git a/arch/arm/mach-mvebu/dove.c b/arch/arm/mach-mvebu/dove.c index d6407f394229..9a3b05d004d5 100644 --- a/arch/arm/mach-mvebu/dove.c +++ b/arch/arm/mach-mvebu/dove.c @@ -54,8

Re: Using LVDS in a iMX6Q/D from Barebox

On 02/15/2017 12:51 PM, Sascha Hauer wrote: On Tue, Feb 14, 2017 at 11:32:44AM +0100, gianluca wrote: On 02/10/2017 08:35 AM, Sascha Hauer wrote: Hi Gianluca, On Thu, Feb 09, 2017 at 03:37:41PM +0100, gianluca wrote: Hello, I would like to know if there is a clear way on using the lvds pins t

Re: problems with ext4

Am 15.02.2017 um 14:39 schrieb Oleksij Rempel: > Am 15.02.2017 um 13:31 schrieb Holger Schurig: >> For what it's worth, my kernel is also in an ext4 partition (on an >> SDCARD or eMMC). >> >> I format them with "mkfs.ext4 -q -F -D -j /dev/" >> >> Inside the partition, I use /boot/vmlinuz as a s

Re: problems with ext4

Am 15.02.2017 um 13:31 schrieb Holger Schurig: > For what it's worth, my kernel is also in an ext4 partition (on an > SDCARD or eMMC). > > I format them with "mkfs.ext4 -q -F -D -j /dev/" > > Inside the partition, I use /boot/vmlinuz as a symlink to the real file > which is in the same direct

Re: [PATCH 0/9] EFI: drop arch efi

Hi Jean-Christophe, On Fri, Feb 10, 2017 at 10:56:55AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: > Today the EFI is build as an other ARCH when in fact it's just a boot mode > > so move it back to arch/x86 for the spicific x86 part and the common > to common and driver > > The following ch

Re: Using LVDS in a iMX6Q/D from Barebox

On Tue, Feb 14, 2017 at 11:32:44AM +0100, gianluca wrote: > On 02/10/2017 08:35 AM, Sascha Hauer wrote: > > Hi Gianluca, > > > > On Thu, Feb 09, 2017 at 03:37:41PM +0100, gianluca wrote: > > > Hello, > > > I would like to know if there is a clear way on using the lvds pins to > > > drive > > > a

[PATCH] mvebu: rn2120: Make available all RAM

binary.0 sets up all RAM but the address decoding isnt' adapted accordingly which makes barebox assume that there are only 512 MiB of RAM on a single bank instead of two banks with 1 GiB each. Signed-off-by: Uwe Kleine-König --- arch/arm/boards/netgear-rn2120/lowlevel.c | 15 +++ 1 f

Re: Using LVDS in a iMX6Q/D from Barebox

On 02/14/2017 11:59 AM, gianluca wrote: On 02/14/2017 11:32 AM, gianluca wrote: On 02/10/2017 08:35 AM, Sascha Hauer wrote: Hi Gianluca, On Thu, Feb 09, 2017 at 03:37:41PM +0100, gianluca wrote: Hello, I would like to know if there is a clear way on using the lvds pins to drive a LVDS display