Related
These are some of the Kaiser's internals.
Here you will find the diagram of it:
DIAGRAM
This is the page I found this on:
Qualcomm MSM7200Chipset In Kaiser
Lemme know what you guys think!
interesting that its chip supports video out but they did not add it in the hardware.
magnamar said:
interesting that its chip supports video out but they did not add it in the hardware.
Click to expand...
Click to collapse
yes, the chip in the 8525/TyTN supported gps but did not support it.
the mogul has the 7500 chip which supports the same as the kaiser but the device doesnt support it all.
KaiserLinux said:
These are some of the Kaiser's internals.
Here you will find the diagram of it:
DIAGRAM
This is the page I found this on:
Qualcomm MSM7200Chipset In Kaiser
Click to expand...
Click to collapse
Interesting - this chipset has HSUPA support by default, but Kaiser doesn't support it (or at least, HTC does not confirm this). Does it mean that Kaiser has limited edition of that chipset, or maybe HSUPA will become available with future ROM updates from HTC?
eva_d said:
Interesting - this chipset has HSUPA support by default, but Kaiser doesn't support it (or at least, HTC does not confirm this). Does it mean that Kaiser has limited edition of that chipset, or maybe HSUPA will become available with future ROM updates from HTC?
Click to expand...
Click to collapse
I am sure this has to do with the carriers network supporting this bandwith upload feature.
iservealot said:
I am sure this has to do with the carriers network supporting this bandwith upload feature.
Click to expand...
Click to collapse
Well, everything will turn out once Kaiser will hit the shelves and people start using it, and sharing (hopefully) their thoughts about it...
eva_d said:
Interesting - this chipset has HSUPA support by default, but Kaiser doesn't support it (or at least, HTC does not confirm this). Does it mean that Kaiser has limited edition of that chipset, or maybe HSUPA will become available with future ROM updates from HTC?
Click to expand...
Click to collapse
I suspect this will have a lot more to do with Microsoft's WM6 not ready to cope with these kind of 3,5G / 3,75G protocols.... (correct me if i'm wrong)
So that should also mean that future upgrades (AKU's i'd suspect) might correct the lack of HSUPA
Interesting - this chipset has HSUPA support by default, but Kaiser doesn't support it (or at least, HTC does not confirm this). Does it mean that Kaiser has limited edition of that chipset, or maybe HSUPA will become available with future ROM updates from HTC?
Click to expand...
Click to collapse
As per the comment above, I definitely think it is based on the carrier.
The radio on kaiser runs L4/Linux Pistachio microkernel, you can read more information here.
Some pr0n for the linux geeks:
Code:
$ strings kaiser_radio_0x301.nb |grep -i linux
M6500C L4/Linux
L4 Linux
NICTNICTA::Pistachio - built on Jan 23 2007 18:10:22 by [email protected] using gcc version 3.4.1
start_linux_cmd
vmlinux != NULL
vmlinux
vmlinux igms_name=ramdisk root=/dev/igms0
start_linux
The radio on kaiser runs L4/Linux Pistachio microkernel, you can read more information here.
Some pr0n for the linux geeks:
Click to expand...
Click to collapse
Thanks for this info! I am reading over it now.
im a bit confused on how it could run the l4 microkernel and windows 6 on it. I was hoping that I could somehow flash the device with a Linux embedded bootloader - > load a kernel that has support for both of these arm cpu's and board -> then load driver modules for all of the different radios and interfaces and drop some minimalistic OS on top of that. Does anyone know the feasibility of accomplishing something like this? Also how the l4 linux kernel can run side by side with wm6?
Think of the radio interface as a computer inside an another computer (the phone itself). The main CPU runs WM6 and interfaces with the radio which runs an embedded linux.
Wrong, on most phones you are correct, they have a cpu and the seperate communications processor. But the kaiser is unique in using the communications processor as the primary CPU for the entire device. So unless there is a seperate arm core (dual core?) inside it, how is it running both linux and wm?
That's the thing that is very interesting. Looking at the diagram the msm7200 board seems to have an ARM11 and an ARM9 cpu on it.
I coudlv'e sworn someone said that it might be a dual core...
KaiserLinux said:
Also how the l4 linux kernel can run side by side with wm6?
Click to expand...
Click to collapse
They can share address space on the same CPU,
wince is a 25bit OS.
Do you have the Kaiser phone ? Can you run haret on it ?
On handhelds.org it's mentioned that a guy named Kevin has modded the source code of haret for the MSM7500 chip. It's not working yet (internals of the chip is unknown), only the CPU gets detected. (more info: http://handhelds.org/moin/moin.cgi/HaRET)
KaiserLinux said:
As per the comment above, I definitely think it is based on the carrier.
Click to expand...
Click to collapse
HSUPA is mostly being trialled by carriers. Most are still absorbing HSDPA.
Hey - Im a nubee and I was wandering if any of you can help with what you estimate the cost of the Qualcomm MSM7200 SOC to be. Its very impressive!
We are starting a new design and could be interseting.
Shadowmite said:
Wrong, on most phones you are correct, they have a cpu and the seperate communications processor. But the kaiser is unique in using the communications processor as the primary CPU for the entire device. So unless there is a seperate arm core (dual core?) inside it, how is it running both linux and wm?
Click to expand...
Click to collapse
It still has a seperate communications processor, it's just in the same chip as opposed to a seperate package now. (See other comments).
I think it's something like 400 MHz ARM11 for applications, 274MHz ARM9 for comms.
Android on kaiser?
Lets start an effort to try to run Android on kaiser? I am sure it will be a huge task, but lets give it a shot.
I am not an embedded system expert, but I am sure we can get people to help us, maybe from the google team once we get serious.
Where can I look/read what kind of GPS Chip run in my diamond?
Is it true thats two different chips have been build-in?
Does nobody know this information?
you should've checked the wiki before posting
anyways, the chipset is Qualcomm's gpsOne
where did you get the idea of two chips from?
blufade said:
you should've checked the wiki before posting
anyways, the chipset is Qualcomm's gpsOne
where did you get the idea of two chips from?
Click to expand...
Click to collapse
Shure - I ve checked wiki and another blogs and I know this information about Qualcomm, thx.
But I wanne know where I can read in my diamond what kind of chip I have.
I´ve read it in a another forum (about 2 versions of chip´s) and I think that was the answer why first Diomonds release work with bad Sat fix and newest edition work´s fine.
on your diamon huh ?...from what i know, neither winmo nor the htc manual reports any info regarding the gps chip, plus i've never come across any s/w that could read gps specifications directly, have you checked out the htc repair maual, actually it has pretty much all info regarding the hardware.
i don't know if htc would alter the gps chip, maybe its just that the newer diamonds come with a better radio s/w...
Hello.
I am sorry I could not post on the development thread. this is my first post. I have been checking the TI developer site and noticed that they just posted an official android Froyo devkit available for download. the link is:
software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html
and the documentation is at:
/processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide
The source code is included and has new drivers for the SGX chip and a devkit for the WL1271 including bluetooth stack.
Also the kit include drivers for the DSP for video decoding and Flash acceleration in android.
I think this could be good to allow update to nookie froyo. I am in the process of testing the release on an OMAP 3530 dev board and will let you know.
Wow this could be just what we need!!!
Plus maybe the CM7 folk can port this over to gingerbread and deeperblue to honeycomb then we can have a true daily driver tablet as I believe these were the rate limiting steps!!!
Canadoc said:
Wow this could be just what we need!!!
Plus maybe the CM7 folk can port this over to gingerbread and deeperblue to honeycomb then we can have a true daily driver tablet as I believe these were the rate limiting steps!!!
Click to expand...
Click to collapse
Kind of neat how these things pop up...
Glad to be on board with the Nook!
Fifcic said:
Hello.
I am sorry I could not post on the development thread. this is my first post. I have been checking the TI developer site and noticed that they just posted an official android Froyo devkit available for download. the link is:
software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html
and the documentation is at:
/processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide
The source code is included and has new drivers for the SGX chip and a devkit for the WL1271 including bluetooth stack.
Also the kit include drivers for the DSP for video decoding and Flash acceleration in android.
I think this could be good to allow update to nookie froyo. I am in the process of testing the release on an OMAP 3530 dev board and will let you know.
Click to expand...
Click to collapse
Lack of OMAP36xx as supported platform (read: NC) by this release is kinda disconcerting...
Thanks for posting. I'll take a look when I get home.
aludal said:
Lack of OMAP36xx as supported platform (read: NC) by this release is kinda disconcerting...
Click to expand...
Click to collapse
The thing to understand is that all the OMAP 3 serires share the same software register interface. the part numbering is based on generation and intended market:
OMAP34xx: High Volume ODM 65nm
OMAP35xx: Embedded Low volume customers (same features as OMAP34xx)
OMAP36xx: High Volume ODM 45nm (Higher clock speed, SGX double clock speed)
AM37xx and DM 37xx: Embedded low volume customers (same features as OMAP36xx)
if you look at the release. this is intended for non ODM customers and enthousiasts access to the SDK they provide to their high volume customer. this is why the OMAP 34and 36 are not mentioned. TI provides them different SDK. the important part is that this provides a stable hardware accelerated kernel with drivers to the comunity.
the OMAP 3621 is an OMAP 3630 nutered. it has the same core but the pins to support pop memory and camera interface are not conected. It is still very powerfull as it still has the DSP and SGX core inside.
I hope this helps.
Thanks for the info - looking at it, and i do see things like the OMAP3630 stuff in there, so this may every well be a useable Kernel for Froyo. Hot damn, maybe i will try my hand at compiling again (or if we are more lucky, dalingrin will find useful stuff, and really knock our socks off. )
Fifcic said:
The thing to understand is that all the OMAP 3 serires share the same software register interface. the part numbering is based on generation and intended market:
OMAP34xx: High Volume ODM 65nm
OMAP35xx: Embedded Low volume customers (same features as OMAP34xx)
OMAP36xx: High Volume ODM 45nm (Higher clock speed, SGX double clock speed)
AM37xx and DM 37xx: Embedded low volume customers (same features as OMAP36xx)
if you look at the release. this is intended for non ODM customers and enthousiasts access to the SDK they provide to their high volume customer. this is why the OMAP 34and 36 are not mentioned. TI provides them different SDK. the important part is that this provides a stable hardware accelerated kernel with drivers to the comunity.
the OMAP 3621 is an OMAP 3630 nutered. it has the same core but the pins to support pop memory and camera interface are not conected. It is still very powerfull as it still has the DSP and SGX core inside.
I hope this helps.
Click to expand...
Click to collapse
Updated drivers/dsp, updated linux kernel and bluetooth stack! This should really make for some interesting progress with nookie froyo, BT support, CM7 and possibly even the honeycomb builds
Assuming this kernel can be made to work, yes, it should really help. Some of the thing that i was looking for that are in the eclair kernel are missing (some of the OMAP stuff specific to our hardware), though, it may be a case of taking them and dropping them in. Either way, i hope this help, as i am dying to see our hardware put to better use.
Shouldn't this be in the development thread?
haganme said:
Shouldn't this be in the development thread?
Click to expand...
Click to collapse
Fifcic said:
Hello.
I am sorry I could not post on the development thread. this is my first post.
Click to expand...
Click to collapse
Yes, but new people to the forum can't post in Dev subforum until we have 10 posts.
Somebody had linked to this thread in the Dev forum, and for some reason, the mods closed it. OK, maybe we don't need two threads, but this really should be in the dev forum. It will get more attention there, and will hopefully be seen by those who need to see it..
I linked it as i thought more devs would see it there. Got a slightly rude post in reply that devs read both so.....
Indeed, i saw that, and it was uncalled for. Fact is, this is a dev thread, and should be there. Yes, a dev MAY read this forum, but truly, I don't expect them to, and things like this need to be as visible as possible - this is not the forum for that.
So.. any actual dev care to give feedback on the usefulness of this package, or are all the dev's handing out in just the dev forum still?
read it from some forum, what does that mean?
BPSW or baseband files regulate the phone's cellular radio and its supposed to give you better reception.
The "baseband processor" is what does the actual communication on the cellular network. Think of it as being like a modem. The BPSW is the software that runs on it. It's tricky stuff. On smartphones the "application processor" is what runs Android (or iOS, etc) and the apps, etc. Apparently they even use a (heavily modified) Hayes-style AT command set to communicate, so calling the BP a "modem" isn't all that inaccurate.
Check out Harald "LaF0rge" Welte's blog if you're interested in learning more about the inner workings of GSM. He and others are working to create an Open Source GSM stack. Based on this work he has written a paper on the anatomy of contemporary GSM cellphone hardware. It is quite technical, but not to the point that the average computer nerd would have difficulty at least skimming through. The "personal rant on the closedness of the GSM industry" at the end is very informative about the business side of things.
Maybe this is all a little too detailed and technical, but I thought some people might be interested in the details.
Jehu screrged
dreamer1212 said:
read it from some forum, what does that mean?
Click to expand...
Click to collapse
For an american milestone would there necessarily be any modifications needed for this to work properly?
Hello guys,
I am a new owner of the GT-P7320 Galaxy Tab 8.9 LTE and I'm a bit confused about the naming and available roms.
First off, what's the difference between 7300/7310 and 7320? All the guides in this section, including the "one-stop ultimate guide" (http://forum.xda-developers.com/showthread.php?t=1406137) are written with 7300 and 7310 in mind. Is there anything I should be aware of, or I can simply follow the guide with my device as well?
Also, I noticed there are separate roms for 7320 in the development forums, yet I managed to find only 1 thread - the OTA ICS one (http://forum.xda-developers.com/showthread.php?t=1901664). Why is that? Did I miss something, or there are no roms available for the device yet?
Is there a point in flashing the OTA ICS 4.0.4 right now? Is it AOSP, or has got the TouchWiz interface? How stable is it? I was really looking forward to ICS just for the sole purpose of being able to use Chrome.
I tried using search and did some research on the forums, also I am quite experienced with rooting and flashing other android devices - but the 7320 got me really confused out there.
Thanks in advance!
The most important difference is that 7320 uses Qualcomm's Snapdragon architecture - to power the LTE chip - while 7300 and 7310 feature a less efficient NVidia Tegra. The LTE is also the least popular amongst the 8.9 Tabs. But we've got root, we know how to deal with OTA updates that Samsung doesn't release to public, and we have Arlicc's ROM that is basically stock Touchwiz ICS with some tweaks.
ICS runs great on this Tab and really there's no reason to stick with the Honeycomb.
Yes, actually, the Arlicc's ROM got released after I made the thread I'm using it right now, very satisfied so far - you are right, ICS runs great and smooth. In fact, it seems faster than 3.2!
Thank you very much for your kind answer! There's one thing I still don't understand though - I have always thought that Qualcomm Snapdragon is a CPU and Tegra is a video card/module - how come Snapdragon in 7320 is more efficent than Tegra in 7300? Aren't 7300/7310 using Snapdragon as well?
Both are "system on chips", basically a CPU, GPU and radio stuffed into a single chip. The 7320 CPU is a 1.5 GHz (compared to 1 GHz on 7300/7310) dual-core. Apparenty a Tegra 2 device wouldn't be able to handle an LTE radio.