From: Hendrik Skarpeid <skarp@online.no>
To: Nameer Kazzaz <nameer.kazzaz@gmail.com>
Cc: "Igor M. Liplianin" <liplianin@me.by>, linux-media@vger.kernel.org
Subject: Re: DM1105: could not attach frontend 195d:1105
Date: Tue, 23 Feb 2010 13:14:56 +0100 [thread overview]
Message-ID: <4B83C6C0.5020708@online.no> (raw)
In-Reply-To: <4B82EF6D.2000707@gmail.com>
No luck here either, still working on it.
My plan is to solder som wires on strategic points on the board and
debug i2c and other activity with an oscilloscope. Will probably start
next week.
Nameer Kazzaz wrote:
> Hey Igor,
> I'm getting the same error:
> dm1105 0000:04:0b.0: could not attach frontend
>
> Did you get your one to work.
>
> Thanks
> Nameer
>
> Igor M. Liplianin wrote:
>> On 18 февраля 2010, liplianin@me.by wrote:
>>
>>> I also got the unbranded dm1105 card. I tried the four possible i2c
>>> addresses, just i case. Noen worked of course. Then I traced the i2c
>>> pins on the tuner to pins 100 and 101 on the DM1105.
>>> These are GPIO pins, so bit-banging i2c on these pins seems to be the
>>> solution.
>>>
>>> scl = p101 = gpio14
>>> sda = p100 = gpio13
>>>
>> Here is the patch to test. Use option card=4.
>> modprobe dm1105 card=4
>>
>
>
>
next prev parent reply other threads:[~2010-02-23 12:29 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B7D83B2.4030709@online.no>
2010-02-20 17:49 ` DM1105: could not attach frontend 195d:1105 Igor M. Liplianin
2010-02-22 20:56 ` Nameer Kazzaz
2010-02-23 12:14 ` Hendrik Skarpeid [this message]
2010-02-23 13:12 ` Nameer Kazzaz
2010-02-23 17:40 ` Igor M. Liplianin
2010-02-23 19:40 ` Nameer Kazzaz
2010-03-02 13:06 ` Hendrik Skarpeid
2010-03-02 19:09 ` Hendrik Skarpeid
2010-03-02 23:10 ` Igor M. Liplianin
2010-03-03 8:38 ` Hendrik Skarpeid
2010-03-03 15:49 ` Igor M. Liplianin
2010-03-03 16:42 ` Hendrik Skarpeid
2010-03-03 19:05 ` Igor M. Liplianin
2010-03-04 21:27 ` Hendrik Skarpeid
2010-03-04 22:16 ` Hendrik Skarpeid
2010-03-04 22:46 ` Hendrik Skarpeid
2010-03-06 11:52 ` Igor M. Liplianin
2010-03-06 19:18 ` Hendrik Skarpeid
2010-03-07 10:12 ` Igor M. Liplianin
2010-03-10 12:15 ` Hendrik Skarpeid
2010-03-31 10:47 ` Hendrik Skarpeid
2010-10-23 9:20 ` Igor M. Liplianin
2011-01-31 9:33 ` Matt Vickers
2011-01-31 17:55 ` Igor M. Liplianin
2011-02-01 5:17 ` Matt Vickers
2011-02-02 18:39 ` Igor M. Liplianin
2011-02-02 18:41 ` Igor M. Liplianin
2011-05-03 21:33 ` Mauro Carvalho Chehab
2011-05-05 18:41 Igor M. Liplianin
2011-05-05 19:01 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2010-01-16 11:55 Igor M. Liplianin
2010-01-16 2:49 paul10
2010-01-16 3:11 ` paul10
2010-01-16 13:18 ` paul10
2010-01-16 14:12 ` Igor M. Liplianin
2010-01-19 8:51 ` paul10
2010-01-19 13:45 ` Igor M. liplianin
2010-01-20 21:20 ` paul10
2010-01-31 13:45 ` Igor M. Liplianin
2010-02-01 12:17 ` Nameer Kazzaz
2010-02-02 15:21 ` Nameer Kazzaz
2010-02-02 16:57 ` Igor M. Liplianin
2010-02-02 17:16 ` Nameer Kazzaz
2010-02-02 22:07 ` Nameer Kazzaz
2010-02-03 17:41 ` Igor M. Liplianin
2010-02-04 9:56 ` Nameer Kazzaz
2010-01-15 23:14 paul10
2010-01-15 23:54 ` Igor M. Liplianin
2010-01-16 0:10 ` Igor M. Liplianin
2010-01-15 9:15 paul10
2010-01-15 15:21 ` 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=4B83C6C0.5020708@online.no \
--to=skarp@online.no \
--cc=linux-media@vger.kernel.org \
--cc=liplianin@me.by \
--cc=nameer.kazzaz@gmail.com \
/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