On Thu, 22 Nov 2012 08:12:17 +0100, Adrian Chadd <adr...@freebsd.org> wrote:

On 21 November 2012 20:16, Ian Smith <smi...@nimnet.asn.au> wrote:
On Wed, 21 Nov 2012 12:08:42 -0800, Adrian Chadd wrote:
 > .. because some of us like kernel behaviour to be predictable and
 > controllable, rather than 'just be dynamic here, what could possibly
 > go wrong.'
 >
 > Just bump the default kernel buffer size up to 64k and leave it
 > hard-coded like that. Us embedded people can drop that down to
 > something smaller.
 >
 > There. Problem solved, right?

Well maybe, but I still tend to take Andriy's point about snd_hda.  For
example, Lars Engels posted several verbose dmesgs the other day, not to
do with sound, one of which was:
 http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10.works

T61_dmesg.boot.10.works (file 1 of 2) lines 1813-1861/1861 byte 82415/82415

Cutting just the hdaa0, pcm0 and pcm1 stuff results in:

hda_pcm.verbose (file 2 of 2) lines 712-760/760 byte 28531/28531

Is there a way to extract this topology information out of the driver
without putting it in the verbose output?

Adrian

Maybe via /dev/sndstat. See hw.snd.verbose in sound(4). An additional level 5 for super verbose information?

Ronald.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to