Causes dmesg trash too.

I *can* use *either* card alone but not BOTH. 

I think both my r128 and mach64 kernel modules are trying to use /dev/drm/card0
and that is causing confusion. 

there might be an options switch for this somewhere but it's not documented... 

The drm.ko should automaticly assign a unique ./drm/card[N] for each device. 

Secondary to this is that my test application (which I am trying to debug)
displays markedly different color blending charactoristics on the two cards! 

I need to know which behavior is correct! =P 


########################
Adding 1004052k swap on /dev/hda2.  Priority:-1 extents:1
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 19 (level, low) -> IRQ 19
[drm] Initialized drm 1.0.0 20040925
[drm] Initialized r128 2.5.0 20030725 on minor 0: ATI Technologies Inc Rage 128
RF/SG AGP
[drm] Used old pci detect: framebuffer loaded
[drm] Initialized mach64 1.0.0 20020904 on minor 1: ATI Technologies Inc 3D Rage
Pro 215GP
[drm] Used old pci detect: framebuffer loaded
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (8188 buckets, 65504 max) - 220 bytes per conntrack
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. 
http://snowman.net/projects/ipt_recent/
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
agpgart: Putting AGP V2 device at 0000:01:05.0 into 0x mode
[drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held, held  0
owner 00000000 f52f8240
[drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held, held  0
owner 00000000 f52f8240
[drm:drm_lock_take] *ERROR* 1 holds heavyweight lock
dmesg.mach64 lines 225-297/297 (END) 
####################