[gyoker]

Hi!I started to look at the kernel logs (dmesg), and I found a few interesting pieces:

eth0: VIA Networking Velocity Family Gigabit Ethernet Adaptereth0: Ethernet Address: 00:40:63:E4:A3:E0

It seems that the kernel detected a gigabit ethernet adapter... so maybe just soldering an RJ45 connector to the right place will add ethernet support ;-)

wmt_pci_initPCI: WonderMidia Technology PCI Bridgepci 0000:00:02.0: reg 10 io port: [0xd8004000-0xd80040ff]pci 0000:00:02.0: reg 14 32bit mmio: [0xd8004000-0xd80040ff]pci 0000:00:04.0: reg 10 32bit mmio: [0xd8007100-0xd80071ff]pci 0000:00:05.0: reg 20 io port: [0xd8007300-0xd800731f]PCI: bus0: Fast back to back transfers disabled

Hmm, pci bus is used, let's see why:

/ # ls -l /sys/bus/pci/devices/lrwxrwxrwx 1 0 0 0 May 29 07:24 0000:00:02.0 -> ../../../devices/pci0000:00/0000:00:02.0lrwxrwxrwx 1 0 0 0 May 29 07:24 0000:00:04.0 -> ../../../devices/pci0000:00/0000:00:04.0lrwxrwxrwx 1 0 0 0 May 29 07:24 0000:00:05.0 -> ../../../devices/pci0000:00/0000:00:05.0/ # ls -l /sys/bus/pci/drivers drwxr-xr-x 2 0 0 0 May 29 07:24 ehci_hcddrwxr-xr-x 2 0 0 0 May 29 07:24 uhci_hcddrwxr-xr-x 2 0 0 0 May 29 07:24 via-velocity

Seems like the usb devices are there, plus something called "via-velocity" (it's the gigabit ethernet)...

Kernel command line: mem=109M noinitrd root=/dev/mtdblock7 rootfstype=yaffs2 rw console=ttyS0,115200n8 init=/init lcdid=1

Hmm, 109M, why not 128M?!

uart.0: ttyS0 at MMIO 0xd8200000 (irq = 32) is a wmt serialuart.1: ttyS1 at MMIO 0xd82b0000 (irq = 33) is a wmt serialuart.2: ttyS2 at MMIO 0xd8210000 (irq = 47) is a wmt serialuart.3: ttyS3 at MMIO 0xd82c0000 (irq = 50) is a wmt serialuart.4: ttyS4 at MMIO 0xd8370000 (irq = 31) is a wmt serialuart.5: ttyS5 at MMIO 0xd8380000 (irq = 30) is a wmt serial

Wow, 6 internal serial ports! Would be nice to get a console on one of those;-)

[wmt-vd] prob /dev/wmt-vd major 236, minor 0, prdt ffc01000/6960000, size 100 KB[wmt-vd] WonderMedia HW decoder driver inited

So, this does have a hardware (video?) decoding block... but:

/ # ls -l /dev/wmt-vdls: /dev/wmt-vd: No such file or directory

Seems like the device is not there, so it's probably not used :-( What a shame... But I'm not 100% sure:

/ # ls -l /dev | grep 236crw-rw-rw- 1 0 0 236, 1 May 29 06:47 jdeccrwxrwxrwx 1 0 0 236, 9 May 29 06:47 vdma

So devices with the same major are there, I suppose jdec = jpec decoder. Maybe it has only hardware jpeg decoder block...

Creating 6 MTD partitions on "mtdsf device":0x000000000000-0x000000d00000 : "filesystem-SF"0x000000d00000-0x000000f80000 : "kernel-SF"0x000000f80000-0x000000fd0000 : "u-boot-SF"0x000000fd0000-0x000000fe0000 : "u-boot env. cfg. 1-SF"0x000000fe0000-0x000000ff0000 : "u-boot env. cfg. 2-SF"0x000000ff0000-0x000001000000 : "w-load-SF"...Creating 6 MTD partitions on "SAMSUNG_K9XXG08UXM":0x000000000000-0x000000300000 : "kernel-NAND"0x000000300000-0x000009900000 : "filesystem-NAND"0x000009900000-0x000012f00000 : "filesystem-data"0x000012f00000-0x000019300000 : "filesystem-cache"0x000019300000-0x000019900000 : "logo-NAND"0x000019900000-0x000080000000 : "user-data-NAND"

Hmm, two flash memories?! First 16MB second 2GB. I suppose the first is the boot flash, it contains uboot and a mini linux filesystem.

udc: VIA UDC driver, version: 3 December 2007 (dma)

udc == usb device composit? (just guessing)

i8042_controller_initI8042_CMD_CTL_TEST ok 0x55write 0x50 cmd 0x1060serio: i8042 AUX port at 0xd8008800,0xd8008804 irq 4serio: i8042 KBD port at 0xd8008800,0xd8008804 irq 23mice: PS/2 mouse device common for all mice

So there is pc keyboard and mouse driver

VT1613 generic driver installed

This is the AC97 audio chipWell, that's it for now...

 

[ricsi]

