On 21-04-22 13:08, Lucas Stach wrote:
> The i.MX reset reason is not really helpful on its own, as it needs
> to be augmented with other information like the watchdog state to get
> the real system reset reason. As it stands this log is more confusing
> than answering any questions a user might
On 4/15/21 5:31 PM, Lucas Stach wrote:
> Am Donnerstag, dem 15.04.2021 um 17:12 +0200 schrieb Sascha Hauer:
>> On Thu, Apr 15, 2021 at 04:59:30PM +0200, Lucas Stach wrote:
>>> Am Donnerstag, dem 15.04.2021 um 16:03 +0200 schrieb Sascha Hauer:
The SabreSD comes with different SoC variants.
Hi,
I'm in the process of fixing up imx-kobs to support
- boot configuration dumps
- boot stream extracts/updates
on iMX6QDL using the GPMI-NAND interface, as provided by some more
"recent" kernels.
I updated barebox on the NAND flash storage using another instance of
barebox. Now it turns out
The i.MX reset reason is not really helpful on its own, as it needs
to be augmented with other information like the watchdog state to get
the real system reset reason. As it stands this log is more confusing
than answering any questions a user might have.
Demote the log to debug level to stop
Hi Oleksij,
Thank you for your inputs.
I will modify the patch as per your suggestions and share it again.
The issue is I already have Qemu virbr0 bridge, so it is very easy to
setup but in case of no already configured bridge available then I am
facing some issues to setup bridge manually, I
