Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #28670
| Path | csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | Paul Rubin <no.email@nospam.invalid> |
| Newsgroups | comp.arch.embedded |
| Subject | Re: H8S2676 faulty chips |
| Date | Sun, 09 Jun 2019 12:53:54 -0700 |
| Organization | A noiseless patient Spider |
| Lines | 12 |
| Message-ID | <87r282fsbx.fsf@nightsong.com> (permalink) |
| References | <bc370e5b-b85c-4a56-adf7-3b4904e03622@googlegroups.com> <qcmbkg$7ar$1@dont-email.me> <3a265bb9-4280-4343-86b5-028f208e1366@googlegroups.com> <qcp81d$bl4$1@news2.open-news-network.org> <qcr54q$2kj$1@gioia.aioe.org> <dsj*Wtfpx@news.chiark.greenend.org.uk> <9767a9be-64b7-48bd-b7bd-86f8ba25e044@googlegroups.com> <csj*5qPpx@news.chiark.greenend.org.uk> <db065587-4c84-4c1e-b3ae-f87b25cd6fb9@googlegroups.com> <503f0e44-5459-46ae-858a-27d2774a3c61@googlegroups.com> <54a1f9d8-7e63-4685-aa8d-b5b4d4066ebd@googlegroups.com> <199dbda3-496c-4db2-bcbb-af475dace086@googlegroups.com> |
| Mime-Version | 1.0 |
| Content-Type | text/plain |
| Injection-Info | reader02.eternal-september.org; posting-host="c94d176a6ea1d57d23efb185ccb2a0e8"; logging-data="14693"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19DnebaKBRctKgV0DtPuKSx" |
| User-Agent | Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
| Cancel-Lock | sha1:hM4gY/VyRtssmo2bd6QbL8lZZ7Q= sha1:XrKHNfPhJFAapI68Xoc2LbKQ8Bo= |
| Xref | csiph.com comp.arch.embedded:28670 |
Show key headers only | View raw
Rick C <gnuarm.deletethisbit@gmail.com> writes: > If they are largely functional but are failing some small detail it is > possible these are clone chips, a fresh design, not a literal > duplicate of the original device. It's weird: are you saying some illicit chipmaker did an unauthorized redesign of this somewhat obscure and not exactly simple part, in order to sell them under counterfeit labels, and left out functionality? Does that really happen? Now that there is a market for working units of the discontinued chip, could the illicit maker issue an erratum and spin another run? There is at least one possible customer...
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
H8S2676 faulty chips xyman8@gmail.com - 2019-05-29 01:23 -0700
Re: H8S2676 faulty chips Dimiter_Popoff <dp@tgi-sci.com> - 2019-05-29 19:22 +0300
Re: H8S2676 faulty chips xyman8@gmail.com - 2019-05-30 04:18 -0700
Re: H8S2676 faulty chips Mike Perkins <spam@spam.com> - 2019-05-30 19:39 +0100
Re: H8S2676 faulty chips Chris <xxx.syseng.yyy@gfsys.co.uk> - 2019-05-31 13:02 +0100
Re: H8S2676 faulty chips Theo <theom+news@chiark.greenend.org.uk> - 2019-05-31 17:18 +0100
Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-07 01:50 -0700
Re: H8S2676 faulty chips Theo <theom+news@chiark.greenend.org.uk> - 2019-06-07 12:56 +0100
Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-08 15:50 -0700
Re: H8S2676 faulty chips Paul Rubin <no.email@nospam.invalid> - 2019-06-08 17:44 -0700
Re: H8S2676 faulty chips Rick C <gnuarm.deletethisbit@gmail.com> - 2019-06-08 20:43 -0700
Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-08 22:40 -0700
Re: H8S2676 faulty chips Paul Rubin <no.email@nospam.invalid> - 2019-06-08 23:03 -0700
Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-08 23:08 -0700
Re: H8S2676 faulty chips Rick C <gnuarm.deletethisbit@gmail.com> - 2019-06-09 12:46 -0700
Re: H8S2676 faulty chips Paul Rubin <no.email@nospam.invalid> - 2019-06-09 12:53 -0700
Re: H8S2676 faulty chips Rick C <gnuarm.deletethisbit@gmail.com> - 2019-06-09 13:27 -0700
Re: H8S2676 faulty chips Theo <theom+news@chiark.greenend.org.uk> - 2019-06-11 14:05 +0100
Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-12 01:11 -0700
Re: H8S2676 faulty chips Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2019-06-11 11:10 +0200
csiph-web