That id is maintained by the generic bus object and doesn't have anything to do with PCI, but I'm still confident your device's BAR registers are being configured with two overlapping memory regions and causing it to conflict with itself. You could add some DPRINTFs to the part of src/dev/pcidev.cc that handles writes to the BAR registers (around line 270) to see how they're being configured.
Gabe On 12/08/10 06:31, Ong Wen Jian wrote: > Hi Gabe,, > > this is the address range that triggered the fatal error that i send > it to you before this as requested ... > > It seems that it conflict with the ID 7 and may I know what does this > mean ? Is that the device that I'm model is refer to Bus = 0, Device 7 > , Function = 0 in M5 simulator or other devices ?? > > 10040415000: system.iobus: received RangeChange from device id 7 > 10040415000: system.iobus: Adding range 0x800f8000000 - 0x800f80000ff > for id 7 > 10040415000: system.iobus: Adding range 0x800f8000000 - 0x800f80000ff > for id 7 > 10040415000: system.iobus: conflit ID value :7 > fatal: system.iobus has two ports with same range: > system.tsunami.GraphicDevice-pioport > system.tsunami.GraphicDevice-pioport > @ cycle 10040415000 > [recvStatusChange:build/ALPHA_FS/mem/bus.cc, line 531] > > > -- > ONG WEN JIAN > Student > Department of Computer and Communication Systems Engineering, > Faculty of Engineering, Universiti Putra Malaysia > 43400 UPM Serdang, Selangor Darul Ehsan > Tel : 014 - 930 2150 / 017 - 613 6231 > > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
