Hi Francesco, > On Wed, Sep 10, 2025 at 02:28:21PM +0200, Łukasz Majewski wrote: > > Hi Francesco, > > > > > Hello, > > > > > > On Tue, Sep 09, 2025 at 07:08:34PM +0300, Svyatoslav Ryhel wrote: > > > > > > > вт, 9 вер. 2025 р. о 18:47 Tom Rini <tr...@konsulko.com> пише: > > > > > > > > > > > > > ... > > > > > It's a devkit where I'm pretty sure the watchdog exists, so > > > > > we can enable it there and be done. Just because it doesn't > > > > > use it today doesn't mean it can't use it in the future if we > > > > > enable it, the "use watchdog to make sure A/B system > > > > > configures are stable" is a common use case. > > > ... > > > > Not sure if changes into colibri_t30_defconfig are needed, but > > > > if Francesco would like them, then ok. > > > > > > I would prefer the defconfig not to be touched. > > > > > > > I'm still puzzled why this cannot be changed? > > In general I like the idea of the watchdog driver to be enabled by > default on the defconfig. This is the sane thing to do in a lot of > situation. > > Enabling it however complicates some use cases, attaching a debugger, > or maybe we have a situation in which the OS is currently not keeping > the WD alive, therefore you would be potentially in trouble if you > would update the bootloader. > > I am not familiar with the general colibri t30 user base to be enough > confident this change will be fine, so this is the reason I am a > little hesitant to change for such an old product. > > With that said, I am ok to change it, no strong arguments against. >
Ok, so I will prepare patch modifying colibri_t30_defconfig after the WDT supporting patches are accepted. > Francesco > > -- Best regards, Lukasz Majewski -- Nabla Software Engineering GmbH HRB 40522 Augsburg Phone: +49 821 45592596 E-Mail: off...@nabladev.com Geschftsfhrer : Stefano Babic
