From: "John W. Linville" <linville@tuxdriver.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: "Dan Williams" <dcbw@redhat.com>,
"Ivo van Doorn" <ivdoorn@gmail.com>,
"Ozan Çağlayan" <ozan@pardus.org.tr>,
linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870
Date: Wed, 14 Oct 2009 10:15:40 -0400 [thread overview]
Message-ID: <20091014141540.GC2890@tuxdriver.com> (raw)
In-Reply-To: <200910140042.39800.bzolnier@gmail.com>
On Wed, Oct 14, 2009 at 12:42:39AM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 14 October 2009 00:24:58 Dan Williams wrote:
> > The point here is, often stuff works for some and not for others. That
> > doesn't mean it's "broken". It's broken for you, and that should get
> > fixed, but the whole system is by no means a loss and its pretty stupid
> > to generalize things like "play skip-lessly on standard AC97/HDA cards
> > is impossible" when it clearly isn't.
>
> Interesting, do you mean that you are able to get skipless mp3 playback
> under i.e. audacious (using the default pulseaudio output plugin) under
> heavy load (i.e. kernel build) with internal speakers (or headphones)?
>
> If so must by my luck then -- F11 on old Acer laptop (Intel 8x0 in ICH4M)
> and fedora-rawhide on new Asus K50AB one (Intel HDA in AMD/ATI SB710)..
Much as I enjoy a good Fedora audio discussion, perhaps it is time
to end this one or move it elsewhere?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-10-14 14:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 11:24 Current status of rt2800usb and staging/rt2870 Ozan Çağlayan
2009-10-13 15:52 ` Ivo van Doorn
2009-10-13 17:27 ` Bartlomiej Zolnierkiewicz
2009-10-13 18:17 ` Ivo van Doorn
2009-10-13 19:21 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:00 ` Ivo van Doorn
2009-10-13 20:42 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:15 ` Dan Williams
2009-10-13 21:57 ` Bartlomiej Zolnierkiewicz
2009-10-13 22:21 ` Luis Correia
2009-10-14 14:14 ` John W. Linville
2009-10-13 22:24 ` Dan Williams
2009-10-13 22:42 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:15 ` John W. Linville [this message]
2009-10-14 1:58 ` Thomas Fjellstrom
2009-10-14 13:51 ` Ivo van Doorn
2009-10-14 14:09 ` John W. Linville
2009-10-14 14:52 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:56 ` John W. Linville
2009-10-14 15:28 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:47 ` John W. Linville
2009-10-14 17:33 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:26 ` Luis Correia
2009-10-14 20:41 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:56 ` Ivo van Doorn
2009-10-14 20:10 ` Bartlomiej Zolnierkiewicz
2009-10-15 6:28 ` Gertjan van Wingerde
2009-10-15 9:47 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:55 ` Luis R. Rodriguez
2009-10-15 14:47 ` Bartlomiej Zolnierkiewicz
2009-10-15 19:06 ` Luis R. Rodriguez
2009-10-16 17:13 ` Bartlomiej Zolnierkiewicz
2009-10-14 1:52 ` Mike Galbraith
2009-10-13 16:44 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:41 ` Ozan Çağlayan
2009-10-13 20:44 ` Bartlomiej Zolnierkiewicz
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=20091014141540.GC2890@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bzolnier@gmail.com \
--cc=dcbw@redhat.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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.