Date: Mon, 21 Jul 1997 20:41:25 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Cc: msmith@atrad.adelaide.edu.au, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: sound driver structure and configuration Message-ID: <199707211111.UAA22939@genesis.atrad.adelaide.edu.au> In-Reply-To: <199707211004.MAA20937@labinfo.iet.unipi.it> from Luigi Rizzo at "Jul 21, 97 12:04:22 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Luigi Rizzo stands accused of saying: > > > > Then a chipset module might say : > > > > struct snddriver_module foo_codec = { > > foocodec_attach, > > SNDD_TYPE_CODEC, > > (void *)foocodec_function_switch, > > "foo_codec" > > } > > DATA_SET(snddriver, foo_codec); > ... > > Does that make more sense? 8) > > well, this is exactly what I have done! One minor difference, I have > used a "struct pnp_device" as follows: Hmm, you are going out further. I think it is not good at all to call this a "PnP" device; I think that the generic PnP support linker set needs more flexibility than this. (But you're on the right track.) > static struct pnp_device cs4236 = { > "cs4236", > cs4236_probe, > cs4236_attach, > &cs4236_count, > NULL, /* shutdown */ > &tty_imask /* imask */ > }; > > so that I can easily use a different imask when needed. > Maybe I will need more fields in the struct pnp_device to make the > mechanism more flexible for other device types. Oops, reading my thoughts. Do you have copies of Doug Rabson's work on cleaning up the ISA autoconfig process? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707211111.UAA22939>