Changes between Version 1 and Version 2 of Gen9A101TurboICSLinuxNotes

Timestamp:

09/13/13 09:28:41 (3 years ago)

Author:

comphuter

Comment:

Added wl12xx (wireless-compat) and btwilink (bluetooth-compat) kernel module build instructions and Bluetooth/UIM setup information

Gen9A101TurboICSLinuxNotes

@@ -3 +3 @@
 = Archos A101 G9 "Turbo ICS" Linux notes =
 
-This is a collection of notes specific to a linux-based system. All of these notes are specific to the Archos 101 G9 Turbo and some things (such as kernel modules) might be different on non-Turbo models or Archos A80 G9 models, respectively. This notes are mostly system-independent, though some things might be Slackware-specific (ARMedslack 14.0) because that's the used baseline system. These notes are the basic low-level steps needed to provide specific functionalities on your native Linux system (e.g. Debian, Slackware or LFS) running on your Archos A101 G9 Turbo and might not be useful for Android systems.
-
-== Hardware drivers / Kernel modules ==
-
-Note that it is highly recommended to use the [http://dev.openaos.org/search?q=wiki%3A%22Gen9Resources%22 archos-gpl-gen9-kernel-ics kernel provided by archos] (Also, I recommend to use the ''linux-ics-3.0.21'' branch of the git-tree). Otherwise there might be no support for the device with a '''very''' high possibility.
-
-'''Note:''' Instructions on building a kernel image, a small initrd to boot a system from MicroSD are to come. Also, I will add some general information on what _exactly_ is needed to build a working kernel for the A101G9 Turbo (i.e., which kernel modules are really necessary and which are just G80/Whatever stuff). That needs some more investigation.
+This is a collection of notes specific to a linux-based system. All of these notes are specific to the Archos 101 G9 Turbo and some things (such as kernel modules) might be different on non-Turbo models or Archos A80 G9 models, respectively. This notes are mostly system-independent. These notes are the basic low-level steps needed to provide specific functionalities on your native Linux system (e.g. Debian, Slackware or LFS) running on your Archos A101 G9 Turbo and might not be useful for Android systems.
+
+Some work was already done beforehand by [http://www.basyskom.com/ BasysKom] and the Mer Project. Packages and patches of their gen9 adaption is still alive on their OBS, provided by some people:
+ * notmart: [https://build.merproject.org/project/show?project=home%3Anotmart%3AMer_Extras%3AAdaptation%3AArchos-gen9 omapfb] and [https://build.merproject.org/project/show?project=home%3Anotmart%3AMer_Extras%3AAdaptation%3AArchos-gen9%3Apvr pvr]
+ * wonko: [https://build.merproject.org/project/show?project=home%3Awonko%3Aarchos-g9-pa-adaptation omapfb] and [https://build.merproject.org/project/show?project=home%3Awonko%3Aarchos-g9-pa-adaptation%3Apvr pvr]
+
+----
+== Hardware drivers / Kernel source ==
+
+There two linux kernel sources available, knowing to work with the G9 series:
+
+=== archos-gpl-gen9-kernel-ics ===
+The [http://dev.openaos.org/search?q=wiki%3A%22Gen9Resources%22 archos-gpl-gen9-kernel-ics kernel provided by archos]. It provides two branches: The (''master'') 3.0.8 and the ''linux-ics-3.0.21'' branch. The latter one is basically what one might want, though there is trouble with the wifi driver.
+
+=== archos-gen9-mer-adaption-kernel-ics ===
+The [http://gitorious.org/archos-gen9-mer-adaptation-kernel/archos-gen9-mer-adaptation-kernel-ics/ Mer gen9 adaption kernel source]. This one also provides two branches: ''master'' and ''pvr''. The master branch is the same as the archos-gpl-gen9-kernel-ics 3.0.8 branch with some additional patches/fixes. The ''pvr'' branch contains several fixes and additional OMAPDRM support. If OMAPDRM is not important for you, you might still want to get the fixes provided by the ''pvr'' branch. If you still insist on sticking with the master branch, take a look at [https://build.merproject.org/package/files?package=kernel-adaptation-archos-gen9&project=home%3Anotmart%3AMer_Extras%3AAdaptation%3AArchos-gen9 notmarts Mer adaption kernel package]. ('''Note:''' The author uses the ''pvr'' branch of this kernel during all further kernel-related instructions)
+
+
+'''Note:''' Whatever kernel you choose, if you use GCC >= 4.7  the compiled kernel '''will not boot''' unless you pass -mno-unaligned-access to the KBUILD_CFLAGS. There is a patch adding this flag in the [https://build.merproject.org/package/view_file?file=mer-toolchain-mno-unaligned-access.patch&package=kernel-adaptation-archos-gen9&project=home%3Anotmart%3AMer_Extras%3AAdaptation%3AArchos-gen9&rev=e9f6291a7b42fb3cc57272eeda6131ff Mer adaption branches]. (According to [http://seabright.co.nz/2012/06/11/kernel-not-booting-with-linaro-gcc/ this article], linaro-gcc is affected even in earlier versions)
+
+----
+
+== Additional wl12xx and btwilink drivers ==
+
+If you have problems getting the kernel-shipped versions of these drivers to work, or anyone of them is causing trouble (e.g. random connection loss, kernel oops), you might want to compile other versions provided by TI. Archos seemed to have taken [http://gitorious.org/archos/archos-gpl-gen9/source/4b2d3c4d1d351df6b7a00e1a09bb5aa53b832822:hardware/ti/wlan_openlink the same approach]. For the author it was impossible to compile the archos-provided compat-wireless sources, but at least the TI version used by them -- r5.00.18-build_199 -- was helpful.
+
+=== WLAN-OpenLink / wl12xx ===
+
+TI provides all the needed code on their [https://github.com/TI-OpenLink/ OpenLink github page]. What we are interested in are the ''compat'', ''compat-wireless'' and ''wl12xx'' repositories. Go to the work directory of your choice and clone these repositories:
+('''Note:''' Let $WORKDIR be the directory you wish to work in)
+
+{{{
+$ cd $WORKDIR
+$ git clone https://github.com/TI-OpenLink/compat.git
+Cloning into 'compat'...
+remote: Counting objects: 3658, done.
+remote: Compressing objects: 100% (1495/1495), done.
+remote: Total 3658 (delta 2100), reused 3657 (delta 2100)
+Receiving objects: 100% (3658/3658), 1.11 MiB | 368 KiB/s, done.
+Resolving deltas: 100% (2100/2100), done.
+$ git clone https://github.com/TI-OpenLink/compat-wireless.git
+Cloning into 'compat-wireless'...
+remote: Counting objects: 8709, done.
+remote: Compressing objects: 100% (3045/3045), done.
+remote: Total 8709 (delta 5651), reused 8701 (delta 5648)
+Receiving objects: 100% (8709/8709), 3.26 MiB | 1.06 MiB/s, done.
+Resolving deltas: 100% (5651/5651), done.
+$ git clone https://github.com/TI-OpenLink/wl12xx.git
+Cloning into 'wl12xx'...
+remote: Counting objects: 2379170, done.
+remote: Compressing objects: 100% (363568/363568), done.
+remote: Total 2379170 (delta 1993125), reused 2379074 (delta 1993039)
+Receiving objects: 100% (2379170/2379170), 506.14 MiB | 1.11 MiB/s, done.
+Resolving deltas: 100% (1993125/1993125), done.
+Checking out files: 100% (37602/37602), done.
+}}}
+
+Now we need the correct branches of all of them. It is up to you to use the r5.00.18-build_199 tagged version of wl12xx or a newer one. The r5_3.2 branch is known to work well. For ''compat'' and ''compat-wireless'', just checkout the ''master'' branches.
+
+{{{
+$ cd $WORKDIR/compat
+$ git checkout master
+Branch master set up to track remote branch master from origin.
+Switched to a new branch 'master'
+$ cd $WORKDIR/compat-wireless
+$ git checkout master
+Branch master set up to track remote branch master from origin.
+Switched to a new branch 'master'
+$ cd $WORKDIR/wl12xx
+$ git checkout r5_3.2
+Branch r5_3.2 set up to track remote branch r5_3.2 from origin.
+Switched to a new branch 'r5_3.2'
+}}}
+('''Note:''' If you wish to use the exact r5.00.18-build_199 version, replace ''r5_3.2'' in the last git command with ''r5.00.18-build_199')
+
+Now we are ready to import all the files into our compat-wireless tree:
+
+{{{
+$ cd $WORKDIR/compat-wireless
+$ export GIT_TREE=$WORKDIR/wl12xx
+$ export GIT_COMPAT_TREE=$WORKDIR/compat-wireless
+$ ./scripts/admin-update.sh
+... lots of output ...
+Base tree: wl12xx.git
+Base tree version: r5.00.19-build_257
+compat-wireless release: ol_R5.SP6.01
+}}}
+
+In general people are cross-compiling stuff for their mobile devices, so these instructions are for this case. If you are not cross-compiling and your tablet is currently using the kernel you wish to compile the module for, then just run ''make''. Otherwise, set KLIB to the proper directory in ''/lib/modules''.
+
+We are ready to to build our module. Set KLIB_BUILD to the path of the kernel-source and KLIB to the path of the module directory you wish to install the modules into. CROSS_COMPILE takes the prefix of the cross compiler, e.g. ''armv7a-unknown-linux-gnueabi-'' or ''arm-linux-gnu-''. It depends on your toolchain.
+
+{{{
+$ make ARCH=arm CROSS_COMPILE=armv7a-unknown-linux-gnueabi- KLIB=/path/to/target/kernel/module/dir KLIB_BUILD=/path/to/target/kernel/dir
+$ make ARCH=arm CROSS_COMPILE=armv7a-unknown-linux-gnueabi- KLIB=/path/to/target/kernel/module/dir KLIB_BUILD=/path/to/target/kernel/dir install-modules
+}}}
+
+For the firmware, just use the one provided by the Archos android system. ('''Note:''' The author used the NVS files from the archos image and the firmware from [https://github.com/TI-OpenLink/firmwares the TI firmware repository])
+
+=== Bluetooth / btwilink ===
+
+TI Provides a already set-up and working bluetooth-compat tree in their [http://git.omapzoom.org/?p=platform/hardware/ti/wpan.git;a=summary OmapZoom WPAN repository]. Clone it, check it out and build it like the wl12xx driver:
+('''Note:''' Instead of the ''ics-mr1-release'' branch, a newer one like ''jb-mr2-release'' might just work fine, though not tested)
+
+{{{
+$ cd $WORKDIR
+$ git clone git://git.omapzoom.org/platform/hardware/ti/wpan.git
+$ cd wpan
+$ git checkout ics-mr1-release
+$ cd bluetooth-compat
+$ make ARCH=arm CROSS_COMPILE=armv7a-unknown-linux-gnueabi- KLIB=/path/to/target/kernel/module/dir KLIB_BUILD=/path/to/target/kernel/dir
+$ make ARCH=arm CROSS_COMPILE=armv7a-unknown-linux-gnueabi- KLIB=/path/to/target/kernel/module/dir KLIB_BUILD=/path/to/target/kernel/dir bt-install-modules
+}}}
+
+You can now use your new btwilink driver. Note that you still need the uim-sysfs package for TI shared transport, i.e. having BT and Wifi working at the same time.
+
+----
+
+== Bluetooth ==
+
+For getting bluetooth to work, you will need [http://gitorious.org/uim/uim UIM].
+
+{{{
+$ cd $WORKDIR
+$ git clone git://gitorious.org/uim/uim.git
+$ cd uim
+$ make CC=armv7a-unknown-linux-gnu-gcc
+}}}
+
+Copy the ''uim'' binary over to a binary dir on your tablet system, e.g. ''/sbin''. Also, if it's not there, copy the 'TIInit_7.2.31.bts' from your android system over to '/lib/firmware/'. For starters, just start ''uim'' and load the ''btwilink'' module. The dmesg output should look like this:
+
+{{{
+Bluetooth: Core ver 2.16
+NET: Registered protocol family 31
+Bluetooth: HCI device and connection manager initialized
+Bluetooth: HCI socket layer initialized
+Bluetooth: L2CAP socket layer initialized
+Bluetooth: SCO socket layer initialized
+Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
+(stc): st_register(4)
+(stc):  chnl_id list empty :4
+(stk) : st_kim_start
+plat_kim_chip_enable
+(stk) :ldisc_install = 1
+Bluetooth: BNEP (Ethernet Emulation) ver 1.3
+Bluetooth: BNEP filters: protocol multicast
+(stc): st_tty_open
+(stk) :line discipline installed
+(stk) :TIInit_7.2.31.bts
+(stc): add_channel_to_table: id 4
+(stc): st_register(2)
+(stc): add_channel_to_table: id 2
+(stc): st_register(3)
+(stc): add_channel_to_table: id 3
+Bluetooth: RFCOMM TTY layer initialized
+Bluetooth: RFCOMM socket layer initialized
+Bluetooth: RFCOMM ver 1.11
+Bluetooth: HIDP (Human Interface Emulation) ver 1.2
+}}}
+
+You can now try to start your bluetooth service and try to pair a device, using your favourite BT frontend. If everything works fine, you will want to add a unit file/init script to your system, that UIM gets started automatically on system boot.
+
+'''NOTE:''' There were issues in the authors case. If the wl12xx module is initializing itself (i.e. the network connection is established and the firmware is loaded) and the bluetooth module is loaded around that time, the wl12xx module just spits out errors. The currently used workaround is a 5 second sleep timeout after the network initialization script, before starting UIM and loading btwilink.
+
+Here are some systemd unit files, as an example (Tested under ArchLinux-ARM). It should be sufficient to load the btwilink module via systemds default way (/etc/modules-load.d) and just put the sleep command into the first unit file:
+
+''btwilink.service'':
+{{{
+[Unit]
+Description=Extra BTWiLink module loader
+After=network.target
+Before=uim.service
+
+[Service]
+Type=oneshot
+ExecStart=/bin/sleep 5 ; /sbin/modprobe btwilink
+KillMode=process
+
+[Install]
+WantedBy=multi-user.target
+}}}
+
+''uim.service'':
+{{{
+[Unit]
+Description=UIM Shared transport service
+After=network.target
+Before=bluetooth.target
+
+[Service]
+ExecStart=/usr/sbin/uim
+KillMode=process
+
+[Install]
+WantedBy=multi-user.target
+}}}
 
 ----
@@ -180 +369 @@
 In that order, I will add the following topics (sorting criteria is importance vs. complexicity):
 
- * Provide more kernel-related information (How to build a kernel, providing a archos-patchset used to patch something like the stock android-omap branch, therefore providing a much newer kernel with features like omapfb)
+ * Sound (Some talk about [http://omappedia.org/wiki/Audio_Drive_Arch OMAP path setting])
+ * Provide more kernel-related information (How to build a kernel+initrd(Maybe? That should be clear), providing a newer kernel with the archos patches (WIP))
  * Graphics(Some words about OMAPDSS, Xorg on top of OMAPFB, when providing a newer kernel: OMAPDRM)
- * Wireless
- * Sound (Some talk about [http://omappedia.org/wiki/Audio_Drive_Arch OMAP path setting])
- * Bluetooth
  * Android-gadget related information(USB-Tethering, ...)
  * Ducati-IVA (Video acceleration & Camera)