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=-15.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 BD0A5C432BE for ; Mon, 30 Aug 2021 01:41:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8C27960F25 for ; Mon, 30 Aug 2021 01:41:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236108AbhH3Bmd (ORCPT ); Sun, 29 Aug 2021 21:42:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43422 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230152AbhH3Bmc (ORCPT ); Sun, 29 Aug 2021 21:42:32 -0400 Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6168EC061575 for ; Sun, 29 Aug 2021 18:41:39 -0700 (PDT) Received: by mail-qt1-x833.google.com with SMTP id c19so10477673qte.7 for ; Sun, 29 Aug 2021 18:41:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jms.id.au; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pFdqIIBcp4naoKXGSG7TY4qC/e9lQpz509K+tkZVCTQ=; b=Iuxg0igurz4XQ/ons9/177yA8AHMROiA8gZgXxYCwrwZql9SP9O2R1GlZfkuYxL/Lp /4IryCO6BYiVW3NodXiSwGht+2S1OSHKRsdJQoo27t7YNuW9K3r+sNiiWsiEU7IgHCnc M0dQwbgM773pmdOqTD8E7BuOxRQE2+vlThtsg= 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=pFdqIIBcp4naoKXGSG7TY4qC/e9lQpz509K+tkZVCTQ=; b=PJmZkW5SxtXMem3aRyypUPF/VCe5TJLMOTVjquxrlsBCgpAEXnMbjACMxnAAzJ4Ker C1T+SdDeWbjH5P0Dm9shJc5/+FDluOHITiwIbmhGpLQen6PdWcBDQ31f3FNcJBTZiHZi CqPD/zqK0c6o3JFPn0RlTlugrnq/1pOZ38Ex+wwK0Jr5h7Nt9awgUONesRfC6xvAfHeq lWP5Bnm4rCy1HGm2SN9Nw2VthZOv1V6mw622kAUnRgEq/pAjh64k9hNMRR8ZIShTNy3p K7sSoHzQV54XCpQmK8KLPFXWxph/uhh0INI8PCnh2AQaDsptDxD5bxXNwqTafSUxoffg 2c7Q== X-Gm-Message-State: AOAM533poknnnebTE2fwe1ygnuu/BT39rn63t/dZciq5GFu9a2VAr6S8 Gt9hSD60Qxaj9uIKPtuqhtAPX3Q9srhMWRiDA5FR6bhmzM0= X-Google-Smtp-Source: ABdhPJzGkATn1TLTxqpx8oNd1PjxixtxPXmIUDnlBRK47I0ec/USZNVKXUgEbwElDD15QtQMFEclWaj0lDifFYPMuCM= X-Received: by 2002:ac8:7245:: with SMTP id l5mr18824297qtp.206.1630287698346; Sun, 29 Aug 2021 18:41:38 -0700 (PDT) MIME-Version: 1.0 References: <20210826132946.3324593-1-joel@jms.id.au> In-Reply-To: From: Joel Stanley Date: Mon, 30 Aug 2021 01:41:26 +0000 Message-ID: Subject: Re: [PATCH 0/3] openrisc/litex: Add liteeth support To: Stafford Horne Cc: openrisc@lists.librecores.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 30 Aug 2021 at 00:17, Stafford Horne wrote: > > On Thu, Aug 26, 2021 at 10:59:43PM +0930, Joel Stanley wrote: > > Hello Stafford, > > > > Here are some changes so that the openrisc kernel can boot with ethernet > > support with the in-tree device tree. > > > > I have also updated the address of the serial device to match recent > > litex. I realise this may keep changing, but it does make it easier to > > test upstream kernels if the basics work. > > > > Joel Stanley (3): > > openrisc/litex: Update uart address > > openrisc/litex: Add ethernet device > > openrisc/litex: Update defconfig > > > > arch/openrisc/boot/dts/or1klitex.dts | 13 ++++++++++-- > > arch/openrisc/configs/or1klitex_defconfig | 26 ++++++++++++++--------- > > 2 files changed, 27 insertions(+), 12 deletions(-) > > Hi, > > These all look fine to me. Note, I have just using the autogenerated .dts file > created by the litex build, so I don't usually use this one other than for some > basic testing. I know auto generated one has it's quirks but it does work. > > It's good to have these here though. Agreed. The auto generated ones need a lot of work to be relevant outside of the vexriscv CPU (I tried to build for rocket, a different riscv, and the script blew up...). In the future it would be good to have this one support the drivers that are merged upstream. > > I will queue these after the ehternet driver is queued. Are you planning me to > queue the ethernet driver? Or will someone else be taking that in? I should have mentioned that the driver and bindings were merged through the network tree last week. You can see them in Friday's linux-next. Cheers, Joel ---------- Forwarded message --------- From: Date: Thu, 26 Aug 2021 at 11:30 Subject: Re: [PATCH v4 0/2] net: Add LiteETH network driver To: Joel Stanley Cc: , , , , , , , , , Hello: This series was applied to netdev/net-next.git (refs/heads/master): On Thu, 26 Aug 2021 07:51:04 +0930 you wrote: > This adds a driver for the LiteX network device, LiteEth. > > v4 Fixes the bindings and adds r-b tags from Gabriel and Rob. > > v3 Updates the bindings to describe the slots in a way that makes more > sense for the hardware, instead of trying to fit some existing > properties. The driver is updated to use these bindings, and fix some > issues pointed out by Gabriel. > > [...] Here is the summary with links: - [v4,1/2] dt-bindings: net: Add bindings for LiteETH https://git.kernel.org/netdev/net-next/c/b0f8d3077f8f - [v4,2/2] net: Add driver for LiteX's LiteETH network interface https://git.kernel.org/netdev/net-next/c/ee7da21ac4c3 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html > > -Stafford