17:13 <javierm> NishanthMenon: hi, is there a place where I can get info about the taxonomy of TI SoCs? I see Sitara, Keystone and Jacinto used interchangeably in docs so I'm confused about which one is the umbrella for the others

17:13 <javierm> NishanthMenon: the best I could find is https://www.ti.com/microcontrollers-mcus-processors/arm-based-processors/overview.html

18:13 <NishanthMenon> javierm: nothing that is public unfortunately. there has been cross polination of devices from one brand to another. :( - but the site you were looking for is the public information unfortunately.

18:14 <javierm> NishanthMenon: Ok, no worries! Just in case I was missing something

18:14 <NishanthMenon> the other place you could find this info is when you open the TRM.. the title will give a list of "branded part numbers" :( - but personally I get confused when mktg changes numbers ..

18:15 <javierm> it seems Keystone3 is some sort of technology generation, Jacinto a variant of Sitara for automotive/industrial/edge/AI

18:16 <javierm> because AM33xx are also Sitara but not Jacinto :)

18:17 <NishanthMenon> kind of correct. K3 - we have been asked not to use keystone brand ;) .. has two pedigree of sub archs - sitara AM62x... and Jacinto -> some products are rebranded to sitara.. example: Jacinto automotive j784s4 - tda4vh - is rebranded as sitara am69 for industrial applications.. j721s2 is also rebranded as am68. at least these are public examples.. am65 is a weird one.. it has a jacinto architecture, but is a sitara

18:17 <NishanthMenon> product..

18:18 <NishanthMenon> i am sure this all clear as mud :( - sorry for the same.. we engineers tried to get some sanity in the product nomenclature.. but we were overriden..

18:19 <javierm> NishanthMenon: thanks for the comments. I was hoping that there was some sort of unified document where I could get the product family tree but I guess that would be too easy for mkt folks :)

18:19 <javierm> anyways, if even you get confused then I guess that is futile for me to wrap my head around the naming

18:19 <NishanthMenon> such a document does exist.. unfortunately it is internal :(

18:19 <javierm> NishanthMenon: ah, Ok. No worries

18:19 <javierm> NishanthMenon: thanks for the examples

18:20 <NishanthMenon> np. dts is usually a sure direction.. we have done reuse where applicable to model real hardware derivatives.. but it does'nt cover all the potential paper spins.. :(

18:21 <javierm> NishanthMenon: yes, I noticed that doing a grep for the .dtsi is what gives me the best hint

18:21 <javierm> *the included .dtsi

18:21 <NishanthMenon> yup :( that was our way of getting the message out :(

18:21 <javierm> awesome

18:22 <NishanthMenon> gotta run and get some food before cafeteria closes.. ttyl

18:22 <javierm> NishanthMenon: enjoy!

18:22 <javierm> and thanks again