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: <20190920172947.51c1fdec@aktux>
Date:   Fri, 20 Sep 2019 17:29:47 +0200
From:   Andreas Kemnade <andreas@...nade.info>
To:     "H. Nikolaus Schaller" <hns@...delico.com>
Cc:     Discussions about the Letux Kernel <letux-kernel@...nphoenux.org>,
        Tony Lindgren <tony@...mide.com>,
        Mark Rutland <mark.rutland@....com>,
        Rob Herring <robh@...nel.org>,
        Linux-OMAP <linux-omap@...r.kernel.org>,
        devicetree <devicetree@...r.kernel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>,
        linux-spi <linux-spi@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>,
        BenoƮt Cousson <bcousson@...libre.com>
Subject: Re: [Letux-kernel] [PATCH 2/2] DTS: ARM: gta04: introduce legacy
 spi-cs-high to make display work again

On Fri, 20 Sep 2019 16:54:18 +0200
"H. Nikolaus Schaller" <hns@...delico.com> wrote:

> > Am 20.09.2019 um 16:20 schrieb Tony Lindgren <tony@...mide.com>:
> > 
> > * H. Nikolaus Schaller <hns@...delico.com> [190920 09:19]:  
> >>> Am 20.09.2019 um 10:55 schrieb Linus Walleij <linus.walleij@...aro.org>:
> >>> I suggest to go both way:
> >>> apply this oneliner and tag for stable so that GTA04 works
> >>> again.
> >>> 
> >>> Then for the next kernel think about a possible more abitious
> >>> whitelist solution and after adding that remove *all* "spi-cs-high"
> >>> flags from all device trees in the kernel after fixing them
> >>> all up.  
> >> 
> >> Ok, that looks like a viable path.  
> > 
> > Please repost the oneline so people can ack easily. At least
> > I've already lost track of this thread.  
> 
> It is all here:
> 
> https://patchwork.kernel.org/patch/11035253/
> 
It is the full one (incl. documentation), not the oneline and does not
apply. Now lets not discuss whether it is well documented or not. First
get it fixed. 

Regards,
Andreas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