public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: nobin matthew <nobin_matthew@yahoo.com>
Cc: kernelnewbies@nl.linux.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: HELP:porting linux PXA audio driver to RTLinux(RTLinux core driver)
Date: Sat, 09 Apr 2005 00:39:38 -0400	[thread overview]
Message-ID: <1113021578.5975.56.camel@mindpipe> (raw)
In-Reply-To: <20050409040327.93029.qmail@web53902.mail.yahoo.com>

On Fri, 2005-04-08 at 21:03 -0700, nobin matthew wrote:
> Dear Friends,
> 
>               I am trying to port Linux PXA audio
> driver to RTLinux. I am using pxa-ac7.c and
> pxa-audio.c
>  and eliminated sound_core.c, and i will register two
> device /dev/mixer and /dev/dsp to RTLinux kernel.
> 
>            The real need is, i wants to generate a sin
> wave using audio codec. With in 600us DMA controller
> should fill the codec FIFO, if that is not met
> distortion will happen. I think normal linux
> interrupts and Process scheduling may cause some
> problems.
> 
> In porting it seems difficult to port kernel
> scheduling , dynamic memory allocation(for DMA) and
> synchronization.

This is the exact same question you posted to linux-audio-dev.  And
you'll get the same answer here:

Don't waste your time with RTLinux.  Use a recent 2.6 kernel with Ingo's
realtime-preempt patches.  Configure with PREEMPT_RT.  This will provide
deterministic, hard realtime performance for any RT constraint down to
about 50 usecs.

RTLinux can meet a ~15 usec RT constraint, the RT preempt kernel will be
able to do this once the timer ISR is made preemptible again.

RTLinux is an obsolescent product that had its place in the 2.4 era but
is being superseded by a solution that's both technically superior and
100% free software.  Real time preemption is the future of hard realtime
on Linux.  All the major real time Linux players have recognized this,
even the ones who had competing solutions for 2.4 are porting their work
to the 2.6 RT-preempt framework.

Besides, RTLinux is a commercial product anyway.  If this project
requires use of RTLinux for political reasons, call your support rep.

Lee


  reply	other threads:[~2005-04-09  4:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-09  4:03 HELP:porting linux PXA audio driver to RTLinux(RTLinux core driver) nobin matthew
2005-04-09  4:39 ` Lee Revell [this message]
2005-04-09  8:26 ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2005-04-09  9:57 nitin ahuja

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=1113021578.5975.56.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=nobin_matthew@yahoo.com \
    /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