From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Cc: video4linux-list@redhat.com, linux-dvb@linuxtv.org
Subject: Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was: Re: When xc3028/xc2028 will be supported?
Date: Tue, 19 Feb 2008 18:20:26 -0300 [thread overview]
Message-ID: <20080219182026.73bb270f@gaivota> (raw)
In-Reply-To: <pan.2008.02.19.17.24.31.993112@gimpelevich.san-francisco.ca.us>
Hi Daniel,
On Tue, 19 Feb 2008 09:24:32 -0800
Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> wrote:
> On Tue, 19 Feb 2008 13:38:45 -0300, Mauro Carvalho Chehab wrote:
>
> > Could you please rebase your changesets fixing the gpio's for PowerColor Real
> > Angel 330 and send them to me?
>
> I intend to do exactly that sometime within the next couple of weeks.
I've contacted Dâniel Fraga and fixed the remaining issue with his PowerColor
Real Angel 330: firmware should be version 2.5 in order to work. He also
confirmed that the GPIOs are the same as yours for his board.
I've already committed the fixes for it at cx88-xc3028. On his board, both radio
and TV worked fine.
To make easier for all I've changed the firmware extracting tool
to get the firmwares from cx88vid.sys. The extracting tool, and the generated
firmware still needs to be tested.
Dâniel & Daniel, could you please test ? Hopefully, I didn't make any mistake
when changing the extracting tool ;)
The tool is available at:
linuxt/Documentation/video4linux/extract_xc3028.pl
The instructions for usage written at the beginning of the file:
# For firmware version 2.5, you can use the following procedure:
# 1) Download the windows driver with something like:
# wget http://www.power-color.com/drivers/real_angel/RA330_Driver_and_Appl
ication.zip
# or
# wget ftp://driver1.cptech.com.tw/Driver/RA330TV/ra330_xp.zip
#
# 2) Extract the file cx88vid.sys from the zip into the current dir:
# unzip -x RA330_Driver_and_Application.zip "Real Angel Driver & Application/Driver/Plug_Play/cx88vid.sys"
# 3) run the script:
# ./extract_xc3028.pl cx88vid.sys
# 4) copy the generated file:
# cp xc3028-v25.fw /lib/firmware
The real test were done using Dâniel's cx88vid.sys from his CD. I expect that
the site has the same file, otherwise, md5 will fail, and the firmware won't
be extracted.
Cheers,
Mauro
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-02-19 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080127173132.551401d9@tux.abusar.org.br>
[not found] ` <20080128165403.1f7137e0@gaivota>
[not found] ` <20080128182634.345bd4e8@tux.abusar.org.br>
[not found] ` <20080128184534.7af7a41b@gaivota>
[not found] ` <20080128192230.59921445@tux.abusar.org.br>
[not found] ` <20080129004104.17e20224@gaivota>
[not found] ` <20080129021904.1d3047d1@tux.abusar.org.br>
[not found] ` <20080129025020.60fa33de@gaivota>
[not found] ` <20080129050103.2fae9d61@tux.abusar.org.br>
[not found] ` <20080129122547.63214371@gaivota>
2008-02-16 19:30 ` [EXPERIMENTAL] cx88+xc3028 - tests are required - was: Re: When xc3028/xc2028 will be supported? Daniel Gimpelevich
2008-02-17 15:35 ` Markus Rechberger
2008-02-19 4:44 ` Michael Krufky
2008-02-19 9:51 ` Mauro Carvalho Chehab
2008-02-19 16:38 ` Mauro Carvalho Chehab
2008-02-19 17:24 ` Daniel Gimpelevich
2008-02-19 21:20 ` Mauro Carvalho Chehab [this message]
2008-02-19 22:27 ` Dâniel Fraga
2008-02-19 20:43 ` [EXPERIMENTAL] cx88+xc3028 - tests are required - was: Re: Wh en " mkrufky
2008-02-19 21:20 ` Mauro Carvalho Chehab
2008-02-22 1:38 ` Michael Krufky
2008-02-22 12:13 ` Mauro Carvalho Chehab
2008-02-22 13:45 ` [linux-dvb] " Michael Krufky
2008-02-22 14:13 ` Michael Krufky
2008-02-22 14:47 ` Vanessa Ezekowitz
2008-02-21 13:48 ` [EXPERIMENTAL] cx88+xc3028 - tests are required - was: Re: When " Adam Pribyl
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=20080219182026.73bb270f@gaivota \
--to=mchehab@infradead.org \
--cc=daniel@gimpelevich.san-francisco.ca.us \
--cc=linux-dvb@linuxtv.org \
--cc=video4linux-list@redhat.com \
/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