some ideas: - start mdb with "-wk". (i'm not actually sure if this will give you read access to device memory, but i'm sure that without you would have to be denied access to device memory since reading devices can change system state.)
- try using kmdb (either load it at boot time with the -k option to the kernel or run mdb -K on the console.) ed On Wed, Feb 07, 2007 at 12:56:22PM -0800, Peter Lawrence wrote: > > > > I'm using mdb -k to view the contents of a schizo interrupt-mapping-register > > 0x4000ee01010\J > > but it fails with > > mdb: failed to read data from target: no mapping for address > > what gives? > > how can io-space and physical addresses be accessed in mdb? > > -Pete. > > (someone allready suggested "mdb -k /dev/ksyms /dev/allkmem", but that > did not help, same error) > > > > ps, the register's physical address can be deduced from the device's > etc/path_to_inst entry: "/ssm at 0,0/pci at 1d,600000/network at 1" 14 "ce" > > > 0x400,0000,0000 IO-space > 0e80,0000 agentID 0x1d << 23 > 60,0000 A-bus > 1000 start offset for Intr-Mapping-Regs > 20 (slot << 2 + pin) * 8 > -------------- > 0x400,0ee0,1020 > > > > _______________________________________________ > mdb-discuss mailing list > mdb-discuss at opensolaris.org
