From owner-freebsd-arm@freebsd.org Fri Oct 9 02:27:34 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 11CE6437225 for ; Fri, 9 Oct 2020 02:27:34 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C6sRT6Wl1z3WTM for ; Fri, 9 Oct 2020 02:27:33 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f170.google.com (mail-qk1-f170.google.com [209.85.222.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id BD2EE26D00 for ; Fri, 9 Oct 2020 02:27:33 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f170.google.com with SMTP id 140so7461717qko.2 for ; Thu, 08 Oct 2020 19:27:33 -0700 (PDT) X-Gm-Message-State: AOAM530B7H8N8l3bhhJroOR+6jLKnqujmF+XTJcxjKk6ZiiLjqEREyuw ZzLQOrPoTEDUyUTb57p/qKqA2fAf1iL8eViTP2w= X-Google-Smtp-Source: ABdhPJxRznWJGQ+nYJTNaOPAzucKrF0zfy2eIW3CY+zdT+obPGhorIWzoFHaGgbBFpVcEiFW8qoPN+3+SJBevOBg28s= X-Received: by 2002:a05:620a:4fb:: with SMTP id b27mr11689948qkh.120.1602210453400; Thu, 08 Oct 2020 19:27:33 -0700 (PDT) MIME-Version: 1.0 References: <20201009021855.GA24977@www.zefox.net> In-Reply-To: <20201009021855.GA24977@www.zefox.net> From: Kyle Evans Date: Thu, 8 Oct 2020 21:27:22 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) To: bob prohaska Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Oct 2020 02:27:34 -0000 On Thu, Oct 8, 2020 at 9:18 PM bob prohaska wrote: > > On Thu, Oct 08, 2020 at 01:34:12PM -0500, Kyle Evans wrote: > > > > Here's a patch that I hacked out and can't test for quite a while yet, > > feel free to give it a shot: > > https://people.freebsd.org/~kevans/bcm2835_vcbus.diff -- the best > > guarantee I can give you is that it builds. We'll need to test it on > > both RPi4 models with the separate bus and the original RPi4s, as well > > as an RPi3 and RPi2/0w. > > > > FWIW, a Pi3B running > FreeBSD www.zefox.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r366466M: Thu Oct 8 17:18:55 PDT 2020 bob@www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 > > seems to build, boot and run without immediate problems. > > A Pi2 running > FreeBSD www.zefox.com 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365692: Thu Oct 8 16:57:50 PDT 2020 bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC-MMCCAM arm > > also built, booted and ran. > > Uptime so far is only a few minutes, but so far, so good. If the MMCCAM > mismatch is significant let me know and I'll fix it. > Thanks for testing! Can you also confirm the output of `dmesg | grep 'WARNING:'`, please? In particular, I'd like to know if you hit either of: WARNING: Improper peripheral attachment ... WARNING: bus for '...' missing dma-ranges MMCAM is fine; by the time you've gone multi-user it's definitely exercised the appropriate bits. Thanks, Kyle Evans