[quote author=gyoker link=topic=355.msg3089#msg3089 date=1275119074]

Kernel command line: mem=109M noinitrd root=/dev/mtdblock7 rootfstype=yaffs2 rw console=ttyS0,115200n8 init=/init lcdid=1

Hmm, 109M, why not 128M?![/quote]16MB Video Buffer, 3MB Kernel RAM

 

[gyoker]

[quote author=ricsi link=topic=355.msg3094#msg3094 date=1275121540]16MB Video Buffer, 3MB Kernel RAM[/quote]Why would it use 16MB for video buffer? It doesn't seem to have any 3d hw accelerator.Also the kernel ram is managed by the kernel, so it should be included in the 109MB.Usually when a device limits the memory, it's because the rest is used by some other cpu... well... maybe it's used by the dsp? for jpeg decoding?

 

[ricsi]

[quote author=gyoker link=topic=355.msg3097#msg3097 date=1275123198][quote author=ricsi link=topic=355.msg3094#msg3094 date=1275121540]16MB Video Buffer, 3MB Kernel RAM[/quote]Why would it use 16MB for video buffer? It doesn't seem to have any 3d hw accelerator.Also the kernel ram is managed by the kernel, so it should be included in the 109MB.Usually when a device limits the memory, it's because the rest is used by some other cpu... well... maybe it's used by the dsp? for jpeg decoding?[/quote]To be honest ... I do not know. Could indeed be a scratch buffer for the motion JPEG decoding.Here is where I read the info about the 109MB:http://slatedroid.com/index.php?topic=238.0

 

[bushing]

[quote author=gyoker link=topic=355.msg3089#msg3089 date=1275119074]Hi!I started to look at the kernel logs (dmesg), and I found a few interesting pieces:

eth0: VIA Networking Velocity Family Gigabit Ethernet Adaptereth0: Ethernet Address: 00:40:63:E4:A3:E0

It seems that the kernel detected a gigabit ethernet adapter... so maybe just soldering an RJ45 connector to the right place will add ethernet support ;-)[/quote]Nope, sorry. Like the JTAG signals, all of the Ethernet signals are probably brought out to pins on the edge connector of the CPU card but they are not routed on the main board -- even with the datasheet, it's hard to tell which of the dozens of unused pins we'd need. It's not a question of just soldering some wires; you'd need to add a PHY chip (such as the VT6103X). You'd be better off just using a USB Ethernet adapter.

wmt_pci_initPCI: WonderMidia Technology PCI Bridge

Hmm, pci bus is used, let's see why:

Again, don't get your hopes up. I don't know why they placed the Ethernet MAC and the USB controllers on an internal PCI bus instead of an AHB, but it's something that's just internal to the chip and not really useful information.

uart.0: ttyS0 at MMIO 0xd8200000 (irq = 32) is a wmt serialuart.1: ttyS1 at MMIO 0xd82b0000 (irq = 33) is a wmt serialuart.2: ttyS2 at MMIO 0xd8210000 (irq = 47) is a wmt serialuart.3: ttyS3 at MMIO 0xd82c0000 (irq = 50) is a wmt serialuart.4: ttyS4 at MMIO 0xd8370000 (irq = 31) is a wmt serialuart.5: ttyS5 at MMIO 0xd8380000 (irq = 30) is a wmt serial

Wow, 6 internal serial ports! Would be nice to get a console on one of those;-)

I don't know about the other five, but the console (ttyS0) is available on 2 pads on the CPU card and 2 pads under the main PCB. It works much as you'd expect, 3.3v TTL RS232, 115200 8N1.

Creating 6 MTD partitions on "mtdsf device":0x000000000000-0x000000d00000 : "filesystem-SF"0x000000d00000-0x000000f80000 : "kernel-SF"0x000000f80000-0x000000fd0000 : "u-boot-SF"0x000000fd0000-0x000000fe0000 : "u-boot env. cfg. 1-SF"0x000000fe0000-0x000000ff0000 : "u-boot env. cfg. 2-SF"0x000000ff0000-0x000001000000 : "w-load-SF"...Creating 6 MTD partitions on "SAMSUNG_K9XXG08UXM":0x000000000000-0x000000300000 : "kernel-NAND"0x000000300000-0x000009900000 : "filesystem-NAND"0x000009900000-0x000012f00000 : "filesystem-data"0x000012f00000-0x000019300000 : "filesystem-cache"0x000019300000-0x000019900000 : "logo-NAND"0x000019900000-0x000080000000 : "user-data-NAND"

Hmm, two flash memories?! First 16MB second 2GB. I suppose the first is the boot flash, it contains uboot and a mini linux filesystem.

There's a SPI flash chip mounted on the CPU card (the 8-pin chip), and a 2GByte NAND flash chip under the main board. There is also an unused NAND flash footprint on the underside of the CPU card which I'll eventually get around to soldering to; no clue if it works. The memory map for the SPI flash seems to be a lie; using U-Boot to dump below f80000 did not work, so I don't believe there's actually a filesystem in SPI flash, or a kernel. All of that is pulled from the NAND flash.The kconfig file is probably more interesting (/proc/config.gz).

 

[headliner]

Just grep'ing through dmesg and noticed that we have the same MAC address: eth0: VIA Networking Velocity Family Gigabit Ethernet Adapter eth0: Ethernet Address: 00:40:63:E4:A3:E0And agree that that a functional Ethernet connection on the M001 would be difficult.