From: Jelle De Loecker <skerit@kipdola.com>
To: "Jens Krehbiel-Gräther" <linux-dvb@okg-computer.de>,
"LinuxTV DVB Mailing" <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Technotrend S2-3200 Scanning
Date: Fri, 16 May 2008 09:10:17 +0200 [thread overview]
Message-ID: <482D3359.2020506@kipdola.com> (raw)
In-Reply-To: <482D2A0E.1030307@okg-computer.de>
Jens Krehbiel-Gräther schreef:
> I postet a patch a few weeks ago (here again).
> These szap and scan patches prepare the apps for actual multiproto
> (well for multiproto a few weeks ago, if the api hasn't changed again,
> these should work).
>
> you have to patch the szap and scan from this sources:
>
> http://abraham.manu.googlepages.com/szap.c
> http://abraham.manu.googlepages.com/szap.c
I fear things have changed too much for the patches to work. (Or I'm
messing up a simple command like patch)
Szap: (Using the other szap.c file I can actually apply the patch, but
the new szap.c seems to be incompatible)
# wget http://abraham.manu.googlepages.com/szap.c
# sudo mv szap.c.1 szap.c
# patch < szap-multiproto-apiv33.diff
patching file szap.c
# make
CC lnb.o
CC azap
CC czap
CC szap
szap.c: In function ‘do_tune’:
szap.c:243: error: storage size of ‘fe_params’ isn’t known
szap.c:282: error: ‘DVBFE_SET_PARAMS’ undeclared (first use in this
function)
szap.c:282: error: (Each undeclared identifier is reported only once
szap.c:282: error: for each function it appears in.)
szap.c:243: warning: unused variable ‘fe_params’
szap.c: In function ‘zap_to’:
szap.c:353: error: storage size of ‘fe_info’ isn’t known
szap.c:354: error: storage size of ‘delivery’ isn’t known
szap.c:369: error: ‘DVBFE_DELSYS_DVBS’ undeclared (first use in this
function)
szap.c:373: error: ‘DVBFE_DELSYS_DSS’ undeclared (first use in this
function)
szap.c:377: error: ‘DVBFE_DELSYS_DVBS2’ undeclared (first use in this
function)
szap.c:395: error: ‘DVBFE_SET_DELSYS’ undeclared (first use in this
function)
szap.c:397: error: ‘DVBFE_GET_INFO’ undeclared (first use in this function)
szap.c:354: warning: unused variable ‘delivery’
szap.c:353: warning: unused variable ‘fe_info’
make: *** [szap] Error 1
Scan: (I'm using the original file, since I can't find another version
on Manu's googlepages)
# patch -i scan-multiproto-3.3.patch
patching file scan.c
Hunk #1 FAILED at 1674.
Hunk #2 FAILED at 1693.
Hunk #3 FAILED at 1704.
3 out of 3 hunks FAILED -- saving rejects to file scan.c.rej
Thank you for your time
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-05-16 7:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 23:02 [linux-dvb] Technotrend S2-3200 Scanning Jelle De Loecker
[not found] ` <E1JwrWW-0006Ye-00.goga777-bk-ru@f139.mail.ru>
2008-05-16 5:25 ` Jelle De Loecker
2008-05-16 5:58 ` Igor
2008-05-16 6:30 ` Jens Krehbiel-Gräther
2008-05-16 7:10 ` Jelle De Loecker [this message]
2008-05-16 8:01 ` ChaosMedia > WebDev
2008-05-18 8:12 ` Igor Nikanov
2008-05-18 9:21 ` Jelle De Loecker
2008-05-18 11:24 ` Faruk A
2008-05-18 11:39 ` Jelle De Loecker
2008-05-18 12:07 ` Faruk A
2008-05-18 12:57 ` Jelle De Loecker
2008-05-18 15:19 ` Faruk A
2008-05-18 19:44 ` Andy Walls
2008-05-18 20:53 ` Jelle De Loecker
2008-05-18 9:53 ` Jelle De Loecker
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=482D3359.2020506@kipdola.com \
--to=skerit@kipdola.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-dvb@okg-computer.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.