Why not a nexus chipset ?

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

John Case case at SDF.ORG
Wed Oct 3 17:52:31 UTC 2012


Paul,

On Mon, 1 Oct 2012, Paul Wise wrote:

> On Mon, Oct 1, 2012 at 10:22 PM, Sylvain Munaut wrote:
>
>> But, do you have links to the datasheet, programmers manual and source
>> code of the baseband ?
>
> We were discussing this on IRC and Peter pointed out this:
>
> http://forum.xda-developers.com/showthread.php?t=1483053
k

I am looking at the list of devices covered by this xda-dev posting - most 
interesting is the Samsung Galaxy Nexus - again, this is a reference 
handset, something that in the past was in the hands of developers only, 
but now many people around the world are using.

So that's very interesting, which was the point of my OP - the google 
nexus phones represent a particularly ripe avenue for osmocom since they 
are reference handsets, and presumably the "warez" that you need are in 
many more hands than previous chipset docs and code.  Perhaps there is a 
flaw in my assumption ?

The bad news is that the list of devices from the xda-dev posting does NOT 
include the Galaxy S II GT-i9100, which was mentioned earlier in this 
thread.

I wonder:

- how did the calypso docs leak in the first place ?  Was it indeed a real 
breach of intellectual property, or did they just get published by TI 
since they were uninteresting in some way ?  How nefarious is the story 
there ?

- What would it actually cost to get the documentation and code needed for 
either of these two items we are discussing above ?  If I go to Qualcomm 
and sign up as a developer (under a corp name, etc.) .... is it $10k ? 
$100k ?  Or are the docs you need not available at any price ?

I would like to think that the "warez" needed for one of these targets are 
so widely distributed (because of the android ecosystem and the aggressive 
push there) that simply putting out a loud and wide "call for leaks" would 
yield some results...




More information about the baseband-devel mailing list