144 Followers
88 Following
650 Posts
Long time Linux engineer and developer, U-Boot custodian, OpenEmbedded developer. For non-technical things @trini
pronounshe/him
githubhttps://github.com/trini/
Gravatarhttps://gravatar.com/tomrini

has anyone had any success success installing an alternative os on a smart tv? it's basically a computer, albeit a shitty one, but i can't find anything anywhere online about it. i can't tell if my ability to web search is declining, or if web search in general is in the shitter

boosts/quotes appreciated

Today is one of those days where I have 20-odd commit messages to write where the explanation all starts off the same (found this problem by ...). At least I can keep dropping in the first few lines of the previous commit.
Working out problems from randconfig is confusing sometimes. I'll have a symbol that says it depends on !X. The generated .config has X=y. Since the symbol in question has select'd Y that depends on !X we get an unmet dependency elsewhere because we have "select Z if Y".
Sure, I could make that be "select Z if !X" but that feels wrong.
Since a year we got some contributions for converting Devicetree bindings from TXT to DT schema as part of some sort mentorship programs (e.g. GSoC). This is great although leads to some misunderstandings in that work, considering mentorships did not ask DT maintainers about some sort of guidance. To clarify:

1. Please convert bindings which have active DTS users. First choose bindings with DTS built by arm64 defconfig, then next choice by arm multi_v7 defconfig. Then any other ARM or different architecture DTS.

2. Be sure dt_binding_check (including yamllint) and checkpatch pass without any warnings. See writing-schema.rst document.

3. Be sure that all DTS files using this binding pass dtbs_check validation. If this means binding needs to be adapted during conversion, mention briefly in commit message changes done comparing to pure TXT->DT schema conversion. Sometimes DTS has to be fixed. Sometimes both - DTS and binding - must be changed, because actual ABI (Linux drivers) is different.

4. Do not send conversions of TXT bindings in staging, because these need to follow standard review process. Bindings in staging are not considered accepted/reviewed DT ABI.

5. Don't ever send output of LLM microslop tools. It's pointless and brings no benefits to the community. Rob already converted all TXT bindings with LLM, so why you doing this again would be beneficial to anyone?

6. Read also Rob's expectations and hints:
https://lore.kernel.org/linux-devicetree/CAL_JsqJp133hGSkja9tabtsE9D7MSA9JErVkmkcy91piHMgfwg@mail.gmail.com/

This is an updated guideline from 2025 https://social.kernel.org/notice/Ai9hYRUKo8suzX3zNY .
Re: DT schema bindings conversion mentorships (was Re: [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema) - Rob Herring

And I half started to defend having autocomplete type stuff for big class abstraction template blah blah 'fun', but then stopped. Yes, that's annoying to deal with, but one of the first lessons I learned was that you don't just silence a warning by doing a cast, you understand what the warning means and then fix it. So yes, you need to think through what the right thing to call (and what to pass), even more so when it's tricky.

RE: https://cosocial.ca/@mhoye/116222876858737682

This of course applies to "AI coding" too.

Today, I met with Colorado Senator Matt Ball, co-author of Colorado OS Age Attestation Bill SB26-051.

Sen. Ball suggested excluding open source software from the bill. This appears to be a real possibility.

Amendments are expected for the CA age attestation bill. It's my hope we can move fast enough to influence excluding open source in the CA bill amendments.

No illusions, it's an uphill battle, but we have an open door to advocate for the open source community.

If someone from Linux Foundation wants a long list of feedback and criticism on this (remember OpenSSF scorecard?) you know where to find me. This is just too much to even rant about in a blog post.
A GitHub Issue Title Compromised 4,000 Developer Machines

A prompt injection in a GitHub issue triggered a chain reaction that ended with 4,000 developers getting OpenClaw installed without consent. The attack composes well-understood vulnerabilities into something new: one AI tool bootstrapping another.