From: mru@kth.se (Måns Rullgård)
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] Driver Core update for 2.6.1
Date: Wed, 21 Jan 2004 19:39:27 +0100 [thread overview]
Message-ID: <yw1xn08hb0yo.fsf@ford.guide> (raw)
In-Reply-To: <20040121021825.GA6981@kroah.com> (Greg KH's message of "Tue, 20: 18:25 -0800")
Greg KH <greg@kroah.com> writes:
> On Wed, Jan 21, 2004 at 02:59:07AM +0100, Måns Rullgård wrote:
>> Greg KH <greg@kroah.com> writes:
>>
>> > On Tue, Jan 20, 2004 at 06:48:50PM +0100, Måns Rullgård wrote:
>> >> Greg KH <greg@kroah.com> writes:
>> >>
>> >> > On Tue, Jan 20, 2004 at 09:40:22AM +0100, Måns Rullgård wrote:
>> >> >> Greg KH <greg@kroah.com> writes:
>> >> >>
>> >> >> > o ALSA: add sysfs class support for ALSA sound devices
>> >> >>
>> >> >> This is still only completed for the intel8x0 driver, right?
>> >> >
>> >> > The "device" and "driver" symlink will only show up for that driver,
>> >> > yes. But the class support will work for all alsa devices. Now we can
>> >> > add 1 line patches for all of the alsa drivers to enable those
>> >> > symlinks...
>> >>
>> >> I see.
>> >>
>> >> BTW, I still don't get a snd/controlC0 in /udev. All the other ALSA
>> >> devices are there.
>> >
>> > Is there for me :)
>> >
>> > What does /sys/class/sound show for you?
>>
>> $ ls /sys/class/sound
>> pcmC0D0c pcmC0D0p pcmC0D1c timer
>>
>> FWIW, I've updated my kernel to ALSA 1.0.1 and merged your patches.
>
> I don't know if any recent ALSA changes took away the controlC nodes,
> but your sound/core/sound.c::alsa_sound_init() should have a line in it
> that looks like:
> class_simple_device_add(sound_class, MKDEV(major, controlnum<<5), NULL, "controlC%d", controlnum);
> and that should always get called (make sure you took the stupid
> #ifdef CONFIG_DEVFS around that for loop.)
>
> I'm guessing you didn't merge quite right :)
It seems like something did go wrong with my merge. I'm still trying
to get the hang of bitkeeper, so I'll blame it on the learning curve.
--
Måns Rullgård
mru@kth.se
prev parent reply other threads:[~2004-01-21 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 1:10 [BK PATCH] Driver Core update for 2.6.1 Greg KH
2004-01-20 1:12 ` [PATCH] Driver Core update and fixes " Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 1:12 ` Greg KH
2004-01-20 8:40 ` [BK PATCH] Driver Core update " Måns Rullgård
2004-01-20 11:13 ` Andreas Jellinghaus
2004-01-20 17:14 ` Greg KH
2004-01-20 17:48 ` Måns Rullgård
2004-01-21 0:10 ` Greg KH
2004-01-21 1:59 ` Måns Rullgård
2004-01-21 2:18 ` Greg KH
2004-01-21 18:39 ` Måns Rullgård [this message]
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=yw1xn08hb0yo.fsf@ford.guide \
--to=mru@kth.se \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox