Bryan Mayland wrote:
> Tyler Trafford wrote:
>
>> Is this on a 2.4 kernel? I apparently broke the cx25840 firmware load
>> for the 2.4 kernel. Patch forthcoming later today.
>
> ha ha! Finally, someone else screwed up. I was getting tired of
> being the only person submitting patches of du
David wrote:
Chris wrote:
Hi Chris,
Should that be newest firmware for all cards or just the 150/500's?
Someone asked the question before but I didn't see an answer, so should I
update the firmware for a pvr-350?
It seems it varys per system, I am seeing the newest firmware work grea
Yeah, the decoder issues could use some attention from me - there are
some log messages that I should collect to track down the troubles I
have been having.
I was just confused about the encoder vs. decoder firmware - I see now
that the decoder firmware hasn't changed in quite a while.
On 6/7/05,
Tyler Trafford wrote:
Is this on a 2.4 kernel? I apparently broke the cx25840 firmware load
for the 2.4 kernel. Patch forthcoming later today.
ha ha! Finally, someone else screwed up. I was getting tired of
being the only person submitting patches of dubious compatibility. :)
Keats wrote:
> Keats wrote:
>
> > bahamut modules # strings ivtv-fw-dec.bin | grep Version
> > Version 2.02.023
> > => no sound with pvr 150 modele 1052 ...
>
> it's not due to the firmware...
> i ve back to the initial one and still have the same problem : no sound...
> maybe it's due to an upda
HcwFalcn.rom is just a replacement for the ivtv-fw-enc.bin, as far as I
know. Can't comment on the poor decoder performance, for I know nothing
about that.
Mike Shields wrote:
Just a general question about upgrading the firmware - I have a PVR-350.
Do I copy HcwFalcn.rom to /lib/modules/ivt
Just a general question about upgrading the firmware - I have a PVR-350.
Do I copy HcwFalcn.rom to /lib/modules/ivtv-fw-enc.bin,
/lib/modules/ivtv-fw-dec.bin, or both?
I only -enc yesterday but was getting poor decoder performance - it
would work fine once, then I'd pretty much have to reboot bef
On Tue, 7 Jun 2005 18:31:48 +0200
Keats <[EMAIL PROTECTED]> wrote:
> done
> bahamut modules # strings ivtv-fw-dec.bin | grep Version
> Version 2.02.023
> => no sound with pvr 150 modele 1052 ...
it's not due to the firmware...
i ve back to the initial one and still have the same problem : no sou
On Sun, 05 Jun 2005 21:36:29 -0500
ckennedy <[EMAIL PROTECTED]> wrote:
> Harry Orenstein wrote:
>
> >How new? Could you post MD5 sums or some other indication of the versions
> >you
> >want people to try? Probably would be best to compare apples to apples.
> >
> >
>
> It's version 2.05.32
Chris wrote:
> I have been experimenting and have found that the newest firmware is
> working ok during my tests now, it seems we have possibly gotten the
> driver to the point of working with the old firmware and newer
> firmware. The newer firmware seems good at framebased DMA, doesn't do
> bl
Brian Litzinger wrote:
On Sun, Jun 05, 2005 at 09:36:29PM -0500, ckennedy wrote:
Harry Orenstein wrote:
How new? Could you post MD5 sums or some other indication of the versions
you want people to try? Probably would be best to compare apples to
apples.
It's version 2.05.
I always use hexedit and view it that way, it's right at the top
of the firmware files, so quick way to tell for sure what exact
version, have now idea why some of the newer ones have all the extra
crap at the end (which is unused and nothing except that, crap, and
throws off our md5 checksumming o
On Sun, 2005-06-05 at 21:28 -0500, William Powers wrote:
> This may be useful:
>
> http://ivtv.writeme.ch/tiki-index.php?page=FirmwareVersions
I've noticed that
strings ivtv-fw-dec.bin | grep Version
shows a version string embedded in each binary file, at least in all the
files I've got.
ckennedy wrote:
ivtv: Encoder revision: 0x02050032
In addition to the pvr_2.0.24.23035.zip version, this is also
available from:
http://hauppauge.lightpath.net/software/pvr150/pvr150_inf.zip
Although they are of different sizes (and subsequently have different
md5sums), the first 256k a
Brian Litzinger wrote:
On Sun, Jun 05, 2005 at 09:36:29PM -0500, ckennedy wrote:
Harry Orenstein wrote:
How new? Could you post MD5 sums or some other indication of the versions
you want people to try? Probably would be best to compare apples to
apples.
It's version 2.05.
ckennedy <[EMAIL PROTECTED]> writes:
> It's version 2.05.32 or greater, I think that's the newest version
> though. It's included on
> every new pvr150/500 CDROM, basically the newest one available on the
> shpvr website
> from the wiki page for firmware. It reports this line in the driver...
On Monday 06 June 2005 04:35 am, ckennedy wrote:
> Louie Ilievski wrote:
> >I think this is some kind of joke or something. Not at all consistent
> > with every single other email I've seen from Chris as far as signature,
> > email address, etc.
> >
> :) nah, just using my new/old email address wh
Great video and sound on all tuners.
pvr350 + pvr500mce
ivtv-0.3.6a
Encoder revision: 0x02050032
PAL
Regards
Sigurd
ivtv wrote:
I have been experimenting and have found that the newest firmware is
working ok during my tests now, it seems we have possibly gotten the
driver to the point of work
Louie Ilievski wrote:
I think this is some kind of joke or something. Not at all consistent with
every single other email I've seen from Chris as far as signature, email
address, etc.
:) nah, just using my new/old email address which isn't work related,
parting from my kmos.org email ad
Per Jönsson wrote:
Hi,
Help me understand something.
In ivtv-firmware.c, there is a check that the firmware size isn't greater
than IVTV_FIRM_IMAGE_SIZE, which is defined as 256*1024 = 262144 bytes.
However, HcwFalcn.rom in the zip file you refer to is 376836 bytes.
Wouldn't that result i
On Monday 06 June 2005 04:36, ckennedy wrote:
> ivtv: Encoder revision: 0x02050032
> ftp://ftp.shspvr.com/download/wintv-pvr_150-500/inf/pvr_2.0.24.23035.zip
>
> Unzip that file and inside you'll see HcwFalcn.rom file, which you'll
> want to move to /lib/modules/ivtv-fw-enc.bin
>
> Thanks,
> Chris
Hi,
Help me understand something.
In ivtv-firmware.c, there is a check that the firmware size isn't greater
than IVTV_FIRM_IMAGE_SIZE, which is defined as 256*1024 = 262144 bytes.
However, HcwFalcn.rom in the zip file you refer to is 376836 bytes.
Wouldn't that result in an error when loading
On 6/6/05, Louie Ilievski <[EMAIL PROTECTED]> wrote:
> I think this is some kind of joke or something. Not at all consistent with
> every single other email I've seen from Chris as far as signature, email
> address, etc.
http://whois.net/whois.cgi2?d=groovy.org
-
I think this is some kind of joke or something. Not at all consistent with
every single other email I've seen from Chris as far as signature, email
address, etc.
~Lou
On Sunday 05 June 2005 06:40 pm, Harry Orenstein wrote:
> On Sunday 05 June 2005 8:53 pm, ivtv wrote:
> > I have been experimen
Harry Orenstein wrote:
How new? Could you post MD5 sums or some other indication of the versions you
want people to try? Probably would be best to compare apples to apples.
It's version 2.05.32 or greater, I think that's the newest version
though. It's included on
every new pvr150/500 C
This may be useful:
http://ivtv.writeme.ch/tiki-index.php?page=FirmwareVersions
Harry Orenstein wrote:
How new? Could you post MD5 sums or some other indication of the
versions you
want people to try? Probably would be best to compare apples to apples.
-- Harry O.
--
On Sunday 05 June 2005 8:53 pm, ivtv wrote:
> I have been experimenting and have found that the newest firmware is
> working ok during my tests now, it seems we have possibly gotten the
> driver to the point of working with the old firmware and newer
> firmware. The newer firmware seems good at f
I have been experimenting and have found that the newest firmware is
working ok during my tests now, it seems we have possibly gotten the
driver to the point of working with the old firmware and newer
firmware. The newer firmware seems good at framebased DMA, doesn't do
block based, while the
28 matches
Mail list logo
