linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Takashi Oe <toe@unlserve.unl.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap
Date: Fri, 19 Jan 2001 10:04:41 +0000	[thread overview]
Message-ID: <20010119100317.203BE2EFC8@apollo.valhalla.net> (raw)


I believe there is a danger we are missing the point of ed21 of the driver.

1/ the main point... is that I believe the dbdma stuff is now working
reliably - which should make record functional and playback robust.

2/ In fact - the driver has, for some time, been compliant (AFAICT) with OSS
Progammer's Guide 1.1 (June 2000).  So, I suppose that I could just say "if
the app gives noise - it's broken".

If anyone believes that there is an error in this compliance - I'll be happy
to try & fix it or help someone else do so.

3/ The "pismo LE fix" is a small part and quite easily backed out of/left in
as people like.  It is no more/less "correct" to include it in the driver
than some of the other stuff that's already there.

4/ The driver offers (in the official, released version) a number of
non-native formats as valid input.  I do not believe it is "strictly
necessary" under OSS rules to do this.

-----

otherwise, I agree with you on the principles (not putting stuff in the
kernel that belongs in user space).

I would find it just as wasteful as you to swap data twice - for 'real'
(a.k.a. paid) work I write a fair bit of real time dsp code...

... but I don't think I had better comment further on stuff which is mostly
reported to me rather than tested (personally) by me.  It is, of course,
possible that people are reporting errors with old versions of apps - but
this path is usually checked in discussion of reported "format bugs" in the
driver.

ciao,
Iain.

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

             reply	other threads:[~2001-01-19 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19 10:04 Iain Sandoe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-19  4:11 [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap Iain Sandoe
2001-01-19  5:21 ` Takashi Oe
2001-01-19  2:30 Iain Sandoe
2001-01-19  3:05 ` 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=20010119100317.203BE2EFC8@apollo.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    /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).