cvs commit: src/sys/dev/aic7xxx ahc_pci.c ahd_pci.c src/sys/dev/ath if_ath_pci.c src/sys/dev/firewire fwohci_pci.c src/sys/dev/fxp if_fxp.c src/sys/dev/puc puc_pci.c src/sys/dev/re if_re.c src/sys/dev/sio sio_pci.c src/sys/dev/uart uart_bus_pci.c ...

Andreas Klemm andreas at FreeBSD.org
Sat Nov 29 10:16:14 PST 2003


On Sat, Nov 29, 2003 at 09:16:03AM +0100, Andreas Klemm wrote:
> On Fri, Nov 28, 2003 at 03:04:04PM -0800, Don Lewis wrote:
> > > Indeed, seems to be the case:
> > > bge0 mem 0xfaff0000-0xfaffffff
> > > cbb0     0xf6000000-0xfbffffff
> > 
> > My R40 located both cbb0 and an0 at 0xc0400000.  Warner tracked down the
> > problem while I was at BSDCon and found an open address range where cbb0
> > could be relocated.  I've now got the following magic incantation in my
> > /boot/loader.conf:
> > 	hw.cbb.start_memory=0xC0800000
> > Look at what address ranges have been allocated and find an open spot.
> > You can type in the above command at the loader prompt for testing
> > purposes.

I was not able to correct my cbb start memory via an entry in 
/boot/loader.conf:

hw.cbb.start_memory=0xc0000000

After next reboot sysctl command shows the correct value in
decimal:

andreas at aklemm[ttyp0]{183} /boot sysctl -a | grep cbb
cbb0: <PCI-CardBus Bridge> at device 1.0 on pci2
pcib2: device cbb0 requested decoded memory range 0xf6000000-0xfbffffff
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb0: [MPSAFE]
cbb0: PCI Configuration space:
cbb1: <PCI-CardBus Bridge> at device 1.1 on pci2
pcib2: device cbb1 requested decoded memory range 0xf6000000-0xfbffffff
cardbus1: <CardBus bus> on cbb1
pccard1: <16-bit PCCard bus> on cbb1
cbb1: [MPSAFE]
cbb1: PCI Configuration space:
cbb0: PC Card card activation failed
hw.cbb.start_memory: 3221225472
                     ^^^^^^^^^^
hw.cbb.start_16_io: 256
hw.cbb.start_32_io: 4096
hw.cbb.debug: 0

But the address ranges of bge0 and cbb0 still overlap:
bge0:                                         mem 0xfaff0000-0xfaffffff
pcib2: device cbb0 requested decoded memory range 0xf6000000-0xfbffffff

Here the complete memory ranges in use:
andreas at aklemm[ttyp0]{185} /boot dmesg | grep mem
agp0: <Intel 82855 host to AGP bridge> mem 0xe0000000-0xe7ffffff at device 0.0 on pci0
pcib1:   memory decode     0xfc000000-0xfdffffff
drm0: <ATI Radeon Lf R250 Mobility 9000 M9> port 0xc000-0xc0ff mem 0xfcff0000-0xfcffffff,0xe8000000-0xefffffff irq 11 at device 0.0 on pci1
pcib2:   memory decode     0xf6000000-0xfbffffff
bge0: <Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002> mem 0xfaff0000-0xfaffffff irq 11 at device 0.0 on pci2
pcib2: device bge0 requested decoded memory range 0xfaff0000-0xfaffffff
pcib2: device cbb0 requested decoded memory range 0xf6000000-0xfbffffff
pcib2: device cbb1 requested decoded memory range 0xf6000000-0xfbffffff
pcm0: <Intel ICH4 (82801DB)> port 0xbc40-0xbc7f,0xb800-0xb8ff mem 0xf4fff400-0xf4fff4ff,0xf4fff800-0xf4fff9ff irq 11 at device 31.5 on pci0
orm0: <Option ROM> at iomem 0xc0000-0xcffff on isa0
pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
pcib2: device pccard0 requested decoded memory range 0xf6000000-0xfbffffff
pcib2: device pccard1 requested decoded memory range 0xf6000000-0xfbffffff
pccard1: function 0, config table entry 1: I/O card; irq mask beb8; iomask 5, iospace 0-1f; memspace 0-ff; io16 irqlevel
pcib2: device pccard1 requested decoded memory range 0xf6000000-0xfbffffff



More information about the cvs-src mailing list