mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcin Dalecki <martin@dalecki.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.de>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Mac mini sound woes
Date: Wed, 30 Mar 2005 03:45:38 +0200	[thread overview]
Message-ID: <42c2bacd5f7669ab10d26893873be38a@dalecki.de> (raw)
In-Reply-To: <1112134385.5386.22.camel@mindpipe>


On 2005-03-30, at 00:13, Lee Revell wrote:

> On Tue, 2005-03-29 at 11:22 +0200, Marcin Dalecki wrote:
>> No. You didn't get it. I'm taking the view that mixing sound is simply
>> a task you would typically love to make a DSP firmware do.
>> However providing a DSP for sound processing at 44kHZ on the same
>> PCB as an 1GHZ CPU is a ridiculous waste of resources. Thus most
>> hardware
>> vendors out there decided to use the main CPU instead. Thus the
>> "firmware"
>> is simply running on the main CPU now. Now where should it go? I'm
>> convinced
>> that its better to put it near the hardware in the whole stack. You
>> think
>> it's best to put it far away and to invent artificial synchronization
>> problems between different applications putting data down to the
>> same hardware device.
>
> This is the exact line of reasoning that led to Winmodems.

Yes and BTW those are from a hardware point of view a technically 
perfectly
fine solution. The obstacles here are two fold: Win32 kernel sucks big 
rocks
on latency issues. However since the time we are over 1GHz and use XP 
they work perfectly
fine. On Linux you don't get the necessary DSP processing code/docs. 
Both are just pragmatical arguments which don't apply to sound 
processing at all.
And for you note - I'm the guy who several years ago wrote the first 
ever GDI-Printer
driver for Linux (oki4linux) despite claims from quite prominent people 
here that this couldn't be ever done. And yes I did it in user space 
because pages are not data streams.


  parent reply	other threads:[~2005-03-30  1:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 23:42 Benjamin Herrenschmidt
2005-03-28  1:42 ` Andrea Arcangeli
2005-03-28  2:34   ` Benjamin Herrenschmidt
2005-03-29  3:36 ` Lee Revell
2005-03-29  3:41   ` Benjamin Herrenschmidt
2005-03-29  7:47   ` Marcin Dalecki
2005-03-29  8:18     ` Benjamin Herrenschmidt
2005-03-29  9:22       ` Marcin Dalecki
2005-03-29 10:22         ` Takashi Iwai
2005-03-30  1:45           ` Marcin Dalecki
2005-03-30  2:08             ` Lee Revell
2005-03-30  4:14             ` Lee Revell
2005-03-30  5:15             ` Steven Rostedt
2005-03-29 22:13         ` Lee Revell
2005-03-29 23:25           ` Chris Friesen
2005-03-29 23:39             ` Benjamin Herrenschmidt
2005-03-30  1:48               ` Marcin Dalecki
2005-03-30  5:42                 ` Lee Revell
2005-03-30  1:45           ` Marcin Dalecki [this message]
2005-03-29 10:02   ` Takashi Iwai
2005-03-29 11:04     ` Benjamin Herrenschmidt
2005-03-29 12:12       ` Takashi Iwai
2005-03-29 19:05       ` Lee Revell
2005-03-29 19:31         ` Takashi Iwai
2005-03-29 20:11           ` Lee Revell
2005-03-29 22:03           ` Benjamin Herrenschmidt

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=42c2bacd5f7669ab10d26893873be38a@dalecki.de \
    --to=martin@dalecki.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=tiwai@suse.de \
    /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®