From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E708CC32753 for ; Wed, 14 Aug 2019 10:48:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C91F7214DA for ; Wed, 14 Aug 2019 10:48:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727484AbfHNKso (ORCPT ); Wed, 14 Aug 2019 06:48:44 -0400 Received: from mail-qk1-f194.google.com ([209.85.222.194]:44110 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726126AbfHNKso (ORCPT ); Wed, 14 Aug 2019 06:48:44 -0400 Received: by mail-qk1-f194.google.com with SMTP id d79so82010405qke.11; Wed, 14 Aug 2019 03:48:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6Pd2kynJ3XCWkX4RKcVEYfgPLi/9H/DDd0NVl7yQPeo=; b=b3WfU4JrlERMYKiLFbBextRd7Yf69VVTW6nuiE21/6RvqXYKge8poIU+J8JMwdJiZH pzUPX8ALt7pm0DOucJNDLl4QMghRb0/j4O8FtrWS3vNMctxx9I3OZCkpQNEohrg1WS1h 5TdReU4oZMhBV92RSRM7DwElUHfP/dQPL/ajWUMIogpyCMeyIJNrII8cLsiX1j9gdbsS 4VVkGJfwKfCCm1Ggi1kI7IlP4Kkldzk+U/h+Gfh7Jm8galthdPkquR1oLPw9QjOZ2BqT Ryrw6u3uIbgPhV+CElyw08M/Isw7bGI8rznYdLlN1j4GVsWmQe3F+8qcUlc7PQzC418l 3WMA== X-Gm-Message-State: APjAAAWq0ebSqKDmFCdj0GJN40JJAkqmONMUNQzD76dwn0L5TEHp5zU8 5sGJLDfPaXhRDLe6ZF6tKMKV6zwixU7SEbSfFDs= X-Google-Smtp-Source: APXvYqzJchKTdX84186eS/GRemJU2ycIuCn2KmHcwgWMevAGnRcm51YC1Y0PGo9zYEARmcpYhVr0785iqWnXPMYbu7s= X-Received: by 2002:a37:4ac3:: with SMTP id x186mr36177300qka.138.1565779720761; Wed, 14 Aug 2019 03:48:40 -0700 (PDT) MIME-Version: 1.0 References: <20190809162956.488941-1-arnd@arndb.de> <20190809163334.489360-1-arnd@arndb.de> <20190812094456.GI10598@jirafa.cyrius.com> In-Reply-To: From: Arnd Bergmann Date: Wed, 14 Aug 2019 12:48:23 +0200 Message-ID: Subject: Re: [PATCH 1/7] [RFC] ARM: remove Intel iop33x and iop13xx support To: Linus Walleij Cc: Martin Michlmayr , Dan Williams , 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 Content-Type: text/plain; charset="UTF-8" Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org On Wed, Aug 14, 2019 at 10:36 AM Linus Walleij wrote: > > 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. OpenWRT also had support in the past and dropped it around the same time as Debian. The way I understand it, a couple of platforms including iop32x were moved out of the main openwrt source tree into https://github.com/openwrt/targets/ because there was little interest in keeping them running. The idea was that any remaining users could add that feed to get minimal support, but I'm not sure if would still work. In particular, iop33x appears to be based on linux-3.3 plus three patches that are no longer needed in mainline. Building a mainline kernel without those patches may or may not work. Arnd