I hope they drop this on the surface 2. It would save it from being a paper weight.
Windows 10 on ARM
11–20 of 290 posts
Re: Windows 10 on ARM
#12If that runs great on phones, and has virtualization support for e.g. running ARM Linux guests, I would change both my Android phone and my Ubuntu laptop for one phone (e.g. Snapdragon 835 or better + 8-12GB RAM + 256GB flash + USB 3.0 OTG), using a dummy screen + keyboard as laptop replacement.
Re: Windows 10 on ARM
#13Does the x86/x64 cpu emulation work for JIT code or other self-modifying code? (Copy protected games, for example?) In the linked presentation they just briefly mention doing a load time(?) transpile of x86 to arm64 and caching the result on disk. What about exe packers that map memory rw then rx after unpacking, such as UPX?
Re: Windows 10 on ARM
#14I hope they drop this on the surface 2. It would save it from being a paper weight.
Was the SurfaceRT an ARM device? I have one collecting dust, would be nice if it got an update
Re: Windows 10 on ARM
#15I hope they drop this on the surface 2. It would save it from being a paper weight.
Edit: Apparently Surface 2 isn't AArch64, so probably not.
Re: Windows 10 on ARM
#16Re: Windows 10 on ARM
#17If that runs great on phones, and has virtualization support for e.g. running ARM Linux guests, I would change both my Android phone and my Ubuntu laptop for one phone (e.g. Snapdragon 835 or better + 8-12GB RAM + 256GB flash + USB 3.0 OTG), using a dummy screen + keyboard as laptop replacement.
I am not sure there is a huge gap from dummy screen + keyboard + battery to laptop and your not going to be able to power a laptop screen from a cellphone battery.
Re: Windows 10 on ARM
#18If that runs great on phones, and has virtualization support for e.g. running ARM Linux guests, I would change both my Android phone and my Ubuntu laptop for one phone (e.g. Snapdragon 835 or better + 8-12GB RAM + 256GB flash + USB 3.0 OTG), using a dummy screen + keyboard as laptop replacement.
Re: Windows 10 on ARM
#191. In the talk they claim that they get "near native" speed from the translation. Can we have some real number of what can be expected? What about warm up time?
2. Is the x86 translation layer only available in user space, or can x86 drivers be loaded for hardware that doesn't have arm drivers yet (or the manufacturer doesn't care about making them)
3. Are there any plans in the future for supporting x64 code as well in the translation layer?
Edit: One more:
4. Are there any plans on supporting Arm v7 in the future, e.g. with Surface/Surface 2 support?
Re: Windows 10 on ARM
#20Great potential for a Win10 phablet I can develop on that also lets me make phonecalls. Not for big projects, but an anywhere device. Does Win10 support non VoIP calls?