All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Arnd Bergmann <arnd@kernel.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Fabio Estevam <festevam@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	John Youn <John.Youn@synopsys.com>,
	Bing Yuan <Bing.Yuan@synopsys.com>,
	"linux-mediatek@lists.infradead.org" 
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kconfig CONFIG_FB dependency regression
Date: Tue, 15 Feb 2022 02:52:48 +0000	[thread overview]
Message-ID: <aaadb6af-0ce7-548c-84a1-f880d1999cbb@synopsys.com> (raw)
In-Reply-To: <CAK8P3a3bJcMKW5QJqoUT8jDe+cbK0A-zSbNZhveX0WwC=ZEUqw@mail.gmail.com>

Arnd Bergmann wrote:
> On Tue, Feb 8, 2022 at 11:42 PM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
>> Randy Dunlap wrote:
>>> On 2/8/22 12:10, Thinh Nguyen wrote:
>>>> Randy Dunlap wrote:
>>>>> On 2/3/22 19:21, Thinh Nguyen wrote:
> 
>> Ah.. It's because I don't use old.config as the base config. I use
>> x86_64_defconfig as the base plus some additional configs I need, and it
>> has CONFIG_FB_EFI set by default.
> 
> Does it hang if you just disable CONFIG_FB_EFI on an otherwise working
> kernel? This is supposed to only disable the framebuffer, but it could be
> the actual cause if something else depends on its presence.
> 

Looks like disabling it works. Not sure why config x86_64_defconfig
needs it.

Thanks,
Thinh

WARNING: multiple messages have this Message-ID (diff)
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Arnd Bergmann <arnd@kernel.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Fabio Estevam <festevam@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	John Youn <John.Youn@synopsys.com>,
	Bing Yuan <Bing.Yuan@synopsys.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kconfig CONFIG_FB dependency regression
Date: Tue, 15 Feb 2022 02:52:48 +0000	[thread overview]
Message-ID: <aaadb6af-0ce7-548c-84a1-f880d1999cbb@synopsys.com> (raw)
In-Reply-To: <CAK8P3a3bJcMKW5QJqoUT8jDe+cbK0A-zSbNZhveX0WwC=ZEUqw@mail.gmail.com>

Arnd Bergmann wrote:
> On Tue, Feb 8, 2022 at 11:42 PM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
>> Randy Dunlap wrote:
>>> On 2/8/22 12:10, Thinh Nguyen wrote:
>>>> Randy Dunlap wrote:
>>>>> On 2/3/22 19:21, Thinh Nguyen wrote:
> 
>> Ah.. It's because I don't use old.config as the base config. I use
>> x86_64_defconfig as the base plus some additional configs I need, and it
>> has CONFIG_FB_EFI set by default.
> 
> Does it hang if you just disable CONFIG_FB_EFI on an otherwise working
> kernel? This is supposed to only disable the framebuffer, but it could be
> the actual cause if something else depends on its presence.
> 

Looks like disabling it works. Not sure why config x86_64_defconfig
needs it.

Thanks,
Thinh
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Arnd Bergmann <arnd@kernel.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Randy Dunlap <rdunlap@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	John Youn <John.Youn@synopsys.com>,
	Bing Yuan <Bing.Yuan@synopsys.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kconfig CONFIG_FB dependency regression
Date: Tue, 15 Feb 2022 02:52:48 +0000	[thread overview]
Message-ID: <aaadb6af-0ce7-548c-84a1-f880d1999cbb@synopsys.com> (raw)
In-Reply-To: <CAK8P3a3bJcMKW5QJqoUT8jDe+cbK0A-zSbNZhveX0WwC=ZEUqw@mail.gmail.com>

Arnd Bergmann wrote:
> On Tue, Feb 8, 2022 at 11:42 PM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
>> Randy Dunlap wrote:
>>> On 2/8/22 12:10, Thinh Nguyen wrote:
>>>> Randy Dunlap wrote:
>>>>> On 2/3/22 19:21, Thinh Nguyen wrote:
> 
>> Ah.. It's because I don't use old.config as the base config. I use
>> x86_64_defconfig as the base plus some additional configs I need, and it
>> has CONFIG_FB_EFI set by default.
> 
> Does it hang if you just disable CONFIG_FB_EFI on an otherwise working
> kernel? This is supposed to only disable the framebuffer, but it could be
> the actual cause if something else depends on its presence.
> 

Looks like disabling it works. Not sure why config x86_64_defconfig
needs it.

Thanks,
Thinh

WARNING: multiple messages have this Message-ID (diff)
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Arnd Bergmann <arnd@kernel.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Fabio Estevam <festevam@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	John Youn <John.Youn@synopsys.com>,
	Bing Yuan <Bing.Yuan@synopsys.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kconfig CONFIG_FB dependency regression
Date: Tue, 15 Feb 2022 02:52:48 +0000	[thread overview]
Message-ID: <aaadb6af-0ce7-548c-84a1-f880d1999cbb@synopsys.com> (raw)
In-Reply-To: <CAK8P3a3bJcMKW5QJqoUT8jDe+cbK0A-zSbNZhveX0WwC=ZEUqw@mail.gmail.com>

