lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqLd+BxW9T99Sx9vgEkxdbMFe+tL7X_nZ7ExvRxVd_9GNQ@mail.gmail.com>
Date:   Tue, 6 Apr 2021 20:16:48 -0500
From:   Rob Herring <robh+dt@...nel.org>
To:     Dario Binacchi <dariobin@...ero.it>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Bin Meng <bmeng.cn@...il.com>,
        Frank Rowand <frowand.list@...il.com>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Tero Kristo <kristo@...nel.org>, devicetree@...r.kernel.org,
        linux-clk <linux-clk@...r.kernel.org>,
        linux-omap <linux-omap@...r.kernel.org>
Subject: Re: [PATCH 0/2] fdt: translate address if #size-cells = <0>

On Tue, Apr 6, 2021 at 5:02 PM Dario Binacchi <dariobin@...ero.it> wrote:
>
>
> > Il 06/04/2021 16:06 Rob Herring <robh+dt@...nel.org> ha scritto:
> >
> >
> > On Fri, Apr 2, 2021 at 2:21 PM Dario Binacchi <dariobin@...ero.it> wrote:
> > >
> > >
> > > The series comes from my commit in U-boot
> > > d64b9cdcd4 ("fdt: translate address if #size-cells = <0>")
> > > and from the subsequent exchange of emails at the end of which I was
> > > suggested to send the patch to the linux kernel
> > > (https://patchwork.ozlabs.org/project/uboot/patch/1614324949-61314-1-git-send-email-bmeng.cn@gmail.com/).
> >
> > It's 'ranges' that determines translatable which is missing from the
> > DT. This should have not had a 0 size either though maybe we could
> > support that.
>
> I have replied to the email you sent to the u-boot mailing list
>
> >
> > Does the DT have to be updated anyways for your spread spectrum support?
>
> The spread spectrum support patch does not need this patch to work. They belong
> to two different series.

That's not what I asked. Is the spread spectrum support forcing a DT
update for users? If the DT has to be changed anyways (not really
great policy), then you could fix this in the DT at the same time.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