Connectivity naming conventions

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
m (MCP and NLCP)
(Software Packages for Connectivity on OMAP)
 
(13 intermediate revisions not shown)
Line 5: Line 5:
==Software Packages for Connectivity on OMAP==
==Software Packages for Connectivity on OMAP==
-
The software for enabling connectivity for the OMAP platforms have taken multiple paths over the years. With multiple chips sets for connectivity (OMAP3 with 127x, OMAP3 with 128x, OMAP4 with 127x, etc., as mentioned here), and for various software distributions running on the OMAP platform (Ubuntu, pastries of Android, QNX, etc.) these splits in the development tree, into different branches, are inevitable. Compounded with these are the merges of software support branches for some connectivity devices through a common efforts or packages. In some cases, back porting of features and functionality has also taken place.
+
The software for enabling connectivity for the OMAP platforms have taken multiple paths over the years. With multiple chip sets for connectivity (OMAP3 with 127x, OMAP3 with 128x, OMAP4 with 127x, etc., as mentioned [http://www.omappedia.org/wiki/Template:Connectivity_Combos here]), and for various software distributions running on the OMAP platform (Ubuntu, pastries of Android, QNX, etc.) these splits in the development tree, into different branches, are inevitable. Compounded with these are the ''merges'' of software support branches for some connectivity devices -- through common efforts or package releases. In some cases, ''back porting'' of features and functionality has also taken place.
-
Internally, TI calls these development trees L23, L24, L25, L26, L27 etc. Some of these branches are released externally, and are hence supported completely. Hence, some of these branches are better known than the others. L24 and L27 are some such branches, which have been well supported, and recognized outside TI.
+
Internally, TI calls these development trees L23, L24, L25, L27, etc. Some of these branches are released externally -- with help provided for those released branches. Hence, some of these branches are better known -- and better supported -- than the others. L24 and L27 are some such branches, which have been released outside TI and well supported. Developers outside TI are more familiar with those branches.
For example, '''L24''' is a "purely" Linux based branch, with Ubuntu as the main distribution platform. Some of the driver software had been upstreamed into the Linux kernel code (available from kernel.org.)
For example, '''L24''' is a "purely" Linux based branch, with Ubuntu as the main distribution platform. Some of the driver software had been upstreamed into the Linux kernel code (available from kernel.org.)
-
Another example, '''L27''' is an Android based branch of the connectivity enabler software. Various Android pastries, such as Elair, Froyo, Gingerbread, and Honeycomb, have been well supported through development effort on this branch.  
+
Another example, '''L27''' is an Android based branch of the connectivity enabler software (for the Blaze OMAP4 platform). Various Android pastries -- such as Eclair, Froyo, Gingerbread, and Honeycomb -- have been well supported through development efforts on this branch.  
-
As the software distributions evolve and as better, faster, novel connectivity technologies emerge, the support for the OMAP platform using these will also evolve and emerge, and in some cases, converge.
+
Similarly, the releases specific to Android (for the Zoom OMAP3 platform) have a L25x tag. The generic Linux versions have L23x or L24x tags.
 +
 
 +
As the software distributions evolve, and as better, faster, novel connectivity technologies emerge, the support for the OMAP platform using these will also evolve and emerge, and in some cases, converge; and some features will be ''back ported'' too.
==MCP and NLCP==
==MCP and NLCP==
-
MCP and NLCP are different branches of code that support WiLink on the OMAP platform. Both the branches are based on open source code.  
+
'''MCP (Mobile Connectivity Package)''' and '''NLCP (Native Linux Connectivity Package)''' are different branches of code that support WiLink on the OMAP platform. MCP is based on TI proprietary WLAN stack and NLCP is based on mac802.11 open source stack. Both are available on the WiLink hardware starting from WiLink 6 onwards.
-
'''MCP''' is TI's own branch of code for the WiLink network stack. Some of the code was also written by others using the OMAP platform for their products. MCP is available for anyone to use and its latest ''daily'' version can be obtained from the TI site. There are ongoing efforts to '''upstream''' as much as possible (from MCP into NLCP, wherever and whenever possible). However, because of the delay in the acceptance process this branch always has the latest ''bells and whistles'' on the OMAP platform.  
+
'''MCP''' is TI's own branch of code for the WiLink network stack. Some of the code was also written by others using the OMAP platform for their products. MCP is available for anyone to use and its latest ''daily'' version can be obtained from the TI site. There are ongoing efforts to '''upstream''' as much as possible (from MCP to NLCP). However, because of the delay in the acceptance process this branch always has the latest ''bells and whistles'' on the OMAP platform.  
Also, MCP is the WiLink stack that is available and supported by TI for any of the '''Android flavors''' on all OMAP platforms. NLCP doesn't completely do that for now; but the aim is to make NLCP the ''de facto'' candidate on Android for the OMAP platforms.
Also, MCP is the WiLink stack that is available and supported by TI for any of the '''Android flavors''' on all OMAP platforms. NLCP doesn't completely do that for now; but the aim is to make NLCP the ''de facto'' candidate on Android for the OMAP platforms.
-
'''NLCP''' is the MAC80211 stack that comes with the general Linux distributions. As mentioned, the intention is to make NLCP code fully support the OMAP platform for all Linux and Android distributions.
+
The '''NLCP''' WLAN driver is based on the Linux mac80211 architecture, available as part of the Linux kernel. TI's WLAN driver is named wl12xx and it is already part of the mainline Linux kernel. For more information, please refer to [http://openlink.org OpenLink.org]
 +
 
 +
[http://www.omappedia.org/wiki/OMAP_WiLink_Connectivity_Home Back to Connectivity Home Page]
[[Category:WLAN]]
[[Category:WLAN]]
[[Category:Connectivity]]
[[Category:Connectivity]]

Latest revision as of 21:50, 12 December 2011

[edit] OMAP based TI's Connectivity Chips

As mentioned in the overview the naming conventions for TI's connectivity chips for the OMAP platforms are WL127x, WL128x, WL18xx and WL19xx. The solutions offered to the customers, which use the different OMAP and WLAN generations -- and hence different software, are mainly the WiLink 6.0 and WiLink 7.0, and are mentioned on this page.

[edit] Software Packages for Connectivity on OMAP

The software for enabling connectivity for the OMAP platforms have taken multiple paths over the years. With multiple chip sets for connectivity (OMAP3 with 127x, OMAP3 with 128x, OMAP4 with 127x, etc., as mentioned here), and for various software distributions running on the OMAP platform (Ubuntu, pastries of Android, QNX, etc.) these splits in the development tree, into different branches, are inevitable. Compounded with these are the merges of software support branches for some connectivity devices -- through common efforts or package releases. In some cases, back porting of features and functionality has also taken place.

Internally, TI calls these development trees L23, L24, L25, L27, etc. Some of these branches are released externally -- with help provided for those released branches. Hence, some of these branches are better known -- and better supported -- than the others. L24 and L27 are some such branches, which have been released outside TI and well supported. Developers outside TI are more familiar with those branches.

For example, L24 is a "purely" Linux based branch, with Ubuntu as the main distribution platform. Some of the driver software had been upstreamed into the Linux kernel code (available from kernel.org.)

Another example, L27 is an Android based branch of the connectivity enabler software (for the Blaze OMAP4 platform). Various Android pastries -- such as Eclair, Froyo, Gingerbread, and Honeycomb -- have been well supported through development efforts on this branch.

Similarly, the releases specific to Android (for the Zoom OMAP3 platform) have a L25x tag. The generic Linux versions have L23x or L24x tags.

As the software distributions evolve, and as better, faster, novel connectivity technologies emerge, the support for the OMAP platform using these will also evolve and emerge, and in some cases, converge; and some features will be back ported too.

[edit] MCP and NLCP

MCP (Mobile Connectivity Package) and NLCP (Native Linux Connectivity Package) are different branches of code that support WiLink on the OMAP platform. MCP is based on TI proprietary WLAN stack and NLCP is based on mac802.11 open source stack. Both are available on the WiLink hardware starting from WiLink 6 onwards.

MCP is TI's own branch of code for the WiLink network stack. Some of the code was also written by others using the OMAP platform for their products. MCP is available for anyone to use and its latest daily version can be obtained from the TI site. There are ongoing efforts to upstream as much as possible (from MCP to NLCP). However, because of the delay in the acceptance process this branch always has the latest bells and whistles on the OMAP platform.

Also, MCP is the WiLink stack that is available and supported by TI for any of the Android flavors on all OMAP platforms. NLCP doesn't completely do that for now; but the aim is to make NLCP the de facto candidate on Android for the OMAP platforms.

The NLCP WLAN driver is based on the Linux mac80211 architecture, available as part of the Linux kernel. TI's WLAN driver is named wl12xx and it is already part of the mainline Linux kernel. For more information, please refer to OpenLink.org

Back to Connectivity Home Page

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox