Tech Insider					     Technology and Trends


	      Linux Video & DVD Project Mailing List Archives

From mpav@purdue.edu Fri, 3 Dec 1999 14:29:54 -0500 (EST)
Date: Fri, 3 Dec 1999 14:29:54 -0500 (EST)
From: Matthew R. Pavlovich mpav@purdue.edu
Subject: [Livid-dev] Quickies..

*Last week I was out of town, and I am still catching up on e-mails.  I
know there are a lot of things along the lines of CVS access, and CVS
modules.. I will send replies to all those by Sunday.

*I'd like to welcome Stea Greene from the GATOS project.  (ATI TV and
video overlay).  He is gonna (hopefully soon) be working on the backend
scalar driver for ATI Rage Pro chips.

http://www.core.binghamton.edu/~insomnia/gatos/

Stea- check out the mga_vid module..  That is the one for Matrox Gx00's.

*I am having issues trying to get the necassary tools on the web server
for the new site.  I hope to get things square by this weekend.

*Matrox notes: I have not recieved any replies from Matrox regarding
documentions for TV Out and more extensive information on the Media Bus.
I hope to have news soon regarding whether or not they use WARP for MPEG2
decoding.  If they do, then hopefully we can get the microcode, in
a similar manner as the GLX project.

*Plans.  Once the new site is up, hopefully I can attract other projects
to join and we can have a more centralized resource for the video
projects.  I would like to start a list of DVD drives that we know work,
as well as titles that have been tested.  It's a little premature for
attracting users, but due to the popularity of the project I hope it will
help alleviate the load on my e-mail box.  A livid-users list may be in
order, but a similar list is not very trafficed w/ the GLX project..
we'll see.

*CVS Access.  I would like to propose just a quick policy on CVS access,
(request for comment, of course), I like the idea of the authors
maintaining control of their code and having a say as to what patches get
applied.  Instead of having to deal with backing out changes, I am asking
that anyone wanting to have CVS write access to send your patches to the
list, contact the author and have them give me the 'ok' to allow new
accounts.  Thoughts?


 Matthew R. Pavlovich

From giles@raj.phys.sfu.ca Fri, 3 Dec 1999 11:55:34 -0800 (PST)
Date: Fri, 3 Dec 1999 11:55:34 -0800 (PST)
From: Ralph Giles giles@raj.phys.sfu.ca
Subject: [Livid-dev] Quickies..

On Fri, 3 Dec 1999, Matthew R. Pavlovich wrote:

> *Last week I was out of town, and I am still catching up on e-mails.  I
> know there are a lot of things along the lines of CVS access, and CVS
> modules.. I will send replies to all those by Sunday.

Welcome back! :)

> *Plans.  Once the new site is up, hopefully I can attract other projects
> to join and we can have a more centralized resource for the video
> projects.  I would like to start a list of DVD drives that we know work,
> as well as titles that have been tested.  It's a little premature for
> attracting users, but due to the popularity of the project I hope it will
> help alleviate the load on my e-mail box.  A livid-users list may be in
> order, but a similar list is not very trafficed w/ the GLX project..
> we'll see.

Hmm, it's true that there's no as much traffic on glx-users, but I've
really liked having it. It's removed all the "It's impossible to compile
this" messages from the devel list, improving the signal-to-noise
in glx-dev. I think it will only be more helpful in the future as the glx
module gets more popular to have a separate forum to support users at
that level of experience. Eliminating support email for those who don't
want it is a good thing. :)

> *CVS Access.  I would like to propose just a quick policy on CVS access,
> (request for comment, of course), I like the idea of the authors
> maintaining control of their code and having a say as to what patches get
> applied.  Instead of having to deal with backing out changes, I am asking
> that anyone wanting to have CVS write access to send your patches to the
> list, contact the author and have them give me the 'ok' to allow new
> accounts.  Thoughts?

I guess we're already doing this with ac3dec. I'm of course happy to
respect any such policy, but imho our problem is not enough commits, not
too many. :)

