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