All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Russell King <rmk+alsa@arm.linux.org.uk>
Cc: Jaroslav Kysela <perex@suse.cz>, alsa-devel@lists.sourceforge.net
Subject: Re: buffer producer/consumer sync
Date: Wed, 31 Mar 2004 12:31:41 +0100	[thread overview]
Message-ID: <406AAC1D.1090406@superbug.demon.co.uk> (raw)
In-Reply-To: <20040331102710.C32258@flint.arm.linux.org.uk>

Russell King wrote:
> On Wed, Mar 31, 2004 at 11:22:56AM +0200, Jaroslav Kysela wrote:
> 
>>On Wed, 31 Mar 2004, Russell King wrote:
>>
>>
>>>I suggest we add a load of preprocessor junk into the ALSA core and
>>>comment exactly _why_ its needed, thereby laying the reason completely
>>>at the door of these ill-defined APIs where questions have been asked
>>>and responses not been received.
>>
>>I'm thinking to prepare more or less complete patch for all 
>>architectures and send it to LKML for a discussion.
> 
> 
> The problem is that not all architecture maintainers are on lkml.
> 
> Besides, I've tried talking to the architecture maintainers - their
> complete silence since two weeks ago indicates that they just don't
> want to know about this issue.
> 
> As I said on the architecture alias - I've put enough non-rewarding
> time into this issue.  I also have various commercial deadlines
> coming up, so I couldn't work on it even if I wanted to.
> 

If something is broken in the linux kernel (in this case for arm), and 
you submit a patch, and no-one else rejects it without suggesting a 
better way to do it, I can't see why your patch could justifiably being 
rejected.
Of course if no-one else even cares about the problem and you don't have 
write access to the kernel tree, the problem will continue.
I think this might be one of the cases of don't bother discussing it, 
create a patch to do the fix how you think best, and then post it.

One can always use the approach of providing a patch for the linux 
kernel separately, so that any users wishing to use alsa have to first 
apply the patch. At least users can use alsa with arm!

As arm is used on a majority of embedded systems, and as more and more 
embedded systems are using linux, the demand for your patches will 
certainly rise.

As you obviously have support from Jaroslav Kysela, one could probably 
make it so that alsa-driver fails to compile on arm, unless your patch 
is applied to the kernel first. That would certainly provide a BIG 
incentive for your patch to get including into the kernel.

I don't have an ARM platform running linux, but I definetly support your 
efforts to bring alsa to more different platforms.

My 2 cents....

James


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-31 11:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31  5:02 buffer producer/consumer sync Gupta, Kshitij
2004-03-31  7:31 ` Russell King
2004-03-31  7:44   ` Jaroslav Kysela
2004-03-31  7:53     ` Russell King
2004-03-31  8:10       ` Jaroslav Kysela
2004-03-31  8:11         ` Russell King
2004-03-31  8:29           ` Jaroslav Kysela
2004-03-31  8:53             ` Russell King
2004-03-31  9:07               ` Jaroslav Kysela
2004-03-31  9:10                 ` Russell King
2004-03-31  9:22                   ` Jaroslav Kysela
2004-03-31  9:27                     ` Russell King
2004-03-31 11:31                       ` James Courtier-Dutton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-09 11:33 Gupta, Kshitij
2004-03-09 11:46 ` Russell King
2004-03-09 10:40 Gupta, Kshitij
2004-03-09  9:51 Gupta, Kshitij
2004-03-09  9:53 ` Jaroslav Kysela
2004-03-09 10:18   ` Russell King
2004-03-09 10:23     ` Jaroslav Kysela
2004-03-09 10:43       ` Russell King

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=406AAC1D.1090406@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    --cc=rmk+alsa@arm.linux.org.uk \
    /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.