From: Chris Friesen <cfriesen@nortel.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Marcin Dalecki <martin@dalecki.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: Mac mini sound woes
Date: Tue, 29 Mar 2005 17:25:40 -0600 [thread overview]
Message-ID: <4249E3F4.8070005@nortel.com> (raw)
In-Reply-To: <1112134385.5386.22.camel@mindpipe>
Lee Revell wrote:
> This is the exact line of reasoning that led to Winmodems.
My main issue with winmodems is not so much the software offload, but
rather that the vendors don't release full specs.
If all winmodem manufacturers released full hardware specs, I doubt
people would really complain all that much. There's a fairly large pool
of talent available to write drivers once the interfaces are known.
Chris
next prev parent reply other threads:[~2005-03-29 23:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 23:42 Mac mini sound woes 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 [this message]
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
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=4249E3F4.8070005@nortel.com \
--to=cfriesen@nortel.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--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