[meta-freescale] [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only
rfindley at usa.net
Sat Nov 8 13:54:35 PST 2014
From Alexander Holler
> But there is absolutely no reason to include this ONE TIME FUNCTIONALITY
> into any kernel meant for the public, especially as it is very
The problem isn't that someone can burn fuses in a commercial product.
Rather, the problem is a designer who ships a product with unburned fuses. If
a designer is unaware of the fuses, and ships them unburned (unless he has
good reason), then he shouldn't be selling commercial products. You can't
design an imx product without knowing about the fuses. They are fundamental
to the design process.
I agree that a config option might be useful, and maybe even disabled by
default. But for manufacturing purposes, having the ability to burn the fuses
during production testing with production software is a good thing. And once
they are burned, the proposed nightmare scenarios no longer exist, and it
doesn't matter whether the kernel has the option enabled.
> And for sure not without any content veryfication and some
> other means to make sure the value one wants to put ONCE into that ONE
> TIME MEMORY isn't wrong.
> That's why I just refuse to change my patch in order to add write
> functionality. I don't want to do (imho) foolish things just because
> someone else tells me to do them. I'm no Lemming.
> At least not without adequate compensations. ;)
> Alexander Holler
More information about the meta-freescale