From: Jelle De Loecker <skerit@kipdola.com>
To: LinuxTV DVB Mailing <linux-dvb@linuxtv.org>
Subject: [linux-dvb] TT S2-3200 LIRC remote - Multiproto drivers merge?
Date: Wed, 21 May 2008 10:11:06 +0200 [thread overview]
Message-ID: <4833D91A.1050101@kipdola.com> (raw)
Hello again,
I finally got the Technotrend S2-3200 to work on LinuxMCE 0710, now I'm
wondering how to get the IR transceiver to work. (Not that I've managed
to get mythtv working, but since activity on that subject is a bit
slower...)
I already tried to ask on the lirc mailing list, but it seems like a
very dead place.
My dmesg output proves the transceiver is discovered and I have a
/dev/class/input kind of file, I just don't know how to get lirc to
work, or how to get a /dev/lirc0 file (I actually already have another
transceiver on this computer which apparantly only works with MCE
remotes (it's an integrated IR transceiver in my Antec Fusion v2 case))
since there isn't a specific driver in lirc for this technotrend card.
Now, I want to get some facts straight about the multiproto driver:
Is it "done"? What's the big difference between multiproto and
multiproto plus? (Even though there hasn't been an update in 5 weeks for
the regular drivers, the plus drivers seemed to have more activity)
Or is it correct to assume that now only the software applications need
to get a patch to work with our multiproto drivers?
And, looking at the multiproto_plus drivers, I see they "merged" with
v4l-dvb - what does this mean exactly?
Thank you for your time,
Jelle De Loecker
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-05-21 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 8:11 Jelle De Loecker [this message]
2008-05-21 18:46 ` [linux-dvb] Re : TT S2-3200 LIRC remote - Multiproto drivers merge? manu
2008-05-22 12:57 ` [linux-dvb] Re : " manu
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=4833D91A.1050101@kipdola.com \
--to=skerit@kipdola.com \
--cc=linux-dvb@linuxtv.org \
/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