From: Bagas Sanjaya <bagasdotme@gmail.com>
To: JPT <j-p-t@gmx.net>,
Linux Media Subsystem <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Antti Palosaari" <crope@iki.fi>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Gon Solo" <gonsolo@gmail.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: si2157 not working at all?
Date: Wed, 25 Oct 2023 07:26:41 +0700 [thread overview]
Message-ID: <ZThgwTieDv7Gi8UG@debian.me> (raw)
In-Reply-To: <1cfa1365-ca0d-4e33-a149-751277183440@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Mon, Oct 23, 2023 at 07:44:28PM +0200, JPT wrote:
> Well,
>
> I was able to make a fresh ubuntu install and build 6.6-rc7
>
> find the logfile here:
> https://pastebin.com/9zsRuYFv
>
> comments inside, at the end.
> the last lines are:
>
> si2168 8-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> si2168 8-0067: firmware version: B 4.0.25
> si2157 9-0063: device is buggy, skipping firmware download
> si2157 9-0063: firmware version: \xff.\xff.255
>
> so even in the newest kernel, the chip is marked as buggy.
>
> could someone please have a look what is the problem with si2157?
>
> here seems to be a patch for kernel 4.19
> https://github.com/brandsimon/debian-kernel-terratec-cinergy-tc2
Please don't top-post; reply inline with appropriate context instead.
What patch do you mean on that repo? Can you try applying that to see
if it helps?
Confused...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-25 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 7:57 si2157 not working at all? JPT
2023-10-22 10:08 ` Bagas Sanjaya
2023-10-23 13:18 ` JPT
2023-10-23 17:44 ` JPT
2023-10-25 0:26 ` Bagas Sanjaya [this message]
[not found] ` <CANL0fFQMiubX3saR7fmQvYjKqDVCbDNTwyzj1_-aiN6HSB-hwg@mail.gmail.com>
2023-10-25 12:37 ` JPT
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=ZThgwTieDv7Gi8UG@debian.me \
--to=bagasdotme@gmail.com \
--cc=crope@iki.fi \
--cc=gonsolo@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=j-p-t@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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