I’ve been part of unrelated projects that involved SoC part selection and negotiation with… large chip vendors. They always pull this shit, although this case seems particularly annoying.
They’ll tie their SoC to some other random part, invent some proprietary protocol to brand it with, and then get upset when you say you don’t want the extras. I’m sure there are some technical advantages to their solutions, but they’re just as often bloated and not appropriate for the design.
We all know that chip vendors don’t exactly write the best code, that’s expected. But inviting even more proprietary drivers or even blobs(!), for a solution that sales says will just work and solve all our problems, is usually a risky move. Heavily modifying or reimplementing boot code and drivers is an inevitability, and no engineer who’s been through that is going to invite more blobs into their codebase if they can avoid it.
They’ll tie their SoC to some other random part, invent some proprietary protocol to brand it with, and then get upset when you say you don’t want the extras. I’m sure there are some technical advantages to their solutions, but they’re just as often bloated and not appropriate for the design.
We all know that chip vendors don’t exactly write the best code, that’s expected. But inviting even more proprietary drivers or even blobs(!), for a solution that sales says will just work and solve all our problems, is usually a risky move. Heavily modifying or reimplementing boot code and drivers is an inevitability, and no engineer who’s been through that is going to invite more blobs into their codebase if they can avoid it.