Slashdot Mirror


Intel To Cut IoT Jobs (electronicsweekly.com)

An anonymous reader shares a report: Intel is laying off people in its IoT group following its recent cuts to three of its IoT products -- the Joule, Edison and Galileo boards. 97 jobs are to be lost in Santa Clara and up to 40 more in Leixlip, Ireland. IoT accounts for less than 5% of Intel's sales.

107 comments

  1. So.... by Anonymous Coward · · Score: 4, Insightful

    ...the IoT bubble exploded before being fully inflated ?

    1. Re:So.... by 0100010001010011 · · Score: 4, Insightful

      More like Intel was playing too much catchup to ARM, AVR, ESP8266, MIPS, PPC and the other embedded chipsets.

      Turns out "But it's x86!" isn't as much of a selling point as they thought it was.

    2. Re:So.... by Anonymous Coward · · Score: 0

      Not exactly, all the hype is ARM these days. A minimal 32 bit ARM core (integer only, in order, single issue, very limited pipelining) is 7000 transistors if I remember correctly. Such a core running at low frequency is also better implemented on far from cutting-edge processes but with low leakage.
      Unreachable with any 32 bit x86 design, and this does directly affect power consumption.
      Sadly, ARM is becoming a monoculture in many areas of computing, as x86(-64) is in desktop/laptop space.
      I'd like to see more architecture choices (MIPS and POWER) in some markets.

    3. Re: So.... by Anonymous Coward · · Score: 1

      No, it's just that Intel was too late to the game with an expensive, closed system. If you can't make a better product than the Pi or Arduino, then you're wasting your time.

    4. Re:So.... by Anonymous Coward · · Score: 0

      ...the IoT bubble exploded before being fully inflated ?

      Intel's attempts to enter the IoT market went down like a lead balloon with plenty of complaints about them being overpriced and under-documented. It'll not stop the IoT market, Intel just fell flat on their faces before even getting into it.

    5. Re:So.... by epyT-R · · Score: 1

      Too bad they didn't take IoT with them. It would put a decent dent into the panopticonic hellhole some seem to want.

    6. Re: So.... by Anonymous Coward · · Score: 0

      Definitely not transistors. Maybe you meant 7K gates. An ARM7 is about 40K gates. I believe the marketing number for the cortex-M0 is 8K gates. I haven't implemented one yet, so I cannot say how real that is.

    7. Re:So.... by Anonymous Coward · · Score: 0

      their board was too expensive - like they were churning out production level, next gen stuff

      turns out, I can't afford several Intel IoT products like I can with the Raspberry Pi.

      FWIW, it also turns out, I've spent hundreds on multiple raspberry pi's + accessories

      I've purchase zero Intel IoT products

    8. Re: So.... by dougdonovan · · Score: 1

      investors will find someplace to cut costs to keep their toys.

    9. Re:So.... by DivineKnight · · Score: 1

      "FWIW, it also turns out, I've spent hundreds on multiple raspberry pi's + accessories"

      Which you would have to, unfortunately (as a once fellow, and many times tempted to again, RPi owner). It's a cheap device that requires buying tons of accessories to get somewhere, which, after you do so, you come to realize you want a proper PC to do the programming / debugging / etc.

      I'll buy a RPi again when it comes with USB 3.0 (and here we are, transitioning into 3.1...), SATA (also as a boot device, and not USB to SATA, I don't want to pay the processor tax), and some RAM (8GB minimum, but if you make it expandable (even to 16GB+) with SO-DIMMs, you can ship it with no memory....I'll take care of the rest). And yes, I know there are other 'options' that offer some of the above, but aren't RPi, but they have even less support that this device.

    10. Re: So.... by Anonymous Coward · · Score: 0

      ARM7 is really modern by my standards, as every Cortex. I believe 7000 transistors was for the very first ARM cores (26 bit addresses, no MMU, no integer multiply, no thumb encoding) in the mid 80s. Cortex-M0 is much larger than that.
      And yes it was marketing number (no interface to external world to start with).
      After all the original 8088/8086 was much more complex and only 29k transistors (including I/O, a prefetch queue, complex microcoded code paths for instructions like multiply and divide, and others that nobody uses like AAA, AAD, AAM, AAS, XLAT, weird instruction encoding with prefixes...)
      29k transistors is about 4-8k gates (large uncertainty, I'm not a specialist).

    11. Re:So.... by Aighearach · · Score: 1

      They can't even keep up with Texas Instruments on features, and then they want an even higher price, when TI is already getting a premium over AVR and Espressif.

      There is basically no use case where they offer an advantage of any sort, unless you only like Intel hardware. If there is at least one other company you're willing to use, they probably have something better for less, and something else for even less than that.

    12. Re:So.... by The123king · · Score: 1

      Why not get rid of that pesky ARM core and replace it with an intel processor... Then you could install it into a clamshell-like chassis, install a battery, screen and a keyboard/trackpad. It would make it super portable and could run standard x86 Windows

      I wonder why no-one has thought of this before...

      --
      If you gave me a choice between a printer and a giraffe with explosive diarrhoea, i'll get my ladder and my raincoat
    13. Re:So.... by DivineKnight · · Score: 1

      A Clamshell-like Chassis you say?: https://www.amazon.com/Officia...

      Battery?: https://www.amazon.com/Makerfo...

      Screen?: https://www.amazon.com/Raspber...

      Mouse & Keyboard?: https://www.amazon.com/Wireles...

      Face it, the vast majority of people are going to buy some, if not most, of some variant of these accessories (don't need the screen if you're hooking it up to an existing HDMI screen, etc.). Who in their right mind would argue for a 10/100 network connection in this day and age? Or a slow ass MicroSD card as their boot device (there may be some faster variants with adapters, but still, capacity will be limited; thus you are stuck putting the boot partition on one device, and everything else on another, which is, even on an Ubuntu-flavored derivative, a PITA). Just solder a pair of SATA connectors (+ controller) onto the board, and be done with it; combined with the GbE controller, it's going to bring the cost of the board up a whole $2. Another $1 for the SO-DIMM connectors. Call it the Raspberry-Pi 3++. Hell, here's another $1, put another two SO-DIMM sockets on it, and do what Intel has had serious trouble doing with their laptop implementations for the longest period of time: make it past 16GB of RAM.

    14. Re:So.... by unixisc · · Score: 1

      8GB minimum for an embedded system? What exactly are you making? Here I thought that we were talking about things that need to be cheap enough to do things like a remote garage door opener, but also enough processing capabilities to support Bluetooth and accept requests from our phones & tablets. Which would suggest having a 32-bit device, but certainly not a 64-bit one.

    15. Re:So.... by arglebargle_xiv · · Score: 1

      In the same way that the 'S' in IoT stands for "security", so the "X" in IoT stands for "x86".

  2. IoT is the old AI by Anonymous Coward · · Score: 0

    Another flop.

  3. Good. Now outlaw IoT. by Anonymous Coward · · Score: 0

    IoT should be outlawed. People don't need connected thermostats, refrigerators, toasters, and things like that. It is, however, a great way to create botnets. Outlaw IoT to reduce the amount of compromised systems available for botnets. It would be a huge win for security.

    1. Re:Good. Now outlaw IoT. by 0100010001010011 · · Score: 1, Insightful

      Tractors should be outlawed. People don't need to be pulling plows, seed drills and combines with artificial horses. It is, however, a great way to become dependent on petroleum.

      It would be a huge win for horse breeders.

    2. Re:Good. Now outlaw IoT. by Anonymous Coward · · Score: 0

      Why stop there? Pansy. Outlaw the internet. Huge win for security.

    3. Re:Good. Now outlaw IoT. by slickwillie · · Score: 1

      But I need my internet-connected toilet.

    4. Re:Good. Now outlaw IoT. by epyT-R · · Score: 1

      Tractors != IoT DaaS (device-as-a-service).

    5. Re:Good. Now outlaw IoT. by Anonymous Coward · · Score: 0

      John Deere disagrees with you: https://news.slashdot.org/story/17/04/10/0340232/american-farmers-are-still-fighting-tractor-software-locks

    6. Re:Good. Now outlaw IoT. by epyT-R · · Score: 1

      I forgot about that. I stand corrected. If it isn't already true, I'm sure they will eventually switch to IoT black boxes for their DMCA/software locks..

    7. Re:Good. Now outlaw IoT. by Anonymous Coward · · Score: 0

      You have been excreting a bit many undigested peanuts this week. Please take corrective measures, lest this begins affecting your citizen score.

      -- the Information ministry

    8. Re:Good. Now outlaw IoT. by 0100010001010011 · · Score: 1

      IoT != DaaS.

      I have a fairly connected home but nothing is hosted outside of my house. All of the IoT devices and cheap Chinese cameras are on their own firewalled VLAN.

      You can do IoT without giving control of your own devices.

    9. Re:Good. Now outlaw IoT. by epyT-R · · Score: 1

      That is true, but DaaS will likely be the most common application. At some point (two decades?), most appliances will require net access to function at all because the real money is in user tracking. Why just sell a $500 refrigerator when you can sell a $500 refrigerator AND track its use and sell the data?

      I hope I am wrong and this never happens.

    10. Re:Good. Now outlaw IoT. by AlanObject · · Score: 1

      People don't need connected ....

      The devices I currently have at my house connected to the Internet include the DVR, security system, lawn sprinkler control, vacuum robot. I haven't installed a Nest thermostat yet.

      I took a pass on an connected refrigerator because yes it is possible to go too crazy with this stuff. But each of the other devices has turned out to be convenient at one time or another and well worth having for the modest cost involved.

      The security thing is really not that hard for anyone with minimal understanding of the issues involved.

      The bottom line is you will have useful IoT and you will have useless IoT. You will have good vendors and you will have crap vendors. Like any other market.

      Fun facts: some of the earliest IoT devices were many years ago and not called that. There was a Christmas tree you could poll or set via an early SNMP demonstration (can't remember what year that was) and I think also a coffee pot. The only thing "new" about IoT is we can make the devices small enough and cheap enough to make small applications commercially viable.

    11. Re:Good. Now outlaw IoT. by Anonymous Coward · · Score: 0

      Until it it gets a virus and you can no more flush it?
      Then you are literally deep in shit!

    12. Re:Good. Now outlaw IoT. by The123king · · Score: 1

      Your tractor is probably an IoT device anyway

      --
      If you gave me a choice between a printer and a giraffe with explosive diarrhoea, i'll get my ladder and my raincoat
  4. ARM ate Intels lunch by Anonymous Coward · · Score: 0

    Arm does purpose built low power soc chips for dirt cheap, intels gear uses tons more juice and provides clock cycles that IoT gear will not use. Seems obvious.

  5. Imagination outstrips Technology by Anonymous Coward · · Score: 0

    It's only Talk
    I overestimated Takeup

  6. IA is not a meaningful differentiator by NeilO · · Score: 2

    Intel never had the right product focus for these IoT devices. Overall cost was too high for hobbyists, and the main product differentiation was basically "we're Intel instruction set compatible" in an age where others are offering JavaScript compatibility. I'm afraid as long as Intel makes their architecture out to be their main selling point they're going to be out of tune with these emerging markets. Same reason they missed the phone and tablet market, in my opinion.

    1. Re:IA is not a meaningful differentiator by Anonymous Coward · · Score: 0

      is IA a liability yet?

  7. whoda thunk it? by Gravis+Zero · · Score: 4, Insightful

    Promoting hopelessly overpriced boards in an area where x86 has no benefit in addition to having insufficient documentation wasn't the gamechanger they expected! If only someone knew why. -_-

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:whoda thunk it? by thegarbz · · Score: 1

      I wouldn't say they were overpriced for what you got. Spec wise they were quite impressive.

      Unfortunately we'll never know if that translates to real world benefit since their documentation was so bloody poor no one ever managed to get anything running on them.

  8. Core Competency by AlanObject · · Score: 4, Interesting

    I learned my lesson long ago with Intel back in the i960 days or maybe before that. With them it is all about the CPU chips. No matter what they say. The one exception are their Network Interface chips

    Here is the pattern: They use their unlimited money+market position+PR machine to fund some kind of tech, pump up a bunch of customers, trade groups, get projects started with generous relationships ("partnerships"), make lots of press.

    A year or two down the road it gets de-funded, spun-out, quietly quashed. The numbers weren't what they wanted so the inevitable corporate-level decision is to return to our "core competency" and that of course is selling CPU chips.

    Anyone who was sucked into designing something with their switch chip product line knows what I am talking about. Remember SSI? If you didn't you dodged a bullet. Infiniband? Network Processors? FPGAs? Then Over 2+ decades (starting with the i186) every 3-4 years they would venture into the embedded controller market just to pull back out of it again. Not Intel Core? Not committed.

    However their current product lineup for embedded is actually pretty damn good. Not only are their designs better thought out but market and ecosystem conditions are fortuitous for them. Most of all, it is now all about selling Intel i3/i5/i7-family CPUs. That alone will keep that line it alive.

    1. Re:Core Competency by Anonymous Coward · · Score: 1

      Intel's incompetence is well-known among Intel employees who had to suffer turbulent middle management changes every time one of the amateur executives decides to play CEO.

    2. Re:Core Competency by Anonymous Coward · · Score: 0

      What about atom?

    3. Re:Core Competency by K.+S.+Kyosuke · · Score: 3, Funny

      Clearly they should stick to their Core competency, not to their Atom competency.

      --
      Ezekiel 23:20
    4. Re:Core Competency by Anonymous Coward · · Score: 0

      The problem is if you allow your competitors to make a good bit of money in an area directly adjacent to your big money-maker and you have a much higher margin, those competitors will get jealous of your margins and start to squeeze into your core areas, putting you under pressure.
      That doesn't mean people will not want Intel's product, but they will want them for cheaper. And it seems unclear how Intel will be able to manage if their margins will shrink, because then suddenly they can't afford all those expensive failures they so far just put up with, but that then again will limit them in their ability to open up new income streams...
      Microsoft have it easier, there are enough people that would have to buy there products that most of their costs like developers are completely optional and they could get rid of them if necessary (they basically did that with their QA already) and then have a long stretch with fabulous margins to discover new ways to make money.

    5. Re:Core Competency by thegarbz · · Score: 1

      Infiniband

      I remember infiniband. It was committed to. Not only that it was THE interconnect of choice for the HPC space. The problem wasn't with Intel. The problem is that Infiniband was an off-standard solution, and then the standard caught up. It's like saying remember SCSI when talking about CD burners. I remember it, I also remember when ATA got good enough to use CD burners without having an additional card installed in my computer.

      Their problem with the IoT stuff is different yet again. It was a garbage product without a use case and with garbage documentation. It's not to say that Intel is transient outside their core, but rather that they don't know what makes products other than CPUs in PCs "tick" with consumers. No one is buying Raspberry Pis for the incredible performance, so you can't just throw out an IoT board and call it a day. It's not "not committed" as much as "not competent".

    6. Re:Core Competency by Anonymous Coward · · Score: 0

      It's like saying remember SCSI when talking about CD burners. I remember it, I also remember when ATA got good enough to use CD burners without having an additional card installed in my computer.

      Unless you're talking SCSI cards with embedded controllers, their own RAM, etc., there's very little difference between a SCSI interface and an ATA/IDE interface from hardware and API perspectives. It's not that ATA got good enough. Manufacturers just started adding RAM to the burners (aka write buffers).

    7. Re:Core Competency by Anonymous Coward · · Score: 0

      True. Though, after their repeated security issues with their CPUs, their Puma6 crap and utter mishandling of everything involved with it, their pi/beagleboard competitor withdrawals here, I'm starting to wonder if even their core competency is being lost. They just straight up suck of late, unable to put out a quality, non-defective product across a line or come to terms when they miss.

      When they design something right, they withdraw it later. When they design something wrong, they look the other way and pretend like there's nothing really wrong. It's not quite as bad as Sony, but I've started to check if a product has Intel in order to avoid it, simply because the alternatives are good enough or even assumed to be superior offerings.

      Is AMD or mobile chip makers cornering the talent market or something? The decisions Intel has made in product support, PR support (and even political support for their manufacturing base), and some designs just have been baffling, like they know they can't compete so they aren't even trying, or they think if they buy more TV ad time that'll be enough to hide their product deficiencies.

    8. Re:Core Competency by JanneM · · Score: 1

      Infiniband is the most common interconnect in the HPC space today though. Doesn't seem right to say it's a failure when it dominates the segment it was designed to handle. Or do you mean specifically the Intel implementation of it?

      --
      Trust the Computer. The Computer is your friend.
    9. Re:Core Competency by Anonymous Coward · · Score: 0

      What about atom?

      The old "in order instruction pipeline" Atom chips were fine IF you recognized their limits and stayed within them.

      The newer "out of order instruction pipeline" Atom chips are impressive, like the C2000 family, are impressive little SoC devices (low thermal power, decent clock speeds, very useable RAM capacity). Again, if you recognize their limits and stay within them, you get good performance for your money.

      The higher end consumer Intel processors are for people that like to burn clock speeds without a clue as to how much processing power they really need. And then there are gamers and their range of "use cases" that simply boggle the sensible mind.

    10. Re:Core Competency by thegarbz · · Score: 1

      I didn't say it was a failure, the GP did for reasons unknown. But I am interested in your source saying it's the most popular today. I know it was 10 years ago, but I thought that changed to Ethernet. The last reference I could find was Wikipedia giving numbers of 181 of the top 500 using Infiniband in 2009, and I thought that one was already a downward trend.

    11. Re:Core Competency by Anonymous Coward · · Score: 0

      Infiniband?

      I don't know what you mean with this. Infiniband is the interconnect of choice in HPC. In 2012 Intel bought QLogic's Infiniband business and they still make their products. They haven't abandoned the market. And given how, for most people, Infiniband is just a fabric, even if they stopped, not much would be lost. People would just move back to Mellanox, where they all came from, and not much would be lost.

    12. Re:Core Competency by JanneM · · Score: 1

      No, more than half of the machines this year were using Infiniband. I get the impression (note: not hard data) that IB is pushing out 10G Ethernet on the lower end of the HPC field. The latency wins are worth it for a lot of applications.

      --
      Trust the Computer. The Computer is your friend.
    13. Re:Core Competency by Anonymous Coward · · Score: 0

      My previous employer uses i960s in slot machines to this day.

    14. Re:Core Competency by thegarbz · · Score: 1

      Sweet, well thanks for the info.

    15. Re:Core Competency by unixisc · · Score: 1

      Ain't the Core line of products way overkill for embedded? All one should need are 32-bits, and that would have a whole host of legacy software available for it

      FPGAs - didn't they acquire Altera? Looks like that's something that Intel's Custom Semiconductor division could readily use (if it doesn't already) for any design requests they get from semiconductor houses, and run a business on that based on volumes.

      On CPUs, Intel never succeeded w/ any of their non-x86 attempts, which was a pity. i960 went into embedded, i860 was used in some supercomputers, Itanium, we all know, XScale ultimately got sold,... I happen to think that instead of the IoT market, Intel should try to become a fab for Apple & Qualcomm in addition to their own PC chips, so that they can have a more diverse coverage of the market

  9. Home AI startup hit by Joule fiasco by mattr · · Score: 1

    Last week I met a startup that had developed a cool personal "AI-powered" robot that did offline voice recognition and motion tracking. When I asked about dev kits they said they had used Joule... the remainder of our chat would be best described by pregnant pauses.

    1. Re: Home AI startup hit by Joule fiasco by Anonymous Coward · · Score: 0

      Intel IoT dev kits were decent for next-gen products that required fast interconnects and lots of processing power in a pseudo-embedded package. Intel needed to stay in the game long enough to have these third-party products come to fruition, or Intel needed to provide more support early on for computationally-intensive sensing (like their RealSense depth sensors.). Depth sensing is coming to ARM-based cell phones later this year, so the embedded industry will build and adopt ARM-based platforms for depth sensing and other high bit-rate sensing. Intel didn't make enough headway to win in the computationally-intensive embedded sensing market over the last 3 years, and now ARM-based products have caught up in capabilities or will soon do so. In terms of capability, Intel was poised to sit between low-end ARM (with bad IO) and embedded GPUs / DSPs, but they couldn't gain market traction with high prices and difficult support for customized single board computers. I almost went with the Joule platform to build something like their ZR300 depth camera, but it was cheaper to use NUCs with USB 3.0 support and RealSense 200 stand-alone cameras.

  10. What is Up with Intel by WindowsStar · · Score: 1

    Intel really needs to get it together, they are a CPU company and GPUs are tall the rage right now and you cannot buy a decent video card, out of stock and the companies cannot keep up with the demand. Intel could very simply make GPU cards (AMD does) and make a billion dollars over night and save the jobs of these hard working people. Just pisses me off they cut jobs instead of making what is needed and keeping the staff working.

    1. Re:What is Up with Intel by Anonymous Coward · · Score: 0

      Intel could very simply make GPU cards (AMD does) and make a billion dollars over night

      How? Wouldn't they need to make a GPU card that is competitive performance wise then?

      The embedded GPU works because it is cheap and small but I don't know of any consumer that would pay extra to get Intel graphics instead of AMD.

    2. Re:What is Up with Intel by thegarbz · · Score: 3, Interesting

      Intel could very simply make GPU cards

      Intel are the number one GPU company in the market.

      Oh you meant high-performance GPUs? Man now don't have a clue about the industry do you? Patents aside, you can't just turn around and plop a high performance GPU at a good cost out overnight. Or even overyear. There are many 10s of thousands of R&D manhours that go into GPUs and lots of those hours end up in the patent office preventing other people from using the same idea.

    3. Re:What is Up with Intel by Anonymous Coward · · Score: 0

      Ha! Intel hasn't made successful graphics IP in years. Their current graphics chips - the integrated HD series found in their desktop/laptop CPUs/APUs - is mostly licensed from Nvidia, with some tweaks. It looks like Intel may be giving up on that and licensing AMD tech instead (ironically). It remains to be seen how that bears out in the future.

    4. Re:What is Up with Intel by Anonymous Coward · · Score: 0

      After almost 10 years, Xeon Phi still lags nVidia significantly in terms of power, performance, price, and programmability.

      Then internal codenames for Xeon Phi all started with "Knight's"... the metaphor was about defending intel's "Castle" against nVidia coming over the wall.

    5. Re:What is Up with Intel by WindowsStar · · Score: 1

      In fact I do have industry knowledge. Work with Intel's engineers a lot. What you may not know is that Intel and AMD were in a CPU war for many years. Then AMD started moving to GPU because it was losing the CPU war, Intel kept a close eye AMD's GPUs and kept up with the technology all these years. I wouldn't be very hard for Intel to tool up and make High End GPUs.

    6. Re:What is Up with Intel by thegarbz · · Score: 1

      Then AMD started moving to GPU because it was losing the CPU war

      Yeah how did that go?
      Oh right spend $5.4bn buying a company, the expertise and associated patents from someone who was already tooled up to make high end GPUs.

      Intel kept a close eye AMD's GPUs and kept up with the technology all these years

      I was in Amsterdam last week and for the life of me I couldn't find anyone selling what you were smoking when you posted that.

  11. No real surprise. by Qbertino · · Score: 1

    No real surprise here. Said it before.

    --
    We suffer more in our imagination than in reality. - Seneca
  12. IoT processor requirements by Anonymous Coward · · Score: 2, Informative

    IoT SoC requirements

    for most applications (switches, dimmers, dumb controllers, sensors) the following should be plenty:
    8 or 16bit instruction set (64bit is way overkill)
    1MB RAM - or perhaps tens or hundreds of KB

    BlueTooth LE

    hardware support required (to not eat battery) for:
    tamper-proof clock
    AES128 encrypt/decrypt
    ECDSA256 sign/verify
    1KB secure nonvolatile memory (unreadable but usable-by-reference) for provisioning keys, signing keys

    not required:
    floating point

    ideally, this should draw less than a milliwatt when in use, negligible on standby. whole part should be less than $1.

    THIS IS NOT INTEL'S MARKET

    extreme example (except lacks security) is http://cubeworks.us

    1. Re:IoT processor requirements by Anonymous Coward · · Score: 1

      Embedded and IoT aren't one-size-fits-all.
      However, Intel really missed the mark on these initiatives.

      The strategy seems to have taken two approaches:
      1. Non-x86-compatible x86 chips, and;
      2. x86 PC, but it isn't really a PC because we don't give you a normal BIOS and only support a wonky dev toolchain which is quirkier than ARM.

      Both approaches suffered from excess complexity which increased cost, and a lack of easily usable documentation.

      Where Intel should have focused was:

      1. A standard PC on-a-chip microcontroller range. Think 486SX and larger, with 1-16MB embedded RAM, a conventional BIOS, and support for CoreBoot. Optimize for lowest possible component count and pin-count, followed by optimizing for lowest cost.

      2. x86 PC, similar to their higher-end chips, but lower-cost, with a conventional BIOS, and again, support for Coreboot. To optimize for cost, multiple product variants are needed:
          single-core + WiFi
          single-core + WiFi + FB video
          single-core + WiFi + 3D accelerated
          single-core + Ethernet w/ internal PHY
          single-core + Ethernet w/ internal PHY + FB video
          single-core + Ethernet w/ internal PHY + 3D accelerated

    2. Re:IoT processor requirements by unixisc · · Score: 1

      What is the oldest/largest process Intel currently runs - which they haven't retooled to newer shrinks? They could use that as the platform for their embedded products, and then build an SoC w/ the 386SX, 1MB of level 1 cache, 2GB of embedded RAM, 1MB of BIOS flash, built on the old 386SX package. Then such a system could support anything from a Minix setup to a Windows XP configuration used in ATMs.

    3. Re:IoT processor requirements by Anonymous Coward · · Score: 0

      I agree with you, with one exception. With the process size for cost-effective 2GB RAM on a single die, it wouldn't make sense to only use a 386SX core -- certainly not when you are good at making CPU cores.

      Mainstream embedded space cares deeply about low cost, just-enough-IO for the task, and ease-of-development.

    4. Re:IoT processor requirements by radarskiy · · Score: 1

      The trouble with just going back to an old process is that there has been a lot of learning in how to make a useable process since then. (The trouble with newer processes being that you needed that learning just to stay afloat.)

      There has been interest of late in "retroscaling", where you take all the techniques and equipment that had to be developed for the smaller processes and select from that to make a new process at a larger node. That way you can chose what's easy to fabricate and design with for the intended customers, e.g. make metal 2 through 6 have exactly the same design rules.

    5. Re:IoT processor requirements by Anonymous Coward · · Score: 0

      But if you have a full-fledged x86 chip that runs Windows compact/embedded/IoT/this-year's-buzword with a .NET framework you can have legions of C# programmers slapping some crap together.

      By the way, note that the products mentioned are not system-on-chips, they're system-on-modules. Which you also want because the EE side of things is much simpler that way.

      (Also, I want hardware floating point support.)

    6. Re:IoT processor requirements by Anonymous Coward · · Score: 0

      BIOS had nuthin' to do with it. We're talking EMBEDDED, not raspberry pi. Which is where intel got confused. The idea of running linux on anything but a gateway is laughable. Just port freakin' FreeRTOS and provide more IO and they would have been fine. But they went the sexy direction rather than the effective direction.

      Which i find incredibly ironic since they are driving I3C which is a spectacular embedded bus.

  13. MAGA! by Anonymous Coward · · Score: 0

    97 jobs are to be lost in Santa Clara

    MAGA!

    That is All.

  14. another inhumane corporation by Anonymous Coward · · Score: 0

    even if intel does not want to keep these product lines (a mistake in my opinion) that does not mean they need to get rid of the people - surely they can repurpose them on other products.

    note: intel has 60% profit margins.

  15. Intel keeps getting StrongARMed by Anonymous Coward · · Score: 0

    Their X86 just doesn't cut it and their StrongARM chips didn't cut it either.

    1. Re:Intel keeps getting StrongARMed by unixisc · · Score: 1

      StrongARM, actually XScale, was sold to Marvel some 10 years ago.

      The 80386EX did enjoy some support, after its predecessor the 80376 fizzled out. Incidentally, has AMD discontinued its 386 as well? How about Via, which had acquired Cyrix ages ago? Some of the 386 CPUs of yesteryear would be fine on embedded systems if they were sold.

  16. CPU choices by unixisc · · Score: 4, Insightful

    Sadly, ARM is becoming a monoculture in many areas of computing, as x86(-64) is in desktop/laptop space. I'd like to see more architecture choices (MIPS and POWER) in some markets.

    Unfortunately, a lot of the semiconductor companies out there have reduced: just like Freescale & NXP have been digested by Qualcomm. Hardly looks like there's much out there. If a company chooses MIPS or Power, they have to make a business case for it to embedded customers on why it should be preferred over ARM, that has all the momentum. And if they choose ARM, they run up against goliaths like Qualcomm, Apple & Samsung.

    Maybe there could be some companies running it on RISC V, where one USP is that since it's a FOSH (Free Open-Source Hardware) architecture, there may be less to pay in terms of patents to ARM or MIPS or IBM. In fact, RISC V could be something that some fabs could decide to do themselves whenever they need to fill capacity: they do have to have designs-in, though

  17. 80386 by unixisc · · Score: 2

    So what was the product Intel was positioning for the IoT market? The 386SX? If they just took that design, added some level 1 cache and put it on their current most inexpensive process, they'd be optimal for it.

    Why wouldn't a 386 be much of a selling point, when every embedded OS out there - not just Linux or BSD, but also things like FreeDOS, QNX, Minix, Minuet, et al exists for that platform. If one is looking for flexibility in number of hardware sources, one can limit themselves to Linux & BSD and go look there. If one is looking for flexibility in the choice of OS platforms, then it makes sense to go w/ 386. Only question - is Intel still the only game in town, or does Via or SiS still have their solutions?

    1. Re:80386 by Anonymous Coward · · Score: 0

      Intel is doing what any company does when its primary market peaks: Try to reinvent itself. After Intel did mass layoffs last year when it realized there was no more growth in the PC sector ("PC does what?" campaign flopped) they tried a big IoT push because it was all the rage, but nobody gave a shit about IoT once they realized it stood for Internet of Threats, so now they're doing more layoffs.

    2. Re:80386 by Waffle+Iron · · Score: 2

      To bring up a new system, getting the applicable device drivers is a much bigger deal than the choice of ARM vs x86 instruction set (which is mostly just a compiler switch). Unless your IoT device has the exact same hardware peripherals as a legacy PC, an x86 CPU doesn't buy you much over an ARM CPU.

    3. Re:80386 by sjames · · Score: 2

      Probably because you could buy 4 or more good ARM boards for the cost of a single Intel board.

      Intel discovered that nobody is going to pay the Intel surcharge in a field without a pile of legacy software.

    4. Re:80386 by TheGratefulNet · · Score: 1

      intel tried iot with the curie chip, too.

      http://www.mouser.com/ProductD...

      $20 for a failure of a chip. no one uses it. it has bugs and its internal features are not really competitive (or even functional, in some cases!)

      they made a tv show from it, too: https://en.wikipedia.org/wiki/... but since it was not a success, they canceled season2 and there won't be any more.

      intel does not have the right people for this area. and they let go anyone who DID have a clue ;(

      oh, intel. sigh..

      --

      --
      "It is now safe to switch off your computer."
    5. Re:80386 by Anonymous Coward · · Score: 0

      I thought that the 80386 was no longer supported by Linux?

    6. Re:80386 by TechyImmigrant · · Score: 1

      I thought that the 80386 was no longer supported by Linux?

      CMOV? Where art thou CMOV?

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    7. Re:80386 by Anonymous Coward · · Score: 0

      It's not CMOV, it's WP (write protect). This causes non-fixable races with kernel access of user-space data in apps that have more than one thread, and yes, even with a single core.

    8. Re:80386 by TechyImmigrant · · Score: 1

      They both count. My troubles installing Linux on an old VIA board stalled first at CMOV.
      Finding a version of linux that was old enough to work on the CPU and new enough to boot from USB was a challenge.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    9. Re:80386 by Aighearach · · Score: 1

      386 is a bear for IoT. Why would you want a bloated CISC system like that if you're not using an ISA bus or something similar?

      That would not compete with ARM using any process at all, and it would not be cheaper than a modern x86 to make other than having a lower transistor count.

      IoT you want a microcontroller or SoC, you don't really want a CPU that is going to need a bunch of other chips to provide required peripherals. And if you add that stuff in, now you don't have legacy code that can use it, and the newer code uses newer things like ARM, so you're building out a whole toolchain.

      That said, there are a few 486 clones floating around that use a modern process and are really tiny. But it isn't popular or useful or easy to use. For embedded systems there is more interest in the 6502, the processor used in the Apple ][, than there is in x86 based stuff. If you ever look at CPU instruction sets, you'll see how unlikely it is that a person would ever use an x86 without a full-featured OS. And when you want that, you can get a full SoC with ARM that runs any of the OSes that an embedded x86 would run, so it would be a silly row to hoe.

    10. Re:80386 by The123king · · Score: 1

      OK then, take a 486, plonk the chipset etc onto the same die, release as a PC compatible SoC.

      --
      If you gave me a choice between a printer and a giraffe with explosive diarrhoea, i'll get my ladder and my raincoat
    11. Re:80386 by Aighearach · · Score: 1

      OK then, take a 486, plonk the chipset etc onto the same die, release as a PC compatible SoC.

      And you have something slower than an ARM Cortex-M that uses more transistors, runs hotter, and is more difficult to program.

      And you better also hire a swarm of extra engineers to write code to include in on-chip ROM to run those peripherals.

      What you'll have is worse than what Intel already flounders offering. It sounds like a good idea, I understand that. I used to say the same thing before I started doing firmware programming and actually working with these things and reading the datasheets. Once you're familiar with the options, it just doesn't look good anymore.

    12. Re:80386 by unixisc · · Score: 1

      But if you're doing the 386, there IS legacy software. While the latest Linux kernels may have dropped 386 support, it still has a bunch of legacy OSs that anyone can dig up.

    13. Re:80386 by unixisc · · Score: 1

      Do they need the latest & greatest kernel release to work? Can't they just pick whichever the last version of the 32-bit kernel was, and work w/ that?

    14. Re:80386 by unixisc · · Score: 1

      The123king was not wrong. At current process nodes, Intel could start by taking either a 386 or 486 (they did experiments w/ the 80376 and 80386EX), putting it on one of their Altera FPGAs, putting the ISA or EISA bus on them, in fact, putting an entire legacy early 90s PC on it, w/ adequate RAM & flash, and there would be a load of software that would support it. All the early versions of Windows, FreeDOS, QNX, Minuet, Minix - platforms that for all practical purposes only exist on x86 but not really on ARM.

      It doesn't have to be hotter - if the frequency of one of these systems is set at, say, 33MHz or even 8MHz, which was the speed of the ISA bus, then it would run pretty cool. One thing they could do - try providing more IRQs so that that does not remain a major hurdle the way it was 20 years ago. Back in the day, systems only had something like 4MiB of RAM or 16kiB of cache, but that is due to where process technology was then: in today's systems, one could use it up to 1GB of memory w/o hitting the barrier from 32-bit to 64-bit. In fact, you could fit in some of the OSs listed in the BIOS flash itself, and have a main storage flash for all the data, downloadable programs, et al. More crudely expressed, make the BIOS + OS drive your C:\ and your data + downloadable programs your D:\ drive. Point is you could have a complete ASIC in a TQFP package that would consume minimal real estate on a PCB, while providing everything the system needs. Only thing - I doubt one could retrofit things like an SD card or a WiFi on such a system, even externally on board.

    15. Re:80386 by sjames · · Score: 1

      IoT itself doesn't have a lot of legacy software that needs x86. It's all embedded stuff and it's fairly new. It's also common to have the source code and so no problem compiling for whatever architecture is convenient.

    16. Re:80386 by Aighearach · · Score: 1

      It does have to be hotter. Physics. Modern micros are designed to need less power by the choice of instructions and features. That old IP block can't be made cool, you would need a new design. Perhaps you're one of those people who think "mobile" (laptop) CPUs are just a scam and that they're really the same?

      Here is the thing: There are already System-on-Chip products that are full-featured. There is no demand for EISA or any of that, and new devices don't have drivers so you don't even get code reuse out of it.

      And for the same reasons that it has to run hotter, it would also be more expensive. Because newer designs are done differently for real reasons. It isn't just new designs are bigger. The small chip designs have been progressing too. The existence of design improvements guarantees that the old designs won't compete with them. The places where old designs, like the 8052, can compete is right where the 8052 lives; at the smallest size of microcontroller that is useful. And the 8052 is a very simple design, it doesn't have a bus with a bunch of strict timing and feature requirements that is going to keep the complexity and heat up. They can get the full benefit of both modern processes and modern design, because compatibility is much easier.

      You would have to create a whole new architecture and simple make it support the x86 instruction set for convenience. Which is probably over twice as much work as creating a new architecture by itself. And now realize that ARM has already been doing that for 30 years, does it really well, and already licenses it to everybody. That's the thing; the harder work that you'd be saving has already been done, and is cheaper to produce.

      The reason IRQs were a PITA was because of software, but adding more is going to increase cost. Hardware interrupts start to get expensive if you want a lot of them. And you're redesigning the chip for that, see above.

      If you want to play games with RAM to avoid bit boundaries, your code complexity goes through the roof and you give up portability and you have to choose between hurting performance really bad, or else losing backwards compatibility. These are solved problems, with known tradeoffs.

      Point is you could have a complete ASIC in a TQFP package that would consume minimal real estate on a PCB, while providing everything the system needs.

      Newer designs already do all that, and "everything the system needs" is simply different for an SoC than for an x86 system. For about $6 single quantity ($3 at quantity) I can get an ARM system with 4MB flash, wifi, modern buses like I2C and a few hardware interrupts. If I want more features, I can get something similar from TI for $5 more that has more features and a huge number of hardware interrupts. And they're ARM, so you can already reuse most of your old x86 code! Having a compiler that supports the old code is way better than having a CPU that supports and ancient bus.

  18. Deploy golden parachutes by Anonymous Coward · · Score: 0

    Why bother innovating when you are close to retirement and you have plenty of life left in your same-old-thing-only-slightly-faster business model? Intel is the very epitome of a top-heavy business, and firing a few IoT "braves" solves nothing with so many overpaid "chiefs" running about.

  19. It was simply price v ARM by Anonymous Coward · · Score: 0

    It was hard to compete when a mfr could get an entire ARM enabled board for the cost of an Intel chip...

    Did Intel run into the end of Moores law? Probably more that Otelenni made the call 10+ years ago not to go after the iPhone cpu market as 'the numbers weren't there'.

    1. Re:It was simply price v ARM by unixisc · · Score: 1

      But at the process nodes that Intel is at today, couldn't Intel easily build an entire legacy 386SX based legacy computer on one of their Altera chips for less than the cost of an ARM board?

  20. overkill by DrYak · · Score: 1

    The 386SX? If they just took that design, added some level 1 cache and put it on their current most inexpensive process, they'd be optimal for it.

    That would be extremely over-complex.
    x86 ISA isn't exactly a lean architecture and instruction set.
    Modern ARM can do much better with a small transistor foot print.

    But too bad, Intel discontinued their StrongARM serie.

    Why wouldn't a 386 be much of a selling point, when every embedded OS out there - not just Linux or BSD, but also things like FreeDOS, QNX, Minix, Minuet, et al exists for that platform.

    The main selling point of a x86 chip would be code compatibility.
    But nobody sane in their mind is going to try to run Windows XP on a IoT device.
    All the other OSes are also available on ARM.

    The other point where x86 shines is raw performance on high range CPUs (simply because Intel and AMD [x86] are the only company spending R&D money on optimizing chips for that segment. Everybody else - Apple, Qualcom, etc. - are optimizing for the embed market)
    but that's absolutely NOT what's needed on IoT devices.
      If one is looking for flexibility in number of hardware sources, one can limit themselves to Linux & BSD and go look there. If one is looking for flexibility in the choice of OS platforms, then it makes sense to go w/ 386. Only question - is Intel still the only game in town, or does Via or SiS still have their solutions?

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:overkill by TechyImmigrant · · Score: 1

      >x86 ISA isn't exactly a lean architecture and instruction set.
      >Modern ARM can do much better with a small transistor foot print.

      In which universe is the ARM instruction set "lean"?

      Every instruction is 32 bits long, clogging one's instruction bandwidth. A little Huffman encoding goes a long way. Gates are cheap, IO bandwidth is not. The benefits of the regularity of RISC instruction sets were quickly lost as gates got smaller and the compute/IO bandwidth tradeoff changed in favour of compute.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    2. Re:overkill by English+Oxygen · · Score: 1

      > Every instruction is 32 bits long, clogging one's instruction bandwidth.

      ARM Cortex-M processors use 16-bit instructions (Thumb and Thumb-2). They've had a while to optimise the instruction set for embedded and SoC.

    3. Re:overkill by unixisc · · Score: 1

      The 386SX? If they just took that design, added some level 1 cache and put it on their current most inexpensive process, they'd be optimal for it.

      That would be extremely over-complex. x86 ISA isn't exactly a lean architecture and instruction set. Modern ARM can do much better with a small transistor foot print.

      But too bad, Intel discontinued their StrongARM serie.

      Actually, that chip was rebranded as Xscale, and sold to Marvel 10 years ago. It's not that Intel didn't try working w/ it.

      Why wouldn't a 386 be much of a selling point, when every embedded OS out there - not just Linux or BSD, but also things like FreeDOS, QNX, Minix, Minuet, et al exists for that platform.

      The main selling point of a x86 chip would be code compatibility. But nobody sane in their mind is going to try to run Windows XP on a IoT device. All the other OSes are also available on ARM.

      The other point where x86 shines is raw performance on high range CPUs (simply because Intel and AMD [x86] are the only company spending R&D money on optimizing chips for that segment. Everybody else - Apple, Qualcom, etc. - are optimizing for the embed market) but that's absolutely NOT what's needed on IoT devices.

      Uh, no. QNX is x86 only, IIRC (unless RIM ported it for Blackberry), and Minuet is written specifically in x86 assembly, so that it could create the most compact code. While Minix is FOSS, it has only been/is being ported to the Beaglebone: if you wanna run it on a Raspberry or an Arduino, good luck!

      I also wouldn't call the tablet & phone markets 'embedded' - they are more of wireless consumer goods. Different segments from electronics that are embedded for all sorts of process control, be it home climate controls and so on. Also, does Apple sell the A series chipset at all - I thought they just use it for internal consumption. Qualcomm has as captive a market as Intel did in PCs - any phonemaker who wants to support not just current 4G & 3G but also legacy architectures like CDMA would have no alternative to Qualcomm, since Intel isn't licensed to include legacy compatibility on their chipsets

    4. Re:overkill by TechyImmigrant · · Score: 1

      > Every instruction is 32 bits long, clogging one's instruction bandwidth.

      ARM Cortex-M processors use 16-bit instructions (Thumb and Thumb-2). They've had a while to optimise the instruction set for embedded and SoC.

      Yes. Thumb. A major mode switch to use a smaller instruction. I've integrated a few ARMs into chips (first the ARM7TMDI) and they were pretty much a nightmare to bring into line with normal OS practices. 15 years later, everyone seems to think this cranky instruction set and system model is normal, because it's what they grew up with. Yet the funky interrupt model, the funky mode switching, the lack of standard device discovery (that Linus Torvalds complained about) and bandwidth hungry instructions do not stand together as an example of a great CPU architecture, just a successful one.

      The 68000 series didn't keep up, by it was an order of magnitude easier to work with. Especially the microcontroller variants. That stuff matters when you are building products. Atmel do some nice CPUs for the low end that are a pleasure to use.

      ARM got their position lodged in our phones by being willing to sell their CPU core at a time in the early 90s when few others would. Back then we were crying out for a PC-on-a-chip, so we could develop a phone radio on a PC card run the software on the PC, then just port directly to the same machine on an ASIC with a PC+phone logic. But the answer was no. GSM back then was heavy lifting. No amount of money would get you access to that core on your ASIC. Meanwhile, ARM was there in Cambridge, ready and willing to take your cheque. If ARC had been a bit quicker, they would have been the incumbent. The ARC CPU certainly was much better (faster, easier, smaller) than the ARM at the time. They sold soft macros too, compared to ARM's hard macros with nightmarish memory bus timing.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
  21. I(di)oT by Anonymous Coward · · Score: 0

    I(di)oT

  22. LAWL by sexconker · · Score: 1

    So predictable that an AC comment on Slashdot predicted it a few weeks ago.

  23. Turns out IoT is not, in fact, the future by Anonymous Coward · · Score: 0

    It turns out that the IoT fad died even faster than the Pokemon fad. I don't need to get a text message from my toaster reminding me to clean the crumb tray. Neither does anyone else.

  24. Re:ta30 by Anonymous Coward · · Score: 0

    Even a VIP needs to VIPoo!

  25. as usual by Anonymous Coward · · Score: 0

    Intel typically fails to see any project through to completion or success that isn't directly tied to its core and xeon processors. I spent 25+ years there and this happens over and over: intel gets excited about something they are losing at, throws a few billion dollars of marketing and new jobs at it, then 18-24 months later when it fails to turn a profit they pull the plug and redeploy. they tried this with teleconferencing in the 90's, a server group that was like "iMac for servers" in the early 2000s, handhelds, integrated PCs, "maker chic"... decades of fail. all they know how to do is make faster processors. which is nothing to sneeze at, but i still have a good chuckle at how they claim they are going to dominate some other market, and always, 100% fail.

  26. wow. just wow by Anonymous Coward · · Score: 0

    Okay. 135+ tech employees couldn't even match what junk routers have been doing for years. At Intel.

    It really isn't that hard picking up any o.s. with documentation and figure out what would bring i.o.t. to life. Watch a few scifi movies about robots being helpful to start. "Hal, open the pod bay doors". That comes to mind. Or, "computer, lights". Hell even that goofy robot from that Alley Sheedy movie is doable. Just look at the kids' toys these days. Voice recognition has been shaky usable for over twenty years now. Dos had it, OS/2 had it, I even remember owning a cartridge for the c64 that worked kinda nice.

    Hmm. You'd think Intel would have seen any of those?

    Parallel and serial ports have run the backbone of most industrial and scientific devices for over two decades now. Collecting data on this, and pushing the cart of that, and automating everything in sight already. And I'm looking at this from a programming standpoint, not a h/w engineer one. Even if these guys were incompetent, you'd think they could have done a working tricorder with that pile of overpriced bits to propel interest.

    Either management is soooo entangled with promoting x86 that they mismanaged it to death, or ...

    Maybe the foreigners are not as clever or competent as management won't pay us to be.

    Maybe a scary mix of both.

    This is the sad true death of the American Dream(t.m.)

    I'm putting up with the weirdness of the raspberry pi just because I just didn't think Intel could 'do' microcontrollers. Glad I wasn't wrong.

    They earned this for sure.

  27. Silicon footprint by DrYak · · Score: 1

    >x86 ISA isn't exactly a lean architecture and instruction set.
    >Modern ARM can do much better with a small transistor foot print.

    In which universe is the ARM instruction set "lean"?
    Every instruction is 32 bits long, clogging one's instruction bandwidth.

    In my universe where the *perfomance* that interests me is the power budget of the IoT device, which is rather closely related to how much the chip maker can cran in as little silicon as possible. the current generation of ARM chips simply provide more with less silicon (among chief reasons : the RISC instruction sets, and the constant instruction width that you've criticized makes the instruction pipeline much simpler) (whereas x86 chips tend to be a RISC-ish backend with a huge x86 interpreter on top of it) (in an over simplified way: ARM just gets rid of the complex instruction decoder, which spares silicon and ends up sparing a few watts which is critical for a IoT device - hence Intel not being king there - whereas nobody give a fuck for a couple of watts on a 200W monster - hence it not being a draw back on high-end desktops and servers).

    On the other hand, memory is cheap, flash is cheap too and it doesn't eat that much into the power budget of IoT.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]