Does anyone know if a port of the ALSA 0.5.x drivers to QNX4 is being
attempted?
TIA,
MJ
It is not being attempted by anyone inside of
QNX Software Systems Ltd. All of the audio guys are
busily moving forward with improved support for QNX RtP
at this time.
In comp.os.qnx Mark Johnson <nooz@my-deja.com> wrote:
Does anyone know if a port of the ALSA 0.5.x drivers to QNX4 is being
attempted?TIA,
MJ
QNX4 is dead, QtP isn’t ready yet. You can either wait a bit for
QtP (like us) or I heard ALSA supports linux very well.
In comp.os.qnx Mark Johnson <> nooz@my-deja.com> > wrote:
Does anyone know if a port of the ALSA 0.5.x drivers to QNX4 is being
attempted?TIA,
MJ
\
The alsa 5 source is available from the free software section
on our webpage (http://www.qnx.com/cgi-bin/dir_find.cgi?/usr/free/).
I am not sure how easy of a port it would be, but, the source is
all there if you want to try it.
Don
In qdn.public.qnx4 Frank Liu <liug@mama.indstate.edu> wrote:
: QNX4 is dead, QtP isn’t ready yet. You can either wait a bit for
: QtP (like us) or I heard ALSA supports linux very well.
:>
:> In comp.os.qnx Mark Johnson <nooz@my-deja.com> wrote:
:> > Does anyone know if a port of the ALSA 0.5.x drivers to QNX4 is being
:> > attempted?
:>
:> > TIA,
:> > MJ
:>
:>
:>
:>
\
Donald Lalonde
OEM Support Specialist
QNX Software Systems Ltd.
mailto: donaldl@qnx.com http://qdn.qnx.com
Build a more reliable world
The QNX Real Time Platform is now available
Get it a http://get.qnx.com
In article <Pine.LNX.4.21.0010311759390.26105-100000@mama.indstate.edu>,
liug@mama.indstate.edu says…
QNX4 is dead, QtP isn’t ready yet. You can either wait a bit for
QtP (like us) or I heard ALSA supports linux very well.
There is a growing gap developing and some of us are about to fall in it. QNX4
is not keeping pace yet RTP/NTO is not ready for prime time in our applications
which require fuller network support than is available now on RTP.
In comp.os.qnx Mark Johnson <> nooz@my-deja.com> > wrote:
Does anyone know if a port of the ALSA 0.5.x drivers to QNX4 is being
attempted?TIA,
MJ
\
In comp.os.qnx Dean Douthat <ddouthat@faac.com> wrote:
: In article <Pine.LNX.4.21.0010311759390.26105-100000@mama.indstate.edu>,
: liug@mama.indstate.edu says…
:>
:>QNX4 is dead, QtP isn’t ready yet. You can either wait a bit for
:>QtP (like us) or I heard ALSA supports linux very well.
: There is a growing gap developing and some of us are about to fall in it. QNX4
: is not keeping pace yet RTP/NTO is not ready for prime time in our applications
: which require fuller network support than is available now on RTP.
Out of curiosity. What type of network support are you looking for under RTP?
-seanb
On 2 Nov 2000, Sean Boudreau wrote:
In comp.os.qnx Dean Douthat <> ddouthat@faac.com> > wrote:
: In article <> Pine.LNX.4.21.0010311759390.26105-100000@mama.indstate.edu> >,
: > liug@mama.indstate.edu > says…
:
:>QNX4 is dead, QtP isn’t ready yet. You can either wait a bit for
:>QtP (like us) or I heard ALSA supports linux very well.: There is a growing gap developing and some of us are about to fall in it. QNX4
: is not keeping pace yet RTP/NTO is not ready for prime time in our applications
: which require fuller network support than is available now on RTP.Out of curiosity. What type of network support are you looking for under RTP?
I am waiting for UDS.
-seanb
In article <8ts191$kgr$1@nntp.qnx.com>, seanb@qnx.com says…
In comp.os.qnx Dean Douthat <> ddouthat@faac.com> > wrote:
: In article <> Pine.LNX.4.21.0010311759390.26105-100000@mama.indstate.edu> >,
: > liug@mama.indstate.edu > says…
:
:>QNX4 is dead, QtP isn’t ready yet. You can either wait a bit for
:>QtP (like us) or I heard ALSA supports linux very well.: There is a growing gap developing and some of us are about to fall in it.
QNX4
: is not keeping pace yet RTP/NTO is not ready for prime time in our
applications
: which require fuller network support than is available now on RTP.Out of curiosity. What type of network support are you looking for under RTP?
We are using multi-casting with the tcpip 5 in our production prototypes.
Production deliveries will begin early next summer. Also, we need proxies
delivered over qnet; I understood these are not yet available on RTP.
-seanb
In comp.os.qnx Dean Douthat <ddouthat@faac.com> wrote:
: In article <8ts191$kgr$1@nntp.qnx.com>, seanb@qnx.com says…
:>
:>In comp.os.qnx Dean Douthat <ddouthat@faac.com> wrote:
:>: In article <Pine.LNX.4.21.0010311759390.26105-100000@mama.indstate.edu>,
:>: liug@mama.indstate.edu says…
:>:>
:>:>QNX4 is dead, QtP isn’t ready yet. You can either wait a bit for
:>:>QtP (like us) or I heard ALSA supports linux very well.
:>
:>: There is a growing gap developing and some of us are about to fall in it.
: QNX4
:>: is not keeping pace yet RTP/NTO is not ready for prime time in our
: applications
:>: which require fuller network support than is available now on RTP.
:>
:>Out of curiosity. What type of network support are you looking for under RTP?
: We are using multi-casting with the tcpip 5 in our production prototypes.
: Production deliveries will begin early next summer. Also, we need proxies
: delivered over qnet; I understood these are not yet available on RTP.
Multicast support is in now. You need to:
- Run the large stack.
- Start your driver with the multicast=1 option.
eg:
slay io-net
io-net -d multicast=1 -ptcpip
ifconfig en0 x.x.x.x
route add default y.y.y.y
It seems that not a lot of people are using it yet but I haven’t heard of
any problems…
You can currently have a “server” raise a pulse on a “client” via
MsgDeliverEvent() over the network. This is not as flexible as
QNX4 where anyone could trigger() but may suit your purposes…
-seanb
In article <8tsi7p$b4$1@nntp.qnx.com>, seanb@qnx.com says…
Multicast support is in now. You need to:
- Run the large stack.
- Start your driver with the multicast=1 option.
eg:
slay io-net
io-net -d multicast=1 -ptcpip
ifconfig en0 x.x.x.x
route add default y.y.y.y
It seems that not a lot of people are using it yet but I haven’t heard of
any problems…You can currently have a “server” raise a pulse on a “client” via
MsgDeliverEvent() over the network. This is not as flexible as
QNX4 where anyone could trigger() but may suit your purposes…
Hmm. Sounds like things have progressed further than I thought. Maybe it’s time
to get serious about moving to RTP. Thanks Sean.
-seanb