I'm concerned that unless the maintaining author is doing active
development with the livid archives as their primary repository, this is
just going to slow down commits even more. The great thing about cvs is
that everybody can easily keep in sync without having to apply interesting
patches by hand.

Just my thoughts,
 -ralph

From aholtzma@ess4.engr.UVic.CA Fri, 3 Dec 1999 12:15:13 -0800
Date: Fri, 3 Dec 1999 12:15:13 -0800
From: Aaron Holtzman aholtzma@ess4.engr.UVic.CA
Subject: [Livid-dev] Quickies..

It would seem that Matthew R. Pavlovich (mpav@purdue.edu) said:
> *I'd like to welcome Stea Greene from the GATOS project.  (ATI TV and
> video overlay).  He is gonna (hopefully soon) be working on the backend
> scalar driver for ATI Rage Pro chips.

We should maybe discuss a common api for talking to the BES on
different cards. 
 
> *CVS Access.  I would like to propose just a quick policy on CVS access,
> (request for comment, of course), I like the idea of the authors
> maintaining control of their code and having a say as to what patches get
> applied. 

Amen. This is exactly how I would like to run things.

On a completely unrelated note, I will release a snapshot of my
work-in-progress MPEG-2 video backend on saturday. It probably
won't do much more than parse the stream and display green
blobish I-frames, but I believe the time has come for other
peoples input and hacks. Bone up on your ISO 13818-2 people,
we need more brains that understand what frame_pred_frame_dct 
means :)

cheers,
aaron

From aholtzma@ess4.engr.UVic.CA Fri, 3 Dec 1999 12:32:50 -0800
Date: Fri, 3 Dec 1999 12:32:50 -0800
From: Aaron Holtzman aholtzma@ess4.engr.UVic.CA
Subject: [Livid-dev] Quickies..

It would seem that Ralph Giles (giles@raj.phys.sfu.ca) said:
> I guess we're already doing this with ac3dec. I'm of course happy to
> respect any such policy, but imho our problem is not enough commits, not
> too many. :)
> 
The ac3dec module in cvs right now is completely pointless. I
could probably be talked into moving my own cvs tree onto a server
somewhere that had ssh access. 

I've been looking at www.sourceforge.org, and it looks like these
guys have their act together. What do people think about moving
new cvs stuff over there? 

cheers,
aaron

From andreas@andreas.org 06 Dec 1999 21:15:28 -0500
Date: 06 Dec 1999 21:15:28 -0500
From: Andreas Bogk andreas@andreas.org
Subject: [Livid-dev] Quickies..

Aaron Holtzman < aholtzma@ess4.engr.UVic.CA> writes:

> The ac3dec module in cvs right now is completely pointless. I
> could probably be talked into moving my own cvs tree onto a server
> somewhere that had ssh access. 

If there's interest, we could offer CVS plus ssh accounts on
linuxtv.org. We do backups, have a dedicated machine for the purpose,
and are conveniently (from a Digital Millenium Copyright Act point of
view) located in Germany.

Andreas

-- 
"We should be willing to look at the source code we produce not as the
end product of a more interesting process, but as an artifact in its
own right. It should look good stuck up on the wall."
 -- http://www.ftech.net/~honeyg/progstone/progstone.html

From axboe@image.dk Tue, 7 Dec 1999 17:52:57 +0000
Date: Tue, 7 Dec 1999 17:52:57 +0000
From: Jens Axboe axboe@image.dk
Subject: [Livid-dev] Quickies..

On Fri, Dec 03 1999, Matthew R. Pavlovich wrote:
> projects.  I would like to start a list of DVD drives that we know work,

Please don't, all drives *should* work.

-- 
*  Jens Axboe < axboe@image.dk>
*  Linux CD-ROM Maintainer
*  http://www.kernel.dk

			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO vs IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or
research.

Electronic mail:			       WorldWideWeb:
   tech-insider@outlook.com			  http://tech-insider.org/