Date: Sat, 04 Nov 2000 22:03:11 -0700 From: Warner Losh <imp@village.org> To: Mike Smith <msmith@FreeBSD.ORG> Cc: hackers@FreeBSD.ORG Subject: Re: user-space resource information... Message-ID: <200011050503.WAA47135@harmony.village.org> In-Reply-To: Your message of "Sat, 04 Nov 2000 03:43:28 PST." <200011041143.eA4BhSF08392@mass.osd.bsdi.com> References: <200011041143.eA4BhSF08392@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200011041143.eA4BhSF08392@mass.osd.bsdi.com> Mike Smith writes: : Well, I'm really sick of people complaining about not being able to get : at the things the resource manager knows from userspace. So I've done : something about it. Cool. I've wanted this for some time now. : 0: Interrupt request lines 0x0-0xf Nuke the leading numbers. No clue what they mean anyway. How are shared interrupts reported? I have several machines that share lots of interrupts. I'd also print decimal for small valued things, like those with a range <= 32. : 2: I/O ports 0x0-0xffff : 0: atdma0 0x0-0xf : 2: atpic0 0x20-0x21 This explains why the pccard code was, for a time, trying to assign 0x10-0x1f for a device I plugged in... :-) : 0: sysresource0 0x0-0x9ffff : 1: vga0 0xa0000-0xbffff active shareable : 3: sysresource0 0xcd000-0xcffff : 5: sysresource0 0xe8000-0xeffff : 6: sysresource0 0xf0000-0xf3fff : 7: sysresource0 0xf4000-0xf7fff : 8: sysresource0 0xf8000-0xfffff : 9: sysresource0 0x100000-0x7ffffff : 11: fxp0 0xe3000000-0xe3000fff active : 13: sysresource0 0xfffe0000-0xffffffff This looks a little ugly as well, but I don't have a better format. I'll dink with things and see if there's any way I can improve the output. How hard would that device tree be now? Or is there extra hair that's needed for that. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011050503.WAA47135>