From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH 1/7] [RFC] ARM: remove Intel iop33x and iop13xx support Date: Wed, 14 Aug 2019 10:36:01 +0200 Message-ID: References: <20190809162956.488941-1-arnd@arndb.de> <20190809163334.489360-1-arnd@arndb.de> <20190812094456.GI10598@jirafa.cyrius.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20190812094456.GI10598@jirafa.cyrius.com> Sender: linux-kernel-owner@vger.kernel.org To: Martin Michlmayr Cc: Dan Williams , Arnd Bergmann , soc@kernel.org, Russell King , Vinod Koul , Bartosz Golaszewski , Linux ARM , Linux Kernel Mailing List , dmaengine@vger.kernel.org, "open list:GPIO SUBSYSTEM" , linux-i2c , Peter Teichmann List-Id: linux-i2c@vger.kernel.org On Mon, Aug 12, 2019 at 11:45 AM Martin Michlmayr wrote: > As Arnd points out, Debian used to have support for various iop32x > devices. While Debian hasn't supported iop32x in a number of years, > these devices are still usable and in use (RMK being a prime example). I suppose it could be a good idea to add support for iop32x to OpenWrt and/or OpenEmbedded, both of which support some pretty constrained systems. I am personally using these distributions to support elder ARM hardware these days. Just my =E2=82=AC0.01 Linus Walleij