Related
Hi
I was just wondering if anyone knew of a linux build for the Kaiser?
that would be awsome...wouldnt it be something like...Android? wait is android on linux....?...time visit google
Kaiser proved to be a tough nut
The MSM7500 phones can already boot linux ...
The Kaiser technical data is already added to wiki
cr2 said:
Kaiser proved to be a tough nut
The MSM7500 phones can already boot linux ...
The Kaiser technical data is already added to wiki
Click to expand...
Click to collapse
wait what do you mean MSM7500 the processor? or a brand of phones?
thentertaina said:
wait what do you mean MSM7500 the processor? or a brand of phones?
Click to expand...
Click to collapse
MSM7500 CPU is used by many new HTC CDMA phones, and their hardware setup
seems to be mostly identical.
Ubuntu is also making a mobile OS. Right now it's aimed at Intel's chips.
http://www.ubuntu.com/products/mobile
nice link really looking forward to mobile ubuntu and maybe redhat or fedora some day
cr2 said:
MSM7500 CPU is used by many new HTC CDMA phones, and their hardware setup
seems to be mostly identical.
Click to expand...
Click to collapse
so they use different processors for gsm and cdma......i would have thought they just have different hardware and code for that hardware
thentertaina said:
so they use different processors for gsm and cdma......i would have thought they just have different hardware and code for that hardware
Click to expand...
Click to collapse
It is a different processor because the qualcomm chip has two cores. One is the radio and the other for the OS and other functions. Since the radios have to differ between gsm and cdma, they must use different processors.
hello,
at the moment, ubuntu project is just for intel device built with atom processor and is just specific device built by intel ( intel phone), but in the futur probably became reality for another device...
tyante said:
It is a different processor because the qualcomm chip has two cores. One is the radio and the other for the OS and other functions. Since the radios have to differ between gsm and cdma, they must use different processors.
Click to expand...
Click to collapse
ahh that makes sense.
tyante said:
It is a different processor because the qualcomm chip has two cores. One is the radio and the other for the OS and other functions. Since the radios have to differ between gsm and cdma, they must use different processors.
Click to expand...
Click to collapse
Had the TyTN 1 also had a dualcore processor?
Qualcomm or not both cores are ARM based and there are plenty versions of ARM linux. It's reverse engineering the drivers for all the various parts of the device that is hard, but it is definately not insurmountable.
The Mio A701 has a pretty usable linux port, everything works on it including the phone part and this is a fairly recent device.
http://handhelds.org/moin/moin.cgi/MitacMioA701
Looks like someone is working on this already:
http://handhelds.org/moin/moin.cgi/SupportedHandheldSummary
Android is just a layer on top of Linux and should be straight forward to port once some devices are out.
DeepThought said:
Had the TyTN 1 also had a dualcore processor?
Click to expand...
Click to collapse
Hermes uses 2 separate CPUs: Samsung S3C2442 and Qualcomm MSM6275.
thentertaina said:
so they use different processors for gsm and cdma...
Click to expand...
Click to collapse
CDMA uses MSM7500, and WCDMA(UMTS) is MSM7200.
They have different DSP parts.
I found something very promising...
http://youtube.com/watch?v=XbgzgJgTY8I
Anyone know who the person on the youtube video is?
marbalon said:
I found something very promising...
http://youtube.com/watch?v=XbgzgJgTY8I
Click to expand...
Click to collapse
I wouldn't take too much from that video.
Firstly, they never show linux booting all the way...becuase it probably doesn't..no drivers to access anything.
Secondly they are launching linux from within WM6...basically emulating it. Even though a VM for WM6 that allows the booting of other OSes sounds like a neat idea, I can't believe it would be practical. The phones run slow enough without any emulation.
When you see a video of a straight boot all the way to a command shell...now that would be the beginning of something usable...
Personally, I don't think I would want linux on my Kaiser. I suppose if everything worked (touch flo, keyboard, all data connections, gps) and it had a faster speed then I would think about it. Otherwise I don't see the point. No one is trying to hack into my mobile phone...I don't have very good network options (no LAN, no promiscuous wi-fi) to use all the good linux tools. And, as much as I like command prompt...not on my Kaiser/Tilt.
If there are any valid uses (other than novelty) to have linux on a Kaiser I'd like to know, because it would probably be worlds easier to develop a WM application to get the functionality that you think linux would provide.
Don't get me wrong...I'd try it the day a first stable linux ROM came out, but if it didn't have all the features above, I would soon be flashing back to WM6+
bengalih said:
I wouldn't take too much from that video.
Firstly, they never show linux booting all the way...becuase it probably doesn't..no drivers to access anything.
Secondly they are launching linux from within WM6...basically emulating it. Even though a VM for WM6 that allows the booting of other OSes sounds like a neat idea, I can't believe it would be practical. The phones run slow enough without any emulation.
Click to expand...
Click to collapse
Your first point is probably right, your second is not quite. The software used to boot linux on Windows Mobile devices is called Haret and can be seen in that video, it is not an emulator but a boot loader.
http://www.handhelds.org/moin/moin.cgi/HaRET
The video stops because the rest of the drivers aren't there yet, probably. It's a pretty good start though.
ahh thanks Miles, i was unaware of that application.
I was squinting to try to read ANYTHING on that you tube screen. All i could really make out was the penguin I assumed based on the GUI look of it that they were in WM already.
I hate threads like this. Just when you think damn someones done it its a question not an answer lol. Got ubuntu on my laptop yellow dog on my ps3 would love a distro on my kaiser
I am just wondering. I am a huge fan of android and am using Desire HD now. But I was wondering if a dual core tablet can be installed with Windows 7? I only need the W7 just to sync with my android phone. Maybe I can install RUU or any other ROMS in the future using my tablet.
Not quite sure what your asking here... Dual Core x86 processor tablets would probably run windows 7, Dual Core Arm Processor can not as windows is x86 processor specification and Android is Arm. All android devices are compatible to the best of my knowledge with windows 7 so if your worried about getting an android tablet and not having support for it then don't worry. Other than that i hope i answered your question.
Moved to general
Windows 7 can only be installed on x86 systems. Older versions of Windows NT could be installed on other CPUs like Alpha and Power PC and Windows server has a version that can run on Itanium/IA-64 but they are dropping it.
Microsoft has claimed Windows 8 will run on ARM systems so when it comes out you may be able to use it but most programs won't run it.
The Old One said:
Windows 7 can only be installed on x86 systems. Older versions of Windows NT could be installed on other CPUs like Alpha and Power PC and Windows server has a version that can run on Itanium/IA-64 but they are dropping it.
Microsoft has claimed Windows 8 will run on ARM systems so when it comes out you may be able to use it but most programs won't run it.
Click to expand...
Click to collapse
Does the dual boot Viewpad 10 use (x)86 processors? Is Android 1.6 the last or latest Android OS that can run on the (x)86 platform?
I'm just curious as to how Viewsonic gets both OS's to run on viewpad 10 platform, so this looks like a good place to ask about that.
Yes, Atom x86 CPU and Android 1.6 (last version to support x86).
Does the dual boot Viewpad 10 use (x)86 processors? Is Android 1.6 the last or latest Android OS that can run on the (x)86 platform?
I'm just curious as to how Viewsonic gets both OS's to run on viewpad 10 platform, so this looks like a good place to ask about that.
Click to expand...
Click to collapse
GaryHypnosis said:
Does the dual boot Viewpad 10 use (x)86 processors? Is Android 1.6 the last or latest Android OS that can run on the (x)86 platform?
I'm just curious as to how Viewsonic gets both OS's to run on viewpad 10 platform, so this looks like a good place to ask about that.
Click to expand...
Click to collapse
Viewsonic's Viewpad 10 uses the intel atom cpu to my knowledge. I don't know the details behind it but have read that Android 1.6 is the last version of Android that can run on x86 architecture. Maybe a dev. will be able to explain that part.
It would have made lots of sense for Google to make 2.x and up compatible with x86/x64 but I suppose there may be politics involved (imho, it can't be much else, since Linux runs on everything and Android is based almost entirely on Linux)....or maybe it would be more work or too much code needed. Since 2.2 is meant primarily for phones first, maybe they didn't see a need to bloat it up.
I wouldn't mind if Android needed a 650MB-1GB install as long as it works well.
Here's a snippet, you will be able to find more if you google it....though I can't find a reason as to why myself.
Hi,
I don't know if VS did their own work or may have used stuff from the Android X86 project:
http://www.android-x86.org/
or something similar (I think that there are other efforts like this)...
As you can see, the project is currently on 1.6, but:
http://www.android-x86.org/#What_we_are_working_on_now
says their working on Froyo:
What we are working on now
Port Froyo to x86 (froyo-x86 branch)
OpenGL hardware accelerator to froyo-x86 (olv, cwhuang)
New x86 toolchain (cwhuang)
Ethernet update (Yi)
Automount for new vold (cwhuang)
New target sparta (Doug)
New target viewpad10 (Al Sutton)
New target viliv s5 (okwon)
Mplayer porting (okwon
BTW, if you have a Windows PC, you can actually run that Android (1.6) on it. I had done that earlier, before getting my Gtab.
Jim
As one of the members pointed out, and if you check out the hands ons that have been done recently, ViewPad10 does indeed use Androidx86 project. GREAT News is, they just released Froyo-x86 (http://www.android-x86.org/releases/release_2_2) and there is a specific ISO for the ViewPad10. I actually just ordered 5 from one of my vendors (1 to keep and 4 to sell) so I am definitely going to pop that Froyo-x86 in mine and see how it whirls! I'm very excited by the prospects of a dual boot Froyo7 tablet!
Did you load the 2.2 iso onto one, and if so how well did it work? I just want to use a copy of android so I can use the apps I already bought for my phone.
Some of the latest so called 'dual-boot' tablets are actually going to be using an android virtual machine which will run within windows.
If anyone's comfortable compiling their own kernel and drivers then they stand a chance of 'rolling their own' VM otherwise unless someone with the knowhow takes up the banner for a particular device, I would consider this option out of reach.
Which tablet devices have you seen running an Android VM? I ran the 2.2 live USB on my VPad10 but it was missing wifi. Everything else seems to run great. Its fast and functional! Except the wifi. :-(
Sent from my HTC HD2 using XDA App
the v10 specific iso didn't support wifi?!?!?!?
VPad and Froyo
I've picked up a VPad10 and have tried upgrading Android to 2.2 and have found that the interface buttons seemed out of place . I had a hard time moving backwards through the various pages - I had to tap the upper right corner on the bar and tap a second time in order to move back to the previous screen.
I found the interface too different from the standard to make it useful. I've since reverted back to 1.6
I had difficulty loading the Froyo (.img.gz) version. I've tried opening the gz on my Linux machine (vcersus my Windows box) and still get the same problem. Can the Froyo beta be loaded as iso image like the others, it would make my life easier?
I placed an order for the 10" gtablet the other day. This thread saved me from some dissapointment by trying to save a couple bucks.
Sent from my GT-I9000 using Tapatalk
I dont understand much about the architecture of software, im asking this because i dont get it, why the processors of our devices cant understand the new kernel and the instructions of WP8. in my head, its exacly the same saying that our pc desktops processors couldnt run the new Windows 8. i would like to know what are the barriers in this case. So guys, what they would be in your opinion?
This was posted by a dude on Reddit.
Disclaimer: I work at Microsoft. But not on Windows Phone.
Windows Phone 7 was built on top of Windows CE kernel (the same as Windows Mobile, and for those who are young enough to remember, Pocket PC and Windows CE Handhelds - this was in 1997).
Windows Phone 8 is moving to NT kernel, the same one as your desktop operating system is using. NT kernel requires radically different hardware - specificaly, TLB mappings in pre-v7 ARM CPU contained logical addresses and this does not work very well on symmetric multiprocessor OS.
So older ARM CPUs did not work with NT kernel, and move to the different OS kernel required radical redesign of the OS. Also, of course the desktop/server OS kernel requires significantly more RAM.
With the large generational shifts it is not uncommon for OS to lose compatibility with old software. These shifts do not happen very often, but they do happen.
For example, Windows NT did not support PCs with 286 CPUs (which were rather common when it shipped), or with less than 12MB RAM (something that is easily upgradeable on a PC, but much more difficult with the phone). Similarly, Windows NT 3.5 dropped support for 386 family entirely.
For Microsoft to have, as you call it, "foresight", it would probably have to drop Windows Phone 7 altogether and go to NT-kernel based solution. It would not have made Phone 8 to appear any faster, however - it would just have lost 2 years.
Click to expand...
Click to collapse
http://www.reddit.com/r/gadgets/comments/vdjwe/designed_to_fail_all_windows_phone_7_handsets/c53rh01
I think that answers your question.
Beautifuly!!! Thanks!!
m125 said:
This was posted by a dude on Reddit.
I think that answers your question.
Click to expand...
Click to collapse
This answer is a complete bull****! MS already run NT kernel on the arm cpus for a years! This guy is referred to the "desktop" kernel but of course Apollo/WinRT/ (whatever the MS ****heads will call it in the future) has a different (from the desktop OS-es) kernel.
What the "older arm cpu" he's mentioned about??? Nokia Lumia 900 has Qualcomm APQ8055 Snapdragon cpu (google or wiki for that). What the hell "pre-arm"???
Sorry, it's not an explanation, just a stupid bull**** from ignoramus. He definitely needs a "radical redesign" of his brain
Oh c'mon, if our CPUs were the same old Qualcomms from Android 1.6 days I would believe it, but they are last-gen Snapdragons, goddamit!
I'm pretty sure Microsoft could support it as easy as adding two drivers, but it won't. Specially since all phones are the exact same hardware, with WP7.
The point about TLB mappings might be valid... if it weren't for the fact that these are all single-CPU, single-core processors (in WP7 devices). There's no need for a kernel to support SMP. In fact, you don't *want* a SMP kernel on such a processor; there are performance optimizations you can make for single-hardware-thead systems.
Historically, Microsoft has actually shipped two copies (per architecture) of the NT kernel on their desktop OS install media, one for SMP and one for single-core. The installer would use the correct one for the hardware. There is no technical reason that they couldn't do similar with WP8, shipping one NT kernel for single-core phones (which would be able to run on ARM v6) and one for multi-core (which would require ARM v7).
As for the RAM issue, that's a red herring. The RAM requirements of a basic MinWin system are far below the half-gig of WP7 devices. Even adding the phone's extra libraries and user interface, it should still be possible to implement msot if not all of the software features of WP8 while leaving a comfortable overhead for running and app or two at a time (that being all that WP7 officially allows anyhow).
@sensboston: The first that I'd heard of Microsoft running NT on ARM was 2010, when multi-core ARM v7 was already available.
Actually, I agree that the guy doesn't seem to know what he's talking about; according to Wikipedia (unreliable but in this case I see no reason to expect incorrectness), the Snapdragon processors use the ARM v7 instruction set anyhow.
@GoodDayToDie, last two days I've heard a lot of very different (but all BS and incompetent) explanations from MS employees... Seems like guys in marketing department don't have enough engineering knowledge, and can't announce any realistic-looking reason. But may be they don't have to: for general public some unknown "martian" words like "TLB mapping", "GDT and IDT" etc. sounds very "reasonable"
guilhermedsx said:
Oh c'mon, if our CPUs were the same old Qualcomms from Android 1.6 days I would believe it, but they are last-gen Snapdragons, goddamit!
I'm pretty sure Microsoft could support it as easy as adding two drivers, but it won't. Specially since all phones are the exact same hardware, with WP7.
Click to expand...
Click to collapse
I really agree with that!! how loudly do we have to yell? But in my point of view nothing about it will be done, microsoft need money and need for yesterday, and yes they will sacrificate the poor white sheeps (that would be us) and watch them bleed just to launch "a completely new OS" that our phones "doesnt support".
I am a beginner on this page. I am writing this to backup the other developers on this form. A lot of people who has been going around on the surface forum repeating over and over fat some functions will never work. I've been around modding phones since when Windows Mobile 3 came out back when I was in middle school. I remember when Windows Mobile came out a website called geekstoolbox.com whats the phone for many modders to build custom firmware for Windows Phones. I remembered and middle school it was difficult to make certain improvements because Windows Mobile phones were close systems. I remember then listen to visit on the forum who actually broken too the phone am I allowed a dump of data to flow in Internet of his phone start new custom ROM custom firmware revolution to begin. Afterwards, I begin saying revolutionary products such as wifi tether, Bluetooth tethering, Mobile sharing, and in custom OS. to those web visiting thi about s forum repeating over and over and over, that there would be no Windows based x86 programs on when does RT we'll be eating crow when it finally does happen within the next few months. I see it being possible when you consider if someone will, compile a virtual machine enabling many features of Windows 8 x86. Furthermore, suppose it becomes like parallels Macintosh. In addition, maybe someone will develop 8 translator package for Windows 82 windows Rt to understand each other's programs. all that I am saying is please do not be downers and out other people expressions about this tablet and is always
Sent from my SGH-T999 using xda premium
I meant to end by saying, please do not doubt other people's expressions about this templates capabilities in with the wish to see on this tablet because the possibilities are there and if someone desires it enough it will come to fruition.
Continuously be blessed signing out!
Sent from my SGH-T999 using xda premium
There are already two x86 emulators (Bochs and DosBox) for Windows RT. Bochs is slow to the point of being unusable, and DosBox is slow to the point of lagging while playing games from 1992.
x86 will likely never run (games) well on Windows RT, but it does in fact already run.
See,! It already possible . I have 1 questions, do they use virtual machines or do they do rely on the Internet
Sent from my SGH-T999 using xda premium
befreshshaveivorysalesoap said:
See,! It already possible . I have 1 questions, do they use virtual machines or do they do rely on the Internet
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
They use virtual machines, but they're slow to the point of complete uselessness. It takes half an hour to boot XP in them.
befreshshaveivorysalesoap said:
I meant to end by saying, please do not doubt other people's expressions about this templates capabilities in with the wish to see on this tablet because the possibilities are there and if someone desires it enough it will come to fruition.
Click to expand...
Click to collapse
Tempered with a dose of reality, when you acknowledge that even a dual core ARM cpu is still very underpowered to emulate a full x86 cpu/environment. If what you want is a good x86 experience, the Surface RT isn't what you want.
That's not saying you can't get a decent toy x86 environment, or really good recompiled for arm desktop apps. Those two work fine.
schettj said:
Tempered with a dose of reality, when you acknowledge that even a dual core ARM cpu is still very underpowered to emulate a full x86 cpu/environment. If what you want is a good x86 experience, the Surface RT isn't what you want.
That's not saying you can't get a decent toy x86 environment, or really good recompiled for arm desktop apps. Those two work fine.
Click to expand...
Click to collapse
Maybe not the full experience but something like WINE on Linux. Most people who buys the RT version aren't power PC users and don't require much anyhow , except for a few apps
befreshshaveivorysalesoap said:
Maybe not the full experience but something like WINE on Linux. Most people who buys the RT version aren't power PC users and don't require much anyhow , except for a few apps
Click to expand...
Click to collapse
Wine on x86 linux isn't emulating the CPU. This is a critical difference.
schettj said:
Tempered with a dose of reality, when you acknowledge that even a dual core ARM cpu is still very underpowered to emulate a full x86 cpu/environment. If what you want is a good x86 experience, the Surface RT isn't what you want.
That's not saying you can't get a decent toy x86 environment, or really good recompiled for arm desktop apps. Those two work fine.
Click to expand...
Click to collapse
I believe that all the Windows RT devices are quad core right now.
befreshshaveivorysalesoap said:
Maybe not the full experience but something like WINE on Linux. Most people who buys the RT version aren't power PC users and don't require much anyhow , except for a few apps
Click to expand...
Click to collapse
It's really very unlikely that any x86 program bigger than Notepad will ever be usability fast/stable. I'd go read up a bit on emulation and the downsides regarding speed with it. This is the same reason that android tablets, which are quite arguably far more suited for this, can't do anything better than emulate 20 year old OSes, and do that poorly.
netham45 said:
I believe that all the Windows RT devices are quad core right now.
Click to expand...
Click to collapse
d'oh! flip flopping between windows phone 8 and windows RT Yep, 4 arm cores. Still like trying to emulate a V8 with an inline4.
netham45 said:
I believe that all the Windows RT devices are quad core right now.
It's really very unlikely that any x86 program bigger than Notepad will ever be usability fast/stable. I'd go read up a bit on emulation and the downsides regarding speed with it. This is the same reason that android tablets, which are quite arguably far more suited for this, can't do anything better than emulate 20 year old OSes, and do that poorly.
Click to expand...
Click to collapse
Instead of emulating an entire OS, would anyone entertain the idea of a program translator; A program could be build with the libraries of some main OS'es. Within the translator, when an x86 program is called the programs determines what operating systems' library to use. The translator would then render a version of the program Windows with RT can understand.
Couldn't this be likely.
netham45 said:
There are already two x86 emulators (Bochs and DosBox) for Windows RT. Bochs is slow to the point of being unusable, and DosBox is slow to the point of lagging while playing games from 1992.
x86 will likely never run (games) well on Windows RT, but it does in fact already run.
Click to expand...
Click to collapse
I believe I no what the issue with these are.......... Bochs and DosBox do not allow users to control processing cores for each emulation. These emulators need to be updated to take advantage of this feature, it's a blessing for other OS'es
There's already a translator project much like what you describe, actually. It's early alpha quality right now, only able to run a few apps and those slowly and with stability problems, but it's a very promising proof of concept. The developer is using the DOSBox dynamic recompilation engine, optimized for THUMB-2 (ARM variant that Windows uses) with some hacks in it to remove support for stuff that only the kernel has to care about like page tables and whatnot (these hacks apparently substantially increase speed). The recompilation engine is not currently thread-safe, which means it has to run on a single core (although it's possible that the translated program itself might be able to run across multiple cores; I don't know for sure) but the possibility of fixing that is being investigated.
The project is on the Dev&Hacking sub-forum, and there's a download link for it and a (mostly playable) demo of Heroes of Might and Magic 3 as an example of what it can currently do.
Can someone point me in the duration to learn about building for ARM. I want to see if I can contribute. In school I am only learning about the x86 and x64 architectural
befreshshaveivorysalesoap said:
Can someone point me in the duration to learn about building for ARM. I want to see if I can contribute. In school I am only learning about the x86 and x64 architectural
Click to expand...
Click to collapse
Currently this is the porting method: http://forum.xda-developers.com/showthread.php?t=2096820&highlight=arm
Requires visual studio to cross compile from a desktop windows machine.
Disclaimer: This is an open discussion thread for How to do virtualization on Android! It's not a reference or guide! But hope this thread can lead us towards making a way to do it!
Intro: Once phones was a tiny piece of electronic device which was mainly used to talk and sending text messages! (I am talking about mobile phones off course! )
Then here comes smartphones like the symbian one and then iphones and Android!
They opened a lot more way to do on a device rather than only talking or texting!
But still we needed to rely on laptops or desktops to do extensive tasks which we couldn't do (yet) on smartphones!
The main reason was the lack of technology or the memory and processing power limitations on these device!
I remember I bought my first Redmi 2 at a cost of 200$ back in April 2015 which featured quadcore Qualcomm processor, 1GB of RAM and 8 GB of internal storage space!
But now the time has changed! Technology advanced exponentially! After 3 years of my first Xiaomi device, I bought another one (Mi A1) with almost the same price! Whuch features double (on the basis of cores) processors and 4X RAM and 8X internal spaces!
In the mean time on the mainstream computing counterpart, virtualization technology becomes so popular that if not all but most of the servers runs based on it! We have also docker now!
We can now use or test any software/OS on any device (mainstream computers off course) by the grace of virtualization!
On the other hand, Android devs still needs to do the hard work to port ROMs let the OS itself! And yet we can't run Windows on a Android device!
But wait! Android is also a Linux! Isn't it?
So, if Linux can run QUEMU/KVM, why not Android?
And most of the Android SOCs now are 64bit!
So, can't we just make it happen? Can't we just find a way to do virtualization and run any OS on a virtual environment right in our hand?
May be!
I don't know if any guys working on this or not!
But here's how to:
1) Enable virtualization support on kernel
2) Make an apps for Android for manging the virtual machines (like VirtualBox, VMWare etc.)
I think the Android kernels (most of them) supports virtualization already!
The hardest part is to make it compatible with the frontend Android! Which brings the apps and interfaces!
I know there's wine exist for Android! But that's just a complete different thing what I am talking about!
And I wasnt able to run wine on my tissot (Xiaomi Mi A1)!
Thanks everyone who is reading!
Give your valuable opinion and ideas!
Hope someone like @CosmicDan can make it!
ARMv8 (every phone) doesn't have hardware virtualisation extensions, so it would be as slow as emulation.
For that, we already have QEMU and KVM. But it's too slow to be of any practical use.
If you want proper virtualisation, you need ARMv8.1, which no phone has.
CosmicDan said:
ARMv8 (every phone) doesn't have hardware virtualisation extensions, so it would be as slow as emulation.
For that, we already have QEMU and KVM. But it's too slow to be of any practical use.
If you want proper virtualisation, you need ARMv8.1, which no phone has.
Click to expand...
Click to collapse
Hmm! I just realised the hardest part: it's ARM and not x86_64!
ProttoyX said:
Hmm! I just realised the hardest part: it's ARM and not x86_64!
Click to expand...
Click to collapse
That's emulation, not virtualisation.
You can use QEMU, Bochs or DOSBox to emulate x86 (x86_64 is probably impossible, idk but it's pointless to try). But it's dog slow and always will be.
CosmicDan said:
That's emulation, not virtualisation.
You can use QEMU, Bochs or DOSBox to emulate x86 (x86_64 is probably impossible, idk but it's pointless to try). But it's dog slow and always will be.
Click to expand...
Click to collapse
Hmm! Got it! This thing came into my mind when I was reading about servers based on ARM! Wondered if they provides virtualization/container service or not! And ARM provides more cores than x86_64! I guess it's it's related to RISC/CISC thing! Not sure though!
ARM servers uses ARMv8.1?
AND PLEASE DON'T MIND ABOUT ENDING EVERY SENTENCE WITH (!)! PLEASE!
No one can always be rude! ?
I am surely not!
Again thanks for what you’ve done for the tissot and other staffs! You are genius! ?
ProttoyX said:
Hmm! Got it! This thing came into my mind when I was reading about servers based on ARM! Wondered if they provides virtualization/container service or not! And ARM provides more cores than x86_64! I guess it's it's related to RISC/CISC thing! Not sure though!
ARM servers uses ARMv8.1?
AND PLEASE DON'T MIND ABOUT ENDING EVERY SENTENCE WITH (!)! PLEASE!
No one can always be rude! ?
I am surely not!
Again thanks for what you’ve done for the tissot and other staffs! You are genius! ?
Click to expand...
Click to collapse
Yes those ARM servers would be 8.1. It's not so much a RISC vs CISC thing but more an SoC vs CPU thing. Our devices are SoC's - sure they have many GHz and cores but they're still a lot slower that a proper CPU which has countless of extensions designed for accelerating tasks, and have more IPC capability and other such things (in short GHz/core count is comparable across different platforms or architectures, it's more relative than that). Our SoC's simply don't have those extensions that would make this feasible.
CosmicDan said:
ARMv8 (every phone) doesn't have hardware virtualisation extensions, so it would be as slow as emulation.
For that, we already have QEMU and KVM. But it's too slow to be of any practical use.
If you want proper virtualisation, you need ARMv8.1, which no phone has.
Click to expand...
Click to collapse
Every ARMv8,and even ARMv7 has.On v8 it's called EL2 while on v7 it's HYP mode.However the biggest headache is that most SoC vendors do not allow users to enter it even with bootloader unlock.
On Qualcomm there are no way except a low level powerful exploit. On Exynos it is possible,needs a specific SMC to trustzone,and can be done only with an unlocked bootloader with custom kernel.
fxsheep said:
Every ARMv8,and even ARMv7 has.On v8 it's called EL2 while on v7 it's HYP mode.However the biggest headache is that most SoC vendors do not allow users to enter it even with bootloader unlock.
On Qualcomm there are no way except a low level powerful exploit. On Exynos it is possible,needs a specific SMC to trustzone,and can be done only with an unlocked bootloader with custom kernel.
Click to expand...
Click to collapse
do you have any references links on this? maybe a cve for the qualcomm exploit?