I will make some code clean and make the sound work in the next few days. It seems the sm501 sound driver needs a hardcoded 8051 firmware to work. Damn it. After these works are done, I will send the patches to loongson-dev maillist and merge it to linux-loongson-community and linux-mips mainline at last.

I am keeping moving....... Please wait.

ps: The linux kernel for gdium repository is here.

kill-bill:~# uname -a
Linux kill-bill 2.6.34-rc2 #24 PREEMPT Fri Apr 16 21:01:51 CST 2010 mips64 GNU/Linux
kill-bill:~# cat /proc/cpuinfo
system type : dexxon-gdium-2f-10inches
processor : 0
cpu model : ICT Loongson-2 V0.3 FPU V0.1
BogoMIPS : 598.01
wait instruction : no
microsecond timers : yes
tlb_entries : 64
extra interrupt vector : no
hardware watchpoint : yes, count: 0, address/irw mask: []
ASEs implemented :
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available

1. gcc-4.3.4
CFLAGS = -s -static -Wall -O3

==========ORIGINAL BYTEMARK RESULTS========
INTEGER INDEX : 16.297
FLOATING-POINT INDEX: 5.864
Baseline (MSDOS*) : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==========LINUX DATA BELOW============
CPU                 :
L2 Cache            :
OS                  : Linux 2.6.24-gdium-1
C compiler          : gcc version 4.3.4 (Debian 4.3.4-5)
libc                : libc-2.9.so
MEMORY INDEX        : 3.156
INTEGER INDEX       : 4.918
FLOATING-POINT INDEX: 3.252
Baseline (LINUX)    : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
* Trademarks are property of their respective holder.

2. gcc-4.4
CFLAGS = -s -static -Wall -O3 -fomit-frame-pointer -funroll-loops
CFLAGS += -march=loongson2f  -mtune=loongson2f  -mabi=n32

==========ORIGINAL BYTEMARK RESULTS========
INTEGER INDEX       : 20.035
FLOATING-POINT INDEX: 10.100
Baseline (MSDOS*)   : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==========LINUX DATA BELOW============
CPU                 :
L2 Cache            :
OS                  : Linux 2.6.24-gdium-1
C compiler          : gcc-4.4
libc                : libc-2.9.so
MEMORY INDEX        : 3.922
INTEGER INDEX       : 5.997
FLOATING-POINT INDEX: 5.602
Baseline (LINUX)    : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
* Trademarks are property of their respective holder.

What I want to post here is not emulating I2C device directly, but emulating GPIO logic which pmon uses to emulate I2C. A little confused? Me too. Ok, let me talk the story from the began.

In pmon, it uses sm502 gpio pin 6 and 13 to emulate I2C master devices, which communicates with other slave device, such as SPD EEPROM and temperature sensors. I do not know why lemote uses gpio to emulate i2c, instead of using the I2C master in sm502. When the data is written to gpio pins according to I2C state machine, pmon expects the gpio pins acting like the I2C master devices. So qemu needs to emulate the I2C cycle accurate state machine, not only the I2C function.

I summarize the I2C emulation code logic of pmon here for reference.

(1) Start Bit

SCL=0 -> SDA=1 -> SCL=1 -> SDA=0 -> SCL=0

(2)Stop Bit

SCL=0 -> SDA=0 ->SCL=1 ->SDA=1 -> SCL=0

(3)Write a bit

Put data on sda -> SCL=1 -> SCL=0

(4)Write a byte

repeating (3) 8 times -> SDA=1

(5)Recv ACK

SCL=1 ->read sda until sda=0 -> SCL=0

(6)Read a bit

SCL=1 -> read data on SDA -> SCL=0

(7)Read a byte

repeating (6) 8 times

(8)Send ACK

put ACK on sda -> SCL=1 -> SCL=0

(9)Send a buffer

Do the following steps until the buffer is empty

1. START
2. Send slave address
3. Recv ACK
4. Send reg address
5. Recv ACK
6. Send one byte
7. Recv ACK
8. STOP

(10) Recv many bytes from slave deviceDo the following steps until finished

1. START
2. Send slave address
3. Recv ACK
4. Send reg address
5. Recv ACK
6. Repeat START
7. Send slave address+1(tell slave we want to recv)
8. Recv ACK
9. Recv a byte
10. Send ACK
11. STOP