Arnd Bergmann wrote:
> On Tue, Feb 8, 2022 at 11:42 PM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
>> Randy Dunlap wrote:
>>> On 2/8/22 12:10, Thinh Nguyen wrote:
>>>> Randy Dunlap wrote:
>>>>> On 2/3/22 19:21, Thinh Nguyen wrote:
> 
>> Ah.. It's because I don't use old.config as the base config. I use
>> x86_64_defconfig as the base plus some additional configs I need, and it
>> has CONFIG_FB_EFI set by default.
> 
> Does it hang if you just disable CONFIG_FB_EFI on an otherwise working
> kernel? This is supposed to only disable the framebuffer, but it could be
> the actual cause if something else depends on its presence.
> 

Looks like disabling it works. Not sure why config x86_64_defconfig
needs it.

Thanks,
Thinh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-02-15  2:53 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 23:01 Kconfig CONFIG_FB dependency regression Thinh Nguyen
2022-02-01 23:01 ` Thinh Nguyen
2022-02-01 23:01 ` Thinh Nguyen
2022-02-01 23:01 ` Thinh Nguyen
2022-02-01 23:06 ` Randy Dunlap
2022-02-01 23:06   ` Randy Dunlap
2022-02-01 23:06   ` Randy Dunlap
2022-02-01 23:06   ` Randy Dunlap
2022-02-01 23:59   ` Fabio Estevam
2022-02-01 23:59     ` Fabio Estevam
2022-02-01 23:59     ` Fabio Estevam
2022-02-01 23:59     ` Fabio Estevam
2022-02-02  0:14     ` Thinh Nguyen
2022-02-02  0:14       ` Thinh Nguyen
2022-02-02  0:14       ` Thinh Nguyen
2022-02-02  0:14       ` Thinh Nguyen
2022-02-02  7:46       ` Arnd Bergmann
2022-02-02  7:46         ` Arnd Bergmann
2022-02-02  7:46         ` Arnd Bergmann
2022-02-02  7:46         ` Arnd Bergmann
2022-02-02 23:55         ` Thinh Nguyen
2022-02-02 23:55           ` Thinh Nguyen
2022-02-02 23:55           ` Thinh Nguyen
2022-02-03  3:15           ` Randy Dunlap
2022-02-03  3:15             ` Randy Dunlap
2022-02-03  3:15             ` Randy Dunlap
2022-02-03  3:15             ` Randy Dunlap
2022-02-03  4:23             ` Thinh Nguyen
2022-02-03  4:23               ` Thinh Nguyen
2022-02-03  4:23               ` Thinh Nguyen
2022-02-03  4:23               ` Thinh Nguyen
2022-02-03  7:18           ` Arnd Bergmann
2022-02-03  7:18             ` Arnd Bergmann
2022-02-03  7:18             ` Arnd Bergmann
2022-02-03  7:18             ` Arnd Bergmann
2022-02-04  3:21             ` Thinh Nguyen
2022-02-04  3:21               ` Thinh Nguyen
2022-02-04  3:21               ` Thinh Nguyen
2022-02-04  3:21               ` Thinh Nguyen
2022-02-04  4:02               ` Randy Dunlap
2022-02-04  4:02                 ` Randy Dunlap
2022-02-04  4:02                 ` Randy Dunlap
2022-02-04  4:02                 ` Randy Dunlap
2022-02-08 20:10                 ` Thinh Nguyen
2022-02-08 20:10                   ` Thinh Nguyen
2022-02-08 20:10                   ` Thinh Nguyen
2022-02-08 20:10                   ` Thinh Nguyen
2022-02-08 20:45                   ` Randy Dunlap
2022-02-08 20:45                     ` Randy Dunlap
2022-02-08 20:45                     ` Randy Dunlap
2022-02-08 20:45                     ` Randy Dunlap
2022-02-08 22:42                     ` Thinh Nguyen
2022-02-08 22:42                       ` Thinh Nguyen
2022-02-08 22:42                       ` Thinh Nguyen
2022-02-08 22:42                       ` Thinh Nguyen
2022-02-09  7:06                       ` Arnd Bergmann
2022-02-09  7:06                         ` Arnd Bergmann
2022-02-09  7:06                         ` Arnd Bergmann
2022-02-09  7:06                         ` Arnd Bergmann
2022-02-15  2:52                         ` Thinh Nguyen [this message]
2022-02-15  2:52                           ` Thinh Nguyen
2022-02-15  2:52                           ` Thinh Nguyen
2022-02-15  2:52                           ` Thinh Nguyen

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=aaadb6af-0ce7-548c-84a1-f880d1999cbb@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=Bing.Yuan@synopsys.com \
    --cc=John.Youn@synopsys.com \
    --cc=arnd@kernel.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=rdunlap@infradead.org \
    /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.