Hi Christian,
On Mon, Feb 11, 2019 at 12:00:58PM +0100, Lucas Stach wrote:
> Hi Christian,
>
> Am Mittwoch, den 06.02.2019, 19:41 +0100 schrieb Christian Hemp:
> > The phyCORE-i.MX8M aka PCL-066 is a SoM containing a i.MX8M SoC.
> >
> > phyCORE-i.MX8M:
> > - 1GB LPDDR4 RAM
> > - eMMC
> > - mi
Add code to make sure that imx8mq_init_syscnt_frequency() is only
executed on i.MX8MQ.
Signed-off-by: Andrey Smirnov
---
arch/arm/mach-imx/imx8mq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-imx/imx8mq.c b/arch/arm/mach-imx/imx8mq.c
index d887092ce..3f6b433a5 100644
---
Port code found in cdn_dp_load_firmware() in Linux kernel to check if
HDMI firmware is running and, if so, report its version.
Signed-off-by: Andrey Smirnov
---
Changes since [v1]:
- Added CPU type check to prevent execution on non-i.MX8MQ SoCs.
- Changes messages to say "HDP" instead
On Tue, Feb 12, 2019 at 5:13 AM Teresa Remmet wrote:
>
> Hello Andrey,
>
> Am Montag, den 11.02.2019, 18:57 -0800 schrieb Andrey Smirnov:
> > On Mon, Feb 11, 2019 at 7:16 AM Teresa Remmet
> > wrote:
> > >
> > > Adds minimal support for the sysc interconnect target module found
> > > on many TI So
On Tue, Feb 12, 2019 at 09:34:39AM +0300, Antony Pavlov wrote:
> Signed-off-by: Antony Pavlov
> ---
> drivers/nvmem/eeprom_93xx46.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/drivers/nvmem/eeprom_93xx46.c b/drivers/nvmem/eeprom_93xx46.c
On Mon, Feb 11, 2019 at 05:44:00PM +0100, Marco Felsch wrote:
> This patch backports linux commit e1b505a60366 ("net: phy: micrel: add
> 125MHz reference clock workaround").
>
> 8<- The original commit message ---
>
> net: phy: micrel: add 125MHz reference cloc
On Mon, Feb 11, 2019 at 06:27:47PM -0800, Andrey Smirnov wrote:
> Invert the logic in imx8mq_cpu_revision() and convert it to use early
> return. This is done in perparation for more corner case logic added
> in the following commits. No functional change intended.
>
> Signed-off-by: Andrey Smirno
On Tue, Feb 12, 2019 at 04:10:40PM +0100, Marco Felsch wrote:
> Sometimes it can be necessary to rename a node, e.g. a upstream node was
> renamed and the whole board logic depends on the old naming scheme.
>
> Signed-off-by: Marco Felsch
> ---
> Note:
> In my v1 this patch was required for the f
On Tue, Feb 12, 2019 at 03:51:10PM +0100, Tomaz Solc wrote:
> "model" pointer is NULL if current board revision isn't in the list of known
> boards.
> ---
> arch/arm/boards/raspberry-pi/rpi-common.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
Applied, thanks
Sascha
>
> diff --g
On Tue, Feb 12, 2019 at 1:42 AM Lucas Stach wrote:
>
> Am Montag, den 11.02.2019, 18:36 -0800 schrieb Andrey Smirnov:
> > Port code found in cdn_dp_load_firmware() in Linux kernel to check if
> > HDMI firmware is running and, if so, report its version.
> >
> > > Signed-off-by: Andrey Smirnov
> >
Hi,
Am 12.02.19 um 15:22 schrieb Yazdani, Reyhaneh:
> Hello everyone,
>
> I am using imx8m-evk board. To boot a cortex-m4 in the system, in u-boot,
> there
> is a bootaux command, which runs the m4-image and boot cortex-m4.
>
> Is there any command available in Barebox to boot m4? Totally, what
Hi Teresa.
> If there is any need for a such a generic driver right now. I will
> rename it.
I see no need for one for now.
So follow Sasha's recommendation and keep it TI specific
is the best choice.
Sam
___
barebox mailing list
barebox@lists
Hi
On 12. 02. 19 12:22, Roland Hieber wrote:
If I remember correctly, there was a patch changing that behaviour... Ah
yes, commit abc0447440d6 [0]:
ARM: dts: bcm2835-rpi: re-enable booting from SD card
Kernel commit a19adf8d86e822eba502486524127595372c85f6 [0] changed the
RPi1 d
Since kernel 4.16 the memory nodes got a @ suffix so the fixup
won't work correctly anymore, because instead of adapting the extisting
one the fixup creates a new node and keeps the old (maybe incorrect)
node.
To be compatible with the old and new layout delete the found memory
node and create a n
Sometimes it can be necessary to rename a node, e.g. a upstream node was
renamed and the whole board logic depends on the old naming scheme.
Signed-off-by: Marco Felsch
---
Note:
In my v1 this patch was required for the followed, but now it isn't. So
feel free to add or drop it. IMHO it can be a
"model" pointer is NULL if current board revision isn't in the list of known
boards.
---
arch/arm/boards/raspberry-pi/rpi-common.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boards/raspberry-pi/rpi-common.c
b/arch/arm/boards/raspberry-pi/rpi-common.c
index 65
On Tue, 12 Feb 2019 12:57:26 +
Kai Che wrote:
Hi!
> does barebox support any kind of Arm-Cortex M0 Boards? e.g. STM32F0 or
> similiar?
At the moment barebox does not support ARM-Cortex.
I suppose there is no problem to port barebox to STM32.
However STM32F0 definitely is not a preferred ST
Hello everyone,
I am using imx8m-evk board. To boot a cortex-m4 in the system, in u-boot, there
is a bootaux command, which runs the m4-image and boot cortex-m4.
Is there any command available in Barebox to boot m4? Totally, what is available
in Barebox regarding cortex-m4?
Thanks in advance,
B
On 12.02.19 14:34, Roland Hieber wrote:
On Tue, Feb 12, 2019 at 12:57:26PM +, Kai Che wrote:
Hi everyone,
does barebox support any kind of Arm-Cortex M0 Boards? e.g. STM32F0 or similiar?
I couldn't find any mention of such a board in the board support section of the
documentation.
I
On Tue, Feb 12, 2019 at 12:57:26PM +, Kai Che wrote:
> Hi everyone,
>
> does barebox support any kind of Arm-Cortex M0 Boards? e.g. STM32F0 or
> similiar?
>
> I couldn't find any mention of such a board in the board support section of
> the documentation.
>
> I hope I didn't overlook some
Hello Sascha,
Am Dienstag, den 12.02.2019, 09:10 +0100 schrieb Sascha Hauer:
> On Mon, Feb 11, 2019 at 04:16:34PM +0100, Teresa Remmet wrote:
> > Adds minimal support for the sysc interconnect target module found
> > on many TI SoCs. With this device tree includes have been
> > rearagned.
> > We n
Hello Sascha and Sam,
Am Dienstag, den 12.02.2019, 09:09 +0100 schrieb Sascha Hauer:
> Hi Sam,
>
> On Mon, Feb 11, 2019 at 04:41:38PM +0100, Sam Ravnborg wrote:
> > Hi Teresa.
> >
> > On Mon, Feb 11, 2019 at 04:16:34PM +0100, Teresa Remmet wrote:
> > > Adds minimal support for the sysc interco
Hello Andrey,
Am Montag, den 11.02.2019, 18:57 -0800 schrieb Andrey Smirnov:
> On Mon, Feb 11, 2019 at 7:16 AM Teresa Remmet
> wrote:
> >
> > Adds minimal support for the sysc interconnect target module found
> > on many TI SoCs. With this device tree includes have been
> > rearagned.
> > We nee
Hi everyone,
does barebox support any kind of Arm-Cortex M0 Boards? e.g. STM32F0 or similiar?
I couldn't find any mention of such a board in the board support section of the
documentation.
I hope I didn't overlook something.
Thanks and best Regards,
Kai Che
Hi Tomaž,
On Mon, Feb 11, 2019 at 04:09:09PM +0100, Tomaž Šolc wrote:
> Dear all,
>
> I've been trying to set up Barebox on a Raspberry Pi Compute Module 3. After
> some small fixes (see below) I've got 2019.01.0 to boot to a command line on
> the serial port. However I can't get access to the MM
Am Montag, den 11.02.2019, 18:36 -0800 schrieb Andrey Smirnov:
> Port code found in cdn_dp_load_firmware() in Linux kernel to check if
> HDMI firmware is running and, if so, report its version.
>
> > Signed-off-by: Andrey Smirnov
> ---
> arch/arm/mach-imx/imx8mq.c | 37 ++
On 19-02-12 09:56, Sascha Hauer wrote:
> On Tue, Feb 12, 2019 at 09:45:25AM +0100, Marco Felsch wrote:
> > Hi Sascha,
> >
> > On 19-02-12 09:03, Sascha Hauer wrote:
> > > On Mon, Feb 11, 2019 at 05:20:13PM +0100, Marco Felsch wrote:
> > > > Since kernel 4.16 the memory nodes got a @ suffix so the
On Tue, Feb 12, 2019 at 09:45:25AM +0100, Marco Felsch wrote:
> Hi Sascha,
>
> On 19-02-12 09:03, Sascha Hauer wrote:
> > On Mon, Feb 11, 2019 at 05:20:13PM +0100, Marco Felsch wrote:
> > > Since kernel 4.16 the memory nodes got a @ suffix so the fixup
> > > won't work correctly anymore, because i
Hi Sascha,
On 19-02-12 08:32, Sascha Hauer wrote:
> Hi Marco,
>
> On Mon, Feb 11, 2019 at 05:20:12PM +0100, Marco Felsch wrote:
> > Sometimes it can be necessary to rename a node, e.g. to override/create
> > a node which gets renamed upstream.
> >
> > Signed-off-by: Marco Felsch
> > ---
> > dr
Hi Sascha,
On 19-02-12 09:03, Sascha Hauer wrote:
> On Mon, Feb 11, 2019 at 05:20:13PM +0100, Marco Felsch wrote:
> > Since kernel 4.16 the memory nodes got a @ suffix so the fixup
> > won't work correctly anymore, because instead of adapting the extisting
> > one it creates a new node.
> >
> > T
On Wed, Feb 06, 2019 at 05:02:37PM -0800, Andrey Smirnov wrote:
> > /*
> > * The IP has errata ERR004536
> > @@ -612,6 +614,10 @@ static int esdhc_init(struct mci_host *mci, struct
> > device_d *dev)
> > /* RSTA doesn't reset MMC_BOOT register, so manually reset it */
> > esdhc_
Hi Thomas,
On Mon, Feb 11, 2019 at 02:10:40PM +, Thomas Hämmerle wrote:
> From: Thomas Haemmerle
>
> Port Xilinx Zynq MPSoC Firmware layer driver from linux.
>
> Signed-off-by: Thomas Haemmerle
> ---
> arch/arm/Kconfig | 1 +
> arch/arm/mach-zynqmp/Make
On Mon, Feb 11, 2019 at 04:16:34PM +0100, Teresa Remmet wrote:
> Adds minimal support for the sysc interconnect target module found
> on many TI SoCs. With this device tree includes have been rearagned.
> We need the driver to probe the child devices of the bus.
>
> Signed-off-by: Teresa Remmet
>
Hi Sam,
On Mon, Feb 11, 2019 at 04:41:38PM +0100, Sam Ravnborg wrote:
> Hi Teresa.
>
> On Mon, Feb 11, 2019 at 04:16:34PM +0100, Teresa Remmet wrote:
> > Adds minimal support for the sysc interconnect target module found
> > on many TI SoCs. With this device tree includes have been rearagned.
> s
On Mon, Feb 11, 2019 at 05:20:13PM +0100, Marco Felsch wrote:
> Since kernel 4.16 the memory nodes got a @ suffix so the fixup
> won't work correctly anymore, because instead of adapting the extisting
> one it creates a new node.
>
> To be compatible with the old and new layout delete the found me
35 matches
Mail list logo
