Date: Thu, 11 Nov 1999 22:40:12 -0700 (MST) From: "Kenneth D. Merry" <ken@kdm.org> To: tanimura@r.dl.itc.u-tokyo.ac.jp (Seigo Tanimura) Cc: chris@calldei.com, sjr@home.net, freebsd-bugs@FreeBSD.ORG Subject: Re: make_dev() warnings Message-ID: <199911120540.WAA32579@panzer.kdm.org> In-Reply-To: <199911120524.OAA11399@rina.r.dl.itc.u-tokyo.ac.jp> from Seigo Tanimura at "Nov 12, 1999 02:24:30 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Seigo Tanimura wrote... > On Thu, 11 Nov 1999 21:14:04 -0700 (MST), > "Kenneth D. Merry" <ken@kdm.org> said: > >> It would help to add a new argument to periph_init_t, so that a unit > >> number(or a periph?) can be passed from sys/cam/cam_xpt.c:xpt_finishconfig() > >> to sys/cam/cam_xpt.c:xpt_periph_init() and the other functions. None > >> of the CAM drivers seem to call make_dev(). > > ken> If I can decipher what you're saying there, I think you're talking about > ken> probably having cam_periph_alloc() or something similar allocate the dev_t > ken> node at attach time. > > Yes, that is my main idea. > > > ken> - the sa and target drivers have multiple minor device nodes, and the > ken> sa(4) driver in particular has a large number of minor entries, and a > ken> weird minor numbering scheme > > pcm(4) has several minor numbers as well. It simply calls make_dev() for > each of mixer, audio, dsp and dspW. Could the number of the minor entries > for sa(4) depend on a drive? The minor numbers for sa(4) are the same for each drive. The problem is that the minor number scheme for sa(4) isn't the same as the minor number scheme for pass(4), which isn't the same as the scheme for the target driver. In other words, there's no clean way to have a common set of make_dev() code for all CAM peripheral drivers. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911120540.WAA32579>