From: Stefan Berndtsson <stefan@nocrew.org>
To: Henry Worth <haworth@ncal.verio.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: xine, ppc and illegal instructions
Date: 24 Mar 2001 11:57:35 +0100 [thread overview]
Message-ID: <874rwj5t9c.fsf@hades.nocrew.org> (raw)
In-Reply-To: <3ABC295A.DBBF800@ncal.verio.com>
Henry Worth <haworth@ncal.verio.com> writes:
> Shutdown esd (best) or use the -A esd option.
I'm afraid that doesn't help at all. It still produces the illegal instruction.
Hmm.. running it using strace, I can sometimes make it get past the plugin-
check and show the box. This nearly never happens with all the plugins
available, but gets easier if I remove some of them.
I'll wait for the new patches and see if that changes anything though.
/Stefan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-24 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-24 4:58 xine, ppc and illegal instructions Henry Worth
2001-03-24 10:57 ` Stefan Berndtsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-30 5:26 Henry Worth
2001-03-31 20:16 ` Bill Fink
2001-03-30 5:20 Henry Worth
2001-03-30 5:29 ` David Edelsohn
2001-03-30 14:59 ` Henry Worth
[not found] <Pine.LNX.4.21.0103262330001.19578-100000@gwiz.nasa.atd.net >
2001-03-27 13:41 ` Franz Sirl
2001-04-01 17:51 ` Bill Fink
2001-04-01 19:39 ` Michel Dänzer
2001-04-01 21:08 ` Bill Fink
2001-04-01 20:02 ` Kevin B. Hendricks
2001-04-01 20:12 ` Benjamin Herrenschmidt
2001-04-01 21:24 ` Bill Fink
2001-04-02 11:50 ` Kevin B. Hendricks
2001-03-27 5:30 Bill Fink
2001-03-24 19:17 Henry Worth
2001-03-24 6:13 Henry Worth
2001-03-23 23:53 Stefan Berndtsson
2001-03-24 0:09 ` Gregorio Gervasio Jr.
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=874rwj5t9c.fsf@hades.nocrew.org \
--to=stefan@nocrew.org \
--cc=haworth@ncal.verio.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).