linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Oe <toe@unlserve.unl.edu>
To: Iain Sandoe <iain@sandoe.co.uk>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap
Date: Thu, 18 Jan 2001 21:05:25 -0600	[thread overview]
Message-ID: <B68D0B14.5857%toe@unlserve.unl.edu> (raw)
In-Reply-To: <20010119022903.3D8D02F01D@apollo.valhalla.net>


On 1/18/01 8:30 PM, Iain Sandoe wrote:

> my only justification is a case of expediency:
>
> many apps ; one driver ; very, very few linux ppc audio developers.

Do you have any hard number?  How many *popular* apps does the pismo change
break?  I don't there are so many linux audio apps to begin with.

> If and when ALSA is accepted into linux we can/will throw this current
> driver away.  If it is built as a module - it has no lasting impact on the
> kernel.

I think ALSA will be in, but do you know for sure OSS will go away?
Besides, people will be using 2.4 for a long time, and I don't think OSS
will go away from 2.4 ever.


Takashi Oe


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-19  3:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19  2:30 [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap Iain Sandoe
2001-01-19  3:05 ` Takashi Oe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-19 10:04 Iain Sandoe
2001-01-19  4:11 Iain Sandoe
2001-01-19  5:21 ` Takashi Oe
2001-01-19  1:47 Iain Sandoe
2001-01-19  2:03 ` Takashi Oe
2001-01-19  0:04 Iain Sandoe
2001-01-19  0:51 ` Takashi Oe

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=B68D0B14.5857%toe@unlserve.unl.edu \
    --to=toe@unlserve.unl.edu \
    --cc=iain@sandoe.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).