From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Chris Lee <updatelee@gmail.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Kworld 330u broken
Date: Sun, 12 Jan 2014 17:43:28 +0100 [thread overview]
Message-ID: <52D2C630.60906@googlemail.com> (raw)
In-Reply-To: <CAA9z4LYNHuORA+QnO_3NBj4mwBxSMFY8pXoF2y-iYjJD+Xqteg@mail.gmail.com>
On 10.01.2014 05:08, Chris Lee wrote:
> Im not sure exactly when it broke but alot of changes have happened in
> em28xx lately and they've broken my Kworld 330u. The issue is that
>
> ctl->demod = XC3028_FE_CHINA;
> ctl->fname = XC2028_DEFAULT_FIRMWARE;
> cfg.ctrl = &ctl;
>
> are no longer being set, this causes xc2028_attach
>
> if (cfg->ctrl)
> xc2028_set_config(fe, cfg->ctrl);
>
> to never get called. Therefore never load the firmware. Ive attached
> my logs to show you what I mean.
>
> I quickly hacked up a patch, my tree is quite different from V4L's now
> so the line numbers may not lineup anymore, and Im sure you guys wont
> like it anyhow lol
>
> Chris Lee
Hi Chris,
thank you for testing and the patch !
The suggested changes in em28xx_attach_xc3028() look good, but instead
of introducing a second copy of em28xx_setup_xc3028() in em28xx-dvb,
we should just move this function from the v4l extension back to the core.
Mauro, I can create a patch, but I assume there is already enough
pending em28xx stuff that requires rebasing, so I assume it's easier for
you to do it yourself.
Let me know if I can assist you.
Regards,
Frank
next prev parent reply other threads:[~2014-01-12 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 4:08 Kworld 330u broken Chris Lee
2014-01-12 14:10 ` [PATCH] em28xx: fix xc3028 demod and firmware setup on DVB Mauro Carvalho Chehab
2014-01-12 16:43 ` Frank Schäfer [this message]
2014-01-12 16:50 ` Kworld 330u broken Mauro Carvalho Chehab
[not found] ` <CAA9z4LbpsnDqS4U8rZzzKk6CmrH9cyAYjOtKOVC5goZz5Q13hA@mail.gmail.com>
2014-01-12 17:40 ` Mauro Carvalho Chehab
2014-01-13 18:34 ` Frank Schäfer
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=52D2C630.60906@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=updatelee@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 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.