gx_saurav said:
This just in, After the recent hack of the iPhone firmware, the iPhone CPU is found. It is a 620 MHz ARM CPU (probabely made by Intel)
I was wondering now, why did Jobs removed JAVA MIDP 2 from iPhone saying that JAVA is slow & no one uses it. I looked at the ARM CPU specification iPhone uses & this CPU has dedicated architecture for JAVA means JAVA works at really high speed on this CPU not slow. HTC, Samsung also uses same ARM CPUs in there PDA. If a JAVA app crashes, only that instance of JVM crashes & not the whole phone.
The processor is a S3C600 , an ARM-11 based core.I always assumed that a Pxa320 would be powering the iPhone.I have worked with the previous versions of the Samsung Arm9 series and always found it lacking against the Pxa270 series anyways Pxa seried monopoly was going for a long time now and thus happy to see some competion to that family.
Anyways comming back to the Java support and a few corrections here.
a)The Cpu is not dedicated for Java, it just has java byte code support as a Co-Processor,Just like MMU,Video accelerator...etc.
b)Not all the Java byte codes are implemented in the H/W (around 40% only if I my memory is proper), after all this is a RISC processor afterall

.The remaining should be Emulated in S/W, in this case the JVM.
c)Just because the processor has Java byte code support does not mean that here would be native support and vice versa, for example Windows Mobile has JVM but Wince does not have JVM.Best of my knowledge PXA270 processor by itself does not have Jazelle but devices based on PXA270 has Java support.
d)Having Java support in the H/W actually makes it difficult to support it in S/W (funny to hear , trust me I know) since the JVM has to be ported to this OS and the hardware.Then again not a impossible task but considering the cost of the iPhone this should have been supported.
These are my observations on the H/W of the iPhone
a) I would have personally prefered the Pxa320 but last I heared it had its won yeild issues, but as far as bench marks goes the 320 was twice faster than a competing ARM-11 based on Freescale.
b)The Motherboard looks S%%Y, but I worry about the power consumption.
c)The Nand flash is a very popular IC which will be used in many future phones since these chips have the capablity to boot directly from the Nand Flash.
d)Not disk on chip or anything to increase the speed. (ie) due to preformance issues in reading from the flash , we generally copy the os (our case Wince) to RAM during bootup and make it Run from there since XIP (execute in place ie from the Flash IC itself is a very slow option).In phone's case (OS-X) being ~700 MB (from what I heard) this is not an option, and thus I expect there to be a performance hit due to the Flash, also do remember there will also be a performance hit because of a WriteBack cache policy (Writethrough can be used for RAM).I also am intresed in knowing in the type of Virtual memory model model they use which will give a lot of clues on the expected performance of the applications.
In all a very well designed H/W but nothing out of the ordinary which current phones does not have or future phones cannot have.
Added later--Sorry for that.
The camera sucks, it really does, the iPhones camera should be called as "Camera for Dummies", No White balancing,No selection of different resolutions,No Red Eye reduction,Video recording........it looks like a Kodak KB10 camera.
No wonder actually, MS had a horrible time porting the Dierct Show framework( The Image Sink Fliter part) for windows Mobile right from Ce 3.0 and it sucks till Ce 5.0. Only in CE 6.0 the pipeline and graphs are implemented to an extent that it can start competing with the Sonly likes.Part of the horrible camera could also deal with the fact the Camera Interface in the samsung processor ( this not USB like PC) is not as good as those available for the Pxa family (called as Quick capture interface).The Camera pipeline needs to improve and improve fast.