From owner-freebsd-arm@freebsd.org Sun Apr 21 12:19:13 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18574158BAAB for ; Sun, 21 Apr 2019 12:19:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A63A56FEB0 for ; Sun, 21 Apr 2019 12:19:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CCB131215F for ; Sun, 21 Apr 2019 12:19:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3LCJB4t036593 for ; Sun, 21 Apr 2019 12:19:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3LCJBwb036585 for freebsd-arm@FreeBSD.org; Sun, 21 Apr 2019 12:19:11 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 237435] [aarch64][KASSERT] panic: pmap_demote_l2: Invalid virtual address - in sys_mprotect while building lang/sbcl with lang/clisp Date: Sun, 21 Apr 2019 12:19:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 12:19:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237435 Bug ID: 237435 Summary: [aarch64][KASSERT] panic: pmap_demote_l2: Invalid virtual address - in sys_mprotect while building lang/sbcl with lang/clisp Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: greg@unrelenting.technology Added clisp as an option for building sbcl on non-x86 platforms (clisp itse= lf requires removing BROKEN in a dependency - bug 237432). When building, an mprotect call fails an assertion: panic: pmap_demote_l2: Invalid virtual address 0x2e0004a7b000 cpuid =3D 20 time =3D 1555847196 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc =3D 0xffff0000006fcb70 lr =3D 0xffff000000123b94 sp =3D 0xffff000103ea44c0 fp =3D 0xffff000103ea46d0 db_trace_self_wrapper() at vpanic+0x18c pc =3D 0xffff000000123b94 lr =3D 0xffff0000003e8e2c sp =3D 0xffff000103ea46e0 fp =3D 0xffff000103ea4790 vpanic() at panic+0x44 pc =3D 0xffff0000003e8e2c lr =3D 0xffff0000003e8bf4 sp =3D 0xffff000103ea47a0 fp =3D 0xffff000103ea4820 panic() at pmap_demote_l2_locked+0xadc pc =3D 0xffff0000003e8bf4 lr =3D 0xffff00000070e674 sp =3D 0xffff000103ea4830 fp =3D 0xffff000103ea48d0 pmap_demote_l2_locked() at pmap_protect+0x1dc pc =3D 0xffff00000070e674 lr =3D 0xffff00000070f4d0 sp =3D 0xffff000103ea48e0 fp =3D 0xffff000103ea4940 pmap_protect() at vm_map_protect+0x2ec pc =3D 0xffff00000070f4d0 lr =3D 0xffff0000006ae188 sp =3D 0xffff000103ea4950 fp =3D 0xffff000103ea49b0 vm_map_protect() at sys_mprotect+0x58 pc =3D 0xffff000 sp =3D 0xffff000103ea49c0 fp =3D 0xffff000103ea= 49c0 sys_mprotect() at do_el0_sync+0x4fc pc =3D 0xffff0000006b3758 lr =3D 0xffff000000717c58 sp =3D 0xffff000103ea49d0 fp =3D 0xffff000103ea4a70 do_el0_sync() at handle_el0_sync+0x84 pc =3D 0xffff000000717c58 lr =3D 0xffff0000006fea00 sp =3D 0xffff000103ea4a80 fp =3D 0xffff000103ea4b90 handle_el0_sync() at 0x43a83c pc =3D 0xffff0000006fea00 lr =3D 0x000000000043a83c sp =3D 0xffff000103ea4ba0 fp =3D 0x0000fffffffee930 The panic does not happen on a NODEBUG kernel and nothing bad seems to happ= en after that :) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Sun Apr 21 17:33:04 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F41F159260F for ; Sun, 21 Apr 2019 17:33:04 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 77631812E2 for ; Sun, 21 Apr 2019 17:33:01 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x3LHEZ1Y079947 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 21 Apr 2019 19:14:36 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1555866876; bh=NLHP6eMTgIjabK5W7wFimSGG5cS1c/oQxiCQZwEKb9c=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=w8OHvXQZfsUKBIhDkHdluts3OFKbotSSICIIpy8THbUojoo0yfwfnYKhiUgZvyzc0 b0/vjxARZ+c7tgAV2lVFKIue+lGLvGlvm6QFM2eGSnA1UG4tXS2lsYGG3pA78ZJd7B 2Pktrswh06XxYEtV9AklTAImflmM4zM46IUwf9NE= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x3LHERth064271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Apr 2019 19:14:27 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x3LHERLw028044; Sun, 21 Apr 2019 19:14:27 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x3LHEPSZ028043; Sun, 21 Apr 2019 19:14:25 +0200 (CEST) (envelope-from ticso) Date: Sun, 21 Apr 2019 19:14:25 +0200 From: Bernd Walter To: Peter Jeremy Cc: ticso@cicely.de, freebsd-arm@freebsd.org, Bernd Walter Subject: Re: no dev.cpu on RPI-B Message-ID: <20190421171425.GB18788@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20190409223917.GK69855@cicely7.cicely.de> <20190409235929.GA8974@server.rulingia.com> <20190410003508.GL69855@cicely7.cicely.de> <20190411202803.GA38343@cicely7.cicely.de> <20190416094811.GA78331@server.rulingia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190416094811.GA78331@server.rulingia.com> X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: 77631812E2 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=w8OHvXQZ X-Spamd-Result: default: False [-1.68 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.99)[-0.988,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.10)[0.097,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; MX_GOOD(-0.01)[mx1.bwct.de]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; NEURAL_HAM_MEDIUM(-0.98)[-0.978,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.01)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 17:33:04 -0000 On Tue, Apr 16, 2019 at 07:48:11PM +1000, Peter Jeremy wrote: > On 2019-Apr-11 22:28:03 +0200, Bernd Walter wrote: > >Much better, but still no temperature: > >[52]matrix# sysctl dev.cpu > >dev.cpu.0.%parent: cpulist0 > >dev.cpu.0.%pnpinfo: name=cpu@0 compat=arm,1176jzf-s > >dev.cpu.0.%location: > >dev.cpu.0.%driver: cpu > >dev.cpu.0.%desc: Open Firmware CPU > >dev.cpu.%parent: > > > >Will take a deeper look into it and compare to the previous FDT once I > >find time. > > I did some digging and found that I'd missed a required patch to > bcm2835_cpufreq which I've just committed as r346265. Sorry about that. Perfect: [48]matrix# sysctl dev.cpu dev.cpu.0.temperature: 33.6C dev.cpu.0.freq_levels: 700/-1 600/-1 500/-1 400/-1 300/-1 dev.cpu.0.freq: 700 dev.cpu.0.%parent: cpulist0 dev.cpu.0.%pnpinfo: name=cpu@0 compat=arm,1176jzf-s dev.cpu.0.%location: dev.cpu.0.%driver: cpu dev.cpu.0.%desc: Open Firmware CPU dev.cpu.%parent: Thank you -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sun Apr 21 17:57:40 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B5DD1592E19 for ; Sun, 21 Apr 2019 17:57:40 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F15F982111 for ; Sun, 21 Apr 2019 17:57:38 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1555869450; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=vImSiOgsngBRzFHdZBFDqlspNTzyO6rf4iewPriXOaaL0sMq+bYfKCrE+KnZxoeUNA7WkOXmXbJmr OUuiqRfxhVFuRb/xmc/I3DKk9hjPlPurVcqOGv+sMzOS7BTzZ8NJyRdo0mhYhCoHMupGYNBgEiIS0M rCEybDCmM4rvulROzloL+a33PgcoPmNUd1GE86iHZQ7n/0miUOvIyham18taSXauBu3THbLGvy0oEl p458WW2wReScfHyBcrzQw9EcJrHOXoVJZIoJ5NFLZmnrU1d7wUa44t9xJPFuZT8J53MYjeXQYiC++I 7faoAJvHovZvDSCUBHQVBan8JSylCZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=00ArG/n+ogebJZ98Hs9krO9Sm9WbyCdaXzr3l8a0bA0=; b=JJDvtM03VO4rRLdQRAPJUXA2yICJztqAaxLAUGQyYb75d8FUFq+pthgEH0hKgXDBVpgnewpS3J0SJ XdOIdu0Jd8I148wI72dHeBt98SpD/xxRakf5hotHgN4aRB6+uOF7s3lG+h1HDcDVMJvxkJTRPWNlHb vhIrzdTRLT+NpuXf+FOQ2+p8HyXTp1HoJ32ITjWkDoAdwmoeYfTSaQBiDIQcDTBcBnNY7mhbUZ1ykU Ak6PQ2cotBd3OWhCXMZdhV1eqD8DGiMqmfEc2Nn3iccXbmq+Fn0tVxjCw2WybxmgrHy+Tu92T1fBub w1t0fA7VEapznxHASu41TQeGZssibPg== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=00ArG/n+ogebJZ98Hs9krO9Sm9WbyCdaXzr3l8a0bA0=; b=XwaUcWSY5osUxPN347agRuZIkiXl6AOhcuB5QEdKKky0Scx7TvwQCwjfSPUoiwlcOG35KrliH6BtV RRkcwRc2OvckP+ZAxMG7YRtnO1gUlNkBa6fBPod8WXEEvH9PqQwWoA524yKx/8+hn2b/58mqMpp2ik AD1EDLv8VWIgj7yanN/swwO0hTK5Zz7QP/AnBExFHtjBF53KmeCtLSUXpNBDWMnEKkby5e9wTItize 08FmLrvYiEz5MKA3R2ewNEFa08P23yOpeGnaWaiJxLrHYGOR7lvBhC2sGuugY3o1D7/+LIGdJqIV7C vP/doKVWeuWjexsf88Z1iqflNX5hxAA== X-MHO-RoutePath: aGlwcGll X-MHO-User: eb7ca132-645e-11e9-919f-112c64a8cf29 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id eb7ca132-645e-11e9-919f-112c64a8cf29; Sun, 21 Apr 2019 17:57:29 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x3LHvOaU061185; Sun, 21 Apr 2019 11:57:24 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: insanely-high interrupt rates -- PARTIAL resolution (Pi2) From: Ian Lepore To: Karl Denninger , Andrew Gierth Cc: "freebsd-arm@freebsd.org" , ticso@cicely.de Date: Sun, 21 Apr 2019 11:57:24 -0600 In-Reply-To: <67133e19-2be5-ccd1-2ded-008b36a866ec@denninger.net> References: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <20190319161423.GH57400@cicely7.cicely.de> <52df098fdc0caf5de1879c93239534fffbd49b56.camel@freebsd.org> <40f57de2-2b25-3981-a416-b9958cc97636@denninger.net> <669892ac3fc37b0843a156c0ab102316829103fd.camel@freebsd.org> <663f2566-b035-7011-70eb-4163b41e6e55@denninger.net> <20190325164827.GL57400@cicely7.cicely.de> <3db9cf8a-68ee-e339-67bf-760ee51464fd@denninger.net> <874l7fyrpr.fsf@news-spur.riddles.org.uk> <701e011f-3088-8ed4-4fbb-6fa93ac698f5@denninger.net> <67133e19-2be5-ccd1-2ded-008b36a866ec@denninger.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: F15F982111 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.985,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 17:57:40 -0000 On Wed, 2019-04-17 at 14:56 -0500, Karl Denninger wrote: > On 4/9/2019 19:25, Ian Lepore wrote: > > On Tue, 2019-04-09 at 09:55 -0500, Karl Denninger wrote: > > > On 4/3/2019 11:48, Andrew Gierth wrote: > > > > [...] > > > > I've just posted https://reviews.freebsd.org/D19871 for this. > > Hopefully I'll get it committed in a day or so and merged to 12- > > stable > > a few days after that. > > > > -- Ian > > I am running that now on a Pi2 and so far the load problem is gone > but > the spurious interrupt warnings are not.... > > [...] > > On my bench without the I2c inputs connected (which do analog reads) I > do NOT get the spurious interrupt prints. With it connected I do. The > process that reads them is code that is running in both cases, but if it > cannot find the I2c devices it logs the error but continues, so all it > gets to is trying to open the unit, doesn't see it when probed, and > gives up. > > It appears that I2c is an inherent part of the spurious interrupt thing > still and while the timer issue appears to be fixed that doesn't resolve > the other problem. > > Any ideas on how to track down exactly what is generating those warnings? > > After spending the whole day yesterday trying all the usual driver techniques for eliminating spurious interrupts, I was unable to make them go away completely, but I also convinced myself they're harmless. I was a little surprised that the "read after write" technique didn't work. That is, after writing to the i2c control register to clear all the interrupt-enable bits, read back that register. In theory, at least on normal arm chips, that ensures that the prior write has reached the hardware before the read can procede, so it's a way to guarantee that the write has taken effect and the interrupt can no longer be asserted, before returning from the interrupt handler. But, on the rpi chips even that doesn't work... you can read back the register and verify the interrupt-enable bits are cleared, and still after returning from the handler, it re-interrupts immediately. If you stick in a nice long DELAY() after clearing the control register, the spurious interrupts go away, but that's a horrible fix. It would be especially horrible for i2c devices that do a lot of transfers, you'd end up with the delay time overwhelming the time to do the actual transfers themselves. So, in r346489, I moved the reporting of the spurious transfers under the bootverbose flag, so that normally you just won't see them anymore, but we can still enable the reporting if we suspect some device driver is behaving badly. I'll mfc that change to 12-stable after a few days. -- Ian From owner-freebsd-arm@freebsd.org Sun Apr 21 17:59:54 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4494C1592EA8 for ; Sun, 21 Apr 2019 17:59:54 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [104.236.120.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A1A98219C; Sun, 21 Apr 2019 17:59:53 +0000 (UTC) (envelope-from karl@denninger.net) Received: from denninger.net (ip68-1-57-197.pn.at.cox.net [68.1.57.197]) by colo1.denninger.net (Postfix) with ESMTP id 4B02D21108A; Sun, 21 Apr 2019 13:59:16 -0400 (EDT) Received: from [192.168.10.17] (D7.Denninger.Net [192.168.10.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id ADB1DC8FD6; Sun, 21 Apr 2019 12:59:15 -0500 (CDT) Subject: Re: insanely-high interrupt rates -- PARTIAL resolution (Pi2) To: Ian Lepore , Andrew Gierth Cc: "freebsd-arm@freebsd.org" , ticso@cicely.de References: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <20190319161423.GH57400@cicely7.cicely.de> <52df098fdc0caf5de1879c93239534fffbd49b56.camel@freebsd.org> <40f57de2-2b25-3981-a416-b9958cc97636@denninger.net> <669892ac3fc37b0843a156c0ab102316829103fd.camel@freebsd.org> <663f2566-b035-7011-70eb-4163b41e6e55@denninger.net> <20190325164827.GL57400@cicely7.cicely.de> <3db9cf8a-68ee-e339-67bf-760ee51464fd@denninger.net> <874l7fyrpr.fsf@news-spur.riddles.org.uk> <701e011f-3088-8ed4-4fbb-6fa93ac698f5@denninger.net> <67133e19-2be5-ccd1-2ded-008b36a866ec@denninger.net> From: Karl Denninger Openpgp: preference=signencrypt Autocrypt: addr=karl@denninger.net; prefer-encrypt=mutual; keydata= mQINBFIX1zsBEADRcJfsQUl9oFeoMfLPJ1kql+3sIaYx0MfJAUhV9LnbWxr0fsWCskM1O4cV tHm5dqPkuPM4Ztc0jLotD1i9ubWvCHOlkLGxFOL+pFbjA+XZ7VKsC/xWmhMwJ3cM8HavK2OV SzEWQ/AEYtMi04IzGSwsxh/5/5R0mPHrsIomV5SbuiI0vjLuDj7fo6146AABI1ULzge4hBYW i/SHrqUrLORmUNBs6bxek79/B0Dzk5cIktD3LOfbT9EAa5J/osVkstMBhToJgQttaMIGv8SG CzpR/HwEokE+7DP+k2mLHnLj6H3kfugOF9pJH8Za4yFmw//s9cPXV8WwtZ2SKfVzn1unpKqf wmJ1PwJoom/d4fGvQDkgkGKRa6RGC6tPmXnqnx+YX4iCOdFfbP8L9rmk2sewDDVzHDU3I3ZZ 8hFIjMYM/QXXYszRatK0LCV0QPZuF7LCf4uQVKw1/oyJInsnH7+6a3c0h21x+CmSja9QJ+y0 yzgEN/nM89d6YTakfR+1xkYgodVmMy/bS8kmXbUUZG/CyeqCqc95RUySjKT2ECrf9GhhoQkl +D8n2MsrAUSMGB4GQSN+TIq9OBTpNuvATGSRuF9wnQcs1iSry+JNCpfRTyWp83uCNApe6oHU EET4Et6KDO3AvjvBMAX0TInTRGW2SQlJMuFKpc7Dg7tHK8zzqQARAQABtCNLYXJsIERlbm5p bmdlciA8a2FybEBkZW5uaW5nZXIubmV0PokCPAQTAQIAJgUCUhfXOwIbIwUJCWYBgAYLCQgH AwIEFQIIAwQWAgMBAh4BAheAAAoJEG6/sivc5s0PLxQP/i6x/QFx9G4Cw7C+LthhLXIm7NSH AtNbz2UjySEx2qkoQQjtsK6mcpEEaky4ky6t8gz0/SifIfJmSmyAx0UhUQ0WBv1vAXwtNrQQ jJd9Bj6l4c2083WaXyHPjt2u2Na6YFowyb4SaQb83hu/Zs25vkPQYJVVE0JX409MFVPUa6E3 zFbd1OTr3T4yNUy4gNeQZfzDqDS8slbIks2sXeoJrZ6qqXVI0ionoivOlaN4T6Q0UYyXtigj dQvvhMt0aNowKFjRqrmSDRpdz+o6yg7Mp7qEZ1V6EZk8KqQTH6htpCTQ8i79ttK4LG6bstSF Re6Fwq52nbrcANrcdmtZXqjo+SGbUqJ8b1ggrxAsJ5MEhRh2peKrCgI/TjQo+ZxfnqEoR4AI 46Cyiz+/lcVvlvmf2iPifS3EEdaH3Itfwt7MxFm6mQORYs6skHDw3tOYB2/AdCW6eRVYs2hB RMAG4uwApZfZDKgRoE95PJmQjeTBiGmRPcsQZtNESe7I7EjHtCDLwtJqvD4HkDDQwpzreT6W XkyIJ7ns7zDfA1E+AQhFR6rsTFGgQZRZKsVeov3SbhYKkCnVDCvb/PKQCAGkSZM9SvYG5Yax 8CMry3AefKktf9fqBFg8pWqtVxDwJr56dhi0GHXRu3jVI995rMGo1fLUG5fSxiZ8L5sAtokh 9WFmQpyl Message-ID: <79f1cd3a-e7e9-de26-d728-0d463f1f4291@denninger.net> Date: Sun, 21 Apr 2019 12:59:16 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms070307020606090102050106" X-Rspamd-Queue-Id: 4A1A98219C X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.54 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; HAS_ATTACHMENT(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[px.denninger.net]; NEURAL_HAM_SHORT(-0.86)[-0.856,0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-2.48)[ip: (-9.88), ipnet: 104.236.64.0/18(-4.02), asn: 14061(1.59), country: US(-0.06)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:14061, ipnet:104.236.64.0/18, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[197.57.1.68.zen.spamhaus.org : 127.0.0.11]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; SIGNED_SMIME(-2.00)[]; RCPT_COUNT_THREE(0.00)[4]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; DMARC_NA(0.00)[denninger.net]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[] X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 17:59:54 -0000 This is a cryptographically signed message in MIME format. --------------ms070307020606090102050106 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 4/21/2019 12:57, Ian Lepore wrote: > On Wed, 2019-04-17 at 14:56 -0500, Karl Denninger wrote: >> On 4/9/2019 19:25, Ian Lepore wrote: >>> On Tue, 2019-04-09 at 09:55 -0500, Karl Denninger wrote: >>>> On 4/3/2019 11:48, Andrew Gierth wrote: >>>>> [...] >>> I've just posted https://reviews.freebsd.org/D19871 for this.=20 >>> Hopefully I'll get it committed in a day or so and merged to 12- >>> stable >>> a few days after that. >>> >>> -- Ian >> I am running that now on a Pi2 and so far the load problem is gone >> but >> the spurious interrupt warnings are not.... >> >> > [...] >> On my bench without the I2c inputs connected (which do analog reads) I= >> do NOT get the spurious interrupt prints. With it connected I do. Th= e >> process that reads them is code that is running in both cases, but if = it >> cannot find the I2c devices it logs the error but continues, so all it= >> gets to is trying to open the unit, doesn't see it when probed, and >> gives up. >> >> It appears that I2c is an inherent part of the spurious interrupt thin= g >> still and while the timer issue appears to be fixed that doesn't resol= ve >> the other problem. >> >> Any ideas on how to track down exactly what is generating those warnin= gs? >> >> > After spending the whole day yesterday trying all the usual driver > techniques for eliminating spurious interrupts, I was unable to make > them go away completely, but I also convinced myself they're harmless. > > I was a little surprised that the "read after write" technique didn't > work. That is, after writing to the i2c control register to clear all > the interrupt-enable bits, read back that register. In theory, at > least on normal arm chips, that ensures that the prior write has > reached the hardware before the read can procede, so it's a way to > guarantee that the write has taken effect and the interrupt can no > longer be asserted, before returning from the interrupt handler. But, > on the rpi chips even that doesn't work... you can read back the > register and verify the interrupt-enable bits are cleared, and still > after returning from the handler, it re-interrupts immediately. > > If you stick in a nice long DELAY() after clearing the control > register, the spurious interrupts go away, but that's a horrible fix.=20 > It would be especially horrible for i2c devices that do a lot of > transfers, you'd end up with the delay time overwhelming the time to do= > the actual transfers themselves. > > So, in r346489, I moved the reporting of the spurious transfers under > the bootverbose flag, so that normally you just won't see them anymore,= > but we can still enable the reporting if we suspect some device driver > is behaving badly. I'll mfc that change to 12-stable after a few days.= > > -- Ian Thanks... --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms070307020606090102050106 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC DdgwggagMIIEiKADAgECAhMA5EiKghDOXrvfxYxjITXYDdhIMA0GCSqGSIb3DQEBCwUAMIGL MQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJTmljZXZpbGxlMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExITAf BgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQTAeFw0xNzA4MTcxNjQyMTdaFw0yNzA4 MTUxNjQyMTdaMHsxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkwFwYDVQQKDBBD dWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExJTAjBgNVBAMMHEN1 ZGEgU3lzdGVtcyBMTEMgMjAxNyBJbnQgQ0EwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIK AoICAQC1aJotNUI+W4jP7xQDO8L/b4XiF4Rss9O0B+3vMH7Njk85fZ052QhZpMVlpaaO+sCI KqG3oNEbuOHzJB/NDJFnqh7ijBwhdWutdsq23Ux6TvxgakyMPpT6TRNEJzcBVQA0kpby1DVD 0EKSK/FrWWBiFmSxg7qUfmIq/mMzgE6epHktyRM3OGq3dbRdOUgfumWrqHXOrdJz06xE9NzY vc9toqZnd79FUtE/nSZVm1VS3Grq7RKV65onvX3QOW4W1ldEHwggaZxgWGNiR/D4eosAGFxn uYeWlKEC70c99Mp1giWux+7ur6hc2E+AaTGh+fGeijO5q40OGd+dNMgK8Es0nDRw81lRcl24 SWUEky9y8DArgIFlRd6d3ZYwgc1DMTWkTavx3ZpASp5TWih6yI8ACwboTvlUYeooMsPtNa9E 6UQ1nt7VEi5syjxnDltbEFoLYcXBcqhRhFETJe9CdenItAHAtOya3w5+fmC2j/xJz29og1KH YqWHlo3Kswi9G77an+zh6nWkMuHs+03DU8DaOEWzZEav3lVD4u76bKRDTbhh0bMAk4eXriGL h4MUoX3Imfcr6JoyheVrAdHDL/BixbMH1UUspeRuqQMQ5b2T6pabXP0oOB4FqldWiDgJBGRd zWLgCYG8wPGJGYgHibl5rFiI5Ix3FQncipc6SdUzOQIDAQABo4IBCjCCAQYwHQYDVR0OBBYE FF3AXsKnjdPND5+bxVECGKtc047PMIHABgNVHSMEgbgwgbWAFBu1oRhUMNEzjODolDka5k4Q EDBioYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJ TmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5 c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYIJAKxAy1WBo2kY MBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4IC AQCB5686UCBVIT52jO3sz9pKuhxuC2npi8ZvoBwt/IH9piPA15/CGF1XeXUdu2qmhOjHkVLN gO7XB1G8CuluxofOIUce0aZGyB+vZ1ylHXlMeB0R82f5dz3/T7RQso55Y2Vog2Zb7PYTC5B9 oNy3ylsnNLzanYlcW3AAfzZcbxYuAdnuq0Im3EpGm8DoItUcf1pDezugKm/yKtNtY6sDyENj tExZ377cYA3IdIwqn1Mh4OAT/Rmh8au2rZAo0+bMYBy9C11Ex0hQ8zWcvPZBDn4v4RtO8g+K uQZQcJnO09LJNtw94W3d2mj4a7XrsKMnZKvm6W9BJIQ4Nmht4wXAtPQ1xA+QpxPTmsGAU0Cv HmqVC7XC3qxFhaOrD2dsvOAK6Sn3MEpH/YrfYCX7a7cz5zW3DsJQ6o3pYfnnQz+hnwLlz4MK 17NIA0WOdAF9IbtQqarf44+PEyUbKtz1r0KGeGLs+VGdd2FLA0e7yuzxJDYcaBTVwqaHhU2/ Fna/jGU7BhrKHtJbb/XlLeFJ24yvuiYKpYWQSSyZu1R/gvZjHeGb344jGBsZdCDrdxtQQcVA 6OxsMAPSUPMrlg9LWELEEYnVulQJerWxpUecGH92O06wwmPgykkz//UmmgjVSh7ErNvL0lUY UMfunYVO/O5hwhW+P4gviCXzBFeTtDZH259O7TCCBzAwggUYoAMCAQICEwCg0WvVwekjGFiO 62SckFwepz0wDQYJKoZIhvcNAQELBQAwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3Jp ZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBD QTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExMQyAyMDE3IEludCBDQTAeFw0xNzA4MTcyMTIx MjBaFw0yMjA4MTYyMTIxMjBaMFcxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRswGQYDVQQDDBJrYXJsQGRlbm5pbmdlci5uZXQw ggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC+HVSyxVtJhy3Ohs+PAGRuO//Dha9A 16l5FPATr6wude9zjX5f2lrkRyU8vhCXTZW7WbvWZKpcZ8r0dtZmiK9uF58Ec6hhvfkxJzbg 96WHBw5Fumd5ahZzuCJDtCAWW8R7/KN+zwzQf1+B3MVLmbaXAFBuKzySKhKMcHbK3/wjUYTg y+3UK6v2SBrowvkUBC+jxNg3Wy12GsTXcUS/8FYIXgVVPgfZZrbJJb5HWOQpvvhILpPCD3xs YJFNKEPltXKWHT7Qtc2HNqikgNwj8oqOb+PeZGMiWapsatKm8mxuOOGOEBhAoTVTwUHlMNTg 6QUCJtuWFCK38qOCyk9Haj+86lUU8RG6FkRXWgMbNQm1mWREQhw3axgGLSntjjnznJr5vsvX SYR6c+XKLd5KQZcS6LL8FHYNjqVKHBYM+hDnrTZMqa20JLAF1YagutDiMRURU23iWS7bA9tM cXcqkclTSDtFtxahRifXRI7Epq2GSKuEXe/1Tfb5CE8QsbCpGsfSwv2tZ/SpqVG08MdRiXxN 5tmZiQWo15IyWoeKOXl/hKxA9KPuDHngXX022b1ly+5ZOZbxBAZZMod4y4b4FiRUhRI97r9l CxsP/EPHuuTIZ82BYhrhbtab8HuRo2ofne2TfAWY2BlA7ExM8XShMd9bRPZrNTokPQPUCWCg CdIATQIDAQABo4IBzzCCAcswPAYIKwYBBQUHAQEEMDAuMCwGCCsGAQUFBzABhiBodHRwOi8v b2NzcC5jdWRhc3lzdGVtcy5uZXQ6ODg4ODAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIF oDAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMDMGCWCG SAGG+EIBDQQmFiRPcGVuU1NMIEdlbmVyYXRlZCBDbGllbnQgQ2VydGlmaWNhdGUwHQYDVR0O BBYEFLElmNWeVgsBPe7O8NiBzjvjYnpRMIHKBgNVHSMEgcIwgb+AFF3AXsKnjdPND5+bxVEC GKtc047PoYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UE BwwJTmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRh IFN5c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYITAORIioIQ zl6738WMYyE12A3YSDAdBgNVHREEFjAUgRJrYXJsQGRlbm5pbmdlci5uZXQwDQYJKoZIhvcN AQELBQADggIBAJXboPFBMLMtaiUt4KEtJCXlHO/3ZzIUIw/eobWFMdhe7M4+0u3te0sr77QR dcPKR0UeHffvpth2Mb3h28WfN0FmJmLwJk+pOx4u6uO3O0E1jNXoKh8fVcL4KU79oEQyYkbu 2HwbXBU9HbldPOOZDnPLi0whi/sbFHdyd4/w/NmnPgzAsQNZ2BYT9uBNr+jZw4SsluQzXG1X lFL/qCBoi1N2mqKPIepfGYF6drbr1RnXEJJsuD+NILLooTNf7PMgHPZ4VSWQXLNeFfygoOOK FiO0qfxPKpDMA+FHa8yNjAJZAgdJX5Mm1kbqipvb+r/H1UAmrzGMbhmf1gConsT5f8KU4n3Q IM2sOpTQe7BoVKlQM/fpQi6aBzu67M1iF1WtODpa5QUPvj1etaK+R3eYBzi4DIbCIWst8MdA 1+fEeKJFvMEZQONpkCwrJ+tJEuGQmjoQZgK1HeloepF0WDcviiho5FlgtAij+iBPtwMuuLiL shAXA5afMX1hYM4l11JXntle12EQFP1r6wOUkpOdxceCcMVDEJBBCHW2ZmdEaXgAm1VU+fnQ qS/wNw/S0X3RJT1qjr5uVlp2Y0auG/eG0jy6TT0KzTJeR9tLSDXprYkN2l/Qf7/nT6Q03qyE QnnKiBXWAZXveafyU/zYa7t3PTWFQGgWoC4w6XqgPo4KV44OMYIFBzCCBQMCAQEwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBglghkgBZQMEAgMFAKCCAkUw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTkwNDIxMTc1OTE2 WjBPBgkqhkiG9w0BCQQxQgRAIH1IJpatruTkBgiGdmAqGr1mYNjelI8X7YVx7u1n3TvCuSY/ yrodPhxgj7690SJoNAV4RQrpftRTd7/LhLlUszBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFl AwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3 DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGjBgkrBgEEAYI3EAQxgZUwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTCBpQYLKoZIhvcNAQkQAgsxgZWg gZIwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lz dGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0 ZW1zIExMQyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBgkqhkiG9w0BAQEF AASCAgAQ2TrHAAkFEBrSdGaTRQWEzIFFnHnQcoewDXOGbZ7K/LWemb0iGdlWSpdp++t9K2Qd HPMS9t5RQCAPdTmSO46VhT9ZjLNIMuKLZlGnfDAUGir4tEDIJtLOgFtux8hznZdY+HMofvqc Wl/vyLDv/dFeKsHyQE8JSbzAvSou4mCnAJqKJBcWUB4WRxJIDvrXoNtEr9WBQ6VQ6Gvexjj0 SJiRFBKj1vQTMeQgtg5k3iywobiP/wY+kECkNXW00sIGdKm7PXJ2Yidn1Bnhz/Zr/cZWsJz1 pp3qs86O5m6ucNL3Ba9JAPjGcXdmCyeoHc+fdQq2Cj69/r2ys+Pvu24+aR576DWLyhaZzfDo 3G1BZtUq/RHIBNcA4ZiDHUTKyA65DXnXh7bTyaxcNYLKH+QYyuRZAOkGnCg7I28u35MG4gON FdgaoxEP5PowWl6F6lrN8gY8E0wR54mU2tRgI8BK04JnyIsPDXtPLz5UxuHNuOIxwOpMVSdx i0350N0LqLVWS09qrliVKssfdDHeYs+njS5CAZqXSxr5R1oL0C0yi6+bGFeqAaxVNHlSx3i5 0VJ6VjVTyiOfj2ADzkvXlvZbkhAoVw5i+SOYr/3QzlDlJeC52FQyF1Ss+3vL+TXu/M9nFfk9 dTmAX9RuSKiCIu5fwEWEfN6fUfS2IUWG2xuZ7gszzQAAAAAAAA== --------------ms070307020606090102050106-- From owner-freebsd-arm@freebsd.org Sun Apr 21 18:00:36 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F0721592EFB for ; Sun, 21 Apr 2019 18:00:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 DC63382206 for ; Sun, 21 Apr 2019 18:00:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x834.google.com with SMTP id w5so10062371qtb.11 for ; Sun, 21 Apr 2019 11:00:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uDCfxXewKkynAhpXvad5dwuSja57wO6Slnux/EDz59k=; b=rBm/R5EoF1h7O14jNvctCbzV1GQOuVrwam4oVKA+AbE4Q0ZmyHn5FCVwHOBX/0QTDp tHBaD+XqtS6mlmiQw6wOwrqVlpeauIOTdX47+Ra5cXpWWAuSK9QjCPwADobYKq+4fHLc m4v7/TO5bRGqTogNdpTUYExgDLE8jafV1IMAxLw18GWWlbGQfcgT1DI8e0RdVtb8n1F4 yUeMaEmtGGtagJE1rlNlFBl5xzrA8agcc8jzKIcZSL/LAVVKzioIP0yHI6AGxe/AtXPB +o1iXtD1NsqBfjtJLezji1kUjxe75jYVquXyf0caL863aHMRcAPl1vduuOrHuYMZGjyO D31w== 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=uDCfxXewKkynAhpXvad5dwuSja57wO6Slnux/EDz59k=; b=PlaUdr1zemmE45BgFYzv5wLmSf1cOQ2+jobjURiHybPEgSBQz75dPvl8y/6fM7zNDF W77unijX7+PFxVPa+WEsRBR1Lc8uY/Fpmxa31U8PYaNprBVpV+xCSy//yye6Q5hQIL8W SDulq0Yc6vAFkgqiuV4hLe83BMaTRdlu209Z6H4A8pJM1n09hndfnrUG7FdYoy5kM+QN hsH2WvSQ8+Mv7yRfHpnqxPYFTqKg2xrPw5xwiamEceiQR6eqqTXn+a+YbZHjcl8KZWUT JndvylC/9iPxazK73bw/7qQ0njp165Up8tgk2O23hf8neq8o+IQ3sYtyU900Sxkisvr0 SVyQ== X-Gm-Message-State: APjAAAVGNERLnLfoCkv8m4oFbq2Xo2DLrtdIZwuYR7c26/YPi9SZ8ZHb T402nsKnCn1V06615UAPue+Jlxo7mVVFpvd3lEVEnLJI X-Google-Smtp-Source: APXvYqzIqNGH8n214J/+IVkv5acuYbCthG1KLLJAAX7Vr09hmRcrK/MNFtOmSNc3FchmvQkUIXpwfh413g4RPnw/qUQ= X-Received: by 2002:a0c:ae50:: with SMTP id z16mr12162370qvc.153.1555869634051; Sun, 21 Apr 2019 11:00:34 -0700 (PDT) MIME-Version: 1.0 References: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <20190319161423.GH57400@cicely7.cicely.de> <52df098fdc0caf5de1879c93239534fffbd49b56.camel@freebsd.org> <40f57de2-2b25-3981-a416-b9958cc97636@denninger.net> <669892ac3fc37b0843a156c0ab102316829103fd.camel@freebsd.org> <663f2566-b035-7011-70eb-4163b41e6e55@denninger.net> <20190325164827.GL57400@cicely7.cicely.de> <3db9cf8a-68ee-e339-67bf-760ee51464fd@denninger.net> <874l7fyrpr.fsf@news-spur.riddles.org.uk> <701e011f-3088-8ed4-4fbb-6fa93ac698f5@denninger.net> <67133e19-2be5-ccd1-2ded-008b36a866ec@denninger.net> In-Reply-To: From: Warner Losh Date: Sun, 21 Apr 2019 12:00:23 -0600 Message-ID: Subject: Re: insanely-high interrupt rates -- PARTIAL resolution (Pi2) To: Ian Lepore Cc: Karl Denninger , Andrew Gierth , "freebsd-arm@freebsd.org" , ticso@cicely.de X-Rspamd-Queue-Id: DC63382206 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=rBm/R5Eo X-Spamd-Result: default: False [-5.86 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[4.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.92)[-0.922,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-2.93)[ip: (-9.18), ipnet: 2607:f8b0::/32(-3.13), asn: 15169(-2.26), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 18:00:36 -0000 On Sun, Apr 21, 2019 at 11:58 AM Ian Lepore wrote: > On Wed, 2019-04-17 at 14:56 -0500, Karl Denninger wrote: > > On 4/9/2019 19:25, Ian Lepore wrote: > > > On Tue, 2019-04-09 at 09:55 -0500, Karl Denninger wrote: > > > > On 4/3/2019 11:48, Andrew Gierth wrote: > > > > > [...] > > > > > > I've just posted https://reviews.freebsd.org/D19871 for this. > > > Hopefully I'll get it committed in a day or so and merged to 12- > > > stable > > > a few days after that. > > > > > > -- Ian > > > > I am running that now on a Pi2 and so far the load problem is gone > > but > > the spurious interrupt warnings are not.... > > > > > [...] > > > > On my bench without the I2c inputs connected (which do analog reads) I > > do NOT get the spurious interrupt prints. With it connected I do. The > > process that reads them is code that is running in both cases, but if it > > cannot find the I2c devices it logs the error but continues, so all it > > gets to is trying to open the unit, doesn't see it when probed, and > > gives up. > > > > It appears that I2c is an inherent part of the spurious interrupt thing > > still and while the timer issue appears to be fixed that doesn't resolve > > the other problem. > > > > Any ideas on how to track down exactly what is generating those warnings? > > > > > > After spending the whole day yesterday trying all the usual driver > techniques for eliminating spurious interrupts, I was unable to make > them go away completely, but I also convinced myself they're harmless. > > I was a little surprised that the "read after write" technique didn't > work. That is, after writing to the i2c control register to clear all > the interrupt-enable bits, read back that register. In theory, at > least on normal arm chips, that ensures that the prior write has > reached the hardware before the read can procede, so it's a way to > guarantee that the write has taken effect and the interrupt can no > longer be asserted, before returning from the interrupt handler. But, > on the rpi chips even that doesn't work... you can read back the > register and verify the interrupt-enable bits are cleared, and still > after returning from the handler, it re-interrupts immediately. > > If you stick in a nice long DELAY() after clearing the control > register, the spurious interrupts go away, but that's a horrible fix. > It would be especially horrible for i2c devices that do a lot of > transfers, you'd end up with the delay time overwhelming the time to do > the actual transfers themselves. > > So, in r346489, I moved the reporting of the spurious transfers under > the bootverbose flag, so that normally you just won't see them anymore, > but we can still enable the reporting if we suspect some device driver > is behaving badly. I'll mfc that change to 12-stable after a few days. > vmstat -i will also show if you're system has an unusually high interrupt rate in general as well, and is preferable to spamming the console with printfs :) Warner From owner-freebsd-arm@freebsd.org Sun Apr 21 18:05:29 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BC3215801C7 for ; Sun, 21 Apr 2019 18:05:29 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9774782692 for ; Sun, 21 Apr 2019 18:05:28 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1555869920; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=NXI68mORWXem7iIkOyzTKlUKnfdv6B0LadE/k3TLNH5E45OSlTrCIT8s5W9xhHqoRGqFKs1HYsgZ1 DuuGT+8JmjxSnZIXpb3gbMsBR1UidLW0vDSXwokk00I7+NP8uUZsw7NeO5sN9QTDZT01VZXfnV6VK7 S3hYQpH7KPnWyLkB8DmKGzuhHALSVSTNBaP6AnVO36nxO/ys/nuJLlcdOD+e3V7byeMcHaaHjqijcs vAvrVVYkhPY4uwdx/w5N1ujB9tpmGlkDcUEj3yJwUhrKY1DPi7pRxeBmMQKw9N6gwXSzKujNb6l+xH 6o3KZAvaISu6PgZYwLSzg+jcFH5XbtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=rA4Eq1tLPF0K70gt0Aw2zjvsRJMrnARA0h5c6Tb2ezs=; b=NYxXhtzsfqQNTWrDfMFwh4KaPVIY+cpFuJNVVjNDioK7oXj4XErP5f6y+UQgFREufLju4rLtmRaG4 rmMj8hK+Okdh9O6kt4tcrnKv53nWhii7Jf0HkIgEShNkm9vrY/6ABGixkYRP4QpKKC/WupzkiocHe8 X/WnZGH25D8KvFmouI+Y64/T30qgYFZ0a6+c2Y9SVS3VCbetEDRXhK6RF1UnDx+xgeOyySWjwlA2Wl WzrQNyjE4axJVcIXqu8P0AdzNpRJCogk29BQYMDCehDeswbUInPZoJVflozptUtiCiDXseqoLL74sQ +LQrEwcz7zmDYFB7J4J+tfIjVG7HpXw== ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=rA4Eq1tLPF0K70gt0Aw2zjvsRJMrnARA0h5c6Tb2ezs=; b=M3t2kVXxLC0Z0JEZUyGMkiYm4G/EFqJy2c7OsI2e2+4XB6uwYbREFSq5958rtKQAv4hYL+T1mEeTu IDY6hNV21EDrD+5NrrQdWxFlhjY37DwLQUFYvGMmFY8kPq5o0IXpFuG5y3Gm3TMI68oz8kfJyzwOWk RLvOKaO3fZcdCoy1JPBqsGeF7zocmGWOC4gqrFpJLRvcKD1L2V6Dd+hFGxeVsDqV/Cafggc6Nkwkls Cz5SFKMQ9sGjEwm6lsY0rioi3Q+AgNsOyI70OE2CZk2dIK1zDgslCP5SLa/5fFQqtfCri9xu6zOW9F KMJYNxXSyr+S+NZwCfkB/lMhejigZ5w== X-MHO-RoutePath: aGlwcGll X-MHO-User: 02387791-6460-11e9-803b-31925da7267c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id 02387791-6460-11e9-803b-31925da7267c; Sun, 21 Apr 2019 18:05:15 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x3LI5Caw061231; Sun, 21 Apr 2019 12:05:12 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <26962ee10cf8c61416dde40d5e8c0c24400316f9.camel@freebsd.org> Subject: Re: insanely-high interrupt rates -- PARTIAL resolution (Pi2) From: Ian Lepore To: Warner Losh Cc: Karl Denninger , Andrew Gierth , "freebsd-arm@freebsd.org" , ticso@cicely.de Date: Sun, 21 Apr 2019 12:05:12 -0600 In-Reply-To: References: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <20190319161423.GH57400@cicely7.cicely.de> <52df098fdc0caf5de1879c93239534fffbd49b56.camel@freebsd.org> <40f57de2-2b25-3981-a416-b9958cc97636@denninger.net> <669892ac3fc37b0843a156c0ab102316829103fd.camel@freebsd.org> <663f2566-b035-7011-70eb-4163b41e6e55@denninger.net> <20190325164827.GL57400@cicely7.cicely.de> <3db9cf8a-68ee-e339-67bf-760ee51464fd@denninger.net> <874l7fyrpr.fsf@news-spur.riddles.org.uk> <701e011f-3088-8ed4-4fbb-6fa93ac698f5@denninger.net> <67133e19-2be5-ccd1-2ded-008b36a866ec@denninger.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 9774782692 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; ASN(0.00)[asn:16509, ipnet:52.58.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 18:05:29 -0000 On Sun, 2019-04-21 at 12:00 -0600, Warner Losh wrote: > On Sun, Apr 21, 2019 at 11:58 AM Ian Lepore wrote: > > > On Wed, 2019-04-17 at 14:56 -0500, Karl Denninger wrote: > > > On 4/9/2019 19:25, Ian Lepore wrote: > > > > On Tue, 2019-04-09 at 09:55 -0500, Karl Denninger wrote: > > > > > On 4/3/2019 11:48, Andrew Gierth wrote: > > > > > > [...] > > > > > > > > I've just posted https://reviews.freebsd.org/D19871 for this. > > > > Hopefully I'll get it committed in a day or so and merged to > > > > 12- > > > > stable > > > > a few days after that. > > > > > > > > -- Ian > > > > > > I am running that now on a Pi2 and so far the load problem is > > > gone > > > but > > > the spurious interrupt warnings are not.... > > > > > > > > > > [...] > > > > > > On my bench without the I2c inputs connected (which do analog > > > reads) I > > > do NOT get the spurious interrupt prints. With it connected I > > > do. The > > > process that reads them is code that is running in both cases, > > > but if it > > > cannot find the I2c devices it logs the error but continues, so > > > all it > > > gets to is trying to open the unit, doesn't see it when probed, > > > and > > > gives up. > > > > > > It appears that I2c is an inherent part of the spurious interrupt > > > thing > > > still and while the timer issue appears to be fixed that doesn't > > > resolve > > > the other problem. > > > > > > Any ideas on how to track down exactly what is generating those > > > warnings? > > > > > > > > > > After spending the whole day yesterday trying all the usual driver > > techniques for eliminating spurious interrupts, I was unable to > > make > > them go away completely, but I also convinced myself they're > > harmless. > > > > I was a little surprised that the "read after write" technique > > didn't > > work. That is, after writing to the i2c control register to clear > > all > > the interrupt-enable bits, read back that register. In theory, at > > least on normal arm chips, that ensures that the prior write has > > reached the hardware before the read can procede, so it's a way to > > guarantee that the write has taken effect and the interrupt can no > > longer be asserted, before returning from the interrupt > > handler. But, > > on the rpi chips even that doesn't work... you can read back the > > register and verify the interrupt-enable bits are cleared, and > > still > > after returning from the handler, it re-interrupts immediately. > > > > If you stick in a nice long DELAY() after clearing the control > > register, the spurious interrupts go away, but that's a horrible > > fix. > > It would be especially horrible for i2c devices that do a lot of > > transfers, you'd end up with the delay time overwhelming the time > > to do > > the actual transfers themselves. > > > > So, in r346489, I moved the reporting of the spurious transfers > > under > > the bootverbose flag, so that normally you just won't see them > > anymore, > > but we can still enable the reporting if we suspect some device > > driver > > is behaving badly. I'll mfc that change to 12-stable after a few > > days. > > > > vmstat -i will also show if you're system has an unusually high interrupt > rate in general as well, and is preferable to spamming the console with > printfs :) > > Warner vmstat doesn't report spurious interrupts in any way, though. I considered making it do so as one of the possible fixes here, but it turns out to be complicated... we need to do a bit of reworking of the INTRNG code as it related to interrupt counts. For example, on x86 you get this from vmstat -i: cpu0:timer 42006521 80 cpu1:timer 32510560 62 But on arm, all timer interrupts are counted as belonging to the generic_timer0 device. When I tried to figure out how to split that into per-cpu reporting like x86 does, I discovered what a mess the intrstats stuff in INTRNG is right now. So, a project for another day, I guess. -- Ian From owner-freebsd-arm@freebsd.org Mon Apr 22 09:17:13 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1139315943DE for ; Mon, 22 Apr 2019 09:17:13 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 27B83820D4 for ; Mon, 22 Apr 2019 09:17:12 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x52a.google.com with SMTP id d46so8985243eda.7 for ; Mon, 22 Apr 2019 02:17:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=M6TtD486tUk0Ipwb9hTbh+CJaWaoMLQrlG5vqJWw050=; b=mLeX61IIw1WXZJUfciG+7xJ2jtuwkmI/zQ1OsthFiEDm96vunY5XpPYlaVwXl6uDos ubJQv99qqzjmjlUNx0RvZ+ubRAKsZqlriIr8pqAMPkKhxEspb8m4BgWYMMMjA3fWdvRL gGVTi7FrrK07ZxSfkEo6auL2ErgivU2+ZwpIhKOdlM1Cow2frvx2sEI2N+c0wsPJlQvl nhaFpl7FH+uprC27ouBPh1HNU9lJssjtRMJIQnbOsZyEcfDNZOLjWkOIqpynuzdOwXXn OMs35UFNQh/Cu8UmqVogPpBnjgqU1K1gK4ibr/GCJThaT3TatD2wr3BFA5lW0H3EGeIg 1GoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=M6TtD486tUk0Ipwb9hTbh+CJaWaoMLQrlG5vqJWw050=; b=b+FUa/tdY43ME4tKjyBLi8c1zk8ZaN9Pe9tgyIURWabPRfREIlUdh6PcI/Sl4lEufq CdJxG7IDJLrula7WPZFVM1i/laAFShe+GqmFKke08Ec9d4RkQ7lfrjYL3GXfwwprU5/f H32YuZ0CLIw98b37+QRqOmIG3SCn0e+DDAyy9H/ca4p5uw2Rdsc/r8ZCsoYSMFdO37ae 9OWWiAFL9CIjzczl8j/oC/4UMhbDMZ7Sqnl8yUEyas19mIXbB8/HJS+KiLgZWyx3MG5l 8Cjv12sowUVREYXRxfcJFptzBIlawMBWgky7iJXDSLsmT1A0E/57TEyKeygH7xyzwBgR Wrqg== X-Gm-Message-State: APjAAAV15vBeBuwy9TvnrdfSEH8Ehwjy1QfOOL8kD3TSt6yZ/16ol2Si kWJGMemhUJHy3JxjmD8HXgOQt80EFYSCTedQNBVgnNvK X-Google-Smtp-Source: APXvYqyVVpxDdoJTFJdf4FKCtZGnNBafyZJTMZAN4c8wk/CDTCx3bkSipxs2dSRGetxj8PCCDkJAStLtdu4w5p19xP4= X-Received: by 2002:a17:906:4d8b:: with SMTP id s11mr8763103eju.31.1555924629999; Mon, 22 Apr 2019 02:17:09 -0700 (PDT) MIME-Version: 1.0 From: Balanga Bar Date: Mon, 22 Apr 2019 11:16:40 +0100 Message-ID: Subject: Installing pkgs on armv5 To: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 27B83820D4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=mLeX61II; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-6.65 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.87)[-0.869,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.77)[ip: (-9.15), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.26), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[a.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2019 09:17:13 -0000 Has anyone got any tips on how to install pkgs on armv5? I've managed to install FreeBSD 11.0-RELEASE on a GoFlex Home but am unable to install pkg. From owner-freebsd-arm@freebsd.org Mon Apr 22 12:01:49 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BC2C1598114 for ; Mon, 22 Apr 2019 12:01:49 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1373587826 for ; Mon, 22 Apr 2019 12:01:46 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1hIXdi-0008QD-4G; Mon, 22 Apr 2019 14:01:38 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org, "Balanga Bar" Subject: Re: Installing pkgs on armv5 References: Date: Mon, 22 Apr 2019 14:01:34 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.2 X-Scan-Signature: 4052b6d1c9976086d5ab5ce040fcf5b8 X-Rspamd-Queue-Id: 1373587826 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 195.190.28.88 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-3.05 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.190.28.64/27]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[klop.ws]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[mx2.greenhost.nl,mx1.greenhost.nl]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.64)[-0.640,0]; IP_SCORE(-0.60)[ip: (-2.03), ipnet: 195.190.28.0/24(-0.56), asn: 47172(-0.43), country: NL(0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:47172, ipnet:195.190.28.0/24, country:NL]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2019 12:01:49 -0000 On Mon, 22 Apr 2019 12:16:40 +0200, Balanga Bar wrote: > Has anyone got any tips on how to install pkgs on armv5? > > I've managed to install FreeBSD 11.0-RELEASE on a GoFlex Home but am > unable > to install pkg. There are no official pre-build pkgs for armv5. See https://pkg.freebsd.org/. I'm not aware of an unofficial repo of pkgs. You can use the ports and build pkgs yourself. https://www.freebsd.org/ports/ https://www.freebsd.org/doc/handbook/ports.html https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html I use https://www.freshports.org/ports-mgmt/portmaster on my armv5, but your milage may vary. It might be possible to cross-compile pkgs on another faster (amd64) computer. But I have never done that, so can't give any advise. Regards, Ronald. From owner-freebsd-arm@freebsd.org Mon Apr 22 12:12:06 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 273EA1598813 for ; Mon, 22 Apr 2019 12:12:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB18F87FC0 for ; Mon, 22 Apr 2019 12:12:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1FD431F0F3 for ; Mon, 22 Apr 2019 12:12:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3MCC47C070363 for ; Mon, 22 Apr 2019 12:12:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3MCC4Yt070351 for freebsd-arm@FreeBSD.org; Mon, 22 Apr 2019 12:12:04 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 237466] remove fslsdma device from arm GENERIC file Date: Mon, 22 Apr 2019 12:12:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: sanpei@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2019 12:12:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237466 Bug ID: 237466 Summary: remove fslsdma device from arm GENERIC file Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: sanpei@FreeBSD.org arm=E3=81=AEGENERIC kernel=E3=81=AB=E3=81=82=E3=82=8B=E3=80=81driver fslsdm= a=E3=81=A7=E3=81=99=E3=81=8C=E3=80=81firmware loader(sys/arm/freescale/imx/files.imx6=E3=81=AEoptional sdma_fw )=E5=BF=85= =E8=A6=81=E3=81=AA=E3=81=AE=E3=81=ABGENERIC kernel=E3=81=AB=E5=85=A5=E3=81=A3=E3=81=A6=E3=81=84=E3=81=AA=E3=81=84=E3=81= =A7=E3=81=99=E3=80=82 (arm=E3=81=AEGENERIC=E3=81=AB=E5=85=A5=E3=82=8C=E3=82=8B=E3=81=A8=E3=81=8D= =E3=81=AB=E5=BF=98=E3=82=8C=E3=81=9F=E3=81=BF=E3=81=9F=E3=81=84) firmware file=E3=82=82=E3=83=A9=E3=82=A4=E3=82=BB=E3=83=B3=E3=82=B9=E3=81= =AE=E9=96=A2=E4=BF=82(Linux=E6=96=B9=E9=9D=A2=E3=81=A7=E3=81=A0=E3=82=8C=E3= =81=8B=E8=B3=AA=E5=95=8F=E3=81=97=E3=81=9F=E3=81=91=E3=81=A9=E3=83=A9=E3=82= =A4=E3=82=BB=E3=83=B3=E3=82=B9=E3=81=AE=E5=9B=9E=E7=AD=94=E3=81=8C=E3=81=8D= =E3=81=A6=E3=81=84=E3=81=AA=E3=81=84=EF=BC=89=E3=81=AE=E3=81=A7source tree=E3=81=AB=E5=85=A5=E3=82=8C=E3=82=89=E3=82=8C=E3=81=AA=E3=81=84=E3=81= =BF=E3=81=9F=E3=81=84=E3=81=AA=E3=81=AE=E3=81=A7=E3=80=82fslsdma=E3=81=AF= =E6=B6=88=E3=81=97=E3=81=9F=E3=81=BB=E3=81=86=E3=81=8C=E8=89=AF=E3=81=84=E3= =81=A8=E6=80=9D=E3=81=86=E3=81=AE=E3=81=A7=E3=81=99=E3=81=8C=E3=80=81 --- sys/arm/conf/GENERIC (revision 346440) +++ sys/arm/conf/GENERIC (working copy) @@ -252,7 +252,6 @@ device ti_mbox # DMA controller -device fslsdma device ti_sdma device a10_dmac device a31_dmac --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Mon Apr 22 17:22:41 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F13E5159FBA8 for ; Mon, 22 Apr 2019 17:22:40 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 A156E6DE5B for ; Mon, 22 Apr 2019 17:22:38 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-vs1-xe2f.google.com with SMTP id g187so6643711vsc.8 for ; Mon, 22 Apr 2019 10:22:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hzeKJt40YukqHeMfpth+BCM/fi0LH7+QVP3h/hAt65g=; b=0KObIRIHAaq7se46uObv8uEs550PvE3cr2MWQfituGEcbbadpmDfdWu9+ndClkBG6n iL6Dzek9EwDySlqetQ0iqFy0b6jM4/sEllym3kd3u85FOF3Ftebnftrqc1hqtvSfvIW1 7ekZfLnsS9CmLntcnvgmZSRYAVVIuYAPTg/yp+HRlQHL+oUBj7+Ww6jH4k1dEY1w37tP h2IDRwVlMnBcZlkLVlmfU0In0ZtVlK7jLiM6+fo9nFwn3bbbp9rHx2t4967sZHEC9zCa FkYNmOLE4eL+nLL72VeQ8YQeN3G7fSi/qfzL1N/h38co5rFH+lNx5kHOd3XvZXR37/+u dKbg== 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=hzeKJt40YukqHeMfpth+BCM/fi0LH7+QVP3h/hAt65g=; b=e7g8nDbjYv1WEvXl1Mf5GbPeYszzgoHmBi2M59XKxYhp2P63V/RyTtag+zs/h0rTfH 7tfn0PMHlfqKv24VX1IBZXsON85WSNWn4YOePXlwZiYLhBfNL/xWxM6RrZyAPiU1/IxQ Mkm98nOvw+BijqRUt5tFo6bx0qUVFhvY5vq6xRMo8cXE6Q92m79WgOzNN302keJVoIlT rqGgj64WDnOxa9itWkRKafsImehU1jZySVJQiyMWdppanFgHvKLlUeFksFX/mrr91ZdL ejm/kmmJC3PaMySpzUL98d7aj6W55LebD7pBjToq7+vbJx99R5dWOU481m8TTN2vB8+1 7o5Q== X-Gm-Message-State: APjAAAVu78h8lNvA5ST1cd9E8SQpEfS5Go3bXWGSVFttTwbGU0gZ0Ask 6YyRdJUFSSlXU52MaIdhLaF8RVVLSNdp4yhiNEyVWQ== X-Google-Smtp-Source: APXvYqxk/7DuirmQD0D3yfMeVwFq3NxJZpXzw6ozW4zD85CcOgVAQENwTtBxq+U+EnM8EasXiUZ9qrmFyqmgtJ/u/ts= X-Received: by 2002:a67:76c7:: with SMTP id r190mr10243722vsc.196.1555953757867; Mon, 22 Apr 2019 10:22:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Chen Date: Tue, 23 Apr 2019 05:22:20 +1200 Message-ID: Subject: Re: Installing pkgs on armv5 To: Balanga Bar Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: A156E6DE5B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=chen-org-nz.20150623.gappssmtp.com header.s=20150623 header.b=0KObIRIH X-Spamd-Result: default: False [-6.24 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[chen-org-nz.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[chen.org.nz]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com]; DKIM_TRACE(0.00)[chen-org-nz.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[f.2.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.90)[-0.904,0]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-3.03)[ip: (-9.71), ipnet: 2607:f8b0::/32(-3.12), asn: 15169(-2.26), country: US(-0.06)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2019 17:22:41 -0000 On Mon, 22 Apr 2019 at 21:21, Balanga Bar wrote: > > Has anyone got any tips on how to install pkgs on armv5? You'll have to set up your own rig for armv5, as I don't believe there are any official repos. I use synth to crossbuild armv6 packages on amd64; there are also references on the 'Net on using pourdriere to achieve this. Cheers. -- Jonathan Chen From owner-freebsd-arm@freebsd.org Tue Apr 23 07:09:04 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1059115907AB for ; Tue, 23 Apr 2019 07:09:04 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 E3FD1926C3; Tue, 23 Apr 2019 07:09:02 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x52a.google.com with SMTP id f53so11632994ede.4; Tue, 23 Apr 2019 00:09:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZbuzJqAmo7CBWFEnzQzwUZbPd2Hy5nyK184zgZyZQko=; b=t5MLJox232uSu9BVeEzFe/6oKAyf8RuAHwu1MsjZ4wv3nVjMu1QomPPhyollxE+ZGp xViEpEgAX3yZJPNkKcDzLH8wWt635frth4e+OHsyWZMF1iTbksPsxQqqqO/jOhrMpxK+ pWTsrk6MSemGPhhjP8LtRJxoljvnJquXxMSi2XD+ilgcmz+AKZHlCH0mIUPuK5nJu2SN ZQKdTZ0MwXuKtesRBRb9qRVRD+xU9wAvbkHYUp0o5N0uxAsbYwEZvVkS99WEOD4XR9hN 1OPdwyue++olGWbf1n6/oBFdJYdEmYWtLGq9ncDM0jxkrkzzP/0kOXPlYV3ppwJxGIiM mgEg== 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=ZbuzJqAmo7CBWFEnzQzwUZbPd2Hy5nyK184zgZyZQko=; b=eGPIWMAxRHV5JygnMFAUkgb5hOk9A1IrPj5KDntiS65RJjphD0tD6UK9+t4ryA25hT eZEI0ADVrLtUZtOdc2Z2QK4G+kayl1JHOTDon45QSXXjT0tZ3ps16r1mr1Ra3YEoUgXf VZcXmyhelMO/OwaVSpLQ8/cX8H9VCQGmbeIarHqODXgE+1Chads06gLBAeDNQITCUx0u /uLswmlAxANHdn65XOSM2kLUJXf6x4XCLOdJfUkRxErVmhd9OTbEO7WVOCnbi/s5BRmt 4vqtlPc/2ckiiAAztYmSi32gPDoxOdB0AQljECViSXYXvgjMHhPLh7V/lJirnp5PpwEG ywog== X-Gm-Message-State: APjAAAX5Ed+2wpVr8NlEXJNnCBDkCCZNi089L++IEbO6ZK7tVmcKAwPB 4qUzp41GMvhoRWEpFxIdpVqQx163EXo6k8TX+CCBpW2m X-Google-Smtp-Source: APXvYqzUF/hTMtvBT5qVYNCC0cgpOo7nb1vW6MCIzi9taug8TgRYXxk/NdxRATkrWGC6niHkefXicqLqU63ptLGuvXQ= X-Received: by 2002:a05:6402:55a:: with SMTP id i26mr6038637edx.249.1556003341005; Tue, 23 Apr 2019 00:09:01 -0700 (PDT) MIME-Version: 1.0 References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> In-Reply-To: From: Balanga Bar Date: Tue, 23 Apr 2019 09:08:28 +0100 Message-ID: Subject: Re: Marvell Kirkwood - anyone? To: Ian Lepore Cc: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: E3FD1926C3 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=t5MLJox2; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-5.73 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.95)[-0.954,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.77)[ip: (-9.14), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.25), country: US(-0.06)]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[a.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 07:09:04 -0000 If I manage to build FreeBSD 8, how would I install any pkgs on it? I've managed to get 11.0 installed but haven't found a pkg repository which I can use. On Wed, Apr 17, 2019 at 10:02 PM Ian Lepore wrote: > On Wed, 2019-04-17 at 22:13 +0100, Balanga Bar wrote: > > Do you have build instructions for building 8.2? It seems that the > > instructions in, for example, https://wiki.freebsd.org/FreeBSDMarvell > > are > > not easily reproduced.... > > > > What target should I use? I presume DOCKSTAR was not available at the > > time... > > > > I suspect in freebsd 8, SHEEVAPLUG is the closest config. The custom > config I use for a dreamplug at $work as available at > > https://people.freebsd.org/~ian/DREAMPLUG8 > > -- Ian > > From owner-freebsd-arm@freebsd.org Tue Apr 23 07:54:22 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1942A1591A99 for ; Tue, 23 Apr 2019 07:54:22 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9C59940D9; Tue, 23 Apr 2019 07:54:20 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id C24D617093; Tue, 23 Apr 2019 07:54:13 +0000 (UTC) Date: Tue, 23 Apr 2019 07:54:12 +0000 From: Mark Linimon To: Balanga Bar Cc: Ian Lepore , freebsd-arm@freebsd.org Subject: Re: Marvell Kirkwood - anyone? Message-ID: <20190423075411.GA18137@lonesome.com> References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: D9C59940D9 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-0.37 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[11.6.222.18.list.dnswl.org : 127.0.5.2]; MX_GOOD(-0.01)[mail.soaustin.net]; NEURAL_HAM_SHORT(-0.46)[-0.463,0]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-0.23)[ipnet: 18.220.0.0/14(0.17), asn: 16509(-1.28), country: US(-0.06)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.71)[-0.710,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-0.66)[-0.656,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 07:54:22 -0000 On Tue, Apr 23, 2019 at 09:08:28AM +0100, Balanga Bar wrote: > If I manage to build FreeBSD 8, how would I install any pkgs on it? You will have to build them yourself. You are likely to have to start with the following: https://svnweb.freebsd.org/ports/tags/RELEASE_8_EOL/ to get a last-known-working ports infrastructure, and then merge specific fixes from the last 3 years of ports commits that you find you need. Fair warning: IMHO this will be a non-trivial exercise. mcl From owner-freebsd-arm@freebsd.org Tue Apr 23 13:19:50 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89F04159A750 for ; Tue, 23 Apr 2019 13:19:50 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 8ADAB71B62; Tue, 23 Apr 2019 13:19:49 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x532.google.com with SMTP id i13so12563131edf.11; Tue, 23 Apr 2019 06:19:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zhQ+P8T+sK0Y1fGsE0hBV/5Y1CWnxo4/LsYzkdMd8xE=; b=fBCsICZez323FARHIkJ9NEC9lQWn9HiqQngp1qCDKWg/tgtPP1OILRftk/f7dlJHpi fFkNhw9YmAm9CWDIksDgU8bFa0worGic7ks9cuKmDOi1rp/+ebERTQeWDgFHiAbhB16d TmuneMUIfxtQtVhQf0jqT6fJ+VgfKfBbgwmFfI8BLsjIO5JvNR0ci05qnZn2JUwRtBNQ I+rviHh1VLU/WQ+S+HbBqWhGVxzHjQXOXyXxpVZ975ZKxAOa9yzBYLEvYsDL4ANDUNuu m53maiQyoitnG6venNWpLa+mEtELVbz7nqHSA2VDlEW10SPNfYplKN5Z1qx2S38vx7PG NGXQ== 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=zhQ+P8T+sK0Y1fGsE0hBV/5Y1CWnxo4/LsYzkdMd8xE=; b=bZat1s1mshi6HAPIdgf2WaQ4ZwdDP8NwTVEXWiN4i2NTUZ1TRbRpUE4rA0d/yHRvi+ af4er1MyWoNekfwNz2tqRaxEvUQhVeO8S6Jg/87/L3otdBTp+uu6SCa0BxbgLip43img jqaZX+p70PjwVeaQtXR5ksM++OYY0oWMS44A2swH79GaaqgQ+3cqCAD37Ud8WE4HJYLv XsIVCeTogFfHAXEzZo1oOep2/+irTlkIk75G/UAH1evaXyT1KFxs1OpNhHXVznm6eHMM hVI5tcdHUJVTrNGjFhcklv7Xw8XStzMX+ACfeaXBO+sMZPabZwy+xv3bmUazJ7S3Mbre GGzg== X-Gm-Message-State: APjAAAWGqliTStQ5YTTVf88//cKdMVxeXWPeRv/vuRnMvSs9K+33gFfA jOz4HNnNz5AxEkSCPzSncEUKl2iO5qnapHIEqf4= X-Google-Smtp-Source: APXvYqx6CahK48sSPtdwZkZGvzSX8Enddkr0yA8ovfDzeXpidAQIZa4gRX8orl6rb3QePo/7OXGa1HmTVUXL22STqFY= X-Received: by 2002:a17:906:7b86:: with SMTP id s6mr12434183ejo.144.1556025588364; Tue, 23 Apr 2019 06:19:48 -0700 (PDT) MIME-Version: 1.0 References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> In-Reply-To: <20190423075411.GA18137@lonesome.com> From: Balanga Bar Date: Tue, 23 Apr 2019 15:19:15 +0100 Message-ID: Subject: Re: Marvell Kirkwood - anyone? To: Mark Linimon Cc: Ian Lepore , freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 8ADAB71B62 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=fBCsICZe; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::532 as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-5.74 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.99)[-0.986,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.74)[ip: (-9.01), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.26), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2.3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 13:19:50 -0000 Is it possible to get a version of portsnap from that point? On Tue, Apr 23, 2019 at 8:54 AM Mark Linimon wrote: > On Tue, Apr 23, 2019 at 09:08:28AM +0100, Balanga Bar wrote: > > If I manage to build FreeBSD 8, how would I install any pkgs on it? > > You will have to build them yourself. > > You are likely to have to start with the following: > > https://svnweb.freebsd.org/ports/tags/RELEASE_8_EOL/ > > to get a last-known-working ports infrastructure, and then merge > specific fixes from the last 3 years of ports commits that you > find you need. > > Fair warning: IMHO this will be a non-trivial exercise. > > mcl > From owner-freebsd-arm@freebsd.org Tue Apr 23 16:57:35 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A162C159F7B6 for ; Tue, 23 Apr 2019 16:57:35 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8BD6F81967; Tue, 23 Apr 2019 16:57:34 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id 4C6EE16E80; Tue, 23 Apr 2019 16:57:33 +0000 (UTC) Date: Tue, 23 Apr 2019 16:57:32 +0000 From: Mark Linimon To: Balanga Bar Cc: Ian Lepore , freebsd-arm@freebsd.org Subject: Re: Marvell Kirkwood - anyone? Message-ID: <20190423165731.GB10587@lonesome.com> References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: 8BD6F81967 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.12 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[11.6.222.18.list.dnswl.org : 127.0.5.2]; MX_GOOD(-0.01)[cached: mail.soaustin.net]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-0.23)[ipnet: 18.220.0.0/14(0.17), asn: 16509(-1.28), country: US(-0.06)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.72)[-0.716,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.85)[0.845,0]; NEURAL_HAM_LONG(-0.46)[-0.462,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 16:57:35 -0000 On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: > Is it possible to get a version of portsnap from that point? I don't know enough to answer that question. I think it would be fair to assume "no". IIUC you seem to be looking for an _easy_ way to get Kirkwood back up and working. I'm going to be honest and say there isn't one. Here are the approaches I think you can take: - stay on 8.x; bring individual port updates to it from ports-head and build your own ports. Difficulty: hard. - figure out what src changes after 8.x regressed Kirkwood; check out src 12-STABLE, build your own src, and use FreeBSD.org packages. Difficulty: expert. - stay on 8.x; attempt to bring a modern ports tree to it and build your own ports. Difficulty: challenging. The difficulty level of the first approach depends on which ports you are going to try to use. shells/bash? Probably not too hard. Anything GUI-related? Very hard. None of these approaches are achievable within hours; they will take days, or, in the case of the third approach, weeks. fwiw, the second approach is the only one where your fixes could be merged back into FreeBSD. If I were personally determined to run Kirkwoord, that's the approach I would take. (I gave my GuruPlug away some time ago.) I'm sorry that I can't be more encouraging. mcl From owner-freebsd-arm@freebsd.org Tue Apr 23 17:09:00 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C5F8159FE92 for ; Tue, 23 Apr 2019 17:09:00 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 9522982493; Tue, 23 Apr 2019 17:08:59 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x52a.google.com with SMTP id u57so13333810edm.3; Tue, 23 Apr 2019 10:08:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VIgiYYMIULlUj/DQFkEqXNEG3RRT2DvT9rnicdwVWVM=; b=u/x5gVEw2hor1nOwmMv96cMTFBn3Xo1Sp5lZJrFIjrlqcFvrtwWoEs2UKasI+bRLxQ TjzhpgDlffsK93qXMjRxRQuxQv7/IgusNeiwThyYsJq8J55FkStRUIaIOmg6IDAz2Vvk P3aq3lPVphufT0Da55PWHNQVsp7Bc8VxLsuSxjBNmqkJKR7BIo1A48jPDYOPQS8W8Bce T+RB0Bw++7sQJSklNo+m+nDZ8S7+7isBcaWbXCs6CVP7x91s/IiGkvuyf8uoRzgZTDP7 pxxeUlSF9HEeNWqwePAs1oGjpOhuryCkx55GlbfsvnoFiH27QPvgTYlDe/W2M4RKIQFv z0Dg== 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=VIgiYYMIULlUj/DQFkEqXNEG3RRT2DvT9rnicdwVWVM=; b=HoNQM/5yloH5GW+fiLvNtuiTbykLFH/0S2Y/QUR/GXuJUo11Dbsf1OSjV8KcG/Nty0 Sfxy71mSk8RRBtdtXNZaOOj0/RMYPwvXKF4F5HIjKOFhw6hRrXs+d6+W9saa/01jZstv iWDaehsjTavd2oSDU9etU8qDQvlJbz40CAb47jxbLjdWSYDYBqZcHo5Y6kU5FWiqg7Kv muftX9z/+GFHUjriArJVjfoSyLJ14Xzqokx4bRwNUhCJUJOxmuOXHjkacFZfF1Rl194l 1EfXuKbZyxw+Wg3eslS75YW8k5IQLaNQrF78KiZz4R7CP8kW9qe7BP76yuW2VOczTWbx ugKQ== X-Gm-Message-State: APjAAAVyk7nVksdDU2HTyEwSEopD2+2rK5i9x2g6bbUrafW4zihU/omd w5333aMf6AXyiMkCtkxsjhm98jK2+pz1AqNMexD/MWjz X-Google-Smtp-Source: APXvYqz/qPYYQaSTreTwFDUNPPdrDnKqH5FREtvJNywkztNQy4bj6W7GV/DmRKVE0JGBR8VkT5cCIOYWDocyoPUS6go= X-Received: by 2002:a17:906:e0c7:: with SMTP id gl7mr6704620ejb.274.1556039337633; Tue, 23 Apr 2019 10:08:57 -0700 (PDT) MIME-Version: 1.0 References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> <20190423165731.GB10587@lonesome.com> In-Reply-To: <20190423165731.GB10587@lonesome.com> From: Balanga Bar Date: Tue, 23 Apr 2019 19:08:24 +0100 Message-ID: Subject: Re: Marvell Kirkwood - anyone? To: Mark Linimon Cc: Ian Lepore , freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 9522982493 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=u/x5gVEw; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-4.66 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[1]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.88)[-0.884,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.77)[ip: (-9.14), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.26), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[a.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 17:09:00 -0000 Actually I have managed to build FreeBSD 11.0-RELEASE on ARM and it has not exhibited any problems on my GoFlexHome apart from being unable install pkgs. That is the current focus at the moment. On Tue, Apr 23, 2019 at 5:57 PM Mark Linimon wrote: > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: > > Is it possible to get a version of portsnap from that point? > > I don't know enough to answer that question. I think it would be fair > to assume "no". > > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up > and working. I'm going to be honest and say there isn't one. > > Here are the approaches I think you can take: > > - stay on 8.x; bring individual port updates to it from ports-head and > build your own ports. Difficulty: hard. > > - figure out what src changes after 8.x regressed Kirkwood; check > out src 12-STABLE, build your own src, and use FreeBSD.org packages. > Difficulty: expert. > > - stay on 8.x; attempt to bring a modern ports tree to it and build > your own ports. Difficulty: challenging. > > The difficulty level of the first approach depends on which ports you > are going to try to use. shells/bash? Probably not too hard. Anything > GUI-related? Very hard. > > None of these approaches are achievable within hours; they will take > days, or, in the case of the third approach, weeks. > > fwiw, the second approach is the only one where your fixes could be > merged back into FreeBSD. If I were personally determined to run > Kirkwoord, that's the approach I would take. (I gave my GuruPlug > away some time ago.) > > I'm sorry that I can't be more encouraging. > > mcl > From owner-freebsd-arm@freebsd.org Tue Apr 23 18:01:40 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 717B215A1734 for ; Tue, 23 Apr 2019 18:01:40 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1784C853B4; Tue, 23 Apr 2019 18:01:38 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3NI1aGJ038943; Tue, 23 Apr 2019 11:01:36 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3NI1ZDj038942; Tue, 23 Apr 2019 11:01:35 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904231801.x3NI1ZDj038942@gndrsh.dnsmgr.net> Subject: Re: Marvell Kirkwood - anyone? In-Reply-To: <20190423165731.GB10587@lonesome.com> To: Mark Linimon Date: Tue, 23 Apr 2019 11:01:35 -0700 (PDT) CC: Balanga Bar , freebsd-arm@freebsd.org, Ian Lepore X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 1784C853B4 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.24 / 15.00]; ARC_NA(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.879,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TAGGED_RCPT(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.50)[0.499,0]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; NEURAL_SPAM_LONG(0.95)[0.948,0]; IP_SCORE(0.03)[ip: (0.11), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.03), country: US(-0.06)]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 18:01:40 -0000 > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: > > Is it possible to get a version of portsnap from that point? > > I don't know enough to answer that question. I think it would be fair > to assume "no". You would not want ot use portsnap I do believe, but what you may want to start with is the ports.txz file that should of shipped on the i386/amd64 disc1 .iso That would of been the copy of the ports tree at the time the system was released. Your going to have probably significant paints in finding tar balls that match, but it is not impossible. The shorter your list of needed ports the better. Your are then going to have to check for CVE's against all that code and either fix or mitigate the issue, if it is a non connected low access device CVE's may not matter at all. For OS sources I think I would either grab from svn the version at releng/8.x that matches what you decided on, or a point on stable/8 slightly after this. My reasoning here is that you would be able to pull in specific changes from later in the life of stable/8 that you may need fairly easily, ie svn merge. > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up > and working. I'm going to be honest and say there isn't one. I Concur. > Here are the approaches I think you can take: All very reasonable too. > > - stay on 8.x; bring individual port updates to it from ports-head and > build your own ports. Difficulty: hard. > > - figure out what src changes after 8.x regressed Kirkwood; check > out src 12-STABLE, build your own src, and use FreeBSD.org packages. > Difficulty: expert. > > - stay on 8.x; attempt to bring a modern ports tree to it and build > your own ports. Difficulty: challenging. > > The difficulty level of the first approach depends on which ports you > are going to try to use. shells/bash? Probably not too hard. Anything > GUI-related? Very hard. > > None of these approaches are achievable within hours; they will take > days, or, in the case of the third approach, weeks. > > fwiw, the second approach is the only one where your fixes could be > merged back into FreeBSD. If I were personally determined to run > Kirkwoord, that's the approach I would take. (I gave my GuruPlug > away some time ago.) > > I'm sorry that I can't be more encouraging. > > mcl -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Tue Apr 23 18:27:47 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 429CD15A2149 for ; Tue, 23 Apr 2019 18:27:47 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 E221E85FBA; Tue, 23 Apr 2019 18:27:45 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x52a.google.com with SMTP id k45so13546247edb.6; Tue, 23 Apr 2019 11:27:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7ce0IRirM83820FSqWLjPJC/QrnogxVS1q/zOddrOfY=; b=WdB271ziX9jlTRRydq3rpaeauiCjfTD9vJuLaHJ04qx9Y5v1g2XJY7obNwRTtK09z8 QJjGGQQ1QSkHMVIxLAaQmCYP45iRp11nVjOTurQyhyK2vtJcd0CzbiBzLtI9iEoWIEkc NDCxUyWiyl8UMcQSRM2xt5LXu/1P9ztB/FscfngNJx2F7oLiiHqBB+soL/rwQ3MyXRXE 11qt5fLTuh/ujF+YUbbfkQ5ZREKJUhplai2VwoGsWR7bHVDeMoxrYrLXn4CVxTojfilZ B1AOlhgjjMwBke56tZdLRQ45/rY/v4C+wKUvIIh3YNyrqSUMv1HWEc9siVCrvFDForpB VmaQ== 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=7ce0IRirM83820FSqWLjPJC/QrnogxVS1q/zOddrOfY=; b=JU/dsZlw04IWygEsA+ZLsQ5w0qk/XvTznLsv9AscjMeCxaQzr4nAMOu/unz3CNkE/h d7HVzP2DZ4qzMcu7ZPV1e1bHMqYhpDLUwreMZpcVlJCSEH03tccU4jS8ZjuVjyTIFwNK RcOtg8/cQekRbgVY3hgrGBvKKXzjoBJhirvnK3subJ19BSA358tIVf5pOfSUAHuAAfKc hAEXUR4ySAR/Y9SaUBG/kfH/LzoU6iVG3mOU9IbZfDLpMGp77yBztWwZvEdZZYW4QxNO sUGrUvHZ2MkF2cg0upibrK4kTqxFpatDqnBLFoDqt2utvv8j86E6J3PCkPyvqBEBkef/ i17Q== X-Gm-Message-State: APjAAAX+Nh7Tv7U56OBwDnix9ykD1drgeLtORfjgladtb2ruA6jXJFDF HK+UQNBD4DN2IH+0dkbv6M5GxifNcfCqd2t1PStnXPkCf8hDKQ== X-Google-Smtp-Source: APXvYqz93fJBV/DmqfjhsFIe8dCKXUdufWDZ0hQzMUDCZ0GAqqAJHnxFWxP99GcuZaPSDEk7yxxRwtD7Juyy9MOZfjA= X-Received: by 2002:a17:906:4d8b:: with SMTP id s11mr13162769eju.31.1556044064023; Tue, 23 Apr 2019 11:27:44 -0700 (PDT) MIME-Version: 1.0 References: <20190423165731.GB10587@lonesome.com> <201904231801.x3NI1ZDj038942@gndrsh.dnsmgr.net> In-Reply-To: <201904231801.x3NI1ZDj038942@gndrsh.dnsmgr.net> From: Balanga Bar Date: Tue, 23 Apr 2019 20:27:10 +0100 Message-ID: Subject: Re: Marvell Kirkwood - anyone? To: "Rodney W. Grimes" Cc: Mark Linimon , freebsd-arm@freebsd.org, Ian Lepore X-Rspamd-Queue-Id: E221E85FBA X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=WdB271zi; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-4.08 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.31)[-0.306,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.77)[ip: (-9.13), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.26), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[a.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 18:27:47 -0000 Many thanks. Is this what I should use? ftp://ftp.fi.freebsd.org/pub/FreeBSD/releases/amd64/11.0-RELEASE/ports.txz Not really sure how this differs from portsnap fetch, but it seems to be what I'm looking for... On Tue, Apr 23, 2019 at 7:01 PM Rodney W. Grimes < freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: > > > Is it possible to get a version of portsnap from that point? > > > > I don't know enough to answer that question. I think it would be fair > > to assume "no". > > You would not want ot use portsnap I do believe, > but what you may want to start with is the ports.txz file > that should of shipped on the i386/amd64 disc1 .iso > > That would of been the copy of the ports tree at the time > the system was released. Your going to have probably significant > paints in finding tar balls that match, but it is not impossible. > > The shorter your list of needed ports the better. > > Your are then going to have to check for CVE's against > all that code and either fix or mitigate the issue, if > it is a non connected low access device CVE's may not > matter at all. > > For OS sources I think I would either grab from svn the version > at releng/8.x that matches what you decided on, or a point > on stable/8 slightly after this. My reasoning here is that you > would be able to pull in specific changes from later in the > life of stable/8 that you may need fairly easily, ie svn merge. > > > > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up > > and working. I'm going to be honest and say there isn't one. > > I Concur. > > > Here are the approaches I think you can take: > All very reasonable too. > > > > > - stay on 8.x; bring individual port updates to it from ports-head and > > build your own ports. Difficulty: hard. > > > > - figure out what src changes after 8.x regressed Kirkwood; check > > out src 12-STABLE, build your own src, and use FreeBSD.org packages. > > Difficulty: expert. > > > > - stay on 8.x; attempt to bring a modern ports tree to it and build > > your own ports. Difficulty: challenging. > > > > The difficulty level of the first approach depends on which ports you > > are going to try to use. shells/bash? Probably not too hard. Anything > > GUI-related? Very hard. > > > > None of these approaches are achievable within hours; they will take > > days, or, in the case of the third approach, weeks. > > > > fwiw, the second approach is the only one where your fixes could be > > merged back into FreeBSD. If I were personally determined to run > > Kirkwoord, that's the approach I would take. (I gave my GuruPlug > > away some time ago.) > > > > I'm sorry that I can't be more encouraging. > > > > mcl > > -- > Rod Grimes > rgrimes@freebsd.org > From owner-freebsd-arm@freebsd.org Tue Apr 23 19:28:51 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01A7315803C4 for ; Tue, 23 Apr 2019 19:28:51 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F44F87DC7; Tue, 23 Apr 2019 19:28:49 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3NJSjtp039313; Tue, 23 Apr 2019 12:28:45 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3NJSi7D039312; Tue, 23 Apr 2019 12:28:44 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904231928.x3NJSi7D039312@gndrsh.dnsmgr.net> Subject: Re: Marvell Kirkwood - anyone? In-Reply-To: To: Balanga Bar Date: Tue, 23 Apr 2019 12:28:44 -0700 (PDT) CC: "Rodney W. Grimes" , Mark Linimon , freebsd-arm@freebsd.org, Ian Lepore X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 8F44F87DC7 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.14 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.81)[0.808,0]; IP_SCORE(0.03)[ip: (0.11), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.03), country: US(-0.06)]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; NEURAL_SPAM_LONG(0.97)[0.972,0]; NEURAL_SPAM_MEDIUM(0.44)[0.439,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 19:28:51 -0000 > Many thanks. Is this what I should use? > > ftp://ftp.fi.freebsd.org/pub/FreeBSD/releases/amd64/11.0-RELEASE/ports.txz If your trying to get 11.0 release ports/packages working on that platform that would be a good place to start. Your going to run into some issues with out of date tar balls, but since you got 11.0 running the amount of this should be greatly reduced. > > Not really sure how this differs from portsnap fetch, but it seems to be > what I'm looking for... portsnap fetch well get you the latest ^head ports, and they may or may not build on 11.0, I believe it does build on 11.2. I am not a consumer of portsnap fetch so take anything I say about it with very light value. I was more trying to give you some starting points if you did need to go down the 8.X path, given your light years ahead of that by being able to run 11.0 much of what I said is less importand and more of that mcl said applies. Another aside of having 11.0 running is you can probably host cross build on a AMD64 11.0 system and speed up your build cycles. I do not think that worked so well back in the 8.x era. > On Tue, Apr 23, 2019 at 7:01 PM Rodney W. Grimes < > freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > > > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: > > > > Is it possible to get a version of portsnap from that point? > > > > > > I don't know enough to answer that question. I think it would be fair > > > to assume "no". > > > > You would not want ot use portsnap I do believe, > > but what you may want to start with is the ports.txz file > > that should of shipped on the i386/amd64 disc1 .iso > > > > That would of been the copy of the ports tree at the time > > the system was released. Your going to have probably significant > > paints in finding tar balls that match, but it is not impossible. > > > > The shorter your list of needed ports the better. > > > > Your are then going to have to check for CVE's against > > all that code and either fix or mitigate the issue, if > > it is a non connected low access device CVE's may not > > matter at all. > > > > For OS sources I think I would either grab from svn the version > > at releng/8.x that matches what you decided on, or a point > > on stable/8 slightly after this. My reasoning here is that you > > would be able to pull in specific changes from later in the > > life of stable/8 that you may need fairly easily, ie svn merge. > > > > > > > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up > > > and working. I'm going to be honest and say there isn't one. > > > > I Concur. > > > > > Here are the approaches I think you can take: > > All very reasonable too. > > > > > > > > - stay on 8.x; bring individual port updates to it from ports-head and > > > build your own ports. Difficulty: hard. > > > > > > - figure out what src changes after 8.x regressed Kirkwood; check > > > out src 12-STABLE, build your own src, and use FreeBSD.org packages. > > > Difficulty: expert. > > > > > > - stay on 8.x; attempt to bring a modern ports tree to it and build > > > your own ports. Difficulty: challenging. > > > > > > The difficulty level of the first approach depends on which ports you > > > are going to try to use. shells/bash? Probably not too hard. Anything > > > GUI-related? Very hard. > > > > > > None of these approaches are achievable within hours; they will take > > > days, or, in the case of the third approach, weeks. > > > > > > fwiw, the second approach is the only one where your fixes could be > > > merged back into FreeBSD. If I were personally determined to run > > > Kirkwoord, that's the approach I would take. (I gave my GuruPlug > > > away some time ago.) > > > > > > I'm sorry that I can't be more encouraging. > > > > > > mcl > > > > -- > > Rod Grimes > > rgrimes@freebsd.org > > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Tue Apr 23 21:01:26 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC7F715829A8 for ; Tue, 23 Apr 2019 21:01:25 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E00CD8B0A1; Tue, 23 Apr 2019 21:01:24 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id 9A11016E80; Tue, 23 Apr 2019 21:01:23 +0000 (UTC) Date: Tue, 23 Apr 2019 21:01:22 +0000 From: Mark Linimon To: Balanga Bar Cc: "Rodney W. Grimes" , freebsd-arm@freebsd.org, Ian Lepore Subject: Re: Marvell Kirkwood - anyone? Message-ID: <20190423210121.GA23266@lonesome.com> References: <20190423165731.GB10587@lonesome.com> <201904231801.x3NI1ZDj038942@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: E00CD8B0A1 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[11.6.222.18.list.dnswl.org : 127.0.5.2]; MX_GOOD(-0.01)[cached: mail.soaustin.net]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-0.23)[ipnet: 18.220.0.0/14(0.17), asn: 16509(-1.28), country: US(-0.06)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.73)[-0.734,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_SPAM_SHORT(0.53)[0.531,0]; NEURAL_HAM_LONG(-0.25)[-0.253,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 21:01:26 -0000 On Tue, Apr 23, 2019 at 08:27:10PM +0100, Balanga Bar wrote: > Many thanks. Is this what I should use? > > ftp://ftp.fi.freebsd.org/pub/FreeBSD/releases/amd64/11.0-RELEASE/ports.txz That is the metadata equivalent of: https://svnweb.freebsd.org/ports/tags/RELEASE_11_0_0/ which is much later than the URL I gave you earlier. (If you are able to run with 11 instead of 8.3 you are _far_ better off.) i.e. there are no packages in it, just the ports tree itself. > Not really sure how this differs from portsnap fetch, but it seems to be > what I'm looking for... portsnap fetch points to a particular point in time (in general, "now"). It's not designed to be used to fetch historical points in time. IMVHO you will quickly find that doing an SVN checkout of the above URL is going to get you further along than just the ports.txz and then just start patching. Yes, there is a learning curve for SVN, but w/rt to the work you want to do on both src and ports, it's the right tool for the job. mcl From owner-freebsd-arm@freebsd.org Tue Apr 23 21:05:58 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB3F71582A5F for ; Tue, 23 Apr 2019 21:05:57 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C43D8B234; Tue, 23 Apr 2019 21:05:57 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id 33F2216E80; Tue, 23 Apr 2019 21:05:56 +0000 (UTC) Date: Tue, 23 Apr 2019 21:05:55 +0000 From: Mark Linimon To: "Rodney W. Grimes" Cc: Balanga Bar , freebsd-arm@freebsd.org, Ian Lepore Subject: Re: Marvell Kirkwood - anyone? Message-ID: <20190423210554.GB23266@lonesome.com> References: <201904231928.x3NJSi7D039312@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201904231928.x3NJSi7D039312@gndrsh.dnsmgr.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: 2C43D8B234 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [0.83 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[11.6.222.18.list.dnswl.org : 127.0.5.2]; MX_GOOD(-0.01)[cached: mail.soaustin.net]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-0.23)[ipnet: 18.220.0.0/14(0.17), asn: 16509(-1.28), country: US(-0.06)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.77)[-0.770,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_SPAM_SHORT(0.48)[0.481,0]; NEURAL_HAM_LONG(-0.34)[-0.338,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 21:05:58 -0000 On Tue, Apr 23, 2019 at 12:28:44PM -0700, Rodney W. Grimes wrote: > portsnap fetch well get you the latest ^head ports, and they may or may > not build on 11.0, I believe it does build on 11.2. The guarantee from portmgr is that "the head ports tree will build on the earliest supported release on each branch" e.g. right now: 11.2R 12.0R Further reading: https://www.freebsd.org/security/security.html#sup https://www.freebsd.org/portmgr/policies_eol.html In particular, the last line of the latter: "Older releases are not maintained; ports and packages may not be able to install or run. Users are strongly encouraged to upgrade to one of the supported releases mentioned above" is the official ports tree guarantee. mcl From owner-freebsd-arm@freebsd.org Wed Apr 24 07:20:13 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B5FD158F75B for ; Wed, 24 Apr 2019 07:20:13 +0000 (UTC) (envelope-from marse4eik@gmail.com) Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com [IPv6:2a00:1450:4864:20::143]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 762CC77DA3 for ; Wed, 24 Apr 2019 07:20:12 +0000 (UTC) (envelope-from marse4eik@gmail.com) Received: by mail-lf1-x143.google.com with SMTP id v1so1327731lfg.5 for ; Wed, 24 Apr 2019 00:20:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:message-id:from:to:mime-version:content-transfer-encoding; bh=FaT//d4sCi3RGDhgmuav5xuayxRDEl3fqTCEInV3Rn0=; b=ezbU/RZ1KLy5eKMdYTwlxcrscadJZjwFxLaQJSrlB6JKBgxnfsHyQ4QXAiddH/De+N 4nWtYWiuPcBTITaKrv4uHWNzxN3Z4hh1JfmyJNG5nEJrXZFgI8ee1QbqojUCkg8/nbc6 NpyayaxdOketo9LOhbywBH30O83dWTw9/61EhM7DlvV18lF/VmrjF4imdTdQ4NgG4ows TarD/zFHbPu/6mLf9jXlhnZE0uVamfy+4Zc99Xj56PglzS+CN4FgjSJbvL+M0SmC0jVR e3c32y4/RGqNjBWMmLTt2oRFoTXekevMb6G4qw4HwvkSzi5COBA0MqIBZjjfHEkW7aAg pFPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:message-id:from:to:mime-version :content-transfer-encoding; bh=FaT//d4sCi3RGDhgmuav5xuayxRDEl3fqTCEInV3Rn0=; b=AG7ZsV48ySs5vRqjv0xRqYWal/hmPcs/JBQfNf9/ev9WWAv0F+fAvwyxU7YQ3qhY24 7oqL8om7u+SOMGsj25Fj5nGNKMcXu7+GYNzjU0LdGdlrkaNtzL13cxmHmnCiLsMgko/K Du7sDrStoWINZS9nEtq9Qicx8BOelHXbiPs7QCzwzEXUePrlW5v/K7i4+Tgw4Y1fpPiO iRwdR5KbeVY0BNrx8ndXuwQ/VE68rllkv/hS9WyuvL9p63UZ7wMvQstSwKZpohQIgoSo lMi26jV0EK0hcEdDLq4bk62ECghBcHPUmuweE0KwxNrw/9tsETWJcZuX4RJN8DjJfyYN mLVw== X-Gm-Message-State: APjAAAWkSRDlb4Vxkyxeb8Eqau1P0zMGFGQZl2KHC0sKqp+UwEnnyL6K FboutdUjLRfTpqAblZIiB88Kit3q X-Google-Smtp-Source: APXvYqyTH6sH9Ues2nCxKqbHj1MrYd4lGHmQ0m97GNTF81aS3HKxwPkwHCqVmZwJXt7uNPWkteJF2Q== X-Received: by 2002:ac2:5a47:: with SMTP id r7mr17477236lfn.116.1556090410772; Wed, 24 Apr 2019 00:20:10 -0700 (PDT) Received: from [100.107.10.60] ([31.13.144.116]) by smtp.gmail.com with ESMTPSA id i64sm4330518lfe.18.2019.04.24.00.20.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Apr 2019 00:20:09 -0700 (PDT) Date: Wed, 24 Apr 2019 12:20:07 +0500 X-Priority: 3 Message-ID: <4v4a5op9vlz7nvgtstrpviud-uvzh6ej5nhnpgfbtey40ql2b-uoicl4fbtwglz3lw6vedfxaz-8bgvgm-j0qse59dbncs-khibw8n9zktnu82ya6-jnce7c-6gj2gikmmkbj2t0qfd4g42ga-u5o8yu.1556090407098@email.android.com> From: NOOB ovich To: "freebsd-arm@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Rspamd-Queue-Id: 762CC77DA3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ezbU/RZ1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of marse4eik@gmail.com designates 2a00:1450:4864:20::143 as permitted sender) smtp.mailfrom=marse4eik@gmail.com X-Spamd-Result: default: False [-0.62 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DKIM_TRACE(0.00)[gmail.com:+]; MISSING_SUBJECT(2.00)[]; HAS_X_PRIO_THREE(0.00)[3]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MIME_BASE64_TEXT(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.51)[ip: (2.14), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.27), country: US(-0.06)]; NEURAL_SPAM_SHORT(0.80)[0.804,0]; RCVD_IN_DNSWL_NONE(0.00)[3.4.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 07:20:13 -0000 YXMgV2hpY2ggc25hcGRyYWdvbiBwcm9jZXNzb3JzIGFyZSBzdXBwb3J0ZWQ/ From owner-freebsd-arm@freebsd.org Wed Apr 24 09:34:29 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 233031592D8F for ; Wed, 24 Apr 2019 09:34:29 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CD6E984649; Wed, 24 Apr 2019 09:34:26 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Date: Wed, 24 Apr 2019 11:34:17 +0200 (CEST) From: Ronald Klop To: Balanga Bar Cc: Ian Lepore , Mark Linimon , freebsd-arm@freebsd.org Message-ID: <1995497096.1.1556098457731@localhost> In-Reply-To: References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> <20190423165731.GB10587@lonesome.com> Subject: Re: Marvell Kirkwood - anyone? MIME-Version: 1.0 X-Mailer: Realworks (455.339.a4f276ae79) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: CD6E984649 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 194.109.157.24 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-0.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.88)[-0.884,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; NEURAL_HAM_LONG(-0.21)[-0.209,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[klop.ws]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[mx2.greenhost.nl,mx1.greenhost.nl]; NEURAL_HAM_SHORT(-0.35)[-0.345,0]; RCVD_IN_DNSWL_NONE(0.00)[24.157.109.194.list.dnswl.org : 127.0.15.0]; HAS_X_PRIO_THREE(0.00)[3]; IP_SCORE(-0.05)[ipnet: 194.109.0.0/16(-0.14), asn: 3265(-0.12), country: NL(0.01)]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 09:34:29 -0000 Dear Balanga, I run 11.2 on my Sheevaplug (armv5 also). uname -a FreeBSD sheeva2.klop.ws 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #4 r339336M: Sat Oct 13 23:31:51 CEST 2018 builder@rpi3:/data/src/obj-11.2/arm.arm/data/src/11.2/sys/SHEEVAPLUG arm It has a ports checkout using portsnap. And that works pretty well. Just do: portsnap auto cd /usr/ports/shells/bash (or whatever port you wish to install) make install make clean I think that is the most simple approach for you to go forward. Regards, Ronald. PS: Sorry for top-posting, my current mail client does not help in this very well. Van: Balanga Bar Datum: dinsdag, 23 april 2019 20:08 Aan: Mark Linimon CC: freebsd-arm@freebsd.org, Ian Lepore Onderwerp: Re: Marvell Kirkwood - anyone? > > Actually I have managed to build FreeBSD 11.0-RELEASE on ARM and it has not > exhibited any problems on my GoFlexHome apart from being unable install > pkgs. That is the current focus at the moment. > > On Tue, Apr 23, 2019 at 5:57 PM Mark Linimon wrote: > > > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: > > > Is it possible to get a version of portsnap from that point? > > > > I don't know enough to answer that question. I think it would be fair > > to assume "no". > > > > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up > > and working. I'm going to be honest and say there isn't one. > > > > Here are the approaches I think you can take: > > > > - stay on 8.x; bring individual port updates to it from ports-head and > > build your own ports. Difficulty: hard. > > > > - figure out what src changes after 8.x regressed Kirkwood; check > > out src 12-STABLE, build your own src, and use FreeBSD.org packages. > > Difficulty: expert. > > > > - stay on 8.x; attempt to bring a modern ports tree to it and build > > your own ports. Difficulty: challenging. > > > > The difficulty level of the first approach depends on which ports you > > are going to try to use. shells/bash? Probably not too hard. Anything > > GUI-related? Very hard. > > > > None of these approaches are achievable within hours; they will take > > days, or, in the case of the third approach, weeks. > > > > fwiw, the second approach is the only one where your fixes could be > > merged back into FreeBSD. If I were personally determined to run > > Kirkwoord, that's the approach I would take. (I gave my GuruPlug > > away some time ago.) > > > > I'm sorry that I can't be more encouraging. > > > > mcl > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > From owner-freebsd-arm@freebsd.org Wed Apr 24 10:24:07 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81CBC1594482 for ; Wed, 24 Apr 2019 10:24:07 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (Client CN "*.freenet.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B2F386497 for ; Wed, 24 Apr 2019 10:24:06 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.164] (helo=mjail1.freenet.de) by mout0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1hJF4O-0007mb-Fd for freebsd-arm@freebsd.org; Wed, 24 Apr 2019 12:24:04 +0200 Received: from [::1] (port=52382 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1hJF4O-00068p-E7 for freebsd-arm@freebsd.org; Wed, 24 Apr 2019 12:24:04 +0200 Received: from sub2.freenet.de ([195.4.92.121]:56736) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1hJF1z-0003y8-C5 for freebsd-arm@freebsd.org; Wed, 24 Apr 2019 12:21:35 +0200 Received: from p4fd9f3ce.dip0.t-ipconnect.de ([79.217.243.206]:58387 helo=freebsd-t450.fritz.box) by sub2.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256) (port 465) (Exim 4.90_1 #2) id 1hJF1z-0000Dv-8y for freebsd-arm@freebsd.org; Wed, 24 Apr 2019 12:21:35 +0200 Date: Wed, 24 Apr 2019 12:21:34 +0200 From: Manuel =?ISO-8859-1?Q?St=FChn?= To: freebsd-arm@freebsd.org Subject: I2C on Allwinner NanoPI Neo2 Message-Id: <20190424122134.36e8dc112c62486d00703d4f@freenet.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originated-At: 79.217.243.206!58387 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 10:24:07 -0000 Hi, On my Allwinner NanoPI NEO2 (H5 aarch64 based) the I2C("allwinner,sun6i-a31-i2c" compatible, debug messages enabled) shows this message: root@bsd-nanopi:~ # i2c -v -f /dev/iic0 -a0x3c -d r -c 1 dev: /dev/iic0, addr: 0x3c, r/w:twsi_locked_start(): no ACK (status: 08) after sending slave address r, offset: 0x00, width: 8, count: 1 ioctl: error sending start condition while trying to communicate with the attached NanoHAT OLED (SSD1306 based I2C 0.96inch 128x64 display). Observing the bus with a logic analyzer shows, that between start condition and the address write there is a 10ms pause. Then the address gets written correctly and the device answers ACK. The I2C-clock is 100kHz which is confirmed by logic analyzer. I'm assuming that this long delay between start condition and address write causes this error, but i do not find any problem in the i2c driver(iicbus/twsi*). I've crosschecked the board with the default Linux image, and I2C works there without problems and there is no visible delay between start and addr-wr. Any ideas? -- Manuel From owner-freebsd-arm@freebsd.org Wed Apr 24 11:00:47 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F13415950FA for ; Wed, 24 Apr 2019 11:00:47 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE0168782A for ; Wed, 24 Apr 2019 11:00:46 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 8b786ff8; Wed, 24 Apr 2019 13:00:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=U8ICVmGt+ABKEaI2+p7PQtcWr5E=; b=sSMDvWbIQmhRhfEWGZ1HIfWaLt7L bcWFBtlDL2H6HNKnNiZYVYtQIlQDjOCY/x0s40JXzU6dd+DMh8sAdBmUw+HEMfGZ lZz5iKikACdt75Uku4MY5oKxgSTBHe7xbk1xmV02lUra++3Dvge5DuHqbO5pYKFK wWaYaAyRkstB5FY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=CxXjjURnK1zHoPB2yhs/NGC9xoCHaZpyJrHm1uK2KqHEPwEoIoCZCjjL EPeC0MUXK3T7IQqFdOg/YwLsGVPgjSbm1U8CDyVtY1FODkbVw+soB0yAodWTFUVk /Cq/6eKDMLZL3M0jWxVPt+8u2AyRayHB4r0n3hoSpaotfCU60Q0= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 16bc6db4 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 24 Apr 2019 13:00:39 +0200 (CEST) Date: Wed, 24 Apr 2019 13:00:39 +0200 From: Emmanuel Vadot To: Manuel =?ISO-8859-1?Q?St=FChn?= Cc: freebsd-arm@freebsd.org Subject: Re: I2C on Allwinner NanoPI Neo2 Message-Id: <20190424130039.2b425b0f3a2dda9affa41952@bidouilliste.com> In-Reply-To: <20190424122134.36e8dc112c62486d00703d4f@freenet.de> References: <20190424122134.36e8dc112c62486d00703d4f@freenet.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: EE0168782A X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-7.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-1.00)[-0.996,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 11:00:47 -0000 Hi Manuel, On Wed, 24 Apr 2019 12:21:34 +0200 Manuel St=FChn wrote: > Hi, >=20 > On my Allwinner NanoPI NEO2 (H5 aarch64 based) the I2C("allwinner,sun6i-a= 31-i2c" compatible, debug messages enabled) shows this message: >=20 > root@bsd-nanopi:~ # i2c -v -f /dev/iic0 -a0x3c -d r -c 1 > dev: /dev/iic0, addr: 0x3c, r/w:twsi_locked_start(): no ACK (status: 08) = after sending slave address r, offset: 0x00, width: 8, count: 1 > ioctl: error sending start condition >=20 > while trying to communicate with the attached NanoHAT OLED (SSD1306 based= I2C 0.96inch 128x64 display). >=20 > Observing the bus with a logic analyzer shows, that between start conditi= on and the address write there is a 10ms pause. Then the address gets writt= en correctly and=20 > the device answers ACK. The I2C-clock is 100kHz which is confirmed by log= ic analyzer. >=20 > I'm assuming that this long delay between start condition and address wri= te causes this error, but i do not find any problem in the i2c driver(iicbu= s/twsi*). I've crosschecked the board with the default Linux image, and I2C= works there without problems and there is no visible delay between start a= nd addr-wr. >=20 > Any ideas? >=20 > --=20 > Manuel i2c(8) uses the start/stop/read/write ioctls on the i2c device and those don't use interrupts but a lots of DELAY calls. I've spent a few hours trying to make things work without interrupts but gave up and added i2c_transfer support to twsi that supports interrupts. I guess that adding I2CRDWR (the ioctls that will call i2c_transfer) to i2c(8) will not be that hard. So either do that or just code a little program that suits your needs (see https://lists.freebsd.org/pipermail/freebsd-arm/2019-April/019672.html for more info on this). Cheers, --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Apr 24 11:02:17 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A61D15952A0 for ; Wed, 24 Apr 2019 11:02:17 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 914B987B76 for ; Wed, 24 Apr 2019 11:02:16 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5536B159529B; Wed, 24 Apr 2019 11:02:16 +0000 (UTC) Delivered-To: arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3146D159529A for ; Wed, 24 Apr 2019 11:02:16 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E90E987B64; Wed, 24 Apr 2019 11:02:13 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 38b13314; Wed, 24 Apr 2019 13:02:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=nyobOcM//g/YeNTcu8KZIgYVW+g=; b=dCris52QJ0LKc2WcGuys5SpQmbCR foXt+c2Fp7VJLqSsE5w374cLUST3BLgEYQWXnoypfH9HfyoLufnd6RaLZBtDbIlR d+rdsJmJEFmjDe/qlv2bbSYTV0YM3/75UmYwWGW2qK3T4bWbHT2tX4xd+ahxA6Uu OH4P4P6lfdVtci4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=IOepMX3wYVZzQh8s4YJsgoUj2iBJjeWxKeysLsgFlZ41HHLPPRXtZxuQ FoAPmLxPwewSV5PZ7MvH2mm01L0bEpfJyUsxdWnll677/jp4Qw2NC9qCPrNIEtBu hcQtEFX1wCRvxNPHF/ZceoXnlFsnkIdz2Q8ZnR0G2vzWSJ3zPR8= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id ede9285b TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 24 Apr 2019 13:02:12 +0200 (CEST) Date: Wed, 24 Apr 2019 13:02:11 +0200 From: Emmanuel Vadot To: Daniel Braniss Cc: Ian Lepore , "freebsd-arm@freebsd.org" Subject: Re: i2c almost working for me, was Re: i2c still not working for me Message-Id: <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> In-Reply-To: <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il> References: <12F641C3-9FAA-4A3A-BA18-A7302F3A0F5E@cs.huji.ac.il> <20190409095819.c560dbc156c46e5ca0244e3e@bidouilliste.com> <23A47048-642A-481C-B7BE-B61E55F82955@cs.huji.ac.il> <20190409171604.GA4581@bluezbox.com> <6119CE3B-6042-4DDC-82BE-B0C0C7ADA838@cs.huji.ac.il> <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il> <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> <64b5598e2c8c7265f89a31b1f191cb1be318788a.camel@freebsd.org> <20190419100502.5546770a5795c20e3f4fa9db@bidouilliste.com> <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: E90E987B64 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=dCris52Q; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [0.11 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; NEURAL_HAM_MEDIUM(-0.76)[-0.763,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_HAM_LONG(-0.17)[-0.168,0]; NEURAL_SPAM_SHORT(0.56)[0.560,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mx-backup.blih.net,mail.blih.net]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.39)[ip: (-0.90), ipnet: 212.83.160.0/19(2.96), asn: 12876(-0.10), country: FR(-0.01)]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 11:02:17 -0000 On Fri, 19 Apr 2019 11:35:09 +0300 Daniel Braniss wrote: > > > > On 19 Apr 2019, at 11:05, Emmanuel Vadot wrote: > > > > On Fri, 19 Apr 2019 10:20:47 +0300 > > Daniel Braniss > wrote: > > > >> > >> > >>> On 18 Apr 2019, at 17:19, Ian Lepore wrote: > >>> > >>> On Thu, 2019-04-18 at 10:12 +0300, Daniel Braniss wrote: > >>>>> On 17 Apr 2019, at 23:26, Emmanuel Vadot > >>>>> wrote: > >>>>> > >>>>> On Tue, 16 Apr 2019 09:16:02 +0300 > >>>>> Daniel Braniss > > >>>>> wrote: > >>>>> > >>>>>> > >>>>>> > >>>>>>> On 11 Apr 2019, at 09:56, Daniel Braniss > >>>>>>> wrote: > >>>>>>> > >>>>>>> if no device is connected, I2CRDWR hangs, > >>>>>>> it also happens with i2c(8) -s, only reboot helps. > >>>>>>> > >>>>>>> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed > >>>>>>> param=2a > >>>>>>> iichb1: TWSI_WRITE: Writing 0 to 18 > >>>>>>> iichb1: TWSI_WRITE: Writing 2a to 14 > >>>>>>> iichb1: TWSI_WRITE: Writing 40 to c > >>>>>>> iichb1: TWSI_WRITE: Writing c4 to c > >>>>>>> iichb1: twsi_transfer: transmitting 2 messages > >>>>>>> iichb1: TWSI_READ: read f8 from 10 > >>>>>>> iichb1: twsi_transfer: status=f8 > >>>>>>> iichb1: twsi_transfer: msg[0] flags: 0 > >>>>>>> iichb1: twsi_transfer: msg[0] len: 9 > >>>>>>> iichb1: TWSI_WRITE: Writing e4 to c > >>>>>>> > >>>>>>> and now it?s hung > >>>>>> > >>>>>> [?] > >>>>> > >>>>> I don't see that on my OrangePi One or Pine64-LTS. > >>>> > >>>> well, mine is are Nanopi Neo, maybe it?s a dts issue? > >>>> I also have a orangepi-zero but it will take me some time to make > >>>> a sdcard > >> > >> I managed to boot my OrangePi Zero, and i2c -s has no issues, does not hang. > >> still, with the latest (r346368) my NanoPi Neo hangs when no i2c device is present, > >> so what is the difference? or where can I look? > > > > Are you using the same i2c controller on both ? > yes, and have tested with several controllers and nanopies, > > > Could you paste somewhere the overlays or dts patches ? > cat ./allwinner/dts/12/h3-i2c.dtso > /dts-v1/; > /plugin/; > > //#include "sun8i-h3-nanopi-neo.dts" > > / { > compatible = "allwinner,sun8i-h3"; > }; > > &i2c0 { > ##frequency = <50000>; > status = "okay"; > }; > > &i2c1 { > ##frequency = <50000>; > status = "okay"; > }; > > And you have hang on both i2c0 and i2c1 ? Also please note that i2c1 pins aren't routed on this PCB, I don't think that this could/should make the i2c controller hangs but ... -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Apr 24 11:15:22 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07ADB159552E for ; Wed, 24 Apr 2019 11:15:22 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DA06F880B8 for ; Wed, 24 Apr 2019 11:15:20 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9AFD3159552D; Wed, 24 Apr 2019 11:15:20 +0000 (UTC) Delivered-To: arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D059159552C for ; Wed, 24 Apr 2019 11:15:20 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AA608880B6; Wed, 24 Apr 2019 11:15:19 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 2c63cb17; Wed, 24 Apr 2019 13:15:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=mail; bh=5IJwOkjXiVrz H4cD9eoB0PmTIn8=; b=mBysUwgQW/rTNxTprWRKVKrhCbcxNr4L20Wi27iOjMhD dfS2yRbosbKYGokHSniVZoj1+Cua1EMBIvKf2PxPUtuVihLlzLjUhwOSCI2I2ZgD 4Jx7IkIcVVvPSS2FvOg7akJr5m7iqrzWcXfysDfsUI+Mjys8/AgbYzuHM83KYCA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=mail; b=pRTszF JGZdPTP0f+R7889BOjv9UmPF7X+Qdh6FmAJCKjwQb4xOBRx2O5FfuV3tyPPWIMes df9cHBCVXzlgZ0hkCJ0+Fq3bRpXOCRTcG+UsBafaJpjVj8OpXz79VQWGl+8Td9dI UhOom9ArjJH3Tk4tEMKJvyRvMj1QmVE3T47rk= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id ea26f177 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 24 Apr 2019 13:15:18 +0200 (CEST) Date: Wed, 24 Apr 2019 13:15:17 +0200 From: Emmanuel Vadot To: Daniel Braniss , "freebsd-arm@freebsd.org" , Ian Lepore Subject: Re: i2c almost working for me, was Re: i2c still not working for me Message-Id: <20190424131517.140d6d4839d2435e08b67d43@bidouilliste.com> In-Reply-To: <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> References: <12F641C3-9FAA-4A3A-BA18-A7302F3A0F5E@cs.huji.ac.il> <20190409095819.c560dbc156c46e5ca0244e3e@bidouilliste.com> <23A47048-642A-481C-B7BE-B61E55F82955@cs.huji.ac.il> <20190409171604.GA4581@bluezbox.com> <6119CE3B-6042-4DDC-82BE-B0C0C7ADA838@cs.huji.ac.il> <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il> <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> <64b5598e2c8c7265f89a31b1f191cb1be318788a.camel@freebsd.org> <20190419100502.5546770a5795c20e3f4fa9db@bidouilliste.com> <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il> <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: AA608880B6 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 11:15:22 -0000 On Wed, 24 Apr 2019 13:02:11 +0200 Emmanuel Vadot wrote: > On Fri, 19 Apr 2019 11:35:09 +0300 > Daniel Braniss wrote: > > > > > > > > On 19 Apr 2019, at 11:05, Emmanuel Vadot wrote: > > > > > > On Fri, 19 Apr 2019 10:20:47 +0300 > > > Daniel Braniss > wrote: > > > > > >> > > >> > > >>> On 18 Apr 2019, at 17:19, Ian Lepore wrote: > > >>> > > >>> On Thu, 2019-04-18 at 10:12 +0300, Daniel Braniss wrote: > > >>>>> On 17 Apr 2019, at 23:26, Emmanuel Vadot > > >>>>> wrote: > > >>>>> > > >>>>> On Tue, 16 Apr 2019 09:16:02 +0300 > > >>>>> Daniel Braniss > > > >>>>> wrote: > > >>>>> > > >>>>>> > > >>>>>> > > >>>>>>> On 11 Apr 2019, at 09:56, Daniel Braniss > > >>>>>>> wrote: > > >>>>>>> > > >>>>>>> if no device is connected, I2CRDWR hangs, > > >>>>>>> it also happens with i2c(8) -s, only reboot helps. > > >>>>>>> > > >>>>>>> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed > > >>>>>>> param=2a > > >>>>>>> iichb1: TWSI_WRITE: Writing 0 to 18 > > >>>>>>> iichb1: TWSI_WRITE: Writing 2a to 14 > > >>>>>>> iichb1: TWSI_WRITE: Writing 40 to c > > >>>>>>> iichb1: TWSI_WRITE: Writing c4 to c > > >>>>>>> iichb1: twsi_transfer: transmitting 2 messages > > >>>>>>> iichb1: TWSI_READ: read f8 from 10 > > >>>>>>> iichb1: twsi_transfer: status=f8 > > >>>>>>> iichb1: twsi_transfer: msg[0] flags: 0 > > >>>>>>> iichb1: twsi_transfer: msg[0] len: 9 > > >>>>>>> iichb1: TWSI_WRITE: Writing e4 to c So looking at this is seems that the "START condition transmitted" interrupt is never triggered, I'll see to add some type of timeout around the pause_sbt. > > >>>>>>> and now it?s hung > > >>>>>> > > >>>>>> [?] > > >>>>> > > >>>>> I don't see that on my OrangePi One or Pine64-LTS. > > >>>> > > >>>> well, mine is are Nanopi Neo, maybe it?s a dts issue? > > >>>> I also have a orangepi-zero but it will take me some time to make > > >>>> a sdcard > > >> > > >> I managed to boot my OrangePi Zero, and i2c -s has no issues, does not hang. > > >> still, with the latest (r346368) my NanoPi Neo hangs when no i2c device is present, > > >> so what is the difference? or where can I look? > > > > > > Are you using the same i2c controller on both ? > > yes, and have tested with several controllers and nanopies, > > > > > Could you paste somewhere the overlays or dts patches ? > > cat ./allwinner/dts/12/h3-i2c.dtso > > /dts-v1/; > > /plugin/; > > > > //#include "sun8i-h3-nanopi-neo.dts" > > > > / { > > compatible = "allwinner,sun8i-h3"; > > }; > > > > &i2c0 { > > ##frequency = <50000>; > > status = "okay"; > > }; > > > > &i2c1 { > > ##frequency = <50000>; > > status = "okay"; > > }; > > > > > > And you have hang on both i2c0 and i2c1 ? > Also please note that i2c1 pins aren't routed on this PCB, I don't > think that this could/should make the i2c controller hangs but ... > > -- > Emmanuel Vadot > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Apr 24 13:06:58 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41C5A159866A for ; Wed, 24 Apr 2019 13:06:58 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8239E8BD31 for ; Wed, 24 Apr 2019 13:06:57 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 4609C1598669; Wed, 24 Apr 2019 13:06:57 +0000 (UTC) Delivered-To: arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21C6F1598668 for ; Wed, 24 Apr 2019 13:06:57 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 909FF8BD2E; Wed, 24 Apr 2019 13:06:56 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=References:To:Cc:In-Reply-To:Date:Subject:Mime-Version:Content-Type:Message-Id:From; bh=m52kNYvOLrX/3+6pC8MHJfbGouyyeOb+zyk1d26cfn8=; b=kJHKeCzXVysi/F2+0q4WSX9h7GO0QceTM8kCE2hePDTJEyLuBvu+w31ubsE5/bmFPbOi2oQDdGlglcsdDE7DBqKjL7cE2FlfUhPAOxBqQwt2MsbEm6rmNzH5zoev+yLLjiuiIuuMOk1u33AB3ee2xQu0rQel4qGKRQcLooSMP1T+Zds+RrSMd4DJf3qbsA0L7oap1QX9n0G2//GcKHa6DzLNskhcuYRYeHjSfIZRbnysaxXzPnwJ1EUdd8gFkGQ7kWCzuWFCGhcSdaDnPAhb/o6u2+ftQgN4S2xNwNomH1UcYtV0L5vcP2wRlEQ2ZES0fS9UXX16OkI0NW/8EZ/2Yg==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1hJHbj-0007ed-Mf; Wed, 24 Apr 2019 16:06:39 +0300 From: Daniel Braniss Message-Id: <7554C2C1-9FC1-4945-AC1B-2EB115A22D4E@cs.huji.ac.il> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: i2c almost working for me, was Re: i2c still not working for me Date: Wed, 24 Apr 2019 16:06:39 +0300 In-Reply-To: <20190424131517.140d6d4839d2435e08b67d43@bidouilliste.com> Cc: "freebsd-arm@freebsd.org" , Ian Lepore To: Emmanuel Vadot References: <12F641C3-9FAA-4A3A-BA18-A7302F3A0F5E@cs.huji.ac.il> <20190409095819.c560dbc156c46e5ca0244e3e@bidouilliste.com> <23A47048-642A-481C-B7BE-B61E55F82955@cs.huji.ac.il> <20190409171604.GA4581@bluezbox.com> <6119CE3B-6042-4DDC-82BE-B0C0C7ADA838@cs.huji.ac.il> <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il> <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> <64b5598e2c8c7265f89a31b1f191cb1be318788a.camel@freebsd.org> <20190419100502.5546770a5795c20e3f4fa9db@bidouilliste.com> <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il> <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> <20190424131517.140d6d4839d2435e08b67d43@bidouilliste.com> X-Mailer: Apple Mail (2.3445.104.8) X-Rspamd-Queue-Id: 909FF8BD2E X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.962,0] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 13:06:58 -0000 > On 24 Apr 2019, at 14:15, Emmanuel Vadot = wrote: >=20 > On Wed, 24 Apr 2019 13:02:11 +0200 > Emmanuel Vadot > = wrote: >=20 >> On Fri, 19 Apr 2019 11:35:09 +0300 >> Daniel Braniss wrote: >>=20 >>>=20 >>>=20 >>>> On 19 Apr 2019, at 11:05, Emmanuel Vadot = wrote: >>>>=20 >>>> On Fri, 19 Apr 2019 10:20:47 +0300 >>>> Daniel Braniss > = wrote: >>>>=20 >>>>>=20 >>>>>=20 >>>>>> On 18 Apr 2019, at 17:19, Ian Lepore wrote: >>>>>>=20 >>>>>> On Thu, 2019-04-18 at 10:12 +0300, Daniel Braniss wrote: >>>>>>>> On 17 Apr 2019, at 23:26, Emmanuel Vadot = >>>>>>>> wrote: >>>>>>>>=20 >>>>>>>> On Tue, 16 Apr 2019 09:16:02 +0300 >>>>>>>> Daniel Braniss > >>>>>>>> wrote: >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>> On 11 Apr 2019, at 09:56, Daniel Braniss = >>>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>> if no device is connected, I2CRDWR hangs,=20 >>>>>>>>>> it also happens with i2c(8) -s, only reboot helps. >>>>>>>>>>=20 >>>>>>>>>> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed >>>>>>>>>> param=3D2a >>>>>>>>>> iichb1: TWSI_WRITE: Writing 0 to 18 >>>>>>>>>> iichb1: TWSI_WRITE: Writing 2a to 14 >>>>>>>>>> iichb1: TWSI_WRITE: Writing 40 to c >>>>>>>>>> iichb1: TWSI_WRITE: Writing c4 to c >>>>>>>>>> iichb1: twsi_transfer: transmitting 2 messages >>>>>>>>>> iichb1: TWSI_READ: read f8 from 10 >>>>>>>>>> iichb1: twsi_transfer: status=3Df8 >>>>>>>>>> iichb1: twsi_transfer: msg[0] flags: 0 >>>>>>>>>> iichb1: twsi_transfer: msg[0] len: 9 >>>>>>>>>> iichb1: TWSI_WRITE: Writing e4 to c >=20 > So looking at this is seems that the "START condition transmitted" > interrupt is never triggered, I'll see to add some type of timeout > around the pause_sbt. GREAT! I was about to send you a Nanopi-neo =E2=80=A6,=20 I might just do that if you send me an address. danny >=20 >>>>>>>>>> and now it?s hung >>>>>>>>>=20 >>>>>>>>> [?] >>>>>>>>=20 >>>>>>>> I don't see that on my OrangePi One or Pine64-LTS. >>>>>>>=20 >>>>>>> well, mine is are Nanopi Neo, maybe it?s a dts issue? >>>>>>> I also have a orangepi-zero but it will take me some time to = make >>>>>>> a sdcard >>>>>=20 >>>>> I managed to boot my OrangePi Zero, and i2c -s has no issues, does = not hang. >>>>> still, with the latest (r346368) my NanoPi Neo hangs when no i2c = device is present, >>>>> so what is the difference? or where can I look? >>>>=20 >>>> Are you using the same i2c controller on both ? >>> yes, and have tested with several controllers and nanopies,=20 >>>=20 >>>> Could you paste somewhere the overlays or dts patches ? >>> cat ./allwinner/dts/12/h3-i2c.dtso >>> /dts-v1/; >>> /plugin/; >>>=20 >>> //#include "sun8i-h3-nanopi-neo.dts" >>>=20 >>> / { >>> compatible =3D "allwinner,sun8i-h3"; >>> }; >>>=20 >>> &i2c0 { >>> ##frequency =3D <50000>; >>> status =3D "okay"; >>> }; >>>=20 >>> &i2c1 { >>> ##frequency =3D <50000>; >>> status =3D "okay"; >>> }; >>>=20 >>>=20 >>=20 >> And you have hang on both i2c0 and i2c1 ? >> Also please note that i2c1 pins aren't routed on this PCB, I don't >> think that this could/should make the i2c controller hangs but ... >>=20 >> --=20 >> Emmanuel Vadot >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm = >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org = " >=20 >=20 > --=20 > Emmanuel Vadot > = > From owner-freebsd-arm@freebsd.org Wed Apr 24 19:24:53 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C07415A100E for ; Wed, 24 Apr 2019 19:24:53 +0000 (UTC) (envelope-from brett@lariat.net) Received: from mail.lariat.net (mail.lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 4AEE775713 for ; Wed, 24 Apr 2019 19:24:52 +0000 (UTC) (envelope-from brett@lariat.net) Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@localhost [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id MAA22188 for ; Wed, 24 Apr 2019 12:46:04 -0600 (MDT) Message-Id: <201904241846.MAA22188@mail.lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 24 Apr 2019 12:43:19 -0600 To: freebsd-arm@freebsd.org From: Brett Glass Subject: Build of FreeBSD-ARM for EspressoBIN Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Rspamd-Queue-Id: 4AEE775713 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of brett@lariat.net designates 66.62.230.51 as permitted sender) smtp.mailfrom=brett@lariat.net X-Spamd-Result: default: False [-0.52 / 15.00]; ARC_NA(0.00)[]; SUBJECT_ENDS_SPACES(0.50)[]; NEURAL_HAM_MEDIUM(-0.71)[-0.709,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.86)[-0.864,0]; DMARC_NA(0.00)[lariat.net]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[secondarymx.lariat.net]; NEURAL_SPAM_SHORT(0.27)[0.271,0]; IP_SCORE(-0.01)[country: US(-0.06)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:19092, ipnet:66.62.228.0/22, country:US]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2019 19:24:53 -0000 Everyone: I see that FreeBSD is up and running on the EspressoBIN board. In fact, it's being sold as part of a shipping product (see https://www.netgate.com/solutions/pfsense/sg-1100.html for a description), so it must be pretty solid. But I don't see a build for that board in the snapshots. Which one should I use if I'd like to try running FreeBSD on the EspressoBIN? Or do I need to do a custom build? --Brett Glass From owner-freebsd-arm@freebsd.org Thu Apr 25 07:37:18 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD474158F231 for ; Thu, 25 Apr 2019 07:37:17 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6ABCF6E9D4 for ; Thu, 25 Apr 2019 07:37:16 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 2B102158F22F; Thu, 25 Apr 2019 07:37:16 +0000 (UTC) Delivered-To: arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3184158F227 for ; Thu, 25 Apr 2019 07:37:15 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F4556E9D1; Thu, 25 Apr 2019 07:37:15 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=/geUD37d9UL10TqZhoRylx9scKLi9/Ok2kYeBGXbK+g=; b=HUgKvZrU5/DZTJeu8tsyXJiV0Xvi2LIreYplm5dzRDi3piuaTQdEYf7WU4/1CHvugwNQ2rRpjnGNBZJhrlv6Hnb9OxSoneHGGrILKsOjCUmNxYM+DCdMlGWejLkaJk7QW3UbTDtO9O5uIKHZuj6VnGejVr/s4xmMU1DQisAmv4PHBDJj07D87ci8AMMIEsP1tHEMKCuIRiMICLK5ZHschhgs11JagULw6EtkeRxUxBxV4E2auC1BQ6RootHlGCZ6snDUCgOVGj+uVnplNHhI75sDeDhpAxtJ4feeVktRcqKwWG2OeSRs7aUJPXiYRsJx+1PrprKERKRkXoNRUVbhug==; Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1hJYwL-0005ws-IF; Thu, 25 Apr 2019 10:37:05 +0300 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: i2c almost working for me, was Re: i2c still not working for me From: Daniel Braniss In-Reply-To: <7554C2C1-9FC1-4945-AC1B-2EB115A22D4E@cs.huji.ac.il> Date: Thu, 25 Apr 2019 10:37:05 +0300 Cc: "freebsd-arm@freebsd.org" , Ian Lepore Content-Transfer-Encoding: quoted-printable Message-Id: References: <12F641C3-9FAA-4A3A-BA18-A7302F3A0F5E@cs.huji.ac.il> <20190409095819.c560dbc156c46e5ca0244e3e@bidouilliste.com> <23A47048-642A-481C-B7BE-B61E55F82955@cs.huji.ac.il> <20190409171604.GA4581@bluezbox.com> <6119CE3B-6042-4DDC-82BE-B0C0C7ADA838@cs.huji.ac.il> <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il> <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> <64b5598e2c8c7265f89a31b1f191cb1be318788a.camel@freebsd.org> <20190419100502.5546770a5795c20e3f4fa9db@bidouilliste.com> <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il> <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> <20190424131517.140d6d4839d2435e08b67d43@bidouilliste.com> <7554C2C1-9FC1-4945-AC1B-2EB115A22D4E@cs.huji.ac.il> To: Emmanuel Vadot X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: 6F4556E9D1 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.92 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.923,0] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2019 07:37:18 -0000 > On 24 Apr 2019, at 16:06, Daniel Braniss wrote: >=20 >=20 >=20 >> On 24 Apr 2019, at 14:15, Emmanuel Vadot = wrote: >>=20 >> On Wed, 24 Apr 2019 13:02:11 +0200 >> Emmanuel Vadot > = wrote: >>=20 >>> On Fri, 19 Apr 2019 11:35:09 +0300 >>> Daniel Braniss wrote: >>>=20 >>>>=20 >>>>=20 >>>>> On 19 Apr 2019, at 11:05, Emmanuel Vadot = wrote: >>>>>=20 >>>>> On Fri, 19 Apr 2019 10:20:47 +0300 >>>>> Daniel Braniss > = wrote: >>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> On 18 Apr 2019, at 17:19, Ian Lepore wrote: >>>>>>>=20 >>>>>>> On Thu, 2019-04-18 at 10:12 +0300, Daniel Braniss wrote: >>>>>>>>> On 17 Apr 2019, at 23:26, Emmanuel Vadot = >>>>>>>>> wrote: >>>>>>>>>=20 >>>>>>>>> On Tue, 16 Apr 2019 09:16:02 +0300 >>>>>>>>> Daniel Braniss > >>>>>>>>> wrote: >>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>> On 11 Apr 2019, at 09:56, Daniel Braniss = >>>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>> if no device is connected, I2CRDWR hangs,=20 >>>>>>>>>>> it also happens with i2c(8) -s, only reboot helps. >>>>>>>>>>>=20 >>>>>>>>>>> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed >>>>>>>>>>> param=3D2a >>>>>>>>>>> iichb1: TWSI_WRITE: Writing 0 to 18 >>>>>>>>>>> iichb1: TWSI_WRITE: Writing 2a to 14 >>>>>>>>>>> iichb1: TWSI_WRITE: Writing 40 to c >>>>>>>>>>> iichb1: TWSI_WRITE: Writing c4 to c >>>>>>>>>>> iichb1: twsi_transfer: transmitting 2 messages >>>>>>>>>>> iichb1: TWSI_READ: read f8 from 10 >>>>>>>>>>> iichb1: twsi_transfer: status=3Df8 >>>>>>>>>>> iichb1: twsi_transfer: msg[0] flags: 0 >>>>>>>>>>> iichb1: twsi_transfer: msg[0] len: 9 >>>>>>>>>>> iichb1: TWSI_WRITE: Writing e4 to c >>=20 >> So looking at this is seems that the "START condition transmitted" >> interrupt is never triggered, I'll see to add some type of timeout >> around the pause_sbt. >=20 > GREAT! I was about to send you a Nanopi-neo =E2=80=A6,=20 > I might just do that if you send me an address. >=20 this patch is not that elegant, but works for me: Index: twsi.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- twsi.c (revision 346538) +++ twsi.c (working copy) @@ -458,8 +458,15 @@ if (sc->msg->len =3D=3D 1) sc->control_val &=3D ~TWSI_CONTROL_ACK; TWSI_WRITE(sc, sc->reg_control, sc->control_val | = TWSI_CONTROL_START); - while (sc->error =3D=3D 0 && sc->transfer !=3D 0) { - pause_sbt("twsi", SBT_1MS * 30, SBT_1MS, 0); + { + int count =3D 10; + while (sc->error =3D=3D 0 && sc->transfer !=3D = 0) { + pause_sbt("twsi", SBT_1MS * 30, = SBT_1MS, 0); + if(count-- =3D=3D 0) { + sc->error =3D EDEADLK; + break; + } + } } debugf(dev, "Done with msg[%d]\n", i); > danny >=20 >>=20 >>>>>>>>>>> and now it?s hung >>>>>>>>>>=20 >>>>>>>>>> [?] >>>>>>>>>=20 >>>>>>>>> I don't see that on my OrangePi One or Pine64-LTS. >>>>>>>>=20 >>>>>>>> well, mine is are Nanopi Neo, maybe it?s a dts issue? >>>>>>>> I also have a orangepi-zero but it will take me some time to = make >>>>>>>> a sdcard >>>>>>=20 >>>>>> I managed to boot my OrangePi Zero, and i2c -s has no issues, = does not hang. >>>>>> still, with the latest (r346368) my NanoPi Neo hangs when no i2c = device is present, >>>>>> so what is the difference? or where can I look? >>>>>=20 >>>>> Are you using the same i2c controller on both ? >>>> yes, and have tested with several controllers and nanopies,=20 >>>>=20 >>>>> Could you paste somewhere the overlays or dts patches ? >>>> cat ./allwinner/dts/12/h3-i2c.dtso >>>> /dts-v1/; >>>> /plugin/; >>>>=20 >>>> //#include "sun8i-h3-nanopi-neo.dts" >>>>=20 >>>> / { >>>> compatible =3D "allwinner,sun8i-h3"; >>>> }; >>>>=20 >>>> &i2c0 { >>>> ##frequency =3D <50000>; >>>> status =3D "okay"; >>>> }; >>>>=20 >>>> &i2c1 { >>>> ##frequency =3D <50000>; >>>> status =3D "okay"; >>>> }; >>>>=20 >>>>=20 >>>=20 >>> And you have hang on both i2c0 and i2c1 ? >>> Also please note that i2c1 pins aren't routed on this PCB, I don't >>> think that this could/should make the i2c controller hangs but ... >>>=20 >>> --=20 >>> Emmanuel Vadot >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing = list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm = >>> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org = " >>=20 >>=20 >> --=20 >> Emmanuel Vadot > = > >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu Apr 25 08:15:25 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31407158FE70 for ; Thu, 25 Apr 2019 08:15:25 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 918F96FA4B; Thu, 25 Apr 2019 08:15:23 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x534.google.com with SMTP id d55so18372814ede.0; Thu, 25 Apr 2019 01:15:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YewK572kxAqeB2ln/j5PC4kXGbXdKYayvfHw9nFjCOU=; b=Qsl50EoLNBaWalsd3MzGt7GRT8EHNPy6iKk88kFqcyI9sqXzCTvGUpV1oRGvy8ZgFt NelkEUSd3876cniqZnebANgLH4GbKunayLIFFdhehVF7b1AJVOe+NsW45udqWR1RZAvy rg4EmN9a4yB2iWQy8g58Tu0WNcwZWtsQdNg3CNzGlljVWTgjc3+atUx7ebCXNSMN50TM mm3MRGOsv43ZYU+ZCpt7H42CaycIThs/6++oijmG1JfysYSgcqxvcJ8jP7ChsIp7nLsZ pblAfB6W3hSgsN0C/9cyJo+jmowufSukspYqWjZZtCOhs+C3a4OY1DtVHBOavzBJ9ubN eYug== 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=YewK572kxAqeB2ln/j5PC4kXGbXdKYayvfHw9nFjCOU=; b=JqH0yixkpLttOqYwOkKaT96Qd3i71LvGrnIqojemF8XFcMkGnsacoBx9AjxLCMnczQ Bd4hs2rVgRcan1PsBPLvhyNH4nUQbxOAOC3Yuso753E6csUJAu8F8kE2DPJpk0JOkZm3 4rGs+iFFg12HkEvJRGODVpkBUiPsBf3c0W/7LPu2DH+zgicvESrIsnOQDfB1mvps69H9 yQxRyntkF5QpO3ZLaLBUBy2VeDjPe+QK56UaHuTQx8JzgSqEzLf9tMmVbuX0R91wgpx8 aJdUdCopypxMJ3ZYTARs3Vc4J9LKT+cJxhcOB8mdzvTDrgPEn/FQuKB9A/GWdxES1+bS CMHw== X-Gm-Message-State: APjAAAUD34Sy8S9bJ7hc4scl+QnVtRLk//PEBQHDp1mshlYWBs6Sk1on WCbIzANp5XQ9CzGKcKA+ycqGUyOug7WdImp6PrDNHTc3 X-Google-Smtp-Source: APXvYqzj4FdHmVsbzWqYOoxtt+PT+QjGdKNQF3/NdFG2dbxvQDym1ypgfuvYqeQk5uEf+8jBVAHBz6X4TKE+qy3H0Lg= X-Received: by 2002:a50:b48f:: with SMTP id w15mr23606615edd.242.1556180121356; Thu, 25 Apr 2019 01:15:21 -0700 (PDT) MIME-Version: 1.0 References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> <20190423165731.GB10587@lonesome.com> <1995497096.1.1556098457731@localhost> In-Reply-To: <1995497096.1.1556098457731@localhost> From: Balanga Bar Date: Thu, 25 Apr 2019 10:15:05 +0100 Message-ID: Subject: Re: Marvell Kirkwood - anyone? To: Ronald Klop Cc: Ian Lepore , Mark Linimon , freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 918F96FA4B X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Qsl50EoL; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::534 as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-4.52 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[5]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.74)[-0.741,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.77)[ip: (-9.16), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.26), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2019 08:15:25 -0000 It's nice to know that someone has 11.2 working on armv5. Could you let me know how you built it? I installed portsnap under 11.0 but was unable to build anything - will try again with 11.2 to see if I can iron out the problems I've had as I now know someone has it working. On Wed, Apr 24, 2019 at 10:34 AM Ronald Klop wrote: > Dear Balanga, > > I run 11.2 on my Sheevaplug (armv5 also). > > uname -a > FreeBSD sheeva2.klop.ws 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #4 > r339336M: Sat Oct 13 23:31:51 CEST 2018 builder@rpi3:/data/src/obj-11.2/arm.arm/data/src/11.2/sys/SHEEVAPLUG > arm > > It has a ports checkout using portsnap. And that works pretty well. > Just do: > portsnap auto > cd /usr/ports/shells/bash (or whatever port you wish to install) > make install > make clean > > I think that is the most simple approach for you to go forward. > > Regards, > Ronald. > > PS: Sorry for top-posting, my current mail client does not help in this > very well. > > > *Van:* Balanga Bar > *Datum:* dinsdag, 23 april 2019 20:08 > *Aan:* Mark Linimon > *CC:* freebsd-arm@freebsd.org, Ian Lepore > *Onderwerp:* Re: Marvell Kirkwood - anyone? > > Actually I have managed to build FreeBSD 11.0-RELEASE on ARM and it has not > exhibited any problems on my GoFlexHome apart from being unable install > pkgs. That is the current focus at the moment. > > On Tue, Apr 23, 2019 at 5:57 PM Mark Linimon wrote: > > > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: > > > Is it possible to get a version of portsnap from that point? > > > > I don't know enough to answer that question. I think it would be fair > > to assume "no". > > > > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up > > and working. I'm going to be honest and say there isn't one. > > > > Here are the approaches I think you can take: > > > > - stay on 8.x; bring individual port updates to it from ports-head and > > build your own ports. Difficulty: hard. > > > > - figure out what src changes after 8.x regressed Kirkwood; check > > out src 12-STABLE, build your own src, and use FreeBSD.org packages. > > Difficulty: expert. > > > > - stay on 8.x; attempt to bring a modern ports tree to it and build > > your own ports. Difficulty: challenging. > > > > The difficulty level of the first approach depends on which ports you > > are going to try to use. shells/bash? Probably not too hard. Anything > > GUI-related? Very hard. > > > > None of these approaches are achievable within hours; they will take > > days, or, in the case of the third approach, weeks. > > > > fwiw, the second approach is the only one where your fixes could be > > merged back into FreeBSD. If I were personally determined to run > > Kirkwoord, that's the approach I would take. (I gave my GuruPlug > > away some time ago.) > > > > I'm sorry that I can't be more encouraging. > > > > mcl > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > ------------------------------ > > From owner-freebsd-arm@freebsd.org Thu Apr 25 13:01:52 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8ED3A15968A7 for ; Thu, 25 Apr 2019 13:01:52 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A831683A1D for ; Thu, 25 Apr 2019 13:01:51 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6901D15968A3; Thu, 25 Apr 2019 13:01:51 +0000 (UTC) Delivered-To: arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44EEC159689F for ; Thu, 25 Apr 2019 13:01:51 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AAC9683A17; Thu, 25 Apr 2019 13:01:50 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id e216026c; Thu, 25 Apr 2019 15:01:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=QHfoIjPwQzjDQ87bWaE3PZ6yDQE=; b=qWA1OypfEVUCa/7V2Q6tB+igJ9NF g9GgrZyeu+h3qv9yX3IKkKkLjXooWCQU+TgIeNuL4r/xs+1IBK8znSF4yLZvwJ0m 9wUbaIeOzCl6dcVYMt3EDV8sFeHbSh3Szdz+H2A98K4VGs0rCaOWJuiy/IA1X0JC m3mw2cHcCU2ikLM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=WwTcexuz7AqkT7lyFpeyEFm71VaPoIz/5m2yvkJpJPhqgUWeIq1E4nMQ JQZX/4wtAuxDWDu3dlM4xq4WHKxrQb8/Hy3rK/Q+t5mH+cc6m1A6VmeZBk+DzFjB nfRSLXsJ0LR2z6Wf2ApBfkXUZopVFfyBXjz0P5BLuF8tqiPg4HI= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id b6a8c6fb TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 25 Apr 2019 15:01:43 +0200 (CEST) Date: Thu, 25 Apr 2019 15:01:42 +0200 From: Emmanuel Vadot To: Daniel Braniss Cc: "freebsd-arm@freebsd.org" , Ian Lepore Subject: Re: i2c almost working for me, was Re: i2c still not working for me Message-Id: <20190425150142.bab9fb212c6c7704fdf950d8@bidouilliste.com> In-Reply-To: References: <12F641C3-9FAA-4A3A-BA18-A7302F3A0F5E@cs.huji.ac.il> <20190409095819.c560dbc156c46e5ca0244e3e@bidouilliste.com> <23A47048-642A-481C-B7BE-B61E55F82955@cs.huji.ac.il> <20190409171604.GA4581@bluezbox.com> <6119CE3B-6042-4DDC-82BE-B0C0C7ADA838@cs.huji.ac.il> <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il> <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> <64b5598e2c8c7265f89a31b1f191cb1be318788a.camel@freebsd.org> <20190419100502.5546770a5795c20e3f4fa9db@bidouilliste.com> <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il> <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> <20190424131517.140d6d4839d2435e08b67d43@bidouilliste.com> <7554C2C1-9FC1-4945-AC1B-2EB115A22D4E@cs.huji.ac.il> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: AAC9683A17 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.963,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2019 13:01:52 -0000 On Thu, 25 Apr 2019 10:37:05 +0300 Daniel Braniss wrote: >=20 >=20 > > On 24 Apr 2019, at 16:06, Daniel Braniss wrote: > >=20 > >=20 > >=20 > >> On 24 Apr 2019, at 14:15, Emmanuel Vadot wrote: > >>=20 > >> On Wed, 24 Apr 2019 13:02:11 +0200 > >> Emmanuel Vadot > = wrote: > >>=20 > >>> On Fri, 19 Apr 2019 11:35:09 +0300 > >>> Daniel Braniss wrote: > >>>=20 > >>>>=20 > >>>>=20 > >>>>> On 19 Apr 2019, at 11:05, Emmanuel Vadot wr= ote: > >>>>>=20 > >>>>> On Fri, 19 Apr 2019 10:20:47 +0300 > >>>>> Daniel Braniss > w= rote: > >>>>>=20 > >>>>>>=20 > >>>>>>=20 > >>>>>>> On 18 Apr 2019, at 17:19, Ian Lepore wrote: > >>>>>>>=20 > >>>>>>> On Thu, 2019-04-18 at 10:12 +0300, Daniel Braniss wrote: > >>>>>>>>> On 17 Apr 2019, at 23:26, Emmanuel Vadot > >>>>>>>>> wrote: > >>>>>>>>>=20 > >>>>>>>>> On Tue, 16 Apr 2019 09:16:02 +0300 > >>>>>>>>> Daniel Braniss > > >>>>>>>>> wrote: > >>>>>>>>>=20 > >>>>>>>>>>=20 > >>>>>>>>>>=20 > >>>>>>>>>>> On 11 Apr 2019, at 09:56, Daniel Braniss > >>>>>>>>>>> wrote: > >>>>>>>>>>>=20 > >>>>>>>>>>> if no device is connected, I2CRDWR hangs,=20 > >>>>>>>>>>> it also happens with i2c(8) -s, only reboot helps. > >>>>>>>>>>>=20 > >>>>>>>>>>> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed > >>>>>>>>>>> param=3D2a > >>>>>>>>>>> iichb1: TWSI_WRITE: Writing 0 to 18 > >>>>>>>>>>> iichb1: TWSI_WRITE: Writing 2a to 14 > >>>>>>>>>>> iichb1: TWSI_WRITE: Writing 40 to c > >>>>>>>>>>> iichb1: TWSI_WRITE: Writing c4 to c > >>>>>>>>>>> iichb1: twsi_transfer: transmitting 2 messages > >>>>>>>>>>> iichb1: TWSI_READ: read f8 from 10 > >>>>>>>>>>> iichb1: twsi_transfer: status=3Df8 > >>>>>>>>>>> iichb1: twsi_transfer: msg[0] flags: 0 > >>>>>>>>>>> iichb1: twsi_transfer: msg[0] len: 9 > >>>>>>>>>>> iichb1: TWSI_WRITE: Writing e4 to c > >>=20 > >> So looking at this is seems that the "START condition transmitted" > >> interrupt is never triggered, I'll see to add some type of timeout > >> around the pause_sbt. > >=20 > > GREAT! I was about to send you a Nanopi-neo ?,=20 > > I might just do that if you send me an address. > >=20 > this patch is not that elegant, but works for me: > Index: twsi.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- twsi.c (revision 346538) > +++ twsi.c (working copy) > @@ -458,8 +458,15 @@ > if (sc->msg->len =3D=3D 1) > sc->control_val &=3D ~TWSI_CONTROL_ACK; > TWSI_WRITE(sc, sc->reg_control, sc->control_val | TWSI_CONTROL_START); > - while (sc->error =3D=3D 0 && sc->transfer !=3D 0) { > - pause_sbt("twsi", SBT_1MS * 30, SBT_1MS, 0); > + { > + int count =3D 10; > + while (sc->error =3D=3D 0 && sc->transfer !=3D 0) { > + pause_sbt("twsi", SBT_1MS * 30, SBT_1MS, 0); > + if(count-- =3D=3D 0) { > + sc->error =3D EDEADLK; > + break; > + } > + } > } >=20 > debugf(dev, "Done with msg[%d]\n", i); I think that pause_sbt returns non-zero if the time has elapsed so check this will possibly be enough. I'm more interested on why the controller didn't triggered an interrupt. > > danny > >=20 > >>=20 > >>>>>>>>>>> and now it?s hung > >>>>>>>>>>=20 > >>>>>>>>>> [?] > >>>>>>>>>=20 > >>>>>>>>> I don't see that on my OrangePi One or Pine64-LTS. > >>>>>>>>=20 > >>>>>>>> well, mine is are Nanopi Neo, maybe it?s a dts issue? > >>>>>>>> I also have a orangepi-zero but it will take me some time to make > >>>>>>>> a sdcard > >>>>>>=20 > >>>>>> I managed to boot my OrangePi Zero, and i2c -s has no issues, does= not hang. > >>>>>> still, with the latest (r346368) my NanoPi Neo hangs when no i2c d= evice is present, > >>>>>> so what is the difference? or where can I look? > >>>>>=20 > >>>>> Are you using the same i2c controller on both ? > >>>> yes, and have tested with several controllers and nanopies,=20 > >>>>=20 > >>>>> Could you paste somewhere the overlays or dts patches ? > >>>> cat ./allwinner/dts/12/h3-i2c.dtso > >>>> /dts-v1/; > >>>> /plugin/; > >>>>=20 > >>>> //#include "sun8i-h3-nanopi-neo.dts" > >>>>=20 > >>>> / { > >>>> compatible =3D "allwinner,sun8i-h3"; > >>>> }; > >>>>=20 > >>>> &i2c0 { > >>>> ##frequency =3D <50000>; > >>>> status =3D "okay"; > >>>> }; > >>>>=20 > >>>> &i2c1 { > >>>> ##frequency =3D <50000>; > >>>> status =3D "okay"; > >>>> }; > >>>>=20 > >>>>=20 > >>>=20 > >>> And you have hang on both i2c0 and i2c1 ? > >>> Also please note that i2c1 pins aren't routed on this PCB, I don't > >>> think that this could/should make the i2c controller hangs but ... > >>>=20 > >>> --=20 > >>> Emmanuel Vadot > >>> _______________________________________________ > >>> freebsd-arm@freebsd.org mailing list > >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org= " > >>=20 > >>=20 > >> --=20 > >> Emmanuel Vadot > = > > >=20 > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Apr 25 13:29:14 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ABA3159737E for ; Thu, 25 Apr 2019 13:29:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A3EC9849AF for ; Thu, 25 Apr 2019 13:29:13 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 67D011597378; Thu, 25 Apr 2019 13:29:13 +0000 (UTC) Delivered-To: arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07E841597376 for ; Thu, 25 Apr 2019 13:29:13 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1BA55849A3; Thu, 25 Apr 2019 13:29:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=References:To:Cc:In-Reply-To:Date:Subject:Mime-Version:Content-Type:Message-Id:From; bh=ibWTu3BgWezA+KTSVrjgS3yj0EpRrRgTn2Aqn+gDC64=; b=ZxjxOtmhK6J3SN+3YxLVU6pdU7LV5WDGqNv4xcqVnJK9P7E+vzSnN5XIFuvqRuvoy8tAcJiOw3X63c4wmmDQzYbW8hVTjXk2BqeBkETRmwwcz3UaOQEWJWaiMTk3vHqKIYvWw+aLj4tSXpMmcwVMQnOIoKIcGIOBpNuQvlOjLkVRcYG2PazV2TJeKkRNiurEMDBDZuu15yhVi+qKRNCWkAY4oGB9QQr3uTuBpD2TS3Hb5QO1WgnCJ8OGpwXSG9twWfk1H4eas9NW9yc7YcYrXinglZwmlTEfV1Irz3VvKktbM5zGXGrZnqoqo3Crf/Yu7/E1SRlNmcBwtkKqKyuWWQ==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1hJeQr-000L96-OF; Thu, 25 Apr 2019 16:28:57 +0300 From: Daniel Braniss Message-Id: <6D8540BA-2612-4FB6-B364-5D9D6569CC46@cs.huji.ac.il> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: i2c almost working for me, was Re: i2c still not working for me Date: Thu, 25 Apr 2019 16:28:57 +0300 In-Reply-To: <20190425150142.bab9fb212c6c7704fdf950d8@bidouilliste.com> Cc: "freebsd-arm@freebsd.org" , Ian Lepore To: Emmanuel Vadot References: <12F641C3-9FAA-4A3A-BA18-A7302F3A0F5E@cs.huji.ac.il> <20190409095819.c560dbc156c46e5ca0244e3e@bidouilliste.com> <23A47048-642A-481C-B7BE-B61E55F82955@cs.huji.ac.il> <20190409171604.GA4581@bluezbox.com> <6119CE3B-6042-4DDC-82BE-B0C0C7ADA838@cs.huji.ac.il> <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il> <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> <64b5598e2c8c7265f89a31b1f191cb1be318788a.camel@freebsd.org> <20190419100502.5546770a5795c20e3f4fa9db@bidouilliste.com> <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il> <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> <20190424131517.140d6d4839d2435e08b67d43@bidouilliste.com> <7554C2C1-9FC1-4945-AC1B-2EB115A22D4E@cs.huji.ac.il> <20190425150142.bab9fb212c6c7704fdf950d8@bidouilliste.com> X-Mailer: Apple Mail (2.3445.104.8) X-Rspamd-Queue-Id: 1BA55849A3 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.95 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.95)[-0.954,0] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2019 13:29:14 -0000 > On 25 Apr 2019, at 16:01, Emmanuel Vadot = wrote: >=20 > On Thu, 25 Apr 2019 10:37:05 +0300 > Daniel Braniss > = wrote: >=20 >>=20 >>=20 >>> On 24 Apr 2019, at 16:06, Daniel Braniss = wrote: >>>=20 >>>=20 >>>=20 >>>> On 24 Apr 2019, at 14:15, Emmanuel Vadot = wrote: >>>>=20 >>>> On Wed, 24 Apr 2019 13:02:11 +0200 >>>> Emmanuel Vadot > wrote: >>>>=20 >>>>> On Fri, 19 Apr 2019 11:35:09 +0300 >>>>> Daniel Braniss wrote: >>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> On 19 Apr 2019, at 11:05, Emmanuel Vadot = wrote: >>>>>>>=20 >>>>>>> On Fri, 19 Apr 2019 10:20:47 +0300 >>>>>>> Daniel Braniss > wrote: >>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>> On 18 Apr 2019, at 17:19, Ian Lepore wrote: >>>>>>>>>=20 >>>>>>>>> On Thu, 2019-04-18 at 10:12 +0300, Daniel Braniss wrote: >>>>>>>>>>> On 17 Apr 2019, at 23:26, Emmanuel Vadot = >>>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>> On Tue, 16 Apr 2019 09:16:02 +0300 >>>>>>>>>>> Daniel Braniss > >>>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>> On 11 Apr 2019, at 09:56, Daniel Braniss = >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>=20 >>>>>>>>>>>>> if no device is connected, I2CRDWR hangs,=20 >>>>>>>>>>>>> it also happens with i2c(8) -s, only reboot helps. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with = speed >>>>>>>>>>>>> param=3D2a >>>>>>>>>>>>> iichb1: TWSI_WRITE: Writing 0 to 18 >>>>>>>>>>>>> iichb1: TWSI_WRITE: Writing 2a to 14 >>>>>>>>>>>>> iichb1: TWSI_WRITE: Writing 40 to c >>>>>>>>>>>>> iichb1: TWSI_WRITE: Writing c4 to c >>>>>>>>>>>>> iichb1: twsi_transfer: transmitting 2 messages >>>>>>>>>>>>> iichb1: TWSI_READ: read f8 from 10 >>>>>>>>>>>>> iichb1: twsi_transfer: status=3Df8 >>>>>>>>>>>>> iichb1: twsi_transfer: msg[0] flags: 0 >>>>>>>>>>>>> iichb1: twsi_transfer: msg[0] len: 9 >>>>>>>>>>>>> iichb1: TWSI_WRITE: Writing e4 to c >>>>=20 >>>> So looking at this is seems that the "START condition transmitted" >>>> interrupt is never triggered, I'll see to add some type of timeout >>>> around the pause_sbt. >>>=20 >>> GREAT! I was about to send you a Nanopi-neo ?,=20 >>> I might just do that if you send me an address. >>>=20 >> this patch is not that elegant, but works for me: >> Index: twsi.c >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- twsi.c (revision 346538) >> +++ twsi.c (working copy) >> @@ -458,8 +458,15 @@ >> if (sc->msg->len =3D=3D 1) >> sc->control_val &=3D ~TWSI_CONTROL_ACK; >> TWSI_WRITE(sc, sc->reg_control, sc->control_val | = TWSI_CONTROL_START); >> - while (sc->error =3D=3D 0 && sc->transfer !=3D 0) { >> - pause_sbt("twsi", SBT_1MS * 30, SBT_1MS, 0); >> + { >> + int count =3D 10; >> + while (sc->error =3D=3D 0 && sc->transfer !=3D = 0) { >> + pause_sbt("twsi", SBT_1MS * 30, = SBT_1MS, 0); >> + if(count-- =3D=3D 0) { >> + sc->error =3D EDEADLK; >> + break; >> + } >> + } >> } >>=20 >> debugf(dev, "Done with msg[%d]\n", i); >=20 > I think that pause_sbt returns non-zero if the time has elapsed so > check this will possibly be enough. > I'm more interested on why the controller didn't triggered an > interrupt. from my signal analyser I can see that nothing is xmitted, may be this a = clue? >=20 >>> danny >>>=20 >>>>=20 >>>>>>>>>>>>> and now it?s hung >>>>>>>>>>>>=20 >>>>>>>>>>>> [?] >>>>>>>>>>>=20 >>>>>>>>>>> I don't see that on my OrangePi One or Pine64-LTS. >>>>>>>>>>=20 >>>>>>>>>> well, mine is are Nanopi Neo, maybe it?s a dts issue? >>>>>>>>>> I also have a orangepi-zero but it will take me some time to = make >>>>>>>>>> a sdcard >>>>>>>>=20 >>>>>>>> I managed to boot my OrangePi Zero, and i2c -s has no issues, = does not hang. >>>>>>>> still, with the latest (r346368) my NanoPi Neo hangs when no = i2c device is present, >>>>>>>> so what is the difference? or where can I look? >>>>>>>=20 >>>>>>> Are you using the same i2c controller on both ? >>>>>> yes, and have tested with several controllers and nanopies,=20 >>>>>>=20 >>>>>>> Could you paste somewhere the overlays or dts patches ? >>>>>> cat ./allwinner/dts/12/h3-i2c.dtso >>>>>> /dts-v1/; >>>>>> /plugin/; >>>>>>=20 >>>>>> //#include "sun8i-h3-nanopi-neo.dts" >>>>>>=20 >>>>>> / { >>>>>> compatible =3D "allwinner,sun8i-h3"; >>>>>> }; >>>>>>=20 >>>>>> &i2c0 { >>>>>> ##frequency =3D <50000>; >>>>>> status =3D "okay"; >>>>>> }; >>>>>>=20 >>>>>> &i2c1 { >>>>>> ##frequency =3D <50000>; >>>>>> status =3D "okay"; >>>>>> }; >>>>>>=20 >>>>>>=20 >>>>>=20 >>>>> And you have hang on both i2c0 and i2c1 ? >>>>> Also please note that i2c1 pins aren't routed on this PCB, I don't >>>>> think that this could/should make the i2c controller hangs but ... >>>>>=20 >>>>> --=20 >>>>> Emmanuel Vadot >>>>> _______________________________________________ >>>>> freebsd-arm@freebsd.org mailing = list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm = >>>>> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org = " >>>>=20 >>>>=20 >>>> --=20 >>>> Emmanuel Vadot > > >>>=20 >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" >=20 >=20 > --=20 > Emmanuel Vadot > = > From owner-freebsd-arm@freebsd.org Thu Apr 25 14:01:26 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDD231597EE6 for ; Thu, 25 Apr 2019 14:01:26 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D774D85C2F; Thu, 25 Apr 2019 14:01:24 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1hJew9-0007EH-Qt; Thu, 25 Apr 2019 16:01:18 +0200 To: "Balanga Bar" Cc: "Ian Lepore" , "Mark Linimon" , freebsd-arm@freebsd.org Subject: Re: Marvell Kirkwood - anyone? References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> <20190423165731.GB10587@lonesome.com> <1995497096.1.1556098457731@localhost> Date: Thu, 25 Apr 2019 16:01:16 +0200 MIME-Version: 1.0 From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50, HTML_MESSAGE autolearn=disabled version=3.4.2 X-Scan-Signature: b0934c0b55c3f104c7e65211ad8f1ad7 X-Rspamd-Queue-Id: D774D85C2F X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 195.190.28.88 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-1.08 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.988,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:195.190.28.64/27]; NEURAL_HAM_LONG(-0.93)[-0.931,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain,multipart/related]; DMARC_NA(0.00)[klop.ws]; TO_DN_SOME(0.00)[]; URI_COUNT_ODD(1.00)[5]; MIME_TRACE(0.00)[0:+,1:+,2:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[mx2.greenhost.nl,mx1.greenhost.nl]; NEURAL_HAM_SHORT(-0.79)[-0.790,0]; IP_SCORE(-0.56)[ip: (-1.89), ipnet: 195.190.28.0/24(-0.53), asn: 47172(-0.41), country: NL(0.01)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:47172, ipnet:195.190.28.0/24, country:NL]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2019 14:01:27 -0000 On Thu, 25 Apr 2019 11:15:05 +0200, Balanga Bar wrote: > It's nice to know that someone has 11.2 working on armv5. Could you let > me know how you built it? I cross-compiled on amd64. cd /usr/src (containing the 11.2 sources of course) export TARGET_ARCH=arm export KERNCONF=SHEEVAPLUG export DESTDIR=/mnt/usbdisk (here the usb stick is mounted) make buildworld make buildkernel cp /usr/obj/arm.arm/usr/src/sys/SHEEVAPLUG/kernel.bin $DESTDIR/boot/msdos/ make installworld make distribution From the top of my head, so I might have missed something. > > I installed portsnap under 11.0 but was unable to build anything - will > try again with 11.2 to see if I can iron out the problems I've >had as I > now know someone has it working. "Unable to build" is not very specific. It helps if you copy paste the actual error message. Ronald. > > On Wed, Apr 24, 2019 at 10:34 AM Ronald Klop > wrote: >> Dear Balanga, >> >> I run 11.2 on my Sheevaplug (armv5 also). >> >> uname -a >> FreeBSD sheeva2.klop.ws 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #4 >> r339336M: Sat Oct 13 23:31:51 CEST 2018 >> >>builder@rpi3:/data/src/obj-11.2/arm.arm/data/src/11.2/sys/SHEEVAPLUG >> arm >> >> It has a ports checkout using portsnap. And that works pretty well. >> Just do: >> portsnap auto >> cd /usr/ports/shells/bash (or whatever port you wish to install) >> make install >> make clean >> >> I think that is the most simple approach for you to go forward. >> >> Regards, >> Ronald. >> >> PS: Sorry for top-posting, my current mail client does not help in this >> very well. >> >> Van: Balanga Bar >> Datum: dinsdag, 23 april 2019 20:08 >> Aan: Mark Linimon >> CC: freebsd-arm@freebsd.org, Ian Lepore >> Onderwerp: Re: Marvell Kirkwood - anyone? >>> Actually I have managed to build FreeBSD 11.0-RELEASE on ARM and it >>> has not >>> exhibited any problems on my GoFlexHome apart from being unable install >>> pkgs. That is the current focus at the moment. >>> >>> On Tue, Apr 23, 2019 at 5:57 PM Mark Linimon >>> wrote: >>> >>>> On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: >>>> > Is it possible to get a version of portsnap from that point? >>>> >>>> I don't know enough to answer that question. I think it would be fair >>>> to assume "no". >>>> >>>> IIUC you seem to be looking for an _easy_ way to get Kirkwood back up >>>> and working. I'm going to be honest and say there isn't one. >>>> >>>> Here are the approaches I think you can take: >>>> >>>> - stay on 8.x; bring individual port updates to it from ports-head >>>> and >>>> build your own ports. Difficulty: hard. >>>> >>>> - figure out what src changes after 8.x regressed Kirkwood; check >>>> out src 12-STABLE, build your own src, and use FreeBSD.org >>>> packages. >>>> Difficulty: expert. >>>> >>>> - stay on 8.x; attempt to bring a modern ports tree to it and build >>>> your own ports. Difficulty: challenging. >>>> >>>> The difficulty level of the first approach depends on which ports you >>>> are going to try to use. shells/bash? Probably not too hard. >>>> Anything >>>> GUI-related? Very hard. >>>> >>>> None of these approaches are achievable within hours; they will take >>>> days, or, in the case of the third approach, weeks. >>>> >>>> fwiw, the second approach is the only one where your fixes could be >>>> merged back into FreeBSD. If I were personally determined to run >>>> Kirkwoord, that's the approach I would take. (I gave my GuruPlug >>>> away some time ago.) >>>> >>>> I'm sorry that I can't be more encouraging. >>>> >>>> mcl >>>> >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu Apr 25 14:14:03 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF0EA15985BF for ; Thu, 25 Apr 2019 14:14:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A4398657B for ; Thu, 25 Apr 2019 14:14:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D17727714 for ; Thu, 25 Apr 2019 14:14:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3PEE1hd084579 for ; Thu, 25 Apr 2019 14:14:01 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3PEE1Sr084578 for freebsd-arm@FreeBSD.org; Thu, 25 Apr 2019 14:14:01 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 236639] Beaglebone Black: Misaligned cache warning until kernel is loaded (FreeBSD 13.0-CURRENT) Date: Thu, 25 Apr 2019 14:14:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gndaryee@uwaterloo.ca X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2019 14:14:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236639 Gerald Aryeetey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Overcome By Events --- Comment #1 from Gerald Aryeetey --- Closing since I don't see this anymore. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Thu Apr 25 14:50:57 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F7EF159940A for ; Thu, 25 Apr 2019 14:50:57 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x543.google.com (mail-ed1-x543.google.com [IPv6:2a00:1450:4864:20::543]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 4DC2E885A0; Thu, 25 Apr 2019 14:50:56 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x543.google.com with SMTP id k45so138605edb.6; Thu, 25 Apr 2019 07:50:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FE7QH34nnva6axhf99zHhueK/QAt/P8YkU8bXi4DXc8=; b=eQvN1kRxtndEGz9iRiyeoqPYyJYyQ3s2zSu2/+iOtnQNPNPuTWggvHAg3BhocLruTO bhpYHKW19vcTuASXjFtBHwFV+v/w3yu2oq3+ZjN4d9ptKiYBnHv8wJ9JifIB3ZuDOAdg w48S1LcB7mVJEdnUEwqqn710ZdCC7KoRq8t7hFSq3wA/MxLyERQa0mOFFBEbBuqBcS/Y 7jFkMK37NLY8KAv/pqrOJfyeeSiLaQfMcMK7nc6vNlTsbYn+SOeGUUAKvly4WkeBBojJ A4supbKKtVgp2KW+U0K6D8VGWL/LnLWCNbYJM0Yi6pbnU5r4qgP+++RolC8m6916Janq hJxw== 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=FE7QH34nnva6axhf99zHhueK/QAt/P8YkU8bXi4DXc8=; b=kWgRuQhcqtl0Nl1JJ/HuSpihRspsS6zTEQcqXAmMnDuFP/ZxBqb7Dm0NpbacVCL5WI dODkiV4CVoDJL/P8NWoECF8gjCmTyT95D0KMGBFQNuc05FEeNySSlYW2A8b1yFLXowCt +P8Gblaqg0k7xngqDfzj5QcOxSsHnRlvoLHBv9hCefXoA/5pM1ZBQAxQu8iw5J7iOYEo UOh9tLqDLAAD6t0QCckbmxbgC8f/jX/Lu+WKFE7+QC0cOEyMjnFjokX5S9tSAlVfk56p nLbz+0wJWoELe6mZIDkMAIzmE9DoCjXUrUUp4ytZiGF2Oj3+EE9aRTaB+brAFXfpx0Q4 SEWA== X-Gm-Message-State: APjAAAVZLXKZxpbBag5k0ReA2BQerSpO+Sw6OlmP769xg/TaXRH1HGnN WnXHVK7vuj8iYtJpQVGgO51rERv3U5mOMYpEGwWZPEaN X-Google-Smtp-Source: APXvYqxIMq27e/qaIFrKG1mHA/MYtNYXTxR8U+irWLWNu/S5l4KxXKlfhS7VrNzAkHv6h8C+o1cz43v4zf9Hesq7Wzg= X-Received: by 2002:a50:b3a7:: with SMTP id s36mr24185618edd.4.1556203854968; Thu, 25 Apr 2019 07:50:54 -0700 (PDT) MIME-Version: 1.0 References: <26ead64e0e79f5d8f9c882273142dc09d95417a7.camel@freebsd.org> In-Reply-To: From: Balanga Bar Date: Thu, 25 Apr 2019 16:50:38 +0100 Message-ID: Subject: Re: loaderdev To: Ian Lepore Cc: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 4DC2E885A0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=eQvN1kRx; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::543 as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-4.93 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; IP_SCORE(-0.95)[ip: (-0.11), ipnet: 2a00:1450::/32(-2.32), asn: 15169(-2.24), country: US(-0.06)]; NEURAL_HAM_SHORT(-0.97)[-0.968,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2019 14:50:57 -0000 Is it possible to used loaderdev or uEnv.txt to boot different versions of FreeBSD from different slices, ie /dev/da0s2 /dev/da0s3 etc. I'm trying to compare different builds and having them all on one USB stick would be convenient. On Sat, Apr 20, 2019 at 9:22 AM Balanga Bar wrote: > I wondered about FreeBSD being able to access uBoot environment > variables... fw_printenv and fw_setenv are available on Linux, so are > equivalent programs available on FreeBSD? > > On Thu, Apr 18, 2019 at 3:25 PM Ian Lepore wrote: > >> On Thu, 2019-04-18 at 09:30 +0100, Balanga Bar wrote: >> > How does uBoot know how to load ubldr? Is this specific to a particular >> > version of uBoot? I'm using a customised uBoot which lets me boot >> OpenWrt, >> > Debian, Arch Linux or FreeBSD depending on the contents of a USB stick. >> > >> > Currently I have a /boot/uEnv.txt file on a FAT partition which includes >> > >> > bootfile=ubldr >> > >> > Will I no longer need a FAT partition? >> > >> > If loaderdev is set to disk, then where is ubldr loaded from since, >> AFAIK, >> > uBoot can only read FAT or EXT3 partitions? >> > >> >> The convention for freebsd mailing lists is to bottom-post replies, >> mixed top and bottom posting makes for unreadable threads. >> >> The loaderdev variable is not used by uboot at all, it is read from the >> uboot environment by ubldr. Basically, loaderdev just gives you a way >> to control where ubldr finds the kernel by setting a uboot env var >> (interactively or via uenv.txt). >> >> You arrange to have uboot load ubldr in whatever way you're currently >> doing, so you will still need a FAT partition, because uboot can't read >> UFS filesystems. >> >> -- Ian >> >> From owner-freebsd-arm@freebsd.org Fri Apr 26 06:59:29 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 651F0158B2FF for ; Fri, 26 Apr 2019 06:59:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E634E86206 for ; Fri, 26 Apr 2019 06:59:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 28A3110877 for ; Fri, 26 Apr 2019 06:59:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3Q6xRbE064099 for ; Fri, 26 Apr 2019 06:59:27 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3Q6xRTw064098 for freebsd-arm@FreeBSD.org; Fri, 26 Apr 2019 06:59:27 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 237571] regression with commit r344894 for H5 based Allwinners Date: Fri, 26 Apr 2019 06:59:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@justmail.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2019 06:59:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237571 Bug ID: 237571 Summary: regression with commit r344894 for H5 based Allwinners Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: freebsd@justmail.de Created attachment 204025 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D204025&action= =3Dedit Bootlog Commit r344894 introduced a driver for CCU DE2 hardware on Allwinner based devices. On the Allwinner Nanopi NEO2 it gets probed but fails to gather pa= rent clock sources and panics (see attached log) If the device is explicitly deactivated (add status =3D "disabled" in dts f= ile) the boot continues. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Sat Apr 27 08:44:44 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48CF8158A15D for ; Sat, 27 Apr 2019 08:44:44 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 D615F755C1; Sat, 27 Apr 2019 08:44:42 +0000 (UTC) (envelope-from balanga.bar@gmail.com) Received: by mail-ed1-x529.google.com with SMTP id d46so5060417eda.7; Sat, 27 Apr 2019 01:44:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Yg0gGv6WumZLnkc1nKWQqFzpSI1UjVt2phjnB8N1znw=; b=ijlc7PZPo6o01xPsjJFPaaKCijdSEnGzVm6MmMtxwrkNev9CS5TbVDDnND50A4BTGY p7/+2o86dAryNtUjei/PeseYIuCP5MorrfYEeXCX6ssOCczG0cd0wImnDe2CKv5C6ITu Z8H22DV7l5VWKhA7ovJjvP3HDQ9DYMFuBWF8ROyLUsHY7yd9RPIXam1ZQ7YK4ka2Ic4e 0fVTRs6UDzc1fBpIWuORGbLZQa+6lXIeV5MRuIyz7Cu0w/zsasoD09AEBONyAUY9Y7Al 3RvyEu7yqzXymh3U+qK8B/pcxrk2XKsYmSfNGJjP87co9si6zymsxBrvGjnAflZ4Nnf/ 1nAQ== 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=Yg0gGv6WumZLnkc1nKWQqFzpSI1UjVt2phjnB8N1znw=; b=M0Pv7E70KnYOQiWq6yI/dPylZrmDjSY4MjIE4RsvXury4diqrRWCuS62tHNfAIFrbD AEkyFQReOpWurrFMHMRKcElfInsmhIlHOYmbaEUvs0OWKKpjrvyR2E/P9MxiTeFaro1T O+4JQ8MKJHAsgN9nUXLD4Xq4Efsodi4EmU1uRPeEifiMlkmNpntvj6fafWKsdsMwCaQ2 wXUTAlzQtoU6Mr2V8CjQKz98rhQp94GWqVOCOQL9WnYZabOOlEgVZDO37d9QLH75ndVS mjegRa5zuPpocoy/3mhw0LgonpkeFn1cSA3/ezYTVKvJgYKHBhCTX/CqI03Vb6mtcNMw 4HpQ== X-Gm-Message-State: APjAAAWTezwubUZbK486OhwNk3iW3uJx5GlIXVBkd8FEdW2Jh3aEIEFw hPnaJk+wtPsquh5p0OTBVLjosAE1qEPeH38rvAOyuL1F X-Google-Smtp-Source: APXvYqx3L8vytJPYczHAvLOsS/dKqWNGWxoYilYqUUvYZnDdgH2AFLnJTnIz5FUAmv6OXj0Jo+1ttCFq0q0G72cBaZ4= X-Received: by 2002:a17:906:b309:: with SMTP id n9mr24234784ejz.210.1556354681524; Sat, 27 Apr 2019 01:44:41 -0700 (PDT) MIME-Version: 1.0 References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> <20190423165731.GB10587@lonesome.com> <1995497096.1.1556098457731@localhost> In-Reply-To: From: Balanga Bar Date: Sat, 27 Apr 2019 10:44:20 +0100 Message-ID: Subject: Re: Marvell Kirkwood - anyone? To: Ronald Klop Cc: Ian Lepore , Mark Linimon , freebsd-arm@freebsd.org X-Rspamd-Queue-Id: D615F755C1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ijlc7PZP; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of balangabar@gmail.com designates 2a00:1450:4864:20::529 as permitted sender) smtp.mailfrom=balangabar@gmail.com X-Spamd-Result: default: False [-4.50 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[5]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.71)[-0.714,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.77)[ip: (-9.22), ipnet: 2a00:1450::/32(-2.32), asn: 15169(-2.27), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[9.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2019 08:44:44 -0000 Didn't you need to include '-DWITH_FDT' ? As for 'unable to build'... I would run make in a directory under /usr/ports and there would be no response. The system would just hang. I have now managed to install 11.1 which seems fairly stable and have built a few pkgs, although building them takes several hours. It would be much better if I was able to build them under amd64, but haven't found a way of doing that yet On Thu, Apr 25, 2019 at 3:01 PM Ronald Klop wrote: > On Thu, 25 Apr 2019 11:15:05 +0200, Balanga Bar > wrote: > > It's nice to know that someone has 11.2 working on armv5. Could you let me > know how you built it? > > > > I cross-compiled on amd64. > cd /usr/src (containing the 11.2 sources of course) > export TARGET_ARCH=arm > export KERNCONF=SHEEVAPLUG > export DESTDIR=/mnt/usbdisk (here the usb stick is mounted) > make buildworld > make buildkernel > cp /usr/obj/arm.arm/usr/src/sys/SHEEVAPLUG/kernel.bin $DESTDIR/boot/msdos/ > make installworld > make distribution > > From the top of my head, so I might have missed something. > > > > I installed portsnap under 11.0 but was unable to build anything - will > try again with 11.2 to see if I can iron out the problems I've had as I now > know someone has it working. > > > "Unable to build" is not very specific. It helps if you copy paste the > actual error message. > > Ronald. > > > > On Wed, Apr 24, 2019 at 10:34 AM Ronald Klop wrote: > >> Dear Balanga, >> >> I run 11.2 on my Sheevaplug (armv5 also). >> >> uname -a >> FreeBSD sheeva2.klop.ws 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #4 >> r339336M: Sat Oct 13 23:31:51 CEST 2018 builder@rpi3:/data/src/obj-11.2/arm.arm/data/src/11.2/sys/SHEEVAPLUG >> arm >> >> It has a ports checkout using portsnap. And that works pretty well. >> Just do: >> portsnap auto >> cd /usr/ports/shells/bash (or whatever port you wish to install) >> make install >> make clean >> >> I think that is the most simple approach for you to go forward. >> >> Regards, >> Ronald. >> >> PS: Sorry for top-posting, my current mail client does not help in this >> very well. >> >> >> *Van:* Balanga Bar >> *Datum:* dinsdag, 23 april 2019 20:08 >> *Aan:* Mark Linimon >> *CC:* freebsd-arm@freebsd.org, Ian Lepore >> *Onderwerp:* Re: Marvell Kirkwood - anyone? >> >> Actually I have managed to build FreeBSD 11.0-RELEASE on ARM and it has >> not >> exhibited any problems on my GoFlexHome apart from being unable install >> pkgs. That is the current focus at the moment. >> >> On Tue, Apr 23, 2019 at 5:57 PM Mark Linimon >> wrote: >> >> > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote: >> > > Is it possible to get a version of portsnap from that point? >> > >> > I don't know enough to answer that question. I think it would be fair >> > to assume "no". >> > >> > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up >> > and working. I'm going to be honest and say there isn't one. >> > >> > Here are the approaches I think you can take: >> > >> > - stay on 8.x; bring individual port updates to it from ports-head and >> > build your own ports. Difficulty: hard. >> > >> > - figure out what src changes after 8.x regressed Kirkwood; check >> > out src 12-STABLE, build your own src, and use FreeBSD.org packages. >> > Difficulty: expert. >> > >> > - stay on 8.x; attempt to bring a modern ports tree to it and build >> > your own ports. Difficulty: challenging. >> > >> > The difficulty level of the first approach depends on which ports you >> > are going to try to use. shells/bash? Probably not too hard. Anything >> > GUI-related? Very hard. >> > >> > None of these approaches are achievable within hours; they will take >> > days, or, in the case of the third approach, weeks. >> > >> > fwiw, the second approach is the only one where your fixes could be >> > merged back into FreeBSD. If I were personally determined to run >> > Kirkwoord, that's the approach I would take. (I gave my GuruPlug >> > away some time ago.) >> > >> > I'm sorry that I can't be more encouraging. >> > >> > mcl >> > >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> ------------------------------ >> >> > > > From owner-freebsd-arm@freebsd.org Sat Apr 27 11:38:39 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C94AB158FD99 for ; Sat, 27 Apr 2019 11:38:38 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B101A82D19; Sat, 27 Apr 2019 11:38:37 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from mather.gromit23.net (c-98-244-101-97.hsd1.va.comcast.net [98.244.101.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 44DD6130; Sat, 27 Apr 2019 07:38:30 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: Marvell Kirkwood - anyone? From: Paul Mather In-Reply-To: Date: Sat, 27 Apr 2019 07:38:29 -0400 Cc: Ronald Klop , Mark Linimon , freebsd-arm@freebsd.org, Ian Lepore Content-Transfer-Encoding: 7bit Message-Id: <471BDE16-1AE2-425A-87F9-8CCE70532A3F@gromit.dlib.vt.edu> References: <693425711bdc5e7fbff22bb4056c33326fca8c4d.camel@freebsd.org> <7a36b81cb2c29293296bac9ae1764f0091281408.camel@freebsd.org> <20190423075411.GA18137@lonesome.com> <20190423165731.GB10587@lonesome.com> <1995497096.1.1556098457731@localhost> To: Balanga Bar X-Mailer: Apple Mail (2.3445.104.8) X-Rspamd-Queue-Id: B101A82D19 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dmarc=fail reason="" header.from=vt.edu (policy=none) X-Spamd-Result: default: False [-2.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; RCPT_COUNT_FIVE(0.00)[5]; MX_GOOD(-0.01)[chumby.dlib.vt.edu,gromit.dlib.vt.edu]; NEURAL_HAM_SHORT(-0.86)[-0.863,0]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[97.101.244.98.zen.spamhaus.org : 127.0.0.10]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:1312, ipnet:128.173.0.0/16, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; IP_SCORE(-1.33)[ip: (-3.45), ipnet: 128.173.0.0/16(-1.72), asn: 1312(-1.43), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[vt.edu : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2019 11:38:39 -0000 On Apr 27, 2019, at 5:44 AM, Balanga Bar wrote: > Didn't you need to include '-DWITH_FDT' ? > > As for 'unable to build'... I would run make in a directory under > /usr/ports and there would be no response. The system would just hang. > > I have now managed to install 11.1 which seems fairly stable and have built > a few pkgs, although building them takes several hours. It would be much > better if I was able to build them under amd64, but haven't found a way of > doing that yet Have you tried using Poudriere with QEMU support to build ports? I am using that to build packages for my arm.armv7 and arm64.aarch64 systems on an amd64 build system. I also use the same build system to cross-build OS packages for those ARM systems, too. That way, I update the OS via "pkg" on the ARM systems, too. https://www.freebsd.org/doc/handbook/ports-poudriere.html Cheers, Paul. From owner-freebsd-arm@freebsd.org Sat Apr 27 14:33:16 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 078DC15942F7 for ; Sat, 27 Apr 2019 14:33:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 820F48782A for ; Sat, 27 Apr 2019 14:33:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C77EA1836 for ; Sat, 27 Apr 2019 14:33:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3REXEOr062273 for ; Sat, 27 Apr 2019 14:33:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3REXEL0062272 for freebsd-arm@FreeBSD.org; Sat, 27 Apr 2019 14:33:14 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 234091] rpi 2b start with hight load, interrupts may be blamed Date: Sat, 27 Apr 2019 14:33:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ian@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2019 14:33:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234091 Ian Lepore changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |ian@FreeBSD.org Status|New |Closed --- Comment #1 from Ian Lepore --- The cause for this was eventually tracked down to configuring interrupts for virtual timers on systems that use physical timers. It was fixed in r346312 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Sat Apr 27 15:00:52 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBBAB1594C14 for ; Sat, 27 Apr 2019 15:00:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 785B588933 for ; Sat, 27 Apr 2019 15:00:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id AA3421B30 for ; Sat, 27 Apr 2019 15:00:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3RF0pa6026232 for ; Sat, 27 Apr 2019 15:00:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3RF0pXx026217 for freebsd-arm@FreeBSD.org; Sat, 27 Apr 2019 15:00:51 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 237401] A10 pin control define bug Date: Sat, 27 Apr 2019 15:00:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-patch, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: manu@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2019 15:00:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237401 Emmanuel Vadot changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Open |Closed --=20 You are receiving this mail because: You are the assignee for the bug.=