Александр
Александр
Hm, it's an unexpected request! Well, I never worked with ARM, but what features would be useful in ARM implementation?
@lucash4x0r, what exactly happens on 'bad' chipsets?
@lucash4x0r, yes, you can, but how do you change this?
@lucash4x0r, oh, wait, 0xF0000..0xFFFFF - it's a physical range, not virtual. You should map it to virtual address space using MmMapIoSpaceEx. You will get a kernel virtual address and ability...
@lucash4x0r, check whether HVCI/DeviceGuard are disabled on your desktop. And check what happens with something like http://rweverything.com/
@lucash4x0r, try to edit this memory using RWEverything. Does it work?
@lucash4x0r, I don't know exactly, but it seems that your chipset rejects all writes to this memory
@lucash4x0r, could you give me a link?
@lucash4x0r, thanx a lot. Seems interesting, I'll check it and will add this to the Kernel-Bridge 2: 
@lucash4x0r, try MmGetVirtualForPhysical or remove PAGE_NOCACHE from MmMapIoSpaceEx