Today I try to compile the kernel by myself and the new kernel works well except for network card. I can not see eth0 using ifconfig command. Then I check the pci list of my gdium PCB and find the RTL8139D is on the list.

kill-bill:~# ifconfig eth0
eth0: error fetching interface information: Device not found

kill-bill:~# lspci
00:00.0 MIPS: STMicroelectronics STLS2F Host Bridge (rev 01)
00:0d.0 Network controller: RaLink RT2561/RT61 802.11g PCI
00:0e.0 Display controller: Silicon Motion, Inc. SM501 VoyagerGX Rev. AA (rev c0
)
00:0f.0 USB Controller: NEC Corporation USB (rev 44)
00:0f.1 USB Controller: NEC Corporation USB 2.0 (rev 05)
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139
C+ (rev 10)
00:11.0 USB Controller: NEC Corporation USB (rev 44)
00:11.1 USB Controller: NEC Corporation USB 2.0 (rev 05)

That shows rtl8139 is successfully initialized by the kernel. But why there is no eth0 device?

Then I grep eth0 in dmesg and find that something is wrong with udev.

kill-bill:~# dmesg | grep eth0
eth0: RealTek RTL8139 at 0x9000000051a2a100, 00:d0:35:10:00:20, IRQ 39
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
udev: renamed network interface eth0 to eth1

I cat the udev net rule and find that it sets 8139d with MAC address 00:d0:35:10:00:20 to eth1. That's exactly the network card on my gdium PCB.

kill-bill:~# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x10ec:0x8139 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:d0:35:10:04:a9", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1814:0x0301 (rt61pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:8e:19:3d:68", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

# PCI device 0x10ec:0x8139 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:d0:35:10:00:20", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x1814:0x0301 (rt61pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:8e:19:3b:18", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1"

I know why dev does that now. The debian system is installed on my gdium, not on the PCB and then I just use it on the PCB board. When udev finds there is another 8139d network card with different MAC address it adds another entry in rules to rename it to eth1. After changing the eth1 to eth0 in 70-persistent-net.rules, the network works now.

Following is the kernel information of my new kernel.:)

kill-bill:~# dmesg | grep 2.6.24
Linux version 2.6.24.5-gdiumv3-2.2mnb (root@debian) (gcc version 4.3.3 (GCC) ) #
2 Sat Mar 28 16:00:59 CST 2009

For the sake of portability, the new version of qemu uses TCG, a tiny code generator, instead of dyngen to generate host code. That means one backend is needed for each host architecture. There are i386,x86_64,ppc,ppc64 and hppa backend in TCG, but MIPS is not on the list.

I confirm this conclusion on the status page of qemu web site. The MIPS's status is 'Not Supported'. Perhaps these days the most emergent work is to add MIPS host support, instead of loongson guest support to qemu.

(1) Prepare the new USB disk

Format the new USB disk with at least tow partitions, one is ext2 partition for the root file system and the other is swap space. You can use fdisk to do this.

(2) Install the debian base system using debootstrap

You need to install the debootstrap in gdium first.

urpmi debootstrap

Mount the new USB disk to your gdium, /mnt for example. Replace /dev/sdc1 to the name of your USB device.

mount /dev/sdc1 /mnt

Install the debian base system using debootstrap. You can change lenny to sid if you want to use the debian testing system. To me, I prefer lenny.

debootstrap --arch=mipsel lenny /mnt

It will download the packages and install to system. So please be patient if your network speed is slow.

Copy /etc/resolv.conf  to your new system and set the hostname of the new system.

copy /etc/resolv.conf  /mnt/etc/resolv.conf

echo YOUHOSTNAME > /mnt/etc/hostname

Chroot to your new system.

chroot /mnt /bin/bash

(3) Install the kernel image

wget http://lebesgue.cowpig.ca/~philippe/gdium/linux-2.6.24-gdium-1_2.6.24-gdium-1_mipsel.deb

dpkg -i linux-2.6.24-gdium-1_2.6.24-gdium-1_mipsel.deb

Change /etc/modules to the following:

gdium_laptop
ipv6
i2c_gpio
sm501_gpio
lm75
hwmon_vid
hwmon
eeprom
i2c_dev

