Hacker News Reader

Comment by kotaKat | Hacker News Reader

But bricking retroactively in the field is a bad move, and sends even more anger and RMA requests back towards parties.

https://github.com/therealdreg/ftdibrick

Pepperidge Farm remembers the FTDI driver bricking.

View on HN

gateway 3ds tried to brick 3ds-es of users of cloned cards, bricked whole swaths of actual users instead

https://www.eurogamer.net/3ds-flashcard-includes-secret-kill...

It's not bricked retroactively from what I've read.

https://github.com/raspberrypi/rpi-eeprom/issues/761

If someone gets updated in the wild (like this person did without realizing they had a counterfeit board), they'll fail to boot.

Consider that that happened a year ago and this submission may be about the fix.

The "fix" in the thread is just not updating ever again.

There is no fix that can be suggested in that thread. Pi LTD doesn't have the modified RAM Pis to test their firmware against nor should they be required to support modified hardware.

The fix is turning the detection of the modified ram from a boot failure into a warning and log output, then tell users asking for support that they don't have support for Pis that were modified by third parties.

Instead we get restrictions on all users because some users buy stuff from random marketplaces online?

I don't know why you're suggesting the fix is that they offer support for 3rd modded RAM.

>I don't know why you're suggesting the fix is that they offer support for 3rd modded RAM.

I'm not.

Reply on news.ycombinator.com