From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:39558 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754860Ab2LLVe2 (ORCPT ); Wed, 12 Dec 2012 16:34:28 -0500 Received: by mail-ee0-f46.google.com with SMTP id e53so817732eek.19 for ; Wed, 12 Dec 2012 13:34:27 -0800 (PST) Message-ID: <50C8F86F.2090503@googlemail.com> Date: Wed, 12 Dec 2012 22:34:39 +0100 From: =?ISO-8859-1?Q?Frank_Sch=E4fer?= MIME-Version: 1.0 To: Antti Palosaari CC: Devin Heitmueller , Matthew Gyurgyik , Linux Media Mailing List , =?ISO-8859-1?Q?David_H=E4rdeman?= Subject: Re: em28xx: msi Digivox ATSC board id [0db0:8810] References: <50B5779A.9090807@pyther.net> <50BFBE39.90901@pyther.net> <50BFC445.6020305@iki.fi> <50BFCBBB.5090407@pyther.net> <50BFECEA.9060808@iki.fi> <50BFFFF6.1000204@pyther.net> <50C11301.10205@googlemail.com> <50C12302.80603@pyther.net> <50C34628.5030407@googlemail.com> <50C34A50.6000207@pyther.net> <50C35AD1.3040000@googlemail.com> <50C48891.2050903@googlemail.com> <50C4A520.6020908@pyther.net> <50C4BA20.8060003@googlemail.com> <50C4BAFB.60304@googlemail.com> <50C4C525.6020006@googlemail.com> <50C4D011.6010700@pyther.net> <50C60220.8050908@googlemail.com> <50C60772.2010904@googlemail.com> <50C6226C.8090302@iki! .fi> <50C636E7.8060003@googlemail.com> <50C64AB0.7020407@iki.fi> <50C79CD6.4060501@googlemail.com> <50C79E9A.3050301@iki.fi> <50C8F645.60308@googlemail.com> In-Reply-To: <50C8F645.60308@googlemail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-media-owner@vger.kernel.org List-ID: Am 12.12.2012 22:25, schrieb Frank Schäfer: ... > Am 11.12.2012 21:59, schrieb Antti Palosaari: >> See current af9015 driver as example how driver makes decision which >> variant of NEC is used. You will need something similar. Read all 4 >> NEC bytes from the hardware and then use driver to make decision which >> variant it is. > Yes, checking for inverted address and key code bytes would be a > possibility... The problem here is of course, that we have to configure the device first. So we need to know the protocol variant before getting any bytes from the device... Frank