From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Bin Meng <bmeng.cn@gmail.com>, Tom Rini <trini@konsulko.com>,
Wolfgang Wallner <wolfgang.wallner@br-automation.com>
Subject: Re: [PATCH v1 1/1] Makefile.lib: Always rebuild DSDT
Date: Wed, 29 Nov 2023 12:07:04 +0200 [thread overview]
Message-ID: <ZWcNSPgiVXcVbbTL@smile.fi.intel.com> (raw)
In-Reply-To: <YkQhFc07R2pOMyyR@smile.fi.intel.com>
On Wed, Mar 30, 2022 at 12:21:25PM +0300, Andy Shevchenko wrote:
> On Mon, Oct 25, 2021 at 09:52:45PM +0300, Andy Shevchenko wrote:
> > On Mon, Oct 25, 2021 at 09:18:56AM -0600, Simon Glass wrote:
> > > On Mon, 25 Oct 2021 at 01:34, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > > > On Sun, Oct 24, 2021 at 11:00 PM Simon Glass <sjg@chromium.org> wrote:
> > > > > On Wed, 20 Oct 2021 at 06:37, Andy Shevchenko
> > > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > > >
> > > > > > The dsdt.asl is usually combined out of several files that are included
> > > > > > in the main one. Whenever we change the content of any of such files,
> > > > > > build system is not able to recognize them. Hence the easiest way is to
> > > > > > force DSDT rebuild each time we run make.
> > > >
> > > > > Ick. Since it uses #include, doesn't the dependency generation work with this?
> > > >
> > > > How?
> > >
> > > If you do a sandbox build you will see this file:
> > >
> > > arch/sandbox/dts/.sandbox.dtb.cmd
> > >
> > > It contains the dependencies used to compile the device tree. Can we
> > > use the same mechanism? There is a .cmd file for the dsdt file but it
> > > does not seem to have the correct contents.
> >
> > A spent more than couple of hours to fight with `make` and failed.
> > Maybe you can improve the below (it still rebuilds always)
>
> So, can we fix this annoying bug, please?
Any news here? If no other solution, please apply this patch.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-11-29 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 12:37 [PATCH v1 1/1] Makefile.lib: Always rebuild DSDT Andy Shevchenko
2021-10-24 19:53 ` Simon Glass
2021-10-25 7:33 ` Andy Shevchenko
2021-10-25 15:18 ` Simon Glass
2021-10-25 18:52 ` Andy Shevchenko
2022-03-30 9:21 ` Andy Shevchenko
2023-11-29 10:07 ` Andy Shevchenko [this message]
2023-11-29 17:16 ` Heinrich Schuchardt
2023-11-30 2:45 ` Simon Glass
2023-12-09 14:39 ` Heinrich Schuchardt
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=ZWcNSPgiVXcVbbTL@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wolfgang.wallner@br-automation.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.