OpenWrt One / project update

[John Crispin]

Hi

> Thank you, I'm reading through now.
you missed the part where you thanked MTK for being ultra cool and 
publishing/disclosing ~2000 PDF pages ;) ... just joking
> I didn't grok all the GPIO pin sharing, there are a lot of choices there
> which I think you've already made when you listed the high-level specs.
that  was a real pain. @pepe2k, thanks for the 3 long days you spent 
with me to figure this out (see attachment)
>
> Will we be able to support the:
>       "the hardware-based NAT engine with QoS embedded in MT7981B"
>       Any IPv6 support down there? Yes, for various tunnel protocols even.
>       Is it the "NEON"?
yes
> I see 64 Tx queues for wired ethernet, but I imagine Dave Taht will want to
> know if there are per-host queues for the wireless.  Hmm. Well, it looks like
> there are at least 4, but I could have mis-understood.

@dangole, please answer that one


> In the first PDF, there is mention of:
>     Security Support 2 * 256-bit multi-key on OTP eFuse
>     Support 64 version OTP eFuse for anti-rollback

the e-fuse stuff requires a license and is considered evil. only know of 
starlink dish-2 based upon mt7921 using it.

we plan to add SW OP-TEE to the ATF2 BL2 soonish


https://trustedfirmware-a.readthedocs.io/en/latest/components/spd/index.html 


https://trustedfirmware-a.readthedocs.io/en/latest/components/spd/optee-dispatcher.html 


> which is often the key to getting IDevID deployed, but I didn't find further
> mention of that in the three datasheets.
requires op-tee ...
>
> I found: 11008014 GLOBAL_SEC_EN, but I think it has to do with locking down
> the timers, or some I2C thing.

no clue, would need to look this up

     John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot 2024-04-12 at 20.03.13.png
Type: image/png
Size: 421306 bytes
Desc: not available
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20240412/24fd1696/attachment-0001.png>