From: stakanov <stakanov@eclipso.eu>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: DVB-S PCI card regression on 4.19 / 4.20
Date: Thu, 22 Nov 2018 21:19:49 +0100 [thread overview]
Message-ID: <12757009.r0OKxgvFl0@roadrunner.suse> (raw)
In-Reply-To: <20181122180611.2e7f1123@coco.lan>
Hello Mauro.
Thank you so much, for this fast reply and especially for the detailed
indications. I expected to have a lack of knowledge.
Well, I am replying to the question as of below: (for convenience I did cut
the before text, if you deem it useful for the list I can then correct that in
the next posts).
In data giovedì 22 novembre 2018 21:06:11 CET, Mauro Carvalho Chehab ha
scritto:
> Are you sure that the difference is just the Kernel version? Perhaps you
> also updated some other package.
To be clear: I had the same system(!) with all three kernel 4.18.15-1, 4.19.1
(when the problem did arise) and 4.20.2 rc3 from Takashi's repo) installed.
In this very configuration: if one booted in 4.18 (that is in perfect parity
with all other packages) the card worked. 4.19.1 no. And the last kernel the
same. So whatever might be different, forcefully it has to be in the kernel.
(Which is not really a problem if I manage to make it work, so settings will
be known to others or, if not, we will find out what is different, and all
will be happy. As you see I am still optimist).
I will proceed as indicated and report back here tomorrow.
Regards.
_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
next prev parent reply other threads:[~2018-11-22 20:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4e0356d6303c128a3e6d0bcc453ba1be@mail.eclipso.de>
[not found] ` <20181120104217.5b487bcd@coco.lan>
[not found] ` <1593929.t9Y74Rdlh1@roadrunner.suse>
2018-11-20 16:08 ` DVB-S PCI card regression on 4.19 / 4.20 Mauro Carvalho Chehab
2018-11-21 21:20 ` Malcolm Priestley
2018-11-22 15:55 ` Mauro Carvalho Chehab
2018-11-22 16:19 ` Mauro Carvalho Chehab
2018-11-22 18:58 ` stakanov
2018-11-22 20:06 ` Mauro Carvalho Chehab
2018-11-22 20:19 ` stakanov [this message]
2018-11-22 20:35 ` Mauro Carvalho Chehab
2018-11-22 21:44 ` stakanov
2018-11-23 15:55 ` stakanov
2018-11-23 17:26 ` Mauro Carvalho Chehab
2018-11-26 13:31 ` Takashi Iwai
2018-11-27 10:02 ` stakanov
2018-11-27 12:49 ` Mauro Carvalho Chehab
2018-11-27 15:58 ` stakanov
2018-11-27 16:03 ` Takashi Iwai
2018-11-27 17:53 ` Mauro Carvalho Chehab
2018-11-27 18:09 ` Mauro Carvalho Chehab
2018-11-19 15:13 Takashi Iwai
2018-11-19 17:53 ` Mauro Carvalho Chehab
2018-11-19 19:07 ` Malcolm Priestley
2018-11-19 19:47 ` Takashi Iwai
2018-11-19 22:59 ` stakanov
2018-11-19 23:08 ` Mauro Carvalho Chehab
2018-11-19 23:19 ` stakanov
2018-11-19 23:58 ` Mauro Carvalho Chehab
2018-11-20 8:07 ` stakanov
2018-11-20 9:18 ` Mauro Carvalho Chehab
2018-11-20 9:51 ` stakanov
2018-11-20 9:54 ` Takashi Iwai
2018-11-20 10:26 ` Mauro Carvalho Chehab
2018-11-20 11:11 ` Takashi Iwai
2018-11-20 11:28 ` Mauro Carvalho Chehab
2018-11-20 7:12 ` Takashi Iwai
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=12757009.r0OKxgvFl0@roadrunner.suse \
--to=stakanov@eclipso.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).