Ben Davis wrote:
> For some reason I'm able to use xawtv just fine, and it's not using any
> video devices in /dev.. (lsof | grep xawtv)..
Because the GATOS team moved all hardware dependent code to X.
All the stuff is now compiled as X modules and if properly
"configured"
it will be loaded along with your X server(s).
A side effect is that ALL user apps now have direct access to the
detected
hardware WITHOUT ANY NEED of V4L - they are compl. separated.
Log the x server loading and you will see the hardware being detected
(or
not).
The idea of creating a video device capable of merging the APIs
already
crossed
my mind - but it is still there.... ;-)
I have tons of GATOS code (since early drafts) and so far I can run
AIW
w/GATOS
as well as with the new X modules using X 4.x.x, with some few hacks.
So far so good, each one is presenting a different set of problems.
The old code base the video overlay into some chunks of pre reserved X
memory.
It was fine until 4.x.x releases. With 4.x.x some mem corruption will
be
noticed.
The modules seems not "fully" implemented yet.
I did not look the whole new code as I would like (no time)- but I do
can
run it
with just some few problems regarding proper PAL- detection. ('M' is
wrong
and not being properly activated [read: correct chip init]).
ASAP i will try to figure out why the new modules are failing to
correctly
initialize the BT chipset while the old ones are not (w/M stand.).
As the olds use a static "config" file you can force and test a bit
more,
besides as it is implemented as library+app you have the benefit of
terminal
logging capabilities... very helpful
Don't know yet if the new modules still read the old configs... (back
compat.)
will take another look ....
Time, time, time.... huh... must run!
The Simpsons are saying that there are monkeys and snakes after me!
Blame it on Lisa!
Abracos
PCastro
--
HOM: http://www.momentus.com.br/users/hook/
GPG: http://www.momentus.com.br/users/hook/GPG-PauloCastro.asc
