From: CityK <cityk@rogers.com>
To: Steve <steve@ganymede.demon.co.uk>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] TechnoTrend S2-3600
Date: Sun, 07 Dec 2008 21:09:51 -0500 [thread overview]
Message-ID: <493C81EF.9010706@rogers.com> (raw)
In-Reply-To: <493C6C68.2060702@ganymede.demon.co.uk>
Hi Steve,
> referring back to the message at
> http://www.linuxtv.org/pipermail/linux-dvb/2008-October/029830.html I
> assume I'm supposed to do something with the attachment
> my_s2api_pctv452e.patch but what?
>
> If anyone can point out what I'm doing wrong, what I need to do, or if
> there is anything I can do to help with support for the TechnoTrend
> S2-3600 then please let me know.
>
I'm not familiar with the device et al., but what you can attempt to do
is apply the patch to the source code. If its one or two lines you can
do this manually or you could use "patch" . ( Download patch if its not
include in your distro already, then cd into the s2-liplianin source
code's top most directory and run (but obviously correct for the proper
pathway) the command "patch -p1 < path_to_/my_s2api_pctv452e.patch". )
Then rebuild the drivers and give it another shot.
Note: I have no idea if the patch has been already applied to that
branch or not, or whether if it will still apply properly (if in the
case where there may have been heavy development changes since whomever
drew up that patch).
_______________________________________________
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-12-08 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 0:38 [linux-dvb] TechnoTrend S2-3600 Steve
2008-12-08 2:09 ` CityK [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-11 10:44 Bob Martin
2008-10-11 12:30 ` Igor M. Liplianin
2008-10-11 17:45 ` Bob Martin
2008-10-11 19:27 ` Igor M. Liplianin
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=493C81EF.9010706@rogers.com \
--to=cityk@rogers.com \
--cc=linux-dvb@linuxtv.org \
--cc=steve@ganymede.demon.co.uk \
/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