9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Ideas???
Date: Mon, 18 Sep 2006 12:54:25 +0200	[thread overview]
Message-ID: <9f3897940609180354n453f94dfq586ac7294cdd523d@mail.gmail.com> (raw)
In-Reply-To: <20060918093221.GV4849@XTL.antioffline.net>

On 9/18/06, Harri Haataja <harriha@mail.student.oulu.fi> wrote:
> On Sun, Sep 17, 2006 at 04:10:58PM -0400, John Floren wrote:
> > On 9/17/06, Pawe? Lasek <pawel.lasek@gmail.com> wrote:
> > >On 9/17/06, tushar mahule <tusharmahule@yahoo.com> wrote:
>
> > >* port mplayer?? It's ugly code, but it works, and it works pretty
> > >fast ;-D
>
> > I second the mplayer vote, because it's possibly the best (from a
> > user's perspective, I don't know what the code is like) media player
> > I've ever used. However, before mplayer is useful, I think we kinda
> > need some more sound drivers.
>
> Also, is there hardware accelerated video (scaling!) and fullscreen
> switching?

Theoretically it should be possible to port mplayer's vidix using
access to graphics card memory with device files (I don't remember
exact files, but there was at least one which allowed to even write
pci drivers as filesystems if one wanted to...)

Integrating it with rio would be much tougher, but I think that at
least vesa driver should be pretty easy to port, considering one finds
a suitable way to return control to rio (like the need for "reset" on
linux vt after using mplayer's -vo vesa).

> --
> Conquering the galaxy is what bacteria with spaceships would do --
> knowing no better, having no choice.
>         -- Greg Egan, "Diaspora" (about alien invasion stories)
>

-- 
Paul Lasek


  reply	other threads:[~2006-09-18 10:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17 12:21 tushar mahule
2006-09-17 12:24 ` Sascha Retzki
2006-09-17 12:28   ` tushar mahule
2006-09-17 12:34     ` Sascha Retzki
2006-09-17 12:41       ` tushar mahule
2006-09-17 13:03         ` Sascha Retzki
2006-09-17 15:31           ` Russ Cox
2006-09-17 20:49             ` geoff
2006-09-17 20:05         ` Paweł Lasek
2006-09-17 20:10           ` John Floren
2006-09-18  9:32             ` Harri Haataja
2006-09-18 10:54               ` Paweł Lasek [this message]
2006-09-18 13:15             ` Sascha Retzki
2006-09-18 14:32               ` Axel Belinfante
2006-09-18 14:53                 ` Sascha Retzki
2006-09-18 17:48                   ` Axel Belinfante
2006-09-18 19:30                   ` Axel Belinfante
2006-09-19 13:43                     ` juke - does it need some love? (was: Re: [9fans] Ideas???) Sascha Retzki
2006-09-20  1:12                       ` Charles Forsyth
2006-09-17 20:34           ` [9fans] Ideas??? erik quanstrom
2006-09-17 12:44       ` tushar mahule
2006-09-17 12:54         ` Benn Newman
2006-09-17 13:02         ` Sascha Retzki
2006-09-17 18:26         ` erik quanstrom
2006-09-18 16:13     ` Ronald G Minnich
2006-09-18 16:49       ` jmk

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=9f3897940609180354n453f94dfq586ac7294cdd523d@mail.gmail.com \
    --to=pawel.lasek@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).