From: "Iain Sandoe" <iain@sandoe.co.uk>
To: "Michel Dänzer" <daenzerm@student.ethz.ch>
Cc: linuxppc-dev@lists.linuxppc.org, Benjamin Herrenschmidt <bh40@calva.net>
Subject: Re: Updated DMASOUND patches
Date: Thu, 03 Aug 2000 08:42:25 +0100 [thread overview]
Message-ID: <200008030742.IAA26688@hyperion.valhalla.net> (raw)
Thu, Aug 3, 2000, Michel Dänzer wrote:
> Iain Sandoe wrote:
>
>> 2.4.0-test5
>>
>> This is much more flaky **with identical code** there is no crashing (yet)
>> - but a strong tendency for almost any activity to cut off the sound.
>> opening the mixer control is a really good way of doing it. Once the panel
>> is open you can restart the sound and all is hunky-dory... but...
>
> I've noticed that 2.4.0-test4 is much more sluggish than any 2.2 kernel I've
> used. Turning on DMA for the HD (yep, didn't do it automatically) helps a bit,
> but not totally.
According to DMESG DMA *is* on for both SCSI & IDE (IDE doesn't enter into
this really for me - all my disks are SCSI). How could I tell if dmesg were
telling fibs?
>> I guess I'm a little suspicious of the new wait-queue stuff (that's really
>> the only major change to the sound side).
>
> There's a whole new kernel around the sound driver ;)
Fair point... I guess we do interact with the fs stuff, and IRQs and...
and... :-)
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-03 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-03 7:42 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-02 19:50 Updated DMASOUND patches Iain Sandoe
2000-08-02 23:27 ` Michel Dänzer
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=200008030742.IAA26688@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=bh40@calva.net \
--cc=daenzerm@student.ethz.ch \
--cc=linuxppc-dev@lists.linuxppc.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 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.