I don't know anything, except that AMD64 introduced a lot more than just a bigger address space. IA32 is really not a good/modern ISA, and it would be quite strange to see Intel falling back 10+ years. one real register, stack-based x87, no vectorization, etc. at the time, 64b extensions were justified as not adding a lot of chip complexity - of course that's relative to OoO/superscalar stuff.
At least according to a few software engineers I asked about this subject, symantec and wind river doesn't offer something unique security-related. It's mostly branding.
I wonder if this is the only benefit for this chip, or are there others planned?
Getting better opportunities on the security and embedded internet stack because of very long stay in the computing environment will be a very good plus point for Intel on getting proven in IoT Processor segment.
I am particularly curious to see what packaging options this device will come in. I am wondering if this product is aimed at the Cortex M market, or the lower end of the Cortex A series? If it is aimed at the M, say M4F with a higher clock speed, it would be interesting to see this type of device in a QFN and QFP. If it is competing with the A series, I expect that this will only be available as a BGA.
I will be very much interested to hear this. Some of the Cortex M devices are reaching this level of performance. If Intel comes down this far, and QFN/QFP packages are available, I could see this being a possible device that a hobbiest could use. I will be very interested to see more about this device.
Happy to hear that this tiny chip could give 486, Pentium kind of performance, that would be great!! Will this be somewhere close to the SoC launched by AMD recently: G-series SoC? Probably having lower performance and features than that?
The part that scares me is "...suggesting it is more of a rushed trial balloon than a nailed-down product and strategy."
I would dare not think about using it if there are no clear strategy and a clear road-map. Any tentative timeline announced for its release?
It seems to me that it would make sense to strip off legacy support in a product like this. Why carry along MS-DOS compatability and segmented memory models when they are competing with ARMs that have a much cleaner architecture? The x86 has been overdue for cleaning out the attic for quite a while. Does anyone know if that is what they are doing here?
The 80376 was replaced by the 80386EX, which still kept the static core capable uf running at low clock speeds all the way down to halt to save power. But it also kept the 26-bit addressing, so wouldn't be appropriate for re-implementing at a smaller process size without a major update. But I do think it is probably a shrunken older core. I chose the P54C because it has already been worked on for the Single-chip Cloud Computer project and Larrabee.
Considering the only requirements we know from the article was "to offer a remote maintenance capability with high security." it's rather far fetched to claim a "poor technical decision" as you maintain. There are lots of reasons, besides the level of security provided, which would come into play in the decision by Daikin; think ease of use, maintainability, support, etc.
Using your reference design for a tablet with military grade security is not revalent as this is not a tablet, not needing to meet military anything, and only "high security."
And, no, I'm not associated with Intel, Freescale, ARM, or anyone else; I'm a retired engineer with well over thirty years experience designing embedded systems.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.