All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [RFC][PATCH] fall back to reserved minor numbers
Date: Fri, 14 May 2010 16:55:26 +0800	[thread overview]
Message-ID: <20100514085526.GA7827@localhost> (raw)
In-Reply-To: <s5hpr0yq4mg.wl%tiwai@suse.de>

On Fri, May 14, 2010 at 04:17:27PM +0800, Takashi Iwai wrote:
> At Fri, 14 May 2010 11:28:28 +0800,
> Wu Fengguang wrote:
> > 
> > When the static minor numbers collide because of too many devices,
> > fall back to the reserved minor numbers 2 and 3.
> > 
> > This for example will allow Intel HDMI audio driver to create three PCM
> > devices (index 3, 7, 8; the minor number of the last index will
> > otherwise collide with the first record device).
> > 
> > The other option is to force enable CONFIG_SND_DYNAMIC_MINORS.
> > 
> > Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> 
> Well, frankly, I don't see a big merit of doing this.
> 
> Most (all?) 2.6-based distros are using udev, thus
> CONFIG_SND_DYNAMIC_MINORS should be used there.  The rest is for old
> distros or for some limited systems like embedded devices, and they
> won't need so much PCM devices.
> 
> Even if we do this, it doesn't make sense unless the user-space side
> creates the corresponding device node.

I was afraid of this case: an embedded system with G45 HDMI codec.
This codec only has 1 PCM playback device, however the driver still
requires enabling CONFIG_SND_DYNAMIC_MINORS in order to support more
capable HDMI codecs.

Thanks,
Fengguang

  reply	other threads:[~2010-05-14  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14  3:28 [RFC][PATCH] fall back to reserved minor numbers Wu Fengguang
2010-05-14  8:17 ` Takashi Iwai
2010-05-14  8:55   ` Wu Fengguang [this message]
2010-05-14  8:59     ` 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=20100514085526.GA7827@localhost \
    --to=fengguang.wu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=tiwai@suse.de \
    /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.