Date: Thu, 3 Sep 2009 16:46:58 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-current@FreeBSD.org, Tim Kientzle <kientzle@FreeBSD.org>, Astrodog <astrodog@gmail.com> Subject: Re: Reducing noise in dmesg output Message-ID: <alpine.BSF.2.00.0909031645560.81808@fledge.watson.org> In-Reply-To: <4A9FDFD6.2090305@icyb.net.ua> References: <200909010931.16880.nick@van-laarhoven.org> <1251841416.1689.4458.camel@balrog.2hip.net> <200909021656.15747.nick@van-laarhoven.org> <2fd864e0909021645p735e22b8id7d41f4b5a0ee89e@mail.gmail.com> <4A9F4DC1.4010002@freebsd.org> <alpine.BSF.2.00.0909031035260.36214@fledge.watson.org> <4A9FDFD6.2090305@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
University of Cambridge On Thu, 3 Sep 2009, Andriy Gapon wrote: > on 03/09/2009 12:38 Robert Watson said the following: [snip] >> devinfo(8) captures some of this, but can't, for example, cleanly represent >> an IRQ being shared by multiple devices > [snip] > > Minor technical nit - devinfo can actually do it (since r192379). I stand pleasantly corrected :-). However, I think the point holds: we're relying on dmesg as the authoritative source of hardware discovery/probe information, and really, we should be using some more structured way of delivering that information, generic or device-specific. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0909031645560.81808>