The GPLv3 model, i.e the need to release all your source, isn't compatible with the mindset of embedded product manufacturers, which are highly afraid of copying.
Until you solve this mindset problem(god knows how), GPLv3 isn't a workable solution.
Oh I'm well aware. Version control with something other than zip files isn't compatible with the mindset of embedded developers :P
Right now I've got a dishwasher that pukes on every second cycle. I know it's a software problem, yet their solution is to replace the whole controller board, taking months to diagnose and order a new one. Luckily I don't own it, so I'm only paying for this circus with my time.
The quip about GPL3 was meant as one possible example, although it does line up incentives pretty well. Users should be wary of devices that have worked quite well with mechanical timers/thermostats/etc being replaced with an essentially infinitely complex microcontroller, and the solution for taming that complexity to be the manufacturer retaining indefinite control.
Sure there's a huge problem with the quality and the reliability of appliances.Basically everything's shit, or there's are high end products which are a bad deal, economically.
But solving that is much, much bigger than just open-sourcing embedded code.
Also
>>Oh I'm well aware. Version control with something other than zip files isn't compatible with the mindset of embedded developers :P
That's one thing the mbed default IDE(web ide) does well - it gets people to use version control.
Until you solve this mindset problem(god knows how), GPLv3 isn't a workable solution.