Stefan,
AMD internal documents also suggest A45/A50M/A55E FCH (Hudson-1) use device ID 438D. Not sure if it's wrong since I don't have a test system.
According to AMD document A55/A60M/A68/A68M/A70M/A75/A85X use device ID 780E. There's also this A77E FCH (codename Bolton) which also uses 780E.
(Please cc me on your future emails since I'm not subscribed to the list)
On Fri, Jul 26, 2013 at 10:29 AM, Wei Hu wei@aristanetworks.com wrote:
On Fri, Jul 26, 2013 at 6:12 AM, Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
The code names are complicated.
Jaguar describes the CPU(APU) architecture (succeeding Bobcat), while Kabini (embedded, htpc, laptops) and Temash (tablets) describe SoC families with those cores.
Hudson seems to be the generic code name(!?) for all FCH aka southbridges since sb9xx which came to be when they started with their fusion aka APU development, hence there are multiple generations of Hudson (3 AFAIK, where Yangtze/Salton are #3).
The integrated FCH for Kabini and Temash are codenamed "Yangtze" and "Salton" respectively. I am not aware of the previous code names... The only other FCH name i could find is Yuba but that was never released because it was cancelled together with Krishna/Wichita.
Is it right to call out Hudson for incompatible SPI changes though? We might need to call it hudson3 or something. What I seem to see in coreboot is they try to bundle compatible changes into hudson and for incompatible changes just call it yangtze.
-
Wei Hu