Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9BCC7C433EF for ; Sun, 13 Mar 2022 12:41:40 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id B04B882DD7; Sun, 13 Mar 2022 13:41:38 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="Wf/ZI4Ss"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id BB72083041; Sun, 13 Mar 2022 13:41:36 +0100 (CET) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id D40C481433 for ; Sun, 13 Mar 2022 13:41:32 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=paweljarosz3691@gmail.com Received: by mail-wm1-x334.google.com with SMTP id v130-20020a1cac88000000b00389d0a5c511so3896991wme.5 for ; Sun, 13 Mar 2022 05:41:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:from:subject:reply-to:to:cc :references:content-language:in-reply-to:content-transfer-encoding; bh=50NazGewKt4MXFQxteWcFQchdjGOMmfYVv6kGqDifKI=; b=Wf/ZI4SsFbWjSdIiYyy4335zetwWYf/pBwyxvd2zAt/F02lVf6Je7W52TwyE7NT/U+ L78HSn74jJfAoNFNaM5owgFn96efUeYLKZNhB7bT1h4AbBvicxp0ObCgWlTRY3zYw3Zm kbcnh8Sqmw0skd47JJZvehN0QgHHZYhtWFldQHisA8YSuPrPVg0A5ohlFj2KUSx5MrE8 I+dE3ogsKZc41e+1IdqwVCpSm+2oUHaH4MSk/2mUOyC11CTOYEuVKh6NTER4MV5ALiII leyg6yIAzElkNBm4+r5DlHO+0bzFAlIfn20rRG+MM6iAGJPthwvBhLpW7POmHUin2brD CMBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:from :subject:reply-to:to:cc:references:content-language:in-reply-to :content-transfer-encoding; bh=50NazGewKt4MXFQxteWcFQchdjGOMmfYVv6kGqDifKI=; b=69WZSWZHLH1TYCy9MoIzUV70jruiGHTHd671alsq7TF7mh5/0PsRC+qXi2t0HXq3r5 EyFvzLCPosn0ADkvsDSI05WYXWI8xDnsDtaRpuRksgN0A9iGhhSevIIAbVKZ49ycuLm1 +5lgygj9fMtqzoz/BZtZoTGUiRmPHS6VzOI5+92oqiN9FaF4x8X2u+zx8MSb2e7/iRNW 5Og51yhZ8Z2AwhWauE6jxNmLueANgvWZeSooQW4MRv8l0P9p/jQVoB6aFo4VHzG7sHh1 s/+ZHS7XK85cODSPYU5gJ2B4ITGD2rF2OXZTinU92S9w0XywXH5LxC6Ng0qWYd1F5GqF ns9Q== X-Gm-Message-State: AOAM532KMNG/o7hEu1zmRi6977R3d4GHxsKATx2QTuPWBo+NUSulHmCm TXMbbOQqk5U2tEMh8zb8pjI= X-Google-Smtp-Source: ABdhPJzZkZSNZQM+w+dOaeN0MS/1qJMTgcq/ZtcjNXrwD899w2YGsTu4pc2BI3oHzgi22NbLU569Bw== X-Received: by 2002:a05:600c:225a:b0:389:76b5:a7c with SMTP id a26-20020a05600c225a00b0038976b50a7cmr22590728wmm.102.1647175292081; Sun, 13 Mar 2022 05:41:32 -0700 (PDT) Received: from [192.168.1.12] ([45.87.35.138]) by smtp.gmail.com with ESMTPSA id h12-20020a5d548c000000b001f1f99e7792sm10727696wrv.111.2022.03.13.05.41.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 13 Mar 2022 05:41:31 -0700 (PDT) Message-ID: <784c7dc5-15d5-5eb9-a463-3fc2231a3243@gmail.com> Date: Sun, 13 Mar 2022 13:41:30 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 From: =?UTF-8?Q?Pawe=c5=82_Jarosz?= Subject: Re: [PATCH v3 1/6] rockchip: move ROCKCHIP_STIMER_BASE to Kconfig To: Kever Yang , Johan Jonker Cc: sjg@chromium.org, philipp.tomsich@vrull.eu, u-boot@lists.denx.de References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: 20211230164825.6489-1-jbx6244@gmail.com Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.5 at phobos.denx.de X-Virus-Status: Clean Hi Kever, > Thanks for you hard working on this, would you mind to share what's the > motivation for support rk3066 and MK808 board? > RK3066 is an SoC release at 2012, which has been EOL for a long time, > and MK808 is a product at 2013, almost 10 years ago. That is true but at least here at Poland there are still rk3066 devices which you can buy. And i don't think it's an exception. There are known cases in opensource community of support for hardware much older than 10 years. I.e. thanks to Linus Torwalds linux still supports EISA FDDI [1]. There are at least a few rk3066a SOC users and in the spirit of Linus Torvalds' open source principles, adding support for this platform is the correct step. RK3066 is a great soc to play with. I use my MK808 for three years now to keep my 3d printer in contact with my local network. I have been using the URZ0350 as a wifi camera for a long time. And guess what! They don't want to break down. [1] https://blog.desdelinux.net/en/linus-supports-a-device-by-a-user/ > I'm not object for enable more SoC support on the mainline, and I know > you have spend a lot > of time on this, I have do something like this before, but to be honest > I don't think it's a good idea to add support for > rk3066 on mainline now. I do not agree. As long as the world is using armv7 architecture adding support for SOC rk3066a is a great and noble idea. I personally am working on following up on my and Johan's patches by adding support for writing firmware to these devices, using only opensource tools like u-boot and rkflashtool. This support can be extended to other devices such as rk3399, rk3568 and others. So other SOCs can also benefit from adding support for rk3066a. I also want to add that Linux actively supports rk3066a [2]. So if linux supports it, U-BOOT SHOULD ALSO! [2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=grep&q=rk3066 I appeal to you Kever Yang in the spirit of opensource, don't give up on rk3066a yet. These devices are there and they work! Thanks -Paweł > I merge the patches from Paweł Jarosz many years ago into rockchip local > u-boot and make it work, > I want to make the branch support as much SoCs as possible at that time. > But later I found there is no people to use > it, and the U-Boot is getting more and more heavy, old SoC support is > the one part people want to clean, > for it always bring in more '#if, #else' or something like this clean up > series patches, and more terrible thing is how to > always maintain the source code works on the old hardware. I do make > everything work for a long time at first, > but one day my only rk3066 board is broken, and I'm not able to do it > anymore. > > Thanks, > - Kever