Install udev in debian. Otherwise the debian will complain about rtc after rebooting.


apt-get install udev

(4) Reboot your gdium and set the env parameters pf PMON

Reboot the gdium and press DEL on the keyboard when gdium powers up to enter the PMON console. Set the env parameters of PMON to let it loads the correct kernel image and find the correct root file system.

set al /dev/fs/ext2@usbg0/boot/vmlinuz-2.6.24-gdium-1

set karg console=tty0 root=/dev/sda1 rootwait video=sm501fb:1024x600 init=/sbin/init

reboot

Please change root=/dev/sda1 according to your USB disk's partition setting.

(5) Install software in debian

apt-get install lm-sensors

Change the /etc/sensors3.conf to the following:

chip "lm75-*"
set temp1_max      40
set temp1_max_hyst 35

Install the video card driver.

apt-get install xorg

wget http://lebesgue.cowpig.ca/~philippe/gdium/xserver-xorg-video-siliconmotion_1.7.0-0_mipsel.deb

dpkg -i xserver-xorg-video-siliconmotion_1.7.0-0_mipsel.deb

Install lxde desktop. Of course you can install xfce4 or gnome.

apt-get install lxde

Install the wireless card driver and wicd. Change the /etc/apt/sources.list to the following.

deb http://ftp.us.debian.org/debian lenny main non-free
deb http://apt.wicd.net lenny extras

apt-get update

apt-get install firmware-ralink wicd wireless-tools

modprobe rt61pci

Ok. Now you have a working debian lenny system with lxde desktop.

Issues & solutions:

(1) portmap hangs and you can't turn off gdium

Add the following lines to /etc/network/interfaces.

auto lo
iface lo inet loopback

(2)cannot access mtab: Input/output error

That's because /etc/fstab is not configured. Add the follow lines into your /etc/fstab. You can add or delete the partitions if you want.

/dev/sda1 / ext3 noatime 1 1
/dev/sda4 swap swap defaults 0 0
none /tmp tmpfs defaults 0 0
none /var/log tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys/kernel/debug debugfs defaults 0 0

(3) Sound does not work on my system!!

Add you the the audio group.

usermod -a - G audio yajin

(4) The system can not display Chinese characters.

apt-get install locales

dpkg-reconfigure locales

Please make sure zh_CN locale is selected. You can install wqy fonts if you want.

apt-get install xfonts-wqy ttf-wqy-zenhei

(5) How to display the flash player in youtube

apt-get install swfdec-mozilla

The feedbacks are welcome.

Although a little dissatisfied with the shipping express, gdium seems very attractive to me at my first glance for its smart size and its black color. It spend me a little time to make the battery work because I do not know how to assemble the battery at first. The speed of gdium is not as good as I had expected for a 900MHZ CPU. But there is room for optimization because of the N32 MIPS ABI. The screen resolution is excellent, 1024*600 is enough for most of the web sites. The Chinese fonts display very well when I visit the sina.com.cn, thanks to wqy fonts. The Youtube videos can also display very well in Firefox. Awesome! I do not find which plugin does firefox use to display the flash, gnash maybe? The gtk desktop is not very fluent, but that's ok because I will replace it with a lightweight desktop.

Gdium, to me, is a development platform more than a notebook for daily use. I want a MIPS development platform for a long time and gdium is the very one. It is better than the yeeloong notebook, which I planned to buy a few months ago, for gdium has an bigger LCD and good look.

I have too many plans on this new toy, porting android, porting lguest and kvm. But the issue is there is no uart interface on gdium. If you want the uart interface, you need to seal it by yourself. That is too hard to me, a hardware beginner.

If there is an emulator of gdium, life would be much easier. I can use the emulator to test the pmon/linux kernel and lguest porting. I know I can develop a gdium emulator based on qemu, but I have done too much about the emulator stuff, qemu-omap3, qemu-jz, virtualmips and a little fed up with emulator development. But emulator is really a big helper for kernel related development......

Following is my todo list these months.

• install debian and a lightweight desktop for gdium
• develop an emulator of gdium based on qemu
• port lguest and kvm to MIPS
• port android to gdium and tune the performance of dalvik runtime on MIPS target