On Monday 04 April 2005 9:40 am, Jeremy Huddleston wrote:
> On Sat, 2005-04-02 at 16:29 -0900, John Andersen wrote:
> > On Saturday 02 April 2005 1:48 pm, David George wrote:
> > > Just a heads up. saa7115.c doesn't compile in 2.6.12-rc1-bk5. The
> > > (hand typed) error is:
> > >
> >
> > Hell
Chris,
Not sure if this helps or not, but here is what I have:
PVR-500 MCE
EPoX-8k3aplus M/B (VIA KT333)
Athlon XP 1800+ (Palomino)
NVidia 440MX (VGA Out not composite, using v7167 drivers)
Gentoo 2004.0
Kernel 2.6.11 (gentoo-sources-2.6.11-r4)
CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CXXFLAGS="${CFLAG
Hi,
I was wondering if you could help me. I don't think I installed
the IVTV driver correctly for this. Can someone please help me out by
posting a simple step by step guide on how I should accomplish this?
I'm not sure how to handle the firmware.
Thanks!
Matt
Odd, it actually doesn't really touch pvr500 functionality at all, just
adds those ioctls. Now the tuner tveeprom patch and 2.4/2.6 compat fixes
are the only suspect, but seems to work here still, on NTSC pvr500 mce cards.
Have to see if anyone else sees anything or maybe a cold boot, also the
ou
Chris Kennedy <[EMAIL PROTECTED]> wrote:
> That would be great, it's odd, I don't see where it overwrites everything,
> teh more I explore the more confusing it seems. I just can't believe I
> write any register, and after a device access it's reset, even ones supposidly
> untouched anywhere in th
> Here's what I have, I did some rearranging of the code while I was at it.
> I may have broken S-Video output since I was working out which
> settings weren't needed and haven't fully tested that, but plugging
> the old settings back into the segment would be easy enough.
>
> This definitely brea
Now that I have the TV part of this card running nicely I would like to
see if FM will work. I've tried using the radio util but nothing seems
to come through on any of the stations. I have my cable coax into both
inputs and on my WinFast xp2000 the fm works great (its in my other
linuxx box
On Apr 4, 2005 8:41 AM, Paul K <[EMAIL PROTECTED]> wrote:
> OK... Now it compiles just fine! Thanks Brad. I'll have to finish it
> later, but it's looking a lot better.
>
> Thank again
>
> Paul
Great, glad I could help. Unfortunately, I'm still waiting for my
pvr-500 to arrive so I haven't yet
On Apr 4, 2005 12:25 PM, Chris Kennedy <[EMAIL PROTECTED]> wrote:
>
> This includes all the recent patches and also allows the ivtvctl -G/-g
> register access to the cx25840 once again like in my original version,
> which should let us change things without going through the interface,
> and view
Didn't mean it personally, it's just hard to develop with it because it
won't let me set any registers, just frustration from trying to get something
done and feel like I'm not moving anywhere. Just wanted some more info too,
felt like this was not very open code to the rest of us hacking at it wi
I tried out ivtv-0.3.2p and it's locked a couple of times
during a commercial skip. My computer isn't locked, just the
TV output.
No error messages in the logs.
I have a PVR 350 and I'm running the 2.6.8.1 Ruby kernel.
This kernel is patched to allow multiple consoles - this
allows me to use Myth o
Ulf <[EMAIL PROTECTED]> wrote:
> Yes you could go for an all anonymous "set address to byte" based driver,
> but I don't think that is a good idea if you want maintainability. Then
> again I don't claim that my code is ready or even maintainable.
I agree, but I think that once all the setting cha
Hey, don't pick on me.
The cx25840-registers stuff was written to support my I2C parser, I then
used it as a fast way of converting the captures into working code. My code
has never been presented as production worthy. It did however work better
then one the original.
Yes the register file is aut
Chris Kennedy wrote:
It also resets all the registers upon any device access, I just realized
this, I set something, then it gets unset, and not a setting normally
set for the driver, so it's going through and resetting all registers
for everything, very horrible.
Is this including the "autoconf
That would be great, it's odd, I don't see where it overwrites everything,
teh more I explore the more confusing it seems. I just can't believe I
write any register, and after a device access it's reset, even ones supposidly
untouched anywhere in the driver. Seems like the cache and dirty bits st
Chris Kennedy <[EMAIL PROTECTED]> wrote:
> It also resets all the registers upon any device access, I just realized
> this, I set something, then it gets unset, and not a setting normally
> set for the driver, so it's going through and resetting all registers
> for everything, very horrible.
Anyth
It also resets all the registers upon any device access, I just realized
this, I set something, then it gets unset, and not a setting normally
set for the driver, so it's going through and resetting all registers
for everything, very horrible.
Thanks,
Chris
On Mon, Apr 04, 2005 at 03:45:33PM -04
Chris Kennedy <[EMAIL PROTECTED]> wrote:
> seems some things aren't set and report back different
> than thought.
The driver currently keeps a map of the registers and updates only the
modified bytes when calling 'execute_settings'. I think there may be
some weird things happening due to some re
Christian Borchmann <[EMAIL PROTECTED]> writes:
> with
>
> ivtvctl -d /dev/video0 -p 0
>
> i got my video input to work and i watch a captured picture from my sony
> digital camera conented to the pvr-350...
>
> when switching to ivtvctl -d /dev/video0 -p 4
Right, input 4 should give you tv. Wh
Chris Kennedy <[EMAIL PROTECTED]> wrote:
> I am
> not happy with the way the driver is programmed being very ambiguous and
> not open to us developing on top of this code easily, little help has been
> given, it looks like an actually great interface and rather advanced, if it
> is solid, else we n
This includes all the recent patches and also allows the ivtvctl -G/-g
register access to the cx25840 once again like in my original version,
which should let us change things without going through the interface,
and view things, seems some things aren't set and report back different
than thought.
Try version 0.3.2r so you can actually access the cx25840 registers now
(surprisingly some not set or different than claimed), in a raw mode,
just like the sa7115 interface (in fact just treat like a sa7115 in the
ivtvctl program). You basically assume your in the 0x4XX register range,
so that's w
with
ivtvctl -d /dev/video0 -p 0
i got my video input to work and i watch a captured picture from my sony
digital camera conented to the pvr-350...
when switching to ivtvctl -d /dev/video0 -p 4
Christian "SPITFIRE" Borchmann
http://www.borchi.de
ICQ #30405670
MSM [EMAIL PROTECTED]
AIM wws
Great...
now i have some kind of dark-grey and withe snow on black backround
Christian "SPITFIRE" Borchmann
http://www.borchi.de
ICQ #30405670
MSM [EMAIL PROTECTED]
AIM wwspitfire
PGP-Key-ID: 0x1475C0980E0B5B40
PGP-Key-File: http://www.borchi.de/pgp/christian_borchmann.asc
PGP-Fingerprint
Chris Kennedy wrote:
...
So what is the
deal here, I also notice for other registers the value listings seem wrong,
like the VBI_MD_LINE1_value_map at line 2326 of the same file, says CC is
{0x0048, "CC525"},, when according to the datasheet it is actually 0x66 to
...
Thanks,
Chris
I get the fe
Christian Borchmann <[EMAIL PROTECTED]> writes:
> Am Montag, 4. April 2005 19:52 schrieb Bruno Hertz:
>
> One thing:
>
> Can u post your settings in the /etc/modutils/ivtv and
> on /etc/modpprobe.d/ivtv ???
I have neither. All I have is an 'ivtv' line in /etc/modules to have the
driver automatic
Quoting Robert Kulagowski <[EMAIL PROTECTED]>:
> Chris Kennedy wrote:
> > Just got word that the place I keep the patches will disappear by
> > April 17th, please thank James Satterfield for have hosted them for
> > so long. So the people with webspace offering before, or anyone with
> > a good pl
Am Montag, 4. April 2005 19:52 schrieb Bruno Hertz:
One thing:
Can u post your settings in the /etc/modutils/ivtv and
on /etc/modpprobe.d/ivtv ???
thanks
Christian "SPITFIRE" Borchmann
http://www.borchi.de
ICQ #30405670
MSM [EMAIL PROTECTED]
AIM wwspitfire
PGP-Key-ID: 0x1475C0980E0B5B40
P
Christian Borchmann <[EMAIL PROTECTED]> writes:
> Am Montag, 4. April 2005 19:26 schrieb Bruno Hertz:
>
>> (1) tvtime probably isn't the application to use because the pvr350
>> stream is mpeg encoded
>
> what application sould i use?
>
>> (2) just because tvtime says /dev/video0 isn't there d
Am Montag, 4. April 2005 19:26 schrieb Bruno Hertz:
> (1) tvtime probably isn't the application to use because the pvr350
> stream is mpeg encoded
what application sould i use?
> (2) just because tvtime says /dev/video0 isn't there doesn't mean it
> reall isn't; please post the output of
Is this a bug, I find some registers setup (which seems static so we
can't freely work with the registers, all predefined for us), are off
in the values allowed. For example the "VBI1_FIFO_MODE" register, or
bits of register 0x457, specifically bits 4-6 on page 217 of the cx25840
datasheet. This
"Bruno Hertz" <[EMAIL PROTECTED]> writes:
> Christian Borchmann <[EMAIL PROTECTED]> writes:
>
>> Hallo,
>>
>> i have problems getting my PVR-350 to work just for watching TV before
>> i start experiments to record videos :o)
>>
>> I installed ivtv drivers after some howto and i see no problems whi
On Sat, 2005-04-02 at 16:29 -0900, John Andersen wrote:
> On Saturday 02 April 2005 1:48 pm, David George wrote:
> > Just a heads up. saa7115.c doesn't compile in 2.6.12-rc1-bk5. The
> > (hand typed) error is:
> >
>
> Hell it doesn't even compile in 2.6.5 why should it .12?
The attached patch
Christian Borchmann <[EMAIL PROTECTED]> writes:
> Hallo,
>
> i have problems getting my PVR-350 to work just for watching TV before
> i start experiments to record videos :o)
>
> I installed ivtv drivers after some howto and i see no problems while
> loading the drivers.
>
> When i try to capture
Hallo,
i have problems getting my PVR-350 to work just for watching TV before i start
experiments to record videos :o)
I installed ivtv drivers after some howto and i see no problems while loading
the drivers.
When i try to capture i get an black .mpg file and tvtime says /dev/video0 not
found
100%. Is it time to relabel 0.2.0rcX to 0.2.0? Since even Amity2 bits
started moving from 0.3.x to 0.2.0 it looks like the older bits have
matured enough, or not?
Well, I'm using version 0.2.0rc3g and it's reasonably stable for capture.
I don't use the output features much anymore - I tend to u
On Mon, Apr 04, 2005 at 08:35:55AM -0500, Robert Kulagowski wrote:
> Chris Kennedy wrote:
> >Just got word that the place I keep the patches will disappear by
> >April 17th, please thank James Satterfield for have hosted them for
> >so long. So the people with webspace offering before, or anyone w
Pardon if I'm way out of date on this. Nothing came up on a web search.
I've been using 0.2.0-rc3d successfully for many months, modulo the
occasional wedging (maybe once a month?) that requires me to reboot my
mythbackend.
Well, this weekend I tried installing 0.2.0-rc3i and, lo and behold, it
Chris Kennedy wrote:
Just got word that the place I keep the patches will disappear by
April 17th, please thank James Satterfield for have hosted them for
so long. So the people with webspace offering before, or anyone with
a good place to keep these, please let me know. Would need ftp access
or
Rudi,
As a quick and dirty work around I have to manually initialize the card with:
# /usr/lib/ivtv/ptune-ui.pl &
# mplayer -vo xv /dev/video0
After that I can record and watch live tv. I have to do this every time I
reboot. This is a fairly new problem since I upgraded the kernel to
2.6.10-1.770
OK... Now it compiles just fine! Thanks Brad. I'll have to finish it
later, but it's looking a lot better.
Thank again
Paul
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real u
Thanks Stephen...
I was going to try that, too. But this weekend didn't turn out like
I had invisioned :p
Now with Brad's new patch it all compiles just fine.
PK
> I'm also using this patch with my pvr-150mce and a 2.4.25 kernel. The
> only thing I had to do was get rid of the msp3400 part
On Mon, 2005-04-04 at 12:29 +0200, Axel Thimm wrote:
> On Sun, Apr 03, 2005 at 04:56:56PM -0800, Jarod Wilson wrote:
> > On Sunday 03 April 2005 17:37, Chris Kennedy wrote:
> > > Just got word that the place I keep the patches will disappear by
> > > April 17th, please thank James Satterfield for h
FWIW: I have been running ivtv-0.2.0-rc3f on a 2.4.29 kernel with no
problems using a PVR-350. I think it's stability is better than the
0.1x I was running before. I haven't ran it very long though as I need
to get into the 0.3.x for pvr500 support.
HTH
Paul
On Sun, Apr 03, 2005 at 04:56:56PM -0800, Jarod Wilson wrote:
> On Sunday 03 April 2005 17:37, Chris Kennedy wrote:
> > Just got word that the place I keep the patches will disappear by
> > April 17th, please thank James Satterfield for have hosted them for
> > so long. So the people with webspace
(Posted this to the sourceforge forum, but that doesn't seem to get
much traffic. So, sorry for this cross posting!)
I'm using the atrpms.net packages of ivtv. After getting a new version
of ivtv my PVR-250 (which has worked like a charm for more than a
year) won't initialize properly. For some re
Hey there,
Well this weekend I succeeded in getting a PAL PVR 500 going complete with
sound (yet to confirm NICAM) with a good picture, changing channels,
recording 2 channels or watching one and recording the other etc etc..
I am using KnoppMyth R5A12 and ivtv-0.3.2q. It took a total of about 30
47 matches
Mail list logo
