From: Takashi Iwai <tiwai@suse.de>
To: Erik de Castro Lopo <erikd-alsa@mega-nerd.com>
Cc: Jaroslav Kysela <perex@suse.cz>, alsa-devel@lists.sourceforge.net
Subject: Re: Removal of /proc/asound ?
Date: Mon, 19 May 2003 11:46:55 +0200 [thread overview]
Message-ID: <s5h4r3re0a8.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030518081331.7b9eca31.erikd-alsa@mega-nerd.com>
At Sun, 18 May 2003 08:13:31 +1000,
Erik de Castro Lopo wrote:
>
> On Sat, 17 May 2003 13:55:19 +0200 (CEST)
> Jaroslav Kysela <perex@suse.cz> wrote:
>
> > I try to explain these things to avoid more confusion.
> >
> > The dynamic devices created in proc filesystem does things similar as
> > DEVFS.
>
> Thats fine, but now many people runnning 2.4 series kernels are using
> DEVFS?
i guess, no. AFAIK, mandrake is the only major distributor which uses
devfs as default.
> > We used it, because in design time, we changed minor and major
> > numbers for our devices heavily. Once we stabilized our devices, and DEVFS
> > obsoleted our code (DEVFS is more generic), there is no reason to maintain
> > this code anymore. Also, we are only one project doing this and we had
> > requests from the kernel people to remove this code.
>
> Was that request from the 2.4 kernel maintainers or the 2.5 people?
from 2.5 people. ALSA is not in 2.4 kernels.
> If it was a request from the 2.5 kernel people, why is this change impacting
> people running 2.4 kernels.
i also thought of this. in theory, it's not difficult to implement
the compatible layer.
meanwhile, it's not too hard to create device files, too. once if you
made them, then the system works like before.
frankly saying, i'm not sure which is the really better way.
if there are MANY demands on the old way, we'll consider to implement
it back again (but not appearing in the 2.5 kernel tree :)
> > The current situation is that used /dev/snd symlink should be replaced
> > with directory containing static device entries (created by mknod). If you
> > use DEVFS, there is no difference and no extra steps are required.
> >
> > If the driver is installed via standard command 'make install' in the
> > alsa-driver directory, the snddevices script is run automatically when
> > /dev/snd is a symlink.
>
> How will this work if the user does not have a DEVFS enabled kernel?
run snddevices script once. that's all.
ciao,
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful,
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-19 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 22:16 Removal of /proc/asound ? Erik de Castro Lopo
2003-05-17 11:55 ` Jaroslav Kysela
2003-05-17 22:13 ` Erik de Castro Lopo
2003-05-19 9:46 ` Takashi Iwai [this message]
2003-05-19 10:03 ` Erik de Castro Lopo
2003-05-19 10:21 ` Jaroslav Kysela
2003-05-20 4:40 ` Conrad Parker
2003-05-20 5:09 ` David B Harris
2003-05-20 5:48 ` Conrad Parker
2003-05-20 8:15 ` Erik de Castro Lopo
2003-05-20 11:37 ` James Courtier-Dutton
2003-05-19 16:36 ` Patrick Shirkey
2003-05-21 11:18 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5h4r3re0a8.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=erikd-alsa@mega-nerd.com \
--cc=perex@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.