Subject: Quick question about autoconf and the emuxki driver
To: None <tech-kern@NetBSD.org>
From: Mark Kirby <firstname.lastname@example.org>
Date: 11/10/2004 09:43:19
I've started reading up on NetBSD kernel hacking and i think i'm starting to
understand the autoconf framework. The reason i'm looking is i want to work
on adding midi support to the emuxki driver.
I have an audigy 2 based sound card, on boot up i get
emuxki0 at pci0 dev 11 function 0: Creative Labs SB Audigy EMU 10000 (audio
multimedia, revision 0x04)
emuxki0: ac97: SigmaTel STAC9721/23 codec; 18 bit DAC, 18 bit ADC, SigmaTel 3D
emuxki0: ac97: ext id 200<AMAP>
audio0 at emuxki0: full duplex, mmap, independent
emuxki0: interrupting at irq 11
Creative Labs product 0x7003 (miscellaneous input, revision 0x04) at pci0 dev
11 function 1 not configured
Creative Labs product 0x4001 (Firewire serial bus, interface 0x10, revision
0x04) at pci0 dev 11 function 2 not configured
I think i understand how the emuxki driver is hooked up to the audio bus, but
what i don't understand is how the two 'not configured' lines are generated.
I was under the impression that the console messages were generated from code
in a drivers attach method, but the emuxki driver's attach method doesn't
seem to have anything related to Firewire or miscellaneous input.
So i'm clearly missing something. Can someone enlighten me or point me in the
right direction, it would be greatly appreciated.