Subject: Support for AMD Geode Cx5530 companion chipset
To: None <port-i386@netbsd.org>
From: Ian Zagorskih <ianzag@megasignal.com>
List: port-i386
Date: 07/05/2004 21:18:31
Hey all,

I have a board which uses the following hardware:

AMD Geode GX1 CPU
AMD Geode CS5530 Companion Chipset

Chipset is described at:
http://www.amd.com/us-en/ConnectivitySolutions/ProductInformation/0,,50_2330_9863_9907^9912,00.html

dmesg output looks like below:

---cut---
NetBSD 2.0_BETA (EmCORE-n513) #0: Fri Jul  2 19:45:04 NOVST 2004
	ianzag@IANZAG:/usr/src/sys/arch/i386/compile/EmCORE-n513
total memory = 30844 KB
avail memory = 27664 KB
BIOS32 rev. 0 found at 0xfaf10
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: Cyrix MMX-enhanced MediaGX (GXm) (586-class), 300.69 MHz, id 0x540
cpu0: features 808131<FPU,TSC,MSR,CX8>
cpu0: features 808131<CMOV,MMX>
cpu0: I-cache 12K uOp cache 8-way
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: Cyrix Corporation MediaGX Built-in PCI Host Controller (rev. 0x00)
rtk0 at pci0 dev 10 function 0: Realtek 8139 10/100BaseTX
rtk0: interrupting at irq 11
rtk0: Ethernet address 00:05:b7:00:2a:f6
ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000000, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcib0 at pci0 dev 18 function 0
pcib0: Cyrix Corporation Cx5530 I/O Companion Multi-Function South Bridge 
(rev. 0x30)
Cyrix Corporation Cx5530 I/O Companion (SMI Status and ACPI Timer) 
(miscellaneous bridge) at pci0 dev 18 function 1 not configured
Cyrix Corporation Cx5530 I/O Companion (IDE Controller) (IDE mass storage) at 
pci0 dev 18 function 2 not configured
Cyrix Corporation Cx5530 I/O Companion (XpressAUDIO) (audio multimedia) at 
pci0 dev 18 function 3 not configured
vga0 at pci0 dev 18 function 4: Cyrix Corporation Cx5530 I/O Companion (Video 
Controller) (rev. 0x00)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
ohci0 at pci0 dev 19 function 0: Compaq USB Controller (rev. 0x06)
ohci0: interrupting at irq 11
ohci0: OHCI version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: Compaq OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
wdc0 at isa0 port 0x1f0-0x1f7 irq 14
atabus0 at wdc0 channel 0
wdc1 at isa0 port 0x170-0x177 irq 15
atabus1 at wdc1 channel 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0-0xff: using exception 16
wd0 at atabus0 drive 0: <FUJITSU MPG3204AH E>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 19092 MB, 38792 cyl, 16 head, 63 sec, 512 bytes/sect x 39102336 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd1 at atabus1 drive 0: <PQI IDE Flash Disk>
wd1: drive supports 1-sector PIO transfers, LBA addressing
wd1: 32000 KB, 500 cyl, 8 head, 16 sec, 512 bytes/sect x 64000 sectors
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)
---cut---

I'v tried to use generic PCIIDE driver but looks like it dosn't work - lots of 
probe/failure and finally "interface is disabled" for both IDE channels. So 
ATM i had to use obsolete wdc interface.

I'm slowly investigating datasheet for CS5530 but i'm afraid i don't have 
enough experience to implement support for this hardware.

If anybody from pciide world want to join my efforts [remotelly] i'm ready to 
help, assist, test and so on. Hardware is idle and waiting for you :)

BTW there are other on-chip interfaces which claim to be "not configured".

// wbr