Hi Sascha,
On Wed, 2021-11-17 at 08:03 +0100, Sascha Hauer wrote:
> On Mon, Nov 15, 2021 at 02:02:05PM +0100, Andrej Picej wrote:
> > Create PHYTEC specific i.MX6 SoM config fragment, which is intended to
> > be merged with the default imx_v7_defconfig. This way, one can clearly
> > outline the di
Wed, 2021-04-14 at 16:36 +0200, s...@pengutronix.de wrote:
> 0.08
>
> Hi Stefan,
>
> On Wed, Apr 14, 2021 at 01:18:39PM +, Stefan Riedmüller wrote:
> > Hi Sascha,
> >
> > just wanted to let you know that the kernel patch has been accepted and is
> >
Hi Sascha,
just wanted to let you know that the kernel patch has been accepted and is
included in the pull request for 5.13.
https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/log/?h=nand/for-5.13
Regards,
Stefan
On Mon, 2021-03-29 at 07:20 +, Stefan Riedmüller wrote:
>
5PM +0000, Stefan Riedmüller wrote:
> > Hi Sascha,
> >
> > On Wed, 2021-03-17 at 10:41 +0100, Sascha Hauer wrote:
> > > Hi Stefan,
> > >
> > > On Tue, Mar 16, 2021 at 01:36:26PM +0100, Stefan Riedmueller wrote:
> > > > The blocks containing the
Hi Sascha,
On Wed, 2021-03-17 at 10:41 +0100, Sascha Hauer wrote:
> Hi Stefan,
>
> On Tue, Mar 16, 2021 at 01:36:26PM +0100, Stefan Riedmueller wrote:
> > The blocks containing the bad block table can become bad as well. So
> > make sure to skip any blocks that are marked bad when searching for t
Hi Andrej,
I like this idea. It is nice to have a working example of DRAM size detection
available aside from the DCD table setups.
Please see my notes below.
On Wed, 2021-01-20 at 13:52 +0100, Andrej Picej wrote:
> Add support for automatic DRAM size detection on phytec phycard imx6q
> machines
Hi Sascha,
let me answer on behalf of Robert.
On 01.07.20 07:58, Sascha Hauer wrote:
Hi Robert,
On Tue, Jun 30, 2020 at 04:20:17PM +0200, Robert Karszniewicz wrote:
The problem is that we want to be able to have the rootfs and kernel on
separate partitions.
Why do you want to have that? It'
Hi Sascha,
On 29.04.20 13:29, Sascha Hauer wrote:
The phyCORE i.MX6 has two memory nodes in the device tree. /memory comes
Here and in the subject line you mention the phyCORE-i.MX 6 but it is
actually the phyFLEX which you change.
Besides that,
Reviewed-by: Stefan Riedmueller
from the b
ctoproject.org/docs/latest/kernel-dev/kernel-dev.html#applying-patches
Best regards,
Stefan
Thank you and best regards
hu
-Original Message-
From: Stefan Riedmüller
Sent: Wednesday, 26 February 2020 14:24
To: Hans-Ulrich Schlieben
Cc: Enrico Jörns ; yo...@lists.yoctoproject.o
-Original Message-
From: Stefan Riedmüller
Sent: Tuesday, 25 February 2020 16:16
To: Hans-Ulrich Schlieben
Cc: Enrico Jörns ; yo...@lists.yoctoproject.org;
barebox@lists.infradead.org; r...@pengutronix.de
Subject: Re: [RAUC] Private: Re: [yocto] #yocto update the kernel with a rau
Hi Hans-Ulrich,
On 24.02.20 13:12, Hans-Ulrich Schlieben wrote:
Hi Enrico,
the boot log looks like this:
barebox 2017.12.0 #1 Tue Feb 18 09:49:36 UTC 2020
Board: Phytec phyCORE-i.MX6 Quad with NAND
detected i.MX6 Quad revision 1.5
i.MX6 unique ID: ee803c540f2359d4
mdio_bus: miibus0: probed
Hi Sascha,
On 10.12.19 11:45, Sascha Hauer wrote:
On Tue, Dec 10, 2019 at 09:15:52AM +0100, Stefan Riedmüller wrote:
Hi Sascha,
On 10.12.19 09:05, Sascha Hauer wrote:
On Tue, Dec 10, 2019 at 08:50:41AM +0100, Stefan Riedmüller wrote:
Hi Sascha,
On 09.12.19 16:37, Sascha Hauer wrote:
On
Hi Sascha,
On 10.12.19 09:05, Sascha Hauer wrote:
On Tue, Dec 10, 2019 at 08:50:41AM +0100, Stefan Riedmüller wrote:
Hi Sascha,
On 09.12.19 16:37, Sascha Hauer wrote:
On Mon, Dec 09, 2019 at 01:31:40PM +0100, Stefan Riedmueller wrote:
Change environment device-path from using a separate
Hi Sascha,
On 09.12.19 16:37, Sascha Hauer wrote:
On Mon, Dec 09, 2019 at 01:31:40PM +0100, Stefan Riedmueller wrote:
Change environment device-path from using a separate label to
referencing a device plus partname.
Why? The way it was is fine.
Just to be consistent with phyCORE and phyFLEX
Hi Roland,
On 09.12.19 11:20, Roland Hieber wrote:
On Mon, Dec 09, 2019 at 10:01:43AM +0100, Stefan Riedmueller wrote:
Make use of SPDX license identifiers and update copyright notices and
model descriptions of the phyCARD-i.MX 6 SOM.
Signed-off-by: Stefan Riedmueller
---
arch/arm/dts/imx6q
Hi,
On 05.12.19 09:37, Ahmad Fatoum wrote:
Hello,
On 12/5/19 9:07 AM, Sascha Hauer wrote:
On Tue, Dec 03, 2019 at 02:48:41PM +0100, Stefan Riedmueller wrote:
There is no driver for the eMMC's vmmc-supply regulator in the barebox.
Use a dummy regulator instead by simply deleting the vmmc-suppl
Hi Marco,
On 02.10.19 15:09, Marco Felsch wrote:
Currently the fixup code assumes that only one i2c bus is active. If we
reuse the board code for other boards this isn't always true. Fix that
by using of_find_i2c_adapter_by_node() to address both cases.
Fixes: b6bebb7aca ("ARM: i.MX: phytec-som
Hi Marco,
On 02.10.19 10:34, Marco Felsch wrote:
Hi Stefan,
On 19-10-02 09:34, Stefan Riedmüller wrote:
Hi Marco, Sascha,
On 02.10.19 09:23, Sascha Hauer wrote:
Marco,
On Wed, Oct 02, 2019 at 09:20:43AM +0200, Sascha Hauer wrote:
+Cc Christian Hemp who is the author of b6bebb7aca
On Wed
Hi Marco, Sascha,
On 02.10.19 09:23, Sascha Hauer wrote:
Marco,
On Wed, Oct 02, 2019 at 09:20:43AM +0200, Sascha Hauer wrote:
+Cc Christian Hemp who is the author of b6bebb7aca
On Wed, Sep 11, 2019 at 04:53:28PM +0200, Marco Felsch wrote:
The PMIC is connected to i2c3 and not i2c1.
Fixes: b6
Hi Marco,
On 23.09.19 13:40, Marco Felsch wrote:
Hi Stefan,
On 19-09-23 10:31, Stefan Riedmüller wrote:
Hi Marco,
Usually we would like to keep the features supported in the barebox to a
minimum set that is mostly supported by the SOM itself and thus is mostly
base board independent.
Yes
Hi Marco,
Usually we would like to keep the features supported in the barebox to a
minimum set that is mostly supported by the SOM itself and thus is mostly
base board independent.
My suggestion would be to just use the upstream phycore devicetree. Would
that be ok with you? Of course that m
Hi Sascha,
On 18.07.19 14:19, Sascha Hauer wrote:
On Thu, Jul 18, 2019 at 10:24:52AM +0200, Stefan Riedmüller wrote:
Hi Sascha,
do you guys have an idea or proposal how to disable the wear-leveling
properly? I will gladly take another look at it and it would be nice to get
your input as I
Hi Sascha,
do you guys have an idea or proposal how to disable the wear-leveling
properly? I will gladly take another look at it and it would be nice to get
your input as I only started to dive into ubi.
Regards,
Stefan
On 11.07.19 13:04, Stefan Riedmüller wrote:
Hi Sascha,
On 11.07.19 09
Hi Sascha,
On 11.07.19 09:01, Sascha Hauer wrote:
On Wed, Jul 10, 2019 at 01:27:30PM +0200, Stefan Riedmueller wrote:
Due to the recursive ubi_thread implementation in the barebox, a large
amount of wear-leveling can lead to a stack overflow.
This was observed during extensive ubi stress tests
Hi Sascha,
Hi Stefan,
On Wed, Jul 10, 2019 at 01:17:28PM +0200, Stefan Riedmueller wrote:
PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_nand_256mb, imx6dl_phytec_phycore_som_nand, SZ_256M, true);
+PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_lc_nand_256mb,
imx6dl_phytec_phycore_som_lc_nan
Hi Roland,
On 09.07.19 10:53, Roland Hieber wrote:
Cc: barebox@lists.infradead.org
Bcc:
Subject: Re: [PATCH 2/8] ARM: dts: imx6qdl: phycore: Add state framework
Reply-To:
In-Reply-To: <1562071065-367410-2-git-send-email-s.riedmuel...@phytec.de>
X-Sent-From: Pengutronix Hildesheim
X-URL: http://
Hi Uwe,
On 19.02.19 14:03, Uwe Kleine-König wrote:
Both Linux and barebox support this new scheme and it's the actually
the recommended one.
Signed-off-by: Uwe Kleine-König
---
Hello,
On Tue, Feb 19, 2019 at 11:54:07AM +0100, Stefan Riedmüller wrote:
On 19.02.19 11:28, Uwe Kleine-
Hi Uwe,
On 19.02.19 11:28, Uwe Kleine-König wrote:
Both Linux and barebox support this new scheme and it's the actually
the recommended one.
Signed-off-by: Uwe Kleine-König
---
On Tue, Feb 19, 2019 at 11:08:56AM +0100, Stefan Riedmüller wrote:
thanks for the patch.
In arch/arm/dts/im
Hi Uwe,
thanks for the patch.
In arch/arm/dts/imx6qdl-phytec-pfla02.dtsi and
arch/arm/dts/imx6qdl-phytec-phycore-som.dtsi are additional gpmi partitions. Did
you leave them out for a reason. I think they can be matched to the new scheme too.
Stefan
On 18.02.19 22:08, Uwe Kleine-König wrote:
Hi Uwe,
On 08.01.19 11:24, Uwe Kleine-König wrote:
barebox doesn't honor that property which yields to inconsitencies
between Linux and barebox after for example filling an UBI with a file
system with barebox and then trying to mount that from Linux.
Note this is an interruptive change as it re
Hi Sascha,
On 02.05.2018 12:49, Sascha Hauer wrote:
Hi Stefan,
On Fri, Apr 20, 2018 at 01:01:01PM +0200, Stefan Riedmueller wrote:
Display timings can now be set with simple-panel method which selects
the required timings by the compatible of the simple panel devicetree
node.
This patch adds
Sascha Hauer wrote on 16/05/2017 07:47:39:
> Von: Sascha Hauer
> An: Stefan Riedmueller
> Kopie: barebox@lists.infradead.org
> Datum: 16/05/2017 07:47
> Betreff: Re: [PATCH 2/3] ARM: i.MX6ul: Add Clock support for i.MX6ull
>
> On Thu, May 11, 2017 at 11:09:27AM +0200, Stefan Riedmueller wrote:
board and the Fresscale SabreSD board with i.MX6 Quad and found the same
behavior. I could not find an explanation yet for this so I hope you can help
me.
Mit freundlichen Grüßen,
Best regards,
Stefan Riedmüller
___
barebox mailing list
barebox@lists.
33 matches
Mail list logo
