Re: [PATCH 00/19] [RESEND] Remove STiH415 and STiH416 SoC platform support
From: Peter Griffin <hidden>
Date: 2016-09-19 08:57:05
Also in:
linux-arm-kernel, lkml
Hi Arnd, On Thu, 15 Sep 2016, Arnd Bergmann wrote:
On Thursday, September 15, 2016 8:01:39 AM CEST Peter Griffin wrote:quoted
STiH415 I'm sure never shipped. I'm reasonably sure STiH416 didn't either. These SoCs were considered legacy even when I was at ST ~3 years ago. Also remember these are STB SoC's, so JTAG fuses are blown in production boxes, and also full security is enabled. This means the primary bootloader will only boot a signed kernel. So if a end user did happen to have a box they would be unable to upgrade their kernel. From the landing team perspective they were interesting in that they shared many IPs with the STiH407 family on which future chipsets were based, and were available to us when that silicon was harder to get hold of. So we used it as a vehicle for upstreaming so that upstream support was already quite good when STiH407 silicon did land on our desk.Ok, makes sense. I did stumble over one machine basedon STiH412 the other day [1], but there probably isn't much shared with that one. Since this a NAS server rather than an STB box, it's probably less locked-down and potentially a target for OpenWRT or similar.
I just double checked with ST and STiH412 is a STiH407 family based SoC so support still exists for this upstream. No idea what if any security is enabled on this product though. Most probably the A/V stack on it will be SDK2, although native upstream multimedia drivers for this chipset are looking pretty good now. Peter.
[1] http://www.heise.de/preisvergleich/synology-diskstation-ds216play-16tb-a1400885.html
-- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html