eLinux.org - Changes related to "Category:Linux" [en]

BeagleBone

2013-05-24T15:11:36Z

‎Debian: Wheezy released

RPi VerifiedPeripherals

2013-05-24T06:17:57Z

update Futronic Fingerprint scanner - libScanApi example modified to print error message

Jobs

2013-05-24T00:22:01Z

added a job description

RPi VerifiedPeripherals

2013-05-23T20:14:46Z

add Fingerprints scanners: Futronic F80, FS88 (devices were borrowed by Innovatrics).

RPi VerifiedPeripherals

2013-05-23T18:51:37Z

‎Working USB Wi-Fi Adapters:

RPi VerifiedPeripherals

2013-05-23T18:44:06Z

‎Working USB Wi-Fi Adapters:

RPi Distributions

2013-05-23T13:01:26Z

‎Comparison: Versions and Links update

RPi VerifiedPeripherals

2013-05-22T23:51:34Z

edit links

RPi Distributions

2013-05-22T18:25:38Z

BeagleBone

2013-05-22T04:35:57Z

‎Home page and Community:

BeagleBone

2013-05-20T16:45:05Z

Add a kernel/Capemgr section

Capemgr

2013-05-20T16:38:29Z

Capemgr page. Take from Capebus which I made a minute ago, but was told was the wrong name.

New page

[[Category: Linux]]
[[Category: BeagleBoard]]
[[Category: BeagleBone]]
[[Category: Kernel]]

This page contains information on Capemgr, an in-kernel mechanism for dynamically loading [[Device_Trees|Device Tree]] fragments from userspace.

<br>

= About =

Capemgr was created out of a need for boards like the [[BeagleBone|BeagleBone]] to be able to detect installed expansion boards at boot time and allocate appropriate resources (load drivers, allocate GPIO, reserve bus addresses, etc) on kernels which use Device Tree. Traditionally, a Device Tree was a static file (or set of files) which described a machine (often an Embedded SoC and the board it's installed on). This of course is not able to support dynamically changing hardware, such as the BeagleBone and its add-on capes.

Further, it is one of the goals of the BeagleBone to allow 3rd parties to create their own capes and to allow users to install and use these capes without re-compiling the kernel.

A key feature of Capemgr is the ability to load Device Tree fragments as overlays to the existing Device Tree at runtime. On the BeagleBone, each cape has a Device Tree fragment which describes it.

= Implementation =

Capemgr is completely implemented in the kernel. There is no userspace component. Since the BeagleBone uses a kernel which is ahead of mainline, the Capemgr implementation is currently located in the BeagleBone kernel patch set at https://github.com/beagleboard/kernel/tree/3.8 .

In the BeagleBone kernel, cape Device Tree fragments are located in <code>firmware/capes</code>. Each cape is represented by a single DTS (Device Tree Source) fragment file. At kernel build time, these fragments are compiled by the Device Tree Compiler into dtbo files (Device Tree Blob Object). At install time, these dtbo objects are copied to <code>/lib/firmware</code>.

Each BeagleBone capes has an EEPROM on SPI bus 0 which contains information about the cape. The format of the data in the EEPROM is described in the System Reference Manual (SRM) [http://circuitco.com/support/index.php Available from CircuitCo]. The Board Name EEPROM field is used by Capemgr to determine which cape fragment to load. There are two ways this board name can be used. The first method is that the Board Name can be mapped in the BeagleBone's main Device Tree Source file (<code>arch/arm/boot/dts/am335x-bone-common.dtsi</code>) to a filename using a structure like the following:

/* mrf24j40 cape */
cape@10 {
part-number = "BB-BONE-MRF24J40";
version@00A0 {
version = "00A0";
dtbo = "cape-bone-mrf24j40-00A0.dtbo";
};
};

The above DT snippet maps the device named BB-BONE-MRF24J40 version 00A0 to the file <code>/lib/firmware/cape-bone-mrf24j40-00A0.dtbo</code>

Alternatively, if there is no mapping the the main DTS file, the Capemgr loader will attempt to load a filename which matches the Board Name and Version fields in the EEPROM. For example, for a board named BB-BONE-LCD7-01 with version 00A2, the Capemgr loader will try to load <code>/lib/firmware/BB-BONE-LCD7-01-00A2.dtbo</code> . This way capes can be added to a system without modifying the BeagleBone's main Device Tree (<code>arch/arm/boot/dts/am335x-bone-common.dtsi</code>).

== Loading a Fragment at Runtime ==

Capemgr provides a sysfs interface to load Device Tree fragments at runtime. <code>/sys/devices/bone_capemgr*/</code>contains information and controls for the Capemgr system. To manually load a DTBO fragment, one can run:

echo BB-BONE-MRF24J40 >/sys/devices/bone_capemgr.7/slots

The above command will cause Capemgr to act as though a device with a Board Name of BB-BONE-MRF24J40 was detected. It will then check if there is a mapping in <code>arch/arm/boot/dts/am335x-bone-common.dtsi</code> and load the appropriate dtbo file from <code>/lib/firmware</code>. If not, it will attempt to load <code>/lib/firmware/BB-BONE-MRF24J40-00A0.dtbo</code> as described in the above section.

One can also specify a version number on the command line:

echo BB-BONE-MRF24J40:00A1 >/sys/devices/bone_capemgr.7/slots

This will attempt to load revision 00A1, first using the mapping in <code>arch/arm/boot/dts/am335x-bone-common.dtsi</code>, and then trying to load <code>/lib/firmware/BB-BONE-MRF24J40-00A1.dtbo</code>.

== Compiling a DTS Fragment Outside the kernel build ==

On a BeagleBone, with the default Angstrom image, use the <code>dtc</code> compiler located at <code>/usr/bin/dtc</code> to compile Device Tree sources into DTBO Device Tree objects without modifying any kernel source. The resulting dtbo can be manually copied into <code>/lib/firmware</code>.

Parallella Software

2013-05-20T15:51:50Z

Parallella Hardware

2013-05-20T15:50:49Z

Category:Parallella

2013-05-20T15:45:49Z

Created Parallella category page

New page

[[Category:Categories]]
[[Category:Linux]]
[[Category:Development Boards]]

BeagleBoardUbuntu

2013-05-20T15:27:33Z

wording...

BeagleBoardDebian

2013-05-20T15:26:53Z

‎Debian Wheezy snapshot: debian-7.0.0-console-armhf-2013-05-18

BeagleBoardUbuntu

2013-05-20T15:25:05Z

‎Quantal 12.10 armhf: ubuntu-12.10-console-armhf-2013-05-18

RPi Distributions

2013-05-20T11:07:51Z

uppdatera

RPi VerifiedPeripherals

2013-05-19T14:41:45Z

Updated WIFI adapters, Patriot Memory PCBOWAU2-N now works plug and play in 2013-02-09 Raspbian, also fixed broken link for Patriot Memory PCUSBW1150

RPi VerifiedPeripherals

2013-05-18T16:07:39Z

‎Working Bluetooth adapters:

RPi Distributions

2013-05-18T14:22:02Z

RPi VerifiedPeripherals

2013-05-18T13:45:35Z

‎Working USB Keyboards: - SolidTek

@@ Line 171: / Line 171: @@
 The ARM EABI port is the default port of the standard Debian distribution of Linux for the ARM architecture ("armel").
 EABI ("Embedded ABI") is actually a family of ABIs, and one of the "subABIs" is the GNU EABI for Linux which is used for this port.
-A newer port targeted at newer hardware with another ABI ("armhf") is currently under development and is expected to ship with Debian 7.0 (Wheezy).
+Starting with Debian 7.0 (Wheezy) there is a port targeted at newer (armv7 with fpu) hardware with another ABI ("armhf").
 The [http://www.debian.org/intro/about Debian Project] is strongly committed to software freedom, and has a long pedigree and a good reputation.

@@ Line 2,698: / Line 2,698: @@
 Single finger scanners Futronic FS80 and FS88 tested - they work well with Raspbian. Example of captured fingerprint here: [[Media:Futronic_fingerprint_example.png]]
-To make it working deploy the Futronic libScanAPI on your Raspberry Pi: [[Media:Futronic_ScanApi_armlinux_gnueabihf_gcc472.zip ‎]]
+To make it working deploy the Futronic libScanAPI on your Raspberry Pi (example code and instructions included): [[Media:ScanApi_armlinux_RPi_gnueabihf_gcc472_update1.zip ‎]]
-−
-The original ftrScanAPI_Ex.c example sometimes won't catch the image properly  on RPi, [https://gist.github.com/petervojtek/5638975 here] is the example modified to be more robust.
 == PS2 / AT to USB Converters ==

@@ Line 23: / Line 23: @@
 ! style="width:200px" | Contact Info
 ! style="width:100px" | Expires date
 |-
 | [http://linaro.org Linaro]

@@ Line 2,692: / Line 2,692: @@
 * TEMPer1 (id: 0c45:7401)
 ** works out of the box on raspbian/wheezy with [https://github.com/petervojtek/usb-thermometer pcsensors library]
 == PS2 / AT to USB Converters ==

@@ Line 1,706: / Line 1,706: @@
 * '''ZyXEL'''
 ** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)
 ** [http://www.zyxel.com/products_services/g_202.shtml G-202] model 0586:3410 ZyXEL Communications Corp. ZyAIR G-202 802.11bg using zd1211rw kernel module and zd1211-firmware package

@@ Line 1,575: / Line 1,575: @@
 * '''GMYLE'''
 **  Wireless 11n USB Adapter. Uses RTL8188CUS chipset - cheap on eBay. Installs and works using the install-rtl8188cus-latest.sh script.
 * '''Hawking'''

@@ Line 228: / Line 228: @@
 |-
 | [http://openelec.tv/component/k2/item/235-openelec-on-raspberry-pi-our-first-arm-device-supported OpenELEC]
-| 2013-03-25 (3.0.0)
+| 2013-05-17 (3.0.3)
 | 2012-05-10
 | Linux 3.6.11 (embedded)
 | [http://www.opensource.org/licenses/index.html OSI mixed] (GPLv2 BSD etc)
-| 85 MiB (inc. XBMC)
+| 88 MiB (incl. XBMC)
 | {{yes}}
-| [http://wiki.openelec.tv/index.php?title=Installing_OpenELEC_on_Raspberry_Pi install instructions]<br />
+| [http://www.openelec.tv/get-openelec/download/viewcategory/10-raspberry-pi-builds - Official Downloadsite]<br />
-[http://openelec.tv/component/k2/item/241-openelec-meets-raspberry-pi-part-1 build instructions - part 1]<br />[http://openelec.tv/component/k2/item/242-openelec-meets-raspberry-pi-part-2 build instructions - part 2]<br />[http://sources.openelec.tv/tmp/image/openelec-rpi/ official builds]<br />[http://sparky0815.de/openelec-download-images-fat-files/ raw image (unofficial)]
+[http://wiki.openelec.tv/index.php?title=Installing_OpenELEC_on_Raspberry_Pi - Install instructions]<br />
 | [https://github.com/OpenELEC/OpenELEC.tv/tree/master/packages ~{{formatnum:140}}] (+ [http://wiki.openelec.tv/index.php?title=OpenELEC_Addons_(official) 7] via xbmc)
 | root:openelec<br/>(ssh only)

@@ Line 2,717: / Line 2,717: @@
 Pi Supply offers a 5.25V (+-0.25v) 1500mA power supply, manufactured specially for the Raspberry Pi to account for voltage drop due to the high current draw of the Raspberry Pi when compared to typical (phone charging etc.) duties. This is available in four varieties :
-* [http://www.pi-supply.com/ UK]
+* [http://www.pi-supply.com/product/uk-micro-usb-raspberry-pi-power-supply-5v-1500ma/ UK]
-* [http://www.pi-supply.com/ EU]
+* [http://www.pi-supply.com/product/european-eu-micro-usb-raspberry-pi-power-supply-5v-1500ma/ EU]
-* [http://www.pi-supply.com/ USA]
+* [http://www.pi-supply.com/product/american-usa-micro-usb-raspberry-pi-power-supply-5v-1500ma/ USA]
-* [http://www.pi-supply.com/ AUS]
+* [http://www.pi-supply.com/product/australian-aus-micro-usb-raspberry-pi-power-supply-5v-1500ma/ AUS]
 The Pi Hut offers a 5V 1500mA power supply, manufactured specially for the Raspberry Pi. This is available in three varieties :
@@ Line 2,839: / Line 2,839: @@
 ** Switching Power Supply. Model: PSAC09R-050. Output: 5&nbsp;V, 1.8&nbsp;A, microUSB.  [http://www.digikey.com/product-detail/en/PSAC09R-050/993-1109-ND/2635771 Digi-key Link]
 * '''Pi Supply'''
-** [http://www.pi-supply.com/ 5.25V 1.5A Raspberry Pi USB Power Supply] Comes in 4 varieties for worldwide compatibility - UK, European (EU), American (USA) and Australian (AUS). Is of the detachable USB type so can double up as iPhone/Smartphone charger.
+** [http://www.pi-supply.com/product-category/raspberry-pi-power-supplies/ 5.25V 1.5A Raspberry Pi USB Power Supply] Comes in 4 varieties for worldwide compatibility - UK, European (EU), American (USA) and Australian (AUS). Is of the detachable USB type so can double up as iPhone/Smartphone charger.
 * '''PortaPow'''
 ** PortaPow UK Mains Wall Power Supply

← Older revision	Revision as of 18:25, 22 May 2013
(One intermediate revision by one user not shown)

@@ Line 277: / Line 277: @@
 = Links =
-== Home page and Community ==
+== Home site and Community ==
 * [http://beagleboard.org/ beagleboard.org] -- home for BeagleBoard and BeagleBone products
 * [http://beagleboard.org/Products/BeagleBone%20Black BeagleBone Black] -- manufacturer's page for the second BeagleBone board
@@ Line 288: / Line 288: @@
 * [https://www.linux.com/news/embedded-mobile/mobile-linux/715298-45-beaglebone-black-keeps-eyes-on-raspberry-pi Linux.com report on BeagleBone Black] -- with words from beagleBoard.org's cofounder Jason Kridner
 * [https://github.com/selsinork/beaglebone-black-pinmux github.com/selsinork/beaglebone-black-pinmux] -- pinmux data for BeagleBone Black, including extraction scripts
 == Tutorials and Videos ==

@@ Line 262: / Line 262: @@
 * Download Netbeans (Windows/Linux/OS-X/Solaris): http://www.netbeans.org/
 * Example tutorial on setting this up: http://mechomaniac.com/BeagleboardDevelopmentWithNetbeans
 = FAQ =

← Older revision		Revision as of 15:51, 20 May 2013
Line 1:		Line 1:
−	[[Category: Parallella]]	+	[[Category:Parallella]]
		+	[[Category:Linux]]

	==Introduction==		==Introduction==

← Older revision		Revision as of 15:50, 20 May 2013
Line 1:		Line 1:
−	[[Category: Parallella]]	+	[[Category:Parallella]]
		+	[[Category:Linux]]
		+	[[Category:Development Boards]]

	==Introduction==		==Introduction==

@@ Line 104: / Line 104: @@
 Services Active:
   Note: Depending on your internal network these may work out the box
-  Apache, Port 80: http://arm/ (Bone: or via usb) http://192.168.7.2
+  Apache, Port 80: http://arm/ (Bone: via usb) http://192.168.7.2
-  SSH, Port 22: ssh ubuntu@arm (Bone: or via usb) ubuntu@192.168.7.2
+  SSH, Port 22: ssh ubuntu@arm (Bone: via usb) ubuntu@192.168.7.2
-  shellinabox, Port 4200: https://arm:4200/ (Bone: or via usb) https://192.168.7.2:4200
+  shellinabox, Port 4200: https://arm:4200/ (Bone: via usb) https://192.168.7.2:4200
   Getty, Serial Port

@@ Line 73: / Line 73: @@
 Image Updated:
 *2013-04-26
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
@@ Line 80: / Line 84: @@
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
 ** Bone: v3.2.33-psp26 kernel (--uboot bone_dtb = v3.8.4-bone9)
 Services Active:
   Note: Depending on your internal network these may work out the box
-  Apache, Port 80: http://arm/
+  Apache, Port 80: http://arm/ (Bone: via usb) http://192.168.7.2
-  SSH, Port 22: ssh ubuntu@arm
+  SSH, Port 22: ssh ubuntu@arm (Bone: via usb) ubuntu@192.168.7.2
   Getty, Serial Port
 Get prebuilt image:
-  wget http://rcn-ee.net/deb/rootfs/wheezy/debian-wheezy-console-armhf-2013-04-26.tar.xz
+  wget http://rcn-ee.net/deb/rootfs/wheezy/debian-7.0.0-console-armhf-2013-05-18.tar.xz
 Verify Image with:
-  md5sum debian-wheezy-console-armhf-2013-04-26.tar.xz
+  md5sum debian-7.0.0-console-armhf-2013-05-18.tar.xz
-a1c4ff53f3b2a42419ee1c7c1f47e40  debian-wheezy-console-armhf-2013-04-26.tar.xz
+  dfe308e3e534d8adef75db5308174cf6  debian-7.0.0-console-armhf-2013-05-18.tar.xz
 Unpack Image:
-  tar xJf debian-wheezy-console-armhf-2013-04-26.tar.xz
+  tar xJf debian-7.0.0-console-armhf-2013-05-18.tar.xz
-  cd debian-wheezy-console-armhf-2013-04-26
+  cd debian-7.0.0-console-armhf-2013-05-18
 Install Image:

@@ Line 90: / Line 90: @@
 === Raring 13.04 armhf ===
 Image Updated:
 *2013-04-26
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
@@ Line 97: / Line 101: @@
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
 ** Bone: v3.2.33-psp26 kernel (--uboot bone_dtb = v3.8.4-bone9)
 Services Active:
   Note: Depending on your internal network these may work out the box
-  Apache, Port 80: http://arm/
+  Apache, Port 80: http://arm/ (Bone: or via usb) http://192.168.7.2
-  SSH, Port 22: ssh ubuntu@arm
+  SSH, Port 22: ssh ubuntu@arm (Bone: or via usb) ubuntu@192.168.7.2
   Getty, Serial Port
@@ Line 111: / Line 113: @@
 Get prebuilt image:
-  wget http://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  wget http://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2013-05-18.tar.xz
   mirrors (will take some time to update):
-  wget http://ynezz.ibawizard.net/beagleboard/raring/ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  wget http://ynezz.ibawizard.net/beagleboard/raring/ubuntu-13.04-console-armhf-2013-05-18.tar.xz
 Verify image with:
-  md5sum ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  md5sum ubuntu-13.04-console-armhf-2013-05-18.tar.xz
-  e54b8693cb92b40d694e5885e4a1b86c  ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+c791b69ee4c6ddfd1ce4c9049ecf23e  ubuntu-13.04-console-armhf-2013-05-18.tar.xz
 Unpack image:
-  tar xJf ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  tar xJf ubuntu-13.04-console-armhf-2013-05-18.tar.xz
-  cd ubuntu-13.04-console-armhf-2013-04-26
+  cd ubuntu-13.04-console-armhf-2013-05-18
 If you don't know the location of your SD card:
@@ Line 202: / Line 204: @@
   git clone git://github.com/RobertCNelson/omap-image-builder.git
   cd omap-image-builder
-  git checkout v2013.04 -b v2013.04
+  git checkout v2013.05 -b v2013.05
   touch release
   ./build_image.sh
@@ Line 209: / Line 211: @@
 Image Updated:
 *2013-04-26
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
@@ Line 216: / Line 222: @@
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
 ** Bone: v3.2.33-psp26 kernel (--uboot bone_dtb = v3.8.4-bone9)
 Get prebuilt image:
-  wget http://rcn-ee.net/deb/rootfs/quantal/ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  wget http://rcn-ee.net/deb/rootfs/quantal/ubuntu-12.10-console-armhf-2013-05-18.tar.xz
 Verify image with:
-  md5sum ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  md5sum ubuntu-12.10-console-armhf-2013-05-18.tar.xz
-  b7cd2f94c0dbc75f8d6897e559d52c0a  ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  feb3e41208dba6ec1593ac0b910cff3d  ubuntu-12.10-console-armhf-2013-05-18.tar.xz
 Unpack image:
-  tar xJf ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  tar xJf ubuntu-12.10-console-armhf-2013-05-18.tar.xz
-  cd ubuntu-12.10-console-armhf-2013-04-26
+  cd ubuntu-12.10-console-armhf-2013-05-18
 Then follow directions show above with the other images...

@@ Line 396: / Line 396: @@
 ==BerryTerminal==
 BerryTerminal is a minimal Linux distribution designed to turn the Raspberry Pi mini computer into a low-cost thin client.
- It allows users to login to a central Edubuntu or other LTSP server, and run applications on the central server
+It allows users to login to a central Edubuntu or other LTSP server, and run applications on the central server
 *[http://www.berryterminal.com/doku.php Main Site]
 *[http://dl.berryboot.com/berryterminal-20130321.zip Download]
@@ Line 404: / Line 404: @@
 [http://www.geexbox.org/category/arm/ http://www.geexbox.org/category/arm/]
 ==DarkElec==
 None of the currently available solutions do a perfect job with running XBMC on the Pi, however OpenELEC comes by far the closest, in spite of its locked down nature.

@@ Line 1,622: / Line 1,622: @@
 * '''Patriot Memory'''
-** [http://patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=1198&type=20 PCUSBW1150] Wireless 11N USB adapter  (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub.
+** [http://www.patriotmemory.com/product/detail.jsp?prodline=6&catid=97&prodgroupid=163&id=1198&type=24 PCUSBW1150] Wireless 11N USB adapter  (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub.
-** [http://www.patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=973&type=20 PCBOWAU2-N] Wireless 11N USB adapter  (uses Realtek RTL8191SU chip) Installed using r8712u Kernel module
+** [http://www.patriotmemory.com/product/detail.jsp?prodline=6&catid=97&prodgroupid=163&id=973&type=24 PCBOWAU2-N] Wireless 11N USB adapter  (uses Realtek RTL8191SU chip) Worked immedietly, plug and play in 2013-02-09 Raspbian via powered USB hub.
 * '''Ralink'''

@@ Line 1,766: / Line 1,766: @@
 * IOGear GBU321 (Broadcom BCM2045 Chipset)
 ** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.
 * Trust BT-2400p
 ** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).
@@ Line 1,780: / Line 1,781: @@
 ** [http://dx.com/p/mini-bluetooth-v3-0-usb-2-0-dongle-71248 Bluetooth "3.0" Dongle]. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.
 ** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.
-* Asus USB-BT211
+* '''Asus USB-BT211'''
 ** Shows up as HCI device in Raspbian, but it does not scan or pair.
 ** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962
 == USB Ethernet adapters ==

@@ Line 394: / Line 394: @@
 *[http://rpitc.blogspot.se/ Homepage]
 *[http://rpitc.blogspot.se/p/download.html Dowload]
 ==GeeXboX ARM==
@@ Line 489: / Line 494: @@
 This debian squeeze image created to perform "pwn plug" type of attacks using Raspberry pi.
 pleas look at the wiki for further details [https://sourceforge.net/p/ha-pi/wiki/Home/ Wiki]
 ==Bodhi==

@@ Line 1,082: / Line 1,082: @@
 ** MTS2219 Wireless Keyboard and mouse set. Powered hub NOT used. (B)
-*'''SolidTek'''
+*'''[http://www.solidtekusa.com/ SolidTek]'''
-** Solid Tek KB-P3100BU ASK-3100U.
+** SolidTek KB-P3100BU ASK-3100U.
 *'''Sony'''