From: "Christopher \"Monty\" Montgomery" <xiphmont@gmail.com>
To: "Pierre Ossman" <drzeus@drzeus.cx>
Cc: "Greg KH" <greg@kroah.com>,
perex@suse.cz, mclasen@redhat.com, jrb@redhat.com,
"Lennart Poettering" <lennart@poettering.net>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
fedora-desktop-list@redhat.com
Subject: Re: [PATCH] alsa: correct nonsensical sysfs device symlinks
Date: Thu, 25 Jan 2007 10:36:55 -0500 [thread overview]
Message-ID: <806dafc20701250736yc5c3048u14ec98e9b6b92574@mail.gmail.com> (raw)
In-Reply-To: <45B8C9A3.6060107@drzeus.cx>
On 1/25/07, Pierre Ossman <drzeus@drzeus.cx> wrote:
> Christopher "Monty" Montgomery wrote:
> >
> > My machines and the fedora rawhide machines using the 2.6.20-rcX
> > releases look nothing like what you pasted. If they did, hald would
> > be working... (I'll note that bugs have also been logged against
> > Pulse and HAL by users having trouble, so it's not just us.)
>
> On my vanilla 2.6.20-rc5, I get the same structure as Greg. Yet hal
> still doesn't pick stuff up as it should.
Interesting to know. Looking more closely, it looks like machines
here are split between the messed up output I forwarded previously and
the output that is expected. All of my personal boxes are messed up.
Having looked at HAL earlier, it appeared to have code to parse the
new format but if it desn't work, it doesn't work. Updating HAL is
relatively easy but I can't test the changes on my own boxes because
they have the messed up /sys/class/sound structure.
Monty
next prev parent reply other threads:[~2007-01-25 15:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 1:50 Christopher "Monty" Montgomery
2007-01-25 4:26 ` Greg KH
2007-01-25 14:11 ` Christopher "Monty" Montgomery
2007-01-25 15:15 ` Pierre Ossman
2007-01-25 15:36 ` Christopher "Monty" Montgomery [this message]
2007-01-25 15:40 ` Pierre Ossman
2007-01-25 15:57 ` Christopher "Monty" Montgomery
2007-01-25 16:54 ` [Alsa-devel] " Takashi Iwai
2007-01-25 17:03 ` Christopher "Monty" Montgomery
2007-01-25 17:30 ` xiphmont
2007-01-25 17:47 ` Takashi Iwai
2007-01-25 18:07 ` xiphmont
2007-01-25 18:23 ` Takashi Iwai
2007-01-25 18:34 ` xiphmont
2007-01-25 18:38 ` Takashi Iwai
2007-01-25 18:51 ` xiphmont
2007-01-25 19:49 ` Greg KH
2007-01-25 20:40 ` xiphmont
2007-01-25 21:59 ` Greg KH
2007-01-26 10:53 ` xiphmont
2007-01-26 11:40 ` Takashi Iwai
2007-01-26 18:04 ` Greg KH
2007-01-26 18:25 ` Takashi Iwai
2007-01-26 18:31 ` xiphmont
2007-01-26 19:06 ` Greg KH
2007-01-26 21:58 ` xiphmont
2007-01-26 18:03 ` xiphmont
2007-01-26 18:42 ` Greg KH
2007-01-25 17:48 ` Christopher "Monty" Montgomery
2007-01-25 11:27 ` Pierre Ossman
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=806dafc20701250736yc5c3048u14ec98e9b6b92574@mail.gmail.com \
--to=xiphmont@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=drzeus@drzeus.cx \
--cc=fedora-desktop-list@redhat.com \
--cc=greg@kroah.com \
--cc=jrb@redhat.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mclasen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®