The oggplay relies on fork() (superficially if you ask me) and does not
display anything when fork() fails (like no-mmu). So if it fails due to
ENOSYS, play the file ourselves, otherwise dump a proper error message.
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
user/oggplay/oggplay.c |
Mike wrote:
The oggplay relies on fork() (superficially if you ask me) and does not
It isn't quite so superficial. The fork is there so that when playing multiple
tracks things don't get clagged up. Was easier doing this than tracking down
all the state destruction and rectifying it. If
On Tuesday 17 March 2009 18:38:49 Mike Frysinger wrote:
On Tuesday 17 March 2009 18:36:46 paul_d...@au.securecomputing.com wrote:
Mike wrote:
The oggplay relies on fork() (superficially if you ask me) and does not
It isn't quite so superficial. The fork is there so that when playing
Mike wrote:
btw, please dont take this the wrong way. i imagine oggplay does all the
crazy things you say it does, but we just wanted to validate that the tremor
decoding library worked (download an ogg and listen to it on the board). so
everything beyond that is cheese to us ;).
I
Hi Mike,
Mike Frysinger wrote:
The oggplay relies on fork() (superficially if you ask me) and does not
display anything when fork() fails (like no-mmu). So if it fails due to
ENOSYS, play the file ourselves, otherwise dump a proper error message.
Signed-off-by: Mike Frysinger
