All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piotr Chmura <chmooreck@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Robert Schlabbach <robert_s@gmx.net>
Cc: Antti Palosaari <crope@iki.fi>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bug 215726 - si2157.c: mention name of the missing firmware file
Date: Wed, 30 Mar 2022 12:35:49 +0200	[thread overview]
Message-ID: <2ce6dc15-51a8-e59c-26ab-4380cdca6209@gmail.com> (raw)
In-Reply-To: <1fc02de2-890e-e8e8-0ab6-aba62a333de5@leemhuis.info>


W dniu 30.03.2022 o 11:55, Thorsten Leemhuis pisze:
> On 29.03.22 21:21, Robert Schlabbach wrote:
>> the patch linked in the bugzilla ticket:
>> https://lore.kernel.org/linux-media/6f84b7f4-3ede-ae55-e99b-a9d4108c80e2@gmail.com/
>> should indeed fix the issue.
> Ahh, the comment mentioning it was added shortly after I sent my mail.
> #regzbot monitor:
> https://lore.kernel.org/linux-media/6f84b7f4-3ede-ae55-e99b-a9d4108c80e2@gmail.com/
>
> Adding Piotr, the patches' author to the CC, who also replied.
>
> BTW: that patch is afaics missing a Fixes tag specifying the culprit and
> a `Cc: stable@vger.kernel.org # 5.17.x` tag to make sure it's quickly
> backported to the stable tree, as among others explained here:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/handling-regressions.rst
Sorry for my inconvenience. I just fixed my device and wanted to share 
solution with the "world". I'm not familiar with all kernel development 
convention (yet).

>
>> The error was that the rom_id and required
>> fields were swapped in the table, so the non-zero rom_id was taken as a
>> "true" required boolean value, thus incorrectly evaluating that the
>> chip requires a firmware file to operate when in fact it does not.
>> I have tested the patch and found it worked for me. But I do not know
>> how to push this further along:
>> https://patchwork.linuxtv.org/project/linux-media/patch/6f84b7f4-3ede-ae55-e99b-a9d4108c80e2@gmail.com/
> Mauro, what's up here? The patch fixes a regression and thus afaics
> should quickly find its way towards mainline to get it into the stable
> tree, as explained in the (bran new) document linked above.
>
> Ciao, Thorsten
>
>> Gesendet: Dienstag, 29. März 2022 um 10:33 Uhr
>> Von: "Thorsten Leemhuis" <regressions@leemhuis.info>
>> An: "Antti Palosaari" <crope@iki.fi>, "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>, "Robert Schlabbach" <robert_s@gmx.net>
>> Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>, az0123456@gmx.de, "Linux Media Mailing List" <linux-media@vger.kernel.org>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
>> Betreff: Bug 215726 - si2157.c: mention name of the missing firmware file
>> Hi, this is your Linux kernel regression tracker.
>>
>> I noticed a regression report in bugzilla.kernel.org that afaics nobody
>> acted upon since it was reported about a week ago, that's why I decided
>> to forward it to the lists and all people that seemed to be relevant
>> here. To quote from https://bugzilla.kernel.org/show_bug.cgi?id=215726 :
>>
>>> I get the following error messages when trying to use si2157.ko in linux 5.17:
>>> si2157 13-0060: found a 'Silicon Labs Si2157-A30 ROM 0x50'
>>> si2157 13-0060: Can't continue without a firmware
>>> I did work in linux 5.16.16 without a firmware file. Unfortunately the driver does not tell me the name of the missing firmware file.
>> Could somebody take a look into this? Or was this discussed somewhere
>> else already? Or even fixed?
>>
>>


  reply	other threads:[~2022-03-30 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  8:33 Bug 215726 - si2157.c: mention name of the missing firmware file Thorsten Leemhuis
2022-03-29 19:21 ` Robert Schlabbach
2022-03-30  9:55   ` Thorsten Leemhuis
2022-03-30 10:35     ` Piotr Chmura [this message]
2022-03-30 10:44       ` Thorsten Leemhuis
2022-03-30 15:47         ` Piotr Chmura
2022-03-31  6:46           ` Thorsten Leemhuis
2022-03-29 21:33 ` Piotr Chmura

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=2ce6dc15-51a8-e59c-26ab-4380cdca6209@gmail.com \
    --to=chmooreck@gmail.com \
    --cc=crope@iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=robert_s@gmx.net \
    /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.