From jayv@synth.net Thu Feb 19 05:00:21 2004 Received: with ECARTIS (v1.0.0; list devfs); Thu, 19 Feb 2004 05:00:27 -0800 (PST) Received: from p15106599.pureserver.info (p15106599.pureserver.info [217.160.134.213]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i1JD0JKO008029 for ; Thu, 19 Feb 2004 05:00:20 -0800 Received: from synth.net (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by p15106599.pureserver.info (8.11.6/8.11.6) with ESMTP id i1JD0JJ04637 for ; Thu, 19 Feb 2004 13:00:19 GMT Received: from 217.225.53.53 (SquirrelMail authenticated user jayv@synth.net) by www.synth.net with HTTP; Thu, 19 Feb 2004 13:00:19 -0000 (GMT) Message-ID: <58175.217.225.53.53.1077195619.squirrel@www.synth.net> Date: Thu, 19 Feb 2004 13:00:19 -0000 (GMT) Subject: devfsd and /dev/midi00 devices? From: To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 174 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: jayv@synth.net Precedence: bulk X-list: devfs hi all, i hope this is the right list for this - please let me know if it isn't. i have a usb-midi interface i'm trying to get working with my brand new devfsd install, which works fine except for this usb-midi device. its a steinberg 2x2, and was supported just fine before i moved to devfsd and a new kernel/linux distro (rock linux). i need to run a user-space device driver, which was designed to just read/write from /dev/midi00 and /dev/midi01 whatever i do, i cannot get devfsd to understand/recognize that it should create these entries in the devfs - i've tried adding this to my compat file in /etc/devfsd.d/ : #midi REGISTER midi/.* MKOLDCOMPAT UNREGISTER midi/.* RMOLDCOMPAT perhaps that needs to be "REGISTER midi00" instead? if anyone can shed some light on this scenario for a newbie devfsd (but relatively experienced linux) hacker, please let me know what i should do next ... thanks! ; From proski@gnu.org Thu Feb 19 11:28:33 2004 Received: with ECARTIS (v1.0.0; list devfs); Thu, 19 Feb 2004 11:28:39 -0800 (PST) Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i1JJSXKO025625 for ; Thu, 19 Feb 2004 11:28:33 -0800 Received: from proski by fencepost.gnu.org with local (Exim 4.24) id 1AttqM-00052a-Cm; Thu, 19 Feb 2004 14:28:18 -0500 Date: Thu, 19 Feb 2004 14:28:24 -0500 (EST) From: Pavel Roskin X-X-Sender: proski@marabou.research.att.com To: jayv@synth.net cc: devfs@oss.sgi.com Subject: Re: devfsd and /dev/midi00 devices? In-Reply-To: <58175.217.225.53.53.1077195619.squirrel@www.synth.net> Message-ID: References: <58175.217.225.53.53.1077195619.squirrel@www.synth.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 175 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: proski@gnu.org Precedence: bulk X-list: devfs On Thu, 19 Feb 2004 jayv@synth.net wrote: > whatever i do, i cannot get devfsd to understand/recognize that it should > create these entries in the devfs - i've tried adding this to my > compat file in /etc/devfsd.d/ : devfsd is not supposed to create device files. It merely creates links for the device files and does a lot of other things when the kernel creates or destroys device entries on devfs or when a userspace program looks for an entry. So you should look for a midi device that already exists when the driver is loaded. Check that it works and then instruct devfs to create a link to the old location if you want. I haven't worked with sound for a long time. I think the file you are looking for should appear under /dev/sound if using OSS or under /dev/asound is using ALSA. -- Regards, Pavel Roskin