All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: linux-media <linux-media@vger.kernel.org>,
	"Michael Büsch" <m@bues.ch>, "Hans-Frieder Vogt" <hfvogt@gmx.net>,
	"Gianluca Gennari" <gennarone@gmail.com>
Subject: Re: AF9035/AF9033 development
Date: Fri, 06 Apr 2012 22:50:56 +0300	[thread overview]
Message-ID: <4F7F4920.6070204@iki.fi> (raw)
In-Reply-To: <4F7EDB6B.7000402@iki.fi>

On 06.04.2012 15:02, Antti Palosaari wrote:
> Here is TODO list I took from mail I wrote 31.3.2012:
>
> * fix af9033 IF freq control (now Zero-IF only)
> DONE
>
> * change firmware download to use new firmware syntax
> DONE
>
> * dual tuner support
>
> * check if IT9035 is enough similar (My personal suspicion is that
> integrated tuner is only main difference, whilst USB-interface and demod
> are same. But someone has told that it is quite different design though.)
> DONE. It is similar. AF9035 code changes are done. New tuner driver
> still needed.
>
> * implement SNR, BER and USB counters
> partly DONE!
>
> * implement remote controller
>
>
>
> Remote controller and dual tuner support are main missing features. I
> will try implement remote controller next, maybe later tonight.

I failed that. After many hours of hacking I did not succeed to disable 
HID. It is very weird since HID outputs some random letters even there 
is no keytable loaded to device and some other than device own NEC 
remote used.
I can read raw key codes from the firmware, but as the HID is still 
there it is useless. I even tried to load some garbage key tables to 
kill HID - but no success. So I will give up as now.
I think it is possible to edit eeprom to kill HID, but that kind of 
eeprom modification is no way to go.

regards
Antti
-- 
http://palosaari.fi/

      reply	other threads:[~2012-04-06 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 12:02 AF9035/AF9033 development Antti Palosaari
2012-04-06 19:50 ` Antti Palosaari [this message]

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=4F7F4920.6070204@iki.fi \
    --to=crope@iki.fi \
    --cc=gennarone@gmail.com \
    --cc=hfvogt@gmx.net \
    --cc=linux-media@vger.kernel.org \
    --cc=m@bues.ch \
    /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.