惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

W
WeLiveSecurity
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
Microsoft Azure Blog
Microsoft Azure Blog
The Register - Security
The Register - Security
Stack Overflow Blog
Stack Overflow Blog
博客园 - 三生石上(FineUI控件)
T
Threat Research - Cisco Blogs
S
SegmentFault 最新的问题
V2EX - 技术
V2EX - 技术
Hacker News: Ask HN
Hacker News: Ask HN
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
P
Proofpoint News Feed
J
Java Code Geeks
Microsoft Security Blog
Microsoft Security Blog
M
MIT News - Artificial intelligence
AI
AI
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
P
Proofpoint News Feed
Hacker News - Newest:
Hacker News - Newest: "LLM"
B
Blog
N
News and Events Feed by Topic
N
News | PayPal Newsroom
Google DeepMind News
Google DeepMind News
酷 壳 – CoolShell
酷 壳 – CoolShell
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
WordPress大学
WordPress大学
C
Cybersecurity and Infrastructure Security Agency CISA
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
博客园 - 【当耐特】
U
Unit 42
腾讯CDC
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
The Cloudflare Blog
H
Help Net Security
Recent Announcements
Recent Announcements
P
Privacy & Cybersecurity Law Blog
IT之家
IT之家
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Security Archives - TechRepublic
Security Archives - TechRepublic
L
LINUX DO - 热门话题
Martin Fowler
Martin Fowler
MongoDB | Blog
MongoDB | Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
H
Heimdal Security Blog
博客园 - 聂微东
S
Securelist
大猫的无限游戏
大猫的无限游戏
Cloudbric
Cloudbric
Cisco Talos Blog
Cisco Talos Blog

HN's home page

Rainbow Query Language | Hacker News Exec into Node via Kubectl An AI native hedge fund The Seven-Action Documentation Model | Hacker News Package Manager for Kubectl Plugins Tongan Castaways | Hacker News Tech overlords plan for conscious AI to conquer the cosmos. What could go wrong? Data Breach Disclosure Lag Is Getting Worse How LLMs Work | Hacker News I Dropped PRDs for Shape Up Go Experiments Explained | Hacker News FCA's Palantir deal could expose UK financial data to Trump's US, critics fear WebXR BCI for Neural-Adaptive Avatar Control in Mixed Reality The first murder conviction via DNA analysis Tom Interviews Theo de Raadt of the OpenBSD Project (2019) [video] Show HN: Replace shell commands with bun shell typescript scripts Quay.io Is Down | Hacker News AI driven analysis of brokerage account fees in the UK Bill Gates Spent Years Crafting His Image. Now It's Cracking Using LLMs to secure source code Wi-Fi 8 in the Lab [video] The household battery revolution that could change energy bills and the world Is Python Becoming Pinyin? | Hacker News Livia – Executive Assistant | Hacker News FindMyPipe – Query Apple Find My from Linux for AI Agents Show HN: Agent skill for creating product launch videos with Remotion RecruitMyself – AI job search copilot for resumes and applications AI coding agents and the erosion of system understanding The 'Resting' Generation and South Korea's Youth Recession AMD Computex 2026: 10 Years of AM4, AM5 Support Through 2029 Docker Networking Explained | Hacker News Textbooks in Tokenland | Hacker News Key Chemistry Question Answered, No Quantum Computer Required Gifts For Retrocomputing Fans – remix yesterday's tech with a modern spin Miscellany № 49: introducing the quasiquote – Shady Characters Amazon Thinks the Future of Data Centers Is a Technical Problem It Just Solved A brief history of the UUID (2017) Flying High Unpressurized (2016) | Hacker News Five Years of Trying to Add Recursion to Lychee How British comfort food won over the French Blorp Language | Hacker News Decache – you might have the internet's lost media in your PC's cache folders Criminal Activities and Migration | Hacker News A free, open-source library of DESIGN.md files for AI-generated UIs MiniMax M3 | Hacker News People are apparently farming citations on ResearchGate – Chuniversiteit Hacker News Basketeer – a typed TS SDK for your Tesco account, with nutrition data 'Penguin' decays from CERN's Large Hadron Collider experiment hint new physics Emergence World: A Laboratory for Evaluating Long-Horizon Agent Autonomy Homebrew lead Mike McQuaid: Sandboxes and Worktrees - My Secure Agentic AI Setup Lean, Not Backpressure | Hacker News AI Dangers Eclipse Nuclear Weapons at Singapore Defense Forum Open source analytics that answers backbase How turkey hacked the hair-transplant industry How GPT Image 2 Is Transforming Marketing Workflows in 2026 Improve Git monorepo performance with a file system monitor Strava for Claude Code MiniMax M3 on Qubrid AI There's Something Else We Should Be Worrying About Celebrity Profile of an A.I. Actress What Is Windows K2? | Hacker News AI is devoid of meaning and humanity. Its vapid voice suits the political moment Show HN: Interpreto – Live Translation for Travel Taxicab Geometry Sealed classes and interfaces in Java (2025) Show HNs | Hacker News My AI Skill Edited This Video That Explains My AI Skill – Arcturus Labs Amazon Pinpoint End of Support The Mystery of the Backward Index MP/M's Process Dispatcher SlimTide Reviews: A Modern Solution for Metabolism and Energy Learning Lustre: Type-safe front end development with gleam Thomas Mann: Goethe Heartened by Panama (As Suez for English, or Danube-Rhine) How to make Message Log of the Unreal Engine 100 times faster Sum-product, unit distances, and number fields Can Meta Buy Belief? | Hacker News Twenty Years of Bigtable | Hacker News Show HN: Combine WigglyPaint GIFs into Video Show HN: AgentThreatBench – Benchmark for AI Agent Memory Security Genius Spotted in the Wild Napkins: Where Ethernet, Compaq and Facebook’s cool data center got their starts (2011) Moderate caffein use alters sleep-related EEG Nvidia Announces RTX Spark | Hacker News Show HN: Ministry of Everything – CLI agent harness for a single operator CEOs blame AI for layoffs, MIT prof says it fits a pattern to find cover story Bugs I didn't expect while building a zsh cleanup script for macOS dev machines Nvidia jumps into PCs with new chip debuting in laptops from Microsoft, Dell, HP Nvidia unveils PC 'superchip' in challenge to Apple and Intel Show HN: Having fun making mini static site apps Synthea API: Create Synthetic Medical Records as a Service Berkshire Hathaway to buy Taylor Morrison for $6.8B in cash The most complex model we understand [video] SanDisk stock is +4,440.53% in the past year Driftwm: What if your window manager worked like a whiteboard? US Immigration enforcement looks into buying ad data AI Is Creating More Work for Australia's Workplace Tribunal Finding New Biblical Cross-References with Codex Glide: A tiling window manager for macOS Ultra-highly efficient enrichment of uranium from seawater via studtite nanodots (2024)
New Texas Instruments 5532 chips are not the 5532s we’ve used for decades
SpikedCola · 2026-06-04 · via HN's home page

An amusing aside: Look at the list of "applications." Netbooks? Multichannel video transcoders? Scalable platforms?

I've seen this in other TI datasheets. One old general purpose 74HC series logic chip included "E Meters" in its applications.

My hunch is that whoever was assigned to add these "applications" to each data sheet was having some harmless fun.

Another note is that I'm a low profile customer of Digi-Key and Mouser. Both of them send out change notifications on parts that I've ordered in the past.


This is the electronics equivalent of Python3's breaking changes to string handling. It's pure evil, and will have 2nd order effects for decades.


How were they python 3 changes pure evil? I think it was a good thing for the language in the long run, and the earlier you do it, the better.


This sort of thing really annoys me. Part numbers are for use of engineers, not for the marketing dept. If you change the specs, change the part number.


Kind of.

I want all 7400s to be four NAND gates, regardless of how they are implemented. As long as the results are correct, you might as well put a little ARM controller pretending to be four NAND gates.

For analog parts, I agree any change to the data sheet should receive at least a different suffix letter.


I can see both sides of this. I really want different part numbers for the same reason you do.

However we deal with a lot of regulated products and to just open a case at one of the Government Paper-Pusher Regulators will cost us $5,000 to just change the part number. We are a small company and $5k hurts.


I'm sure it does and you have my sympathies, but your situation would not be a reason to let Texas freakin' Instruments off the hook. They're not exactly "a small company", and I wouldn't be surprised if the $5k would have been cheaper than dealing with the response to this, so this just comes across as incompetence on their end.


... How do the "paper-pusher regulators" feel about getting a completely different part unannounced? I would guess unhappy, tbh. Like based on the thread it's not trivial changes.


Kind of like keeping a certain plane model number the same, and claiming that re-training isn't needed even when it clearly is


It annoys me too but part numbers are not a spec but more of a strong hint. The attitude of the industry is that it’s up to you to read data sheets carefully and test. Even for a 2N2222 or whatever.


Keeping in mind, though, that this is a jellybean part. You're supposed to be able to order "a" 5532 without specifying the supplier, because many vendors produce "a" 5532, and they're all the same. Different vendors' 5532s are supposed to be able to be treated as the same SKU — literally dumped into co-mingled stock in warehouses — with no ill consequence!

(And yes, until TI's recent move, that was true of the 5532. All the other vendors' 5532s had matching datasheet specs, including the 22V max input voltage. Because a design that was built for "a" 5532 was usually built to run it up to 100%; and that a vendor couldn't offer their part as a swap-in if it couldn't do that.)

But now, if your purchasing department (or the supplier they purchase from) happens to order TI 5532s — or if the warehouse they're sourcing from has comingled any TI 5532s into the general 5532 stock — then your product is now broken, with no real recourse except to change your entirely supply chain to one that specifically excludes TI.


The EEVBlog[1] video about this has a nice example of only a single chinese manufacturer offering the same stuff as TI now does, even with the same PNP instead of NPN topology. All the others are comparable to the original.

1: https://youtu.be/22ZmmZ67SMY


MPF102 is my favourite there.

“It’s a JFET” is your only guarantee.

Buy binned parts and design spec spread into it.


Specs are just that... specs. A 7400 is one thing, but if you designed a circuit that barely avoids oscillating with a 10 MHz GBW, an unsolicited "upgrade" to the opamp that raises its GBW to 12 MHz may be more of a disaster than a favor.

Frankly it's not OK to "upgrade" plain old TTL parts, either, since a faster 7400 might expose a race condition that never caused problems before, or cause EMI problems that didn't exist before.


> The attitude of the industry is that it’s up to you to read data sheets carefully and test.

Is this backed up by court precedent? This seems like you could easily claim damages due to a differently speccd part.

I’m not doubting that’s how the industry operates, but it seems wrong so I’m curious what is supporting such a dysfunctional form of doing business.


It has worked this way since the days of the vacuum tube, so there probably is some legal precedence somewhere. I think part of this with the NE5532 is just that these days most EEs spend most of their time with digital where the data sheet and its spec is absolute; in the linear world the spec sheet is an ideal and an average because the parts themselves are an ideal and the real world never lines up with the math. Back when the NE5532 came out it was still common to see power supplies that were unregulated or barely regulated or cheap regulators with poor tolerance that would vary a fair amount with wall voltage and massive tolerances on passives, data sheets and EEs took this into account, most parts would survive max voltage but there would be a higher failure rate, so run at 70% or 80% and you don't have to worry about it.

In these days of cheap SMPS and EEs that are trained with a strong lean towards digital and much improved IC fab, the max seems to be treated as the max safe voltage for good reliability and life, and you don't have to worry much about the tolerances of everything else so much. Back in the 90s when I was learning this stuff, the old EEs scolded me when ever I ran at max voltage and would patiently explain it all to me and that even if it can operate at that voltage, you can't be certain your PS will still be putting out that voltage in a year, parts drift as they age and accidents happen and the world is not ideal. They were right.


They’re just not really standardized at all, especially semiconductors. Not in the sense you’d expect naively. Some were a long time ago, and supposedly the old Japanese sc parts were, down to die geometry and process. But otherwise, the part number means “this is like the part with a similar number first made by someone else”, not “this is an exact replacement in every way”


I got one of those take down notices because I had their catalog of Space Grade Rad Hard parts on my website. About six directory levels down; did I give TI permission to invade my site?. Any Human would have seen it as promoting their parts, which was not the direct intention. The Bot just said it was a Copyright violation and I had to remove it from my site or they would send lawyers after me. It wasn't worth the time to fight.

I've been screwed by TI many times in one way or other. As have colleagues. They did a die-change of a MSP430 and it stopped working in their product. No answer was forthcoming from TI.

I had designed in a Silicon Labs Bluetooth module a few years ago. Now that TI has bought SiLabs, I'm designing it out. I simply don't trust TI. They once were a good company. They went downhill fast after they got rid of all of the support people and moved support online via forums.


Why do companies always do this? Always the largest companies with all the money to quietly host what at most a couple hundred mb of data and they just don't. Kill the old download links. Ruin all the old support articles that point to those old download links. Ruin all the old forum posts that point there. What is even crazier is sometimes they still have the files they just don't expose them, they make you beg for them with the support agent from across the world who asks if you have tried unplugging the thing first when you ask for the download you know you already want. Infuriating, boring dystopia.


Because they're changing out their backend CMS and have deemed it too expensive to port ask three old documentation over.


Oh, wow, I was expecting from the title that, eh, maybe they changed the process or something, and someone was being a bit fussy. But yeah, no, different part.


Across the board TI is moving to new fabs, new fab processes and 300 mm wafers. So the old tooling is going away and they're adapting legacy designs to the new processes. This changes component behavior, particularly analog stuff, like these op amps.

That's all inevitable and has happened in the semiconductor business before. When it happens, manufacturers are forced to choose; obsolete old parts that can't be indistinguishably reproduced on the new node, or and sell substantially different components under existing SKUs, so they can keep booking orders from high volume customers without disruption.

In this case, the latter is happening. In all probability their high volume customers have already accounted for the PCN because TI told them it was coming years ago, back when the new fab buildout started and the lithography machines were first ordered.


> so they can keep booking orders from high volume customers without disruption.

Clearly there is disruption though. It's more a matter of whether or not it's openly acknowledged.


There's no reason it isn't as the die is likely the same just in a different package.


This is fucking dire. Lowering voltage will just lead to early failures for poor clueless designers/repairmen that had old datasheet saved and just assume it will never change but slew rate chance is just "well it works, but suddenly it's worse in certain applications"


This is why you should always order new parts for a new design and never, never trust the old guy with the magic parts box. Also why learning to read and compare data sheets skeptically is a fundamental skill.


No, I’m talking about the guy that builds prototypes out of his magic parts box and says “oh, you can still get those” when the last direct substitute was obsoleted in 2008. Or he’s using the old version of a part like this in a “proven” subcircuit and NOT checking for change notices or other the new data sheets. That’s what I mean by the “magic parts box”. Buy new parts for new prototypes and read all the latest data, folks.