5 ms·

I believe it comes from here: https://blogs.windows.com/windowsexperience/2016/01/15/windows-10-embracing-silicon-innovation/ https://blogs.windows.com/windowse

I believe it comes from here: https://blogs.windows.com/windowsexperience/2016/01/15/windows-10-embracing-silicon-innovation/ https://blogs.windows.com/windowsexperience/2016/01/15/windo... "Going forward, as new silicon generations are introduced, they will require the latest Windows platform at that time for support....For example, Windows 10 will be the only supported Windows platform on Intel’s upcoming “Kaby Lake” silicon, Qualcomm’s upcoming “8996” silicon, and AMD’s upcoming “Bristol Ridge” silicon."

revelation 10y ago
This isn't saying anything either.
- colejohnson66 10y ago
  That clearly says that if you have a Kaby Lake CPU, you can only run Windows 10. Not 7. Not 8 or 8.1. Only 10.
  - scott_s 10y ago
    The difficulty people have with the statement is that the relationship is inverted: it's Windows 7 which does not support the new processor. The processor does not have some explicit blacklist that prevents Windows 7 from running. Rather, the processor does things that Windows 7 was never designed to deal with, as Windows 7 is a decade old.
    - 0x0 10y ago
      But can you run MS-DOS on it? Lilo? Grub? Does it no longer boot in 8086 mode? If windows 10 is the only supported OS, why not get rid of 16bit real mode and 32bit protected mode, leaving only 64bit long mode as the only execution environment?
      - rincebrain 10y ago
        While Microsoft has been trying to push for being able to run 64-bit Windows without the 32-bit parts installed (starting with 2008 R2, the WoW64 bits are optional for Server Core), I'm pretty certain that you can't (yet) get a complete interactive environment using only 64-bit mode. Just looking at the list of Microsoft applications currently running on my 64-bit Win10 desktop, there's still at least a half-dozen different Windows desktop services that are running in 32-bit mode - including the "Microsoft Bing Service". I'm sure they'll eventually want to reach a point where they can cut that off, presuming that a hybrid approach like x32 doesn't turn out to have phenomenal benefits, but it's not yet here.
        0x0 10y ago
        When I said removing 32bit protected mode, I meant the original 32bit protected mode which is now called "legacy mode". I believe you cannot exit long mode after enabling it, but there's a sub-mode in 64bit long mode that allows running in 32 bits - which is distinct from legacy 32bit protected mode. I guess I should have said, "leaving only long mode" (which can be 64bit or 32bit)
        rincebrain 10y ago
        Ah, my apologies. I wonder how much they'd actually save, in die area, if they removed 32bit mode while leaving in the ability to run 32bit code in 64bit mode. If it's just decoding to similar microops with slightly different parameters depending on the mode they're returning to, probably not that much, except in the decoder itself...
- rincebrain 10y ago
  Nobody's been clear on how this will be accomplished, but I can really only see three options. 1) Actual blacklisting of the CPU in a Win7 update. This would be foolish at best, since people would just decline the patch or use modified install media. 2) Lack of support through lack of drivers for new hardware Maybe the most likely, but still not guaranteed to prevent people from running Windows 7 and either working around missing support or disabling the signed driver requirement and hacking up newer drivers until they do what's desired on Win7. 3) Requiring Win7 backward-compat hooks in BIOS/UEFI not be present on Kaby Lake+ motherboards. This would probably be the most effective, though it would require more coordination and signoff than I'd necessarily guess they'll muster.
benaadams 10y ago
Probably means it won't have microcode updates to patch the CPU https://support.microsoft.com/en-gb/kb/3064209 https://support.microsoft.com/en-gb/kb/3064209
szatkus 10y ago
Both Kaby Lake and Bristol Ridge are APUs. Probably it's about graphics part. There is no breaking changes in these CPUS.

revelation 10y ago

This isn't saying anything either.

colejohnson66 10y ago
That clearly says that if you have a Kaby Lake CPU, you can only run Windows 10. Not 7. Not 8 or 8.1. Only 10.
- scott_s 10y ago
  The difficulty people have with the statement is that the relationship is inverted: it's Windows 7 which does not support the new processor. The processor does not have some explicit blacklist that prevents Windows 7 from running. Rather, the processor does things that Windows 7 was never designed to deal with, as Windows 7 is a decade old.
  - 0x0 10y ago
    But can you run MS-DOS on it? Lilo? Grub? Does it no longer boot in 8086 mode? If windows 10 is the only supported OS, why not get rid of 16bit real mode and 32bit protected mode, leaving only 64bit long mode as the only execution environment?
    - rincebrain 10y ago
      While Microsoft has been trying to push for being able to run 64-bit Windows without the 32-bit parts installed (starting with 2008 R2, the WoW64 bits are optional for Server Core), I'm pretty certain that you can't (yet) get a complete interactive environment using only 64-bit mode. Just looking at the list of Microsoft applications currently running on my 64-bit Win10 desktop, there's still at least a half-dozen different Windows desktop services that are running in 32-bit mode - including the "Microsoft Bing Service". I'm sure they'll eventually want to reach a point where they can cut that off, presuming that a hybrid approach like x32 doesn't turn out to have phenomenal benefits, but it's not yet here.
      - 0x0 10y ago
        When I said removing 32bit protected mode, I meant the original 32bit protected mode which is now called "legacy mode". I believe you cannot exit long mode after enabling it, but there's a sub-mode in 64bit long mode that allows running in 32 bits - which is distinct from legacy 32bit protected mode. I guess I should have said, "leaving only long mode" (which can be 64bit or 32bit)
        rincebrain 10y ago
        Ah, my apologies. I wonder how much they'd actually save, in die area, if they removed 32bit mode while leaving in the ability to run 32bit code in 64bit mode. If it's just decoding to similar microops with slightly different parameters depending on the mode they're returning to, probably not that much, except in the decoder itself...
rincebrain 10y ago
Nobody's been clear on how this will be accomplished, but I can really only see three options. 1) Actual blacklisting of the CPU in a Win7 update. This would be foolish at best, since people would just decline the patch or use modified install media. 2) Lack of support through lack of drivers for new hardware Maybe the most likely, but still not guaranteed to prevent people from running Windows 7 and either working around missing support or disabling the signed driver requirement and hacking up newer drivers until they do what's desired on Win7. 3) Requiring Win7 backward-compat hooks in BIOS/UEFI not be present on Kaby Lake+ motherboards. This would probably be the most effective, though it would require more coordination and signoff than I'd necessarily guess they'll muster.

benaadams 10y ago

Probably means it won't have microcode updates to patch the CPU https://support.microsoft.com/en-gb/kb/3064209 https://support.microsoft.com/en-gb/kb/3064209

szatkus 10y ago

Both Kaby Lake and Bristol Ridge are APUs. Probably it's about graphics part. There is no breaking changes in these CPUS.