From owner-freebsd-arm@freebsd.org Sun Sep 27 21:06:46 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 F1E203718B8 for ; Sun, 27 Sep 2020 21:06:46 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BzyrQ05hzz4PVN; Sun, 27 Sep 2020 21:06:45 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f43.google.com with SMTP id v8so8998267iom.6; Sun, 27 Sep 2020 14:06:45 -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=yTdXt2uHefwBQJq3Vzm28VCMBGC2g/Cj4n7SCVQl8nA=; b=FvKZLDCsgWIeHRn7VK8brrgMI1hAWP4uy0vGIIDGxs388ieE0viQ2PMz7Sz5Lhrk3Y 14oYe6zQ52WxAZ47Q9S9vMWXQP0MPhPi6fH2pxXdFkrcURVu7zos23LYXSad5oKQqv4L mW4K23LD+5GfCgaLZ3HeYkf5VjtztGQbUYhj79+Gc/Aa9wSTS3+t0WaiD+TBwrEq2Pfd NH/j5O81E9O8Rxn+6I6jTD3xyLbfVg+j+YpajX1tBZvcXxLLWqsqTiqyUjl8AfDaQnuQ NyWdYS14PLYcJEuDhuCTqw2XwIftsPSsr8sZxJOmGx08gDDftfg36/pJz3cL3woDvIg+ oBHg== X-Gm-Message-State: AOAM530HFzjAD5qXncnClxAcarNMd6vgNP96qnbAlv0XXpGFlBiynvpw U1jgdSgmK2/9MFvvCrz2x9g1KZ/eR8n1ApUIoHNq0s6W X-Google-Smtp-Source: ABdhPJx1ccj/iJrFAggeqGIQWDndSHNgSIwtRobu2othoOQAreiyDeRNuLmmAbQ8fPIZJaEFktu8s4yrWpqiJM8VHdc= X-Received: by 2002:a5d:8352:: with SMTP id q18mr5304292ior.31.1601240804371; Sun, 27 Sep 2020 14:06:44 -0700 (PDT) MIME-Version: 1.0 References: <20200925003347.GG60607@FreeBSD.org> <202009250507.08P573Bh045283@mail.karels.net> <20200925093334.GH60607@FreeBSD.org> <97b52e71-9dfe-6b5f-13f0-8dc466ef376f@freebsd.org> <20200925112906.GF26726@FreeBSD.org> <4432eabd-2ef1-c435-085e-11319aec09e0@freebsd.org> In-Reply-To: <4432eabd-2ef1-c435-085e-11319aec09e0@freebsd.org> From: Ed Maste Date: Sun, 27 Sep 2020 17:06:32 -0400 Message-ID: Subject: Re: clock problems with BeagleBone Black on 12.2BETA2 To: Michal Meloun Cc: Glen Barber , "freebsd-arm@freebsd.org" , FreeBSD Release Engineering Team Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4BzyrQ05hzz4PVN X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.43 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-1.78 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-0.97)[-0.966]; NEURAL_SPAM_SHORT(0.19)[0.189]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.43:from]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.43:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; MAILMAN_DEST(0.00)[freebsd-arm]; RCVD_COUNT_TWO(0.00)[2] 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: Sun, 27 Sep 2020 21:06:47 -0000 On Fri, 25 Sep 2020 at 08:43, Michal Meloun wrote: > > Thanks for response. > I currently preparing (slightly) bigger patchset which should > "normalize" situation about TI clock in CURRENT. These must be MFCed to > STABLE ASAP but I afraid that we miss 12.2 target :( Assuming this issue isn't going to be resolved it looks like we should remove the BBB images from the 12.2 release.