Some older pca100 boards were available with 64MB RAM. The chips
require a slightly different sdram controller initialization. Support
this by building bootloader images for both variants.
Signed-off-by: Florian Bäuerle
---
arch/arm/boards/phytec-phycard-imx27/lowlevel.c | 52 +++
Hi Ian,
On Fri, Dec 07, 2018 at 03:19:58PM +, Ian Abbott wrote:
> Hi,
>
> Commit 8a680e3c9b5dd8470b7437654877d5439e9a6407 ("ARM: socfpga: Arria10:
> support programming FPGA in PBL") deselected GPIOLIB, so none of the SoCFPGA
> boards support GPIO any more. There is no mention of this in the
Hi Sascha,
On 07/12/2018 15:29, Sascha Hauer wrote:
Hi Ian,
On Fri, Dec 07, 2018 at 03:19:58PM +, Ian Abbott wrote:
Hi,
Commit 8a680e3c9b5dd8470b7437654877d5439e9a6407 ("ARM: socfpga: Arria10:
support programming FPGA in PBL") deselected GPIOLIB, so none of the SoCFPGA
boards support GPIO
Hi,
Commit 8a680e3c9b5dd8470b7437654877d5439e9a6407 ("ARM: socfpga: Arria10:
support programming FPGA in PBL") deselected GPIOLIB, so none of the
SoCFPGA boards support GPIO any more. There is no mention of this in
the commit message. Was this a deliberate change, or accidental? Where
is t
We used to end the fastboot session once we received the boot command.
Now that we end the session during shutdown we can do better: We can
end the session once we actually shutdown, or more importantly in the
case of an error.
Signed-off-by: Sascha Hauer
---
drivers/usb/gadget/f_fastboot.c | 16
This series has a few improvements for fastboot.
So far the host always timed out when we issued a command that caused
barebox to shutdown, like "oem bootm ..." or similar. We now finish
the fastboot session beforehand to let the host know what is going on.
Also we now print the fastboot messages
Some commands like booting a kernel will trigger a shutdown of barebox,
but the host will never notice and timeout later. Be more friendly and
tell the host we are going to shutdown and end the current fastboot
session.
Signed-off-by: Sascha Hauer
---
drivers/usb/gadget/f_fastboot.c | 43 +++
Now that we end the fastboot session when shutting down barebox
we can call restart_machine() directly and not in the completion
callback of the answer request.
Signed-off-by: Sascha Hauer
---
drivers/usb/gadget/f_fastboot.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --gi
Instead of setting the context for in_req we have set the context
for out_req twice. This didn't trigger an error because we haven't
used the context. So instead of fixing it we can equally well just
remove it.
Signed-off-by: Sascha Hauer
---
drivers/usb/gadget/f_fastboot.c | 1 -
1 file changed
Polling for the status of a request does not require a global variable.
We can poll for the status directly.
Signed-off-by: Sascha Hauer
---
drivers/usb/gadget/f_fastboot.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/f_fastboot.c b/driver
It's nice to also see on the barebox side what is going on with
fastboot, so print the messages to the logs also.
Signed-off-by: Sascha Hauer
---
drivers/usb/gadget/f_fastboot.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/f_fastboot.c b/drivers/u
We used to pass the message type ("INFO", "FAIL", "OKAY") as strings
to fastboot_tx_print(). Change this to a enum type. This allows
fastboot_tx_print() to react on the message type in the next step.
Signed-off-by: Sascha Hauer
---
drivers/usb/gadget/f_fastboot.c | 153 --
Add support for the Xilinx Zynq Ultrascale+ MPSoC architecture (ZynqMP)
and the Xilinx ZCU104 board.
Barebox is booted as BL33 in EL-1 and expects that a BL2 (i.e. the FSBL)
already took care of initializing the RAM. Also for debug_ll, the UART
is expected to be already setup correctly. Thus, you
This is v3 of the series to add support for the Xilinx Zynq Ultrascale+ MPSoC
platform and the ZCU104 Evaluation Kit.
I checked the SPDX-License-Identifiers and added them on all newly added
source files.
Michael
Changelog:
v2 -> v3:
- add SPDX-License-Identifiers to all newly added source file
arm64 has no __naked__ attribute and the compiler adds a function prologue
for saving x29 and x30 to the stack for all C functions. This includes
functions defined using the ENTRY_FUNCTION macro. Therefore, the stack
needs to be setup before entering a C function, which is not possible if
the entry
Commit e1287b1a8b27 ("arm: rework lib directory to support arm64")
restructured the lib directory and added the lib64 directory. It moved
the existing .gitignore to the lib32 directory but didn't add a new
.gitignore for lib64.
Thus building Barebox for arm64 results in stray barebox.lds files.
C
Without this flag, gcc generates code to save the Q/V registers to the
stack for handling the va_list in pr_print(). Saving the registers is
useless, as the registers are never restored, but accessing the
registers to save them hangs the CPU.
Follow the Linux arch/arm64/Makefile and use the genera
Am Freitag, den 07.12.2018, 09:18 +0100 schrieb Uwe Kleine-König:
> On Thu, Dec 06, 2018 at 12:45:07PM +0100, Lucas Stach wrote:
> > It's a dependency for IMX_OCOTP, which is selected by VF610.
>
> I didn't look into the details, but the commit log sounds as if
> IMX_OCOTP should select OFDEVICE i
Hello Sascha,
On 7/12/18 08:43, Sascha Hauer wrote:
> On Fri, Dec 07, 2018 at 07:34:37AM +0100, Ahmad Fatoum wrote:
>> Users can have reasons to inhibit barebox from fixing up partitions nodes
>> into the kernel device tree, like if it's a boot0-partitions node, which
>> doesn't have a kernel bind
On Thu, Dec 06, 2018 at 12:45:07PM +0100, Lucas Stach wrote:
> It's a dependency for IMX_OCOTP, which is selected by VF610.
I didn't look into the details, but the commit log sounds as if
IMX_OCOTP should select OFDEVICE instead?
Best regards
Uwe
--
Pengutronix e.K. |
Document a way to avoid clashes between i.MX boot info/Barebox and
GPT's Partition Entry Array.
Signed-off-by: Andrey Smirnov
---
Documentation/boards/imx.rst | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/boards/imx.rst b/Documentation/boards/imx.rst
inde
21 matches
Mail list logo
