On Sun, Nov 13, 2016 at 1:55 PM, Alexander Graf <[email protected]> wrote:
>
>
> On 13/11/2016 18:48, Tony Su wrote:
>>
>> Probably not possible, but a simple Google search returns these hits...
>>
>> A Windows RT Jailbreak tool
>> http://forum.xda-developers.com/showthread.php?t=2092158
>>
>> You can try turning off "secure boot" in your BIOS settings
>>
>> http://venturebeat.com/2013/02/06/yes-you-can-run-linux-on-your-microsoft-surface-pro/
>>
>> And, applying general principles without at all looking at how an RT
>> boots, I'd assume that it should be possible to chainload the Windows
>> bootloader like x86 Windows. This assumes that the RT bootloader is
>> likely the same as x86 Windows bootloaders so can be modified the same
>> way. Don't know why there are no hits of anyone trying to do this.
>
>
> Well, IIUC the jailbreak came years after release, so hardware was already
> not terribly interesting at that point. Also there are much more hackable
> alternatives around, so people never really cared.

Worse.  The jailbreak came out early on, but it only allowed users to
run unsigned userspace code inside RT.

No significant value to a Linux hacker.  And the jailbreak only works
on the old RT 8 release, and probably and unpatched RT 8 OS at that.
It definitely doesn't work on the Surface RT I'm working with.  (  I
tried it. :)  )

I've read nothing that says an unsigned kernel can be booted on a
Surface RT.  It's either do it right, or don't do it.

> However, I'm not going to stop you from porting anything over :). Patches
> are always welcome and if you manage to make Linux and openSUSE work on your
> Surface, I'm happy to help you integrate that work in our code stream.
>
> Keep in mind though that the work necessary to get Linux ported to an
> undocumented new platform is above the 1 man-year level. If you know exactly
> what you're doing and have prior experience in such porting efforts.

Seriously?  That is unbelievably hard.

> Alex

Greg
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to