Date: Wed, 1 Sep 2004 23:24:32 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: cg <cg@ijcg.net> Cc: current@freebsd.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item Message-ID: <20040901202432.GB416@ip.net.ua> In-Reply-To: <opsdnw5vq797cmaj@tacitblue3.rings> References: <20040828142503.GA52613@ip.net.ua> <20040829190833.GA9796@cnd.mcgill.ca> <20040829205942.GC39813@ip.net.ua> <opsdjxaeq397cmaj@tacitblue3.rings> <20040831133654.GF31981@ip.net.ua> <opsdnw5vq797cmaj@tacitblue3.rings>
next in thread | previous in thread | raw e-mail | index | archive | help
--L6iaP+gRLNZHKoI4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 01, 2004 at 08:16:33PM +0100, cg wrote: [...] > the /dev entries are /dev/dsp* and /dev/audio*, /dev/sndstat, /dev/mixer*= , =20 > plus the midi ones: /dev/midi* and /dev/sequencer. all of these names ar= e =20 > mandated by the oss spec. >=20 Oh, of course I meant /dev/dsp* when I wrote /dev/pcm*. ;) > i'm not sure about midi device numbering; i believe some cards can =20 > implement multiple midi devices, eg an fm synth, io port and a wavetable = =20 > synth simultaneously. >=20 > pcm won't be a separate device as such; it won't appear in dmesg. this = =20 > probably applies to midi too. >=20 OK. > >So, to summarize, I'd have liked to see the following happen: > > > >- "snd" is the generic sound device (module snd.ko) > >- "snd_foo" is the sound driver for foo (module snd_foo.ko) > >- "pcm" devclass renamed to "snd" > >- "pcm", "mixer", and "midi" devices are created as children of "snd" >=20 > no. pcm and midi will effectively be part of snd. making them separate = =20 > newbus drivers would be tricky and require every driver to be modified. >=20 OK, sounds very good. But what about PCM-related sysctls then? How will hw.snd.pcm0.vchans be represented, for example? hw.snd.0.vchans maybe? > >- repo-copy (and tweak as necessary) all bridge drivers manpages, > > as shown in my patch; > > > >- do *not* repo-copy pcm(4) to sound(4) yet, just link it, possibly > > mentioning in the manpage that the generic driver will soon be > > renamed from "sound" to "snd", > > > >- fix hints in NOTES (as in my patch) to match reality. >=20 > this sounds ok to me. >=20 OK, I will it then. > >When "sound" -> "snd" conversion is actually done, repo-copy > >pcm(4) to sound(4), tweak as necessary, documenting what the > >"sound" device really is, mentioning "pcm", "mixer", and "midi" > >sub-devices, link sound(4) to pcm(4), mixer(4), and midi(4). > > > >Please let me know how to proceed... >=20 > i don't think i can cope with the pressure of getting it into 5.3, so it'= d =20 > be better to postpone it until 5.4 i think. >=20 Sure, that's fine. ;) Can you please send me some plain text paragraph for the pcm(4) manpage that will be linked to the sound(4) manpage, documenting future plans like renaming "sound" to "snd", so people stay tuned? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --L6iaP+gRLNZHKoI4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBNjAAqRfpzJluFF4RAonZAJwLgPFwLuUVr8NKDNdmbRqij/fDdgCgk7Sj 2O3Po8WlV2Aj45TPXMO67aE= =YKeJ -----END PGP SIGNATURE----- --L6iaP+gRLNZHKoI4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040901202432.GB416>