public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Dave Jones <davej@redhat.com>
Cc: Olivier Galibert <galibert@pobox.com>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [RFC] userland swsusp
Date: Thu, 17 Nov 2005 15:46:07 -0500	[thread overview]
Message-ID: <1132260368.5959.4.camel@mindpipe> (raw)
In-Reply-To: <20051117203731.GG5772@redhat.com>

On Thu, 2005-11-17 at 15:37 -0500, Dave Jones wrote:
> I don't know about other distros, but here's how that usually goes for Fedora users..
> 
> 1. user installs new release, and sound doesn't work.
> 2. user blames ALSA, bug gets filed against kernel.
> 3. I take a look, sometimes we get to play "ping pong the bug between
>    userspace & kernel component" for a while
> 4. I throw my hands in the air and say "tell the upstream ALSA developers"
> 5. user does so
> 6. user comes back to Fedora bugzilla with the response
>    "Alsa people told me its a Fedora bug".
> 
> So, given we ship unpatched[1] ALSA, my faith in the
> possibility of ALSA working "OOTB" is somewhat lacking.
> 
> These bugs usually sit in our bugzilla, every so often
> I'll ping them after I've rebased to a new release, and
> surprise surprise, they magically get fixed.
> (Although every release we seem to trade one set of
>  working sound drivers for a new set of broken ones).

The process would work a lot faster if the Fedora project would
contribute anything at all to ALSA development.  It's a lot of work!  I
haven't seen a line of sound driver code from anyone at Red Hat since
the OSS->ALSA transition, years ago.  Meanwhile the vendors keep getting
cheaper and cheaper, which means more functionality that used to be in
hardware has to be done in the drivers.

For example the Debian people are very helpful, they have someone who
filters out the real bug reports from their users and pushes them into
the ALSA bug tracker.  Fedora just points clueless users at the ALSA bug
tracker and tells them "good luck".

Lee


  reply	other threads:[~2005-11-17 20:46 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 16:10 [linux-pm] [RFC] userland swsusp Gross, Mark
2005-11-16 16:44 ` Greg KH
2005-11-16 20:20   ` Nigel Cunningham
2005-11-16 22:05     ` Pavel Machek
2005-11-16 21:13       ` Nigel Cunningham
2005-11-16 22:41         ` Rafael J. Wysocki
2005-11-16 22:50         ` Pavel Machek
2005-11-17 17:02       ` Olivier Galibert
2005-11-17 19:57         ` Lee Revell
2005-11-17 20:12           ` Olivier Galibert
2005-11-17 20:20             ` Lee Revell
2005-11-17 20:37               ` Dave Jones
2005-11-17 20:46                 ` Lee Revell [this message]
2005-11-17 20:59                   ` Dave Jones
2005-11-17 20:54                 ` Lee Revell
2005-11-17 21:01                   ` Dave Jones
2005-11-17 21:06                   ` Chris Wright
2005-11-17 21:14                     ` Lee Revell
2005-11-17 21:18                       ` Chris Wright
2005-11-17 21:45                         ` Diego Calleja
2005-11-17 21:09                 ` Matthew Garrett
2005-11-17 21:16                   ` Lee Revell
2005-11-17 20:47             ` Lee Revell
2005-11-17 20:50             ` software mixing [was Re: [linux-pm] [RFC] userland swsusp] Lee Revell
2005-11-16 22:10     ` [linux-pm] [RFC] userland swsusp Greg KH
2005-11-16 21:25       ` Nigel Cunningham
2005-11-17  7:14         ` Arjan van de Ven
2005-11-16 19:10 ` Pavel Machek
2005-11-17 16:54   ` Olivier Galibert
2005-11-17 16:44     ` Greg KH
2005-11-17 17:03       ` Patrick Mochel
2005-11-17 17:31       ` Olivier Galibert
2005-11-17 20:15       ` Jacek Kawa
2005-11-17 21:56         ` Greg KH
2005-11-18 17:41           ` Jacek Kawa
2005-11-18 23:22     ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2005-11-17 18:50 Starikovskiy, Alexey Y
2005-11-15 21:29 Pavel Machek
2005-11-15 21:32 ` [linux-pm] " Greg KH
2005-11-15 22:03   ` Pavel Machek
2005-11-15 22:25 ` Dave Jones
2005-11-15 23:32   ` Pavel Machek
2005-11-15 23:40     ` Dave Jones
2005-11-16  8:56       ` Pavel Machek
2005-11-16 21:41       ` Rafael J. Wysocki
2005-11-16  4:35     ` Dumitru Ciobarcianu
2005-11-16  6:14       ` Greg KH
2005-11-16  6:00         ` Nigel Cunningham
2005-11-16 16:50           ` Greg KH
2005-11-16 19:57             ` Nigel Cunningham
2005-11-16 21:35               ` Pavel Machek
2005-11-16 21:13                 ` Nigel Cunningham
2005-11-16 22:47                   ` Pavel Machek
2005-11-16 21:53                     ` Nigel Cunningham
2005-11-23 10:16                     ` Lorenzo Colitti
2005-11-23 12:02                       ` Pavel Machek
2005-11-19  9:32           ` Rob Landley
2005-11-19 23:51             ` Pavel Machek
2005-11-18 19:36   ` Alan Cox
2005-11-18 21:18     ` Dave Jones
2005-11-18 21:20       ` Greg KH
2005-11-19 23:43       ` Pavel Machek
2005-11-20 21:48         ` Dave Jones
2005-11-20 22:09           ` Pavel Machek
2005-11-21 11:47             ` Rafael J. Wysocki
2005-11-21 14:19               ` Pavel Machek
2005-11-18 21:23     ` Arjan van de Ven
2005-11-18 22:07       ` Alan Cox
2005-11-19  4:18         ` Jesse Barnes
2005-11-19  8:44         ` Arjan van de Ven
2005-11-18 23:34     ` Pavel Machek

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=1132260368.5959.4.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=davej@redhat.com \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.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