Full text: "ADAPTOR PEDESTAL T239 PEDESTAL 21 OR 23 MM X 21 OR 23MM SUBZ A01-001941", HSN code 85437099 (electrical equipment).
No idea what an adaptor pedestal is, but I doubt it's very interesting in practice, unless the area (between 21 mm² and 23 mm²) tells us something. But unless someone with the right background actually knows what that is, speculating about that could tip us into bad conclusions pretty easily.
I don't think there is any industry standard "adapter pedestal." LiC rightly warns away from from wild speculation while the thread is hot, but I will stoke the fire slightly.
This could be a random breadboard purely for hardware development. This could be like the FPGA in the back of existing Switch devkits, that allow access to all the debugging tools that devs need. However, I will just note that the existing Switch has a piece of hardware that could be clinically described as an adapter pedestal - namely the dock.
If it is any of those three, at the moment, you can't really infer anything useful from the existence of the thing.
Okay, while there's not been a lot of pages since yesterday evening, i still need some short summary from someone who's in the know about all this tech stuff what the recent findings mean. ^^
I get it definitely means that any talk or thought about ReDraketed's SoC being shelved should be left behind (not that they weren't already unrealistic before).
Oh and also ... about some posts from a few pages back ... all i say is: Respect the elderly! ;_; ;D
I'm still sorting through P4bl0's info as well. As best as I can tell, right now we have a few pieces of confirmation:
- Recent confirmation of T239 development
- A shipping timeline that matches the prior, speculative tape-out/sampling timeline
- A public statement of the size of T239's memory bus, which matches Thraktor's finds
- Incidentally, there is a very early pre-finalized design comment in the Linux driver that also hints at the size of T239's memory bus
There has been a "April sampling, September chip wrap up" timeline inferred from some Linux commits and LinkedIn profiles. If that timeline is correct, then the design in the Nvidia hack would have to be close to final, with only last minute bug-fixes remaining.
The above bullet points essentially doubles down on all of that being correct.
Not only does it confirm that T239 is still the chip, but it heavily reinforces the timeline. The memory bus wasn't directly listed in either the Linux or Nvidia dumps. By hard confirming that memory bus, not only does it lend credence to the idea that the chip hasn't changed, but that some of our more indirect detective work holds up.
We've seen smoke, and we've seen a gun, and we've spent 18 months connecting the two together with 90% confidence, and along comes a picture of the gun, smoking.
P4bl0's finds include other parts, but so far they all seem OG Switch related. Searching shipping records is an interesting source of data that might turn something up, but right now I believe we've not discovered anything fresh.
And I want to add that I don't think Nvidia would've asked Linux to
add support for T239 on 5 September 2022, and I think Nvidia would've stopped updating the files associated with T239 much earlier than
8 April 2022 for L4T on GitHub, if T239's designed with Samsung's 8N process node in mind initially before Nintendo and Nvidia decided to switch to TSMC's 4N process node. (I could be remembering wrong, but I believe Nvidia did continue to update the files associated with T239 for L4T on GitHub beyond 8 April 2022. Please do correct me if I'm wrong, @oldpuck.)
Correct, I believe the last update was in September.
When did we first catch wind of the NG code name? It wasn't the T239 leak was it?
I do want to chase up on the NG point, but here's essentially my take on the information:
I'm a newer member around here (since shortly after Gamescomm leak) but to my understanding, only a few here supposedly know the real codename, and is not sharing it publicly for unknown reason. I never bother to ask why but I'm sure they have their reasons. However one of them did say it's how they know which leaks can be dismissed.
The Activision/Microsoft court documents is not going to have next-gen Switch codename in those. Activision/Microsoft was simply using "NG" to generically refer to "next gen Switch", nothing more.
On Codenames:
The Switch had multiple code names during development. There was "NX" which all of us know, and was essentially Nintendo's codename. In the case of the Switch this was weirdly retroactive. Nintendo had come up with the name "Switch" when they settled on the hybrid console, and seem to have decided that they'd use it for the actual product name and needed to come up with a code name they could use instead.
Inside Nvidia, the project was known as "Odin". This is because Nvidia reuses chips in different products - the obvious example is the Shield and the Switch both using TX1. Nvidia uses Norse influence code names for their Tegra based products, and in fact, there are parts of the Switch hardware that still bear the ODN identifier.
Right now, there are at least two similar names for Switch NG - an Nvidia code name and an internal Nintendo name. The Nvidia one has floated around for sometime. The Nintendo one came to light not long ago. I'm honestly surprised that neither have showed up in the press.
These names are very plain. It's fun to know them, because it's fun to know things, but they don't
tell you anything. The only use they have to us, collectively, is that they are a
shibboleth that can be used to identify fake leaks or games of telephone. Because of that, I have been reluctant to mention them myself, as their only use lies in their relative secrecy.
However if someone with search-fu and
inside knowledge wanted to hit these shipping records with those code names, they should do so. I don't have the time at the moment to do that deep dive, but might be revealing. (
@LiC?)
I'm wounded... you're also probably right.
Eh, it happens. As someone who got into the "insider game" kinda by accident, it took me a bit to figure out how to deal with it. Being up-front about the situation, as you have, is the best you can do. You can't control how things get spread.
