From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 07:08:30 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A4169E3 for ; Sun, 2 Nov 2014 07:08:30 +0000 (UTC) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1446310C for ; Sun, 2 Nov 2014 07:08:30 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id lj1so10244241pab.36 for ; Sun, 02 Nov 2014 00:08:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XujyF87TOBMDRJ/Prqw85QVj6NClqzEy99Ru8029SF4=; b=dKNCQnWGUSnJ6ZBMiEegIFseyfE1zaM4uDiokoRCIAB9mvCziqcpa/O7aaL6jU4Q22 XN1l7CRaMZSdVyQki9l+dgz4DNy0w7W1AsN+5rl3GUvSQ62z1eNkSnqdDQA83b8zMwTR Ckmdwyrgg5jpXcw2GeiLoSCINXYQlgoGGk32QvZFdhyoBNbX8TTm82BwqApJwofnERCa n6Py/lQVcS8JIOOzIPDNx+bQ+hKXCs3weWCS7DsNdHNZcR+a18/LWFQnBCSOR1eGxNAM d7lENGsN0rZzIc+k6rtzcU4I12ti1bMe0W/E04waxt80XvNckq9vud5BlDbvlgCp28Bm 4ijg== MIME-Version: 1.0 X-Received: by 10.70.22.195 with SMTP id g3mr35024198pdf.37.1414912109517; Sun, 02 Nov 2014 00:08:29 -0700 (PDT) Received: by 10.70.83.193 with HTTP; Sun, 2 Nov 2014 00:08:29 -0700 (PDT) In-Reply-To: <54527218.2090008@ceetonetechnology.com> References: <54527218.2090008@ceetonetechnology.com> Date: Sun, 2 Nov 2014 08:08:29 +0100 Message-ID: Subject: Re: building cross-compiling tools on -CURRENT From: Zsolt Udvari To: George Rosamond Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 07:08:30 -0000 I've tried similar about a one month ago and I ran into linker error too. I've read this: " For 64-bit targets (i.e. mips64) use an 64-bit host (i.e. amd64). For 32-bit targets (i.e. armv6) use an 32-bit host (i.e. i386) or compat-32. It may be possible to emulate 32-bit targets on a 64-bit host in the future but currently that is not possible. " https://wiki.freebsd.org/QemuUserModeHowTo I don't find the url but as I remember it was written somewhere that it maybe causes linker errors. 2014-10-30 18:15 GMT+01:00 George Rosamond : > Using a new build box running head with r273764, and running into an > issue building the cross compiler tools. Using source based in /usr/src > on an amd64 box. I do have devel/gperf installed as per /usr/src/UPDATING. > > Running this from /usr/src: > > make TARGET=arm TARGET_ARCH=armv6 WITH_GCC=1 WITH_GCC_BOOTSTRAP=1 > WITHOUT_CLANG=1 WITHOUT_CLANG_BOOTSTRAP=1 WITHOUT_CLANG_IS_CC=1 xdev > > I changed "XDEV" and "XDEV_ARCH to "TARGET" and "TARGET_ARCH" as per > /usr/src/UPDATING from 20140723, but also tried "XDEV" "XDEV_ARCH". If > I'm reading this right, Crochet should take that into account. > > I did clear out /usr/obj, updated and cleaned /usr/src... > > Anyone else? Here's the relevant end of the failure AFAIK: > > except.o: In function `nothrow_libfn_p': > /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/except.c:(.text+0x10fb): > undefined reference to `libc_name_p' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > *** Error code 1 > > Stop. > make[3]: stopped in /usr/src/gnu/usr.bin/cc/cc1plus > *** Error code 1 > > Stop. > make[2]: stopped in /usr/src/gnu/usr.bin/cc > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 08:46:12 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6CA2A386 for ; Sun, 2 Nov 2014 08:46:12 +0000 (UTC) Received: from frontend2.warwick.net (lm-3.warwick.net [204.255.24.103]) by mx1.freebsd.org (Postfix) with SMTP id 22FBBAF1 for ; Sun, 2 Nov 2014 08:46:11 +0000 (UTC) Received: (qmail 13729 invoked from network); 2 Nov 2014 08:46:05 -0000 Received: from 70.44.113.89.res-cmts.sefg.ptd.net (HELO [70.44.113.89]) (egunther@warwick.net@70.44.113.89) by frontend2.warwick.net with SMTP (ae240dde-626c-11e4-bb12-001f2909bf3e); Sun, 02 Nov 2014 03:46:05 -0500 Message-ID: <1414917964.3427.2.camel@res-cmts> Subject: Re: RPI, config.txt: overscan, not working From: ito To: freebsd-arm@freebsd.org Date: Sun, 02 Nov 2014 03:46:04 -0500 In-Reply-To: <1414774843.3499.18.camel@res-cmts> References: <1414774843.3499.18.camel@res-cmts> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-MagicMail-UUID: ae240dde-626c-11e4-bb12-001f2909bf3e X-MagicMail-Authenticated: egunther@warwick.net X-MagicMail-SourceIP: 70.44.113.89 X-MagicMail-EnvelopeFrom: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 08:46:12 -0000 Is there anyone with an idea as to how I can stop the text from spilling off the screen. The display is in excess of 1/2 an inch all around. Thanks, ito On Fri, 2014-10-31 at 13:00 -0400, ito wrote: > Hello, > > I have a raspberry pi, > > Model B Revision 2.0 (512MB) > which has the logo along with: > Raspberry Pi > (c)2011.12 > written on it. > > I have obtained a image for freebsd to run from here: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/10.0/ > > > I uncompressed the image on a OpenSUSE system, and used, > > sudo dd if=FreeBSD-10.0-RELEASE-arm-armv6-RPI-B-20140131-r260789.img > of=/dev/sdd > > to put the image on a micro SD... with that card and adapter I have > successfully boot freebsd. > > The problem I am facing now is that I am using the yellow SVGA (RCA type > plug) cables to use an old Television as a monitor, with this setup I > have an issue with the text running off of the screen. > > I have tried the config.txt file with > overscan_disable=0 > overscan_left=20 > overscan_right=20 > overscan_top=20 > overscan_bottom=20 > > > added to the existing config.txt > > > > I have tried to load vesa: > > kldload vesa > > where I get a prompt that it does not exist. > > I looked in the kernel directory (/boot/kernel/) and there is no vesa, > not sure what that means. > > > I am assuming that there is something that is not happening with the > config.txt. I saw mention of using the files here to replace the files > on the pi; > > https://github.com/raspberrypi/firmware > > > SO, essentially, how do I get the text to stop from spilling off of the > screen (command prompt-no gui). > > > Thank You, > > ito From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 09:46:49 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A95B2463 for ; Sun, 2 Nov 2014 09:46:49 +0000 (UTC) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F396FA6 for ; Sun, 2 Nov 2014 09:46:48 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id E72E139D0A; Sun, 2 Nov 2014 18:46:40 +0900 (JST) Received: from artemis (unknown [172.18.0.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id B75F239D09; Sun, 2 Nov 2014 18:46:40 +0900 (JST) Message-ID: <7FEFD928A4254E84BCB539D523E9D571@ad.peach.ne.jp> From: "Daisuke Aoyama" To: "Hans Petter Selasky" , "Rui Paulo" References: <0A8390C3FC2B444B9AA8AC934B79DCD6@ad.peach.ne.jp> <7946CCA3-26D0-4B6E-AEBB-8623CAAA9725@me.com> <840772A7305444C1B1AF7CE31A89BD7D@ad.peach.ne.jp> <09F2506B-11E9-43A2-A783-784AA6E39976@me.com> <5DC02CC61B85442AADD2BDD28496421E@ad.peach.ne.jp> <60F13E5C-A166-497B-8CB7-6C76AFB6BDB8@me.com> <54548EC8.5020707@selasky.org> In-Reply-To: <54548EC8.5020707@selasky.org> Subject: Re: FreeBSD 11-CURRENT on Raspberry Pi 512MB Date: Sun, 2 Nov 2014 18:46:37 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 09:46:49 -0000 > On 11/01/14 02:54, Rui Paulo wrote: >> On Oct 31, 2014, at 12:32, Daisuke Aoyama wrote: >>> >>>> That patch has a lot of unrelated changes. Could you produce a patch with svn that is just >>>> related to cpufreq and its mbox changes? >>> >>> I have uploaded as: >>> http://www.peach.ne.jp/archives/rpi/patch/cpufreq-20141101.tar.gz >>> >>> Please use this archive. >>> >>> CHANGES: >>> modify for style(9) and 80 columns >>> remove multiple cast >>> remove bootverbose of error case >>> remove unused code and g_XXXX variables >>> fix wrong message/comments. >>> add DPRINTF and dump into #ifdef DEBUG >>> add tunable int for verbose and lowest_freq >>> suppress default boot log >> >> Thanks, I've updated the review page: >> >> https://reviews.freebsd.org/D1025 >> >> I'm going to review it again during the weekend. >> >> > > Regarding the tunables: > > Why don't you make them into SYSCTLS with the TUN flag set. Then they will also be visible in > the "sysctl -a" output! Hi, The reason is that the existing code of bcm2835_sdhci.c is used. Does it is required in read-only? Regards, -- Daisuke Aoyama From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 13:39:50 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4AC42677 for ; Sun, 2 Nov 2014 13:39:50 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD27874E for ; Sun, 2 Nov 2014 13:39:49 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id b6so114357lbj.16 for ; Sun, 02 Nov 2014 05:39:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=zHRqHJEeidRI9pQMVQU1ICBd//+ouykwPEcsvw5dXmw=; b=0Mbwe66YHbvVwk5c/jZ/OfqCMJqIRQ6om737b/ELVuwKRSnPNcXPxJ2ZFMgb16ZScY 0u21aoFtahxVQxQ8OIM5BaOyz/EtrWkg/ffsR5V+bviWtqFQZhitorV9d6MbEdoQFzGq xiYOs9k99PBhJCITQq1jC54I5z/ps5TsNOoBFlA1YWJSOYUPZOKKvdqEiec8V5spKmao Tc3XHghMrQTDl1v5YLDF/4HxyBoF+YSnsOk03vM6KBYqf/vFUTkA4sk4jAVyUVdwyWHw wRY3bZFQCZNNZ93yI6w8haKkd4NVCs14A4PynmOxlpbEwJORn8e4PTti6f42eFF5XMgv M4Zg== X-Received: by 10.112.169.106 with SMTP id ad10mr42717593lbc.13.1414935587530; Sun, 02 Nov 2014 05:39:47 -0800 (PST) MIME-Version: 1.0 From: Mario Sangiorgio Date: Sun, 02 Nov 2014 13:39:47 +0000 Message-ID: Subject: FreeBSD on Raspberry PI To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 13:39:50 -0000 Hello, I am considering installing FreeBSD on my Raspberry Pi to use it a a personal server. I read the documentation on the wiki but I still have some concerns. First, the wiki says: As of January 2013, FreeBSD-CURRENT fully supports either a video console (you'll need a USB keyboard and display connected) or it can be configured to use a serial console (you'll need a serial adapter cable such as the one sold by Adafruit.com). Does it mean that by default the access via the serial adapter is not enabled by default and it needs to be configured in a special way? Second: I found links to a few unofficial packages repositories compatible with the Raspberry Pi. Is there any official (or a recommended) repository? I assume that compilation on the device would be quite slow, so I'd prefer to avoid it. Third: does FreeBSD have any special command to update Raspberry PI firmware? Linux package managers have it and I am wondering if there is any FreeBSD equivalent or what is the procedure to update the firmware. Thanks, Mario From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 14:57:19 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5EEB583D for ; Sun, 2 Nov 2014 14:57:19 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41A16D81 for ; Sun, 2 Nov 2014 14:57:18 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Xkwai-0000kp-RI for freebsd-arm@freebsd.org; Sun, 02 Nov 2014 06:57:16 -0800 Date: Sun, 2 Nov 2014 06:57:16 -0800 (PST) From: sson To: freebsd-arm@freebsd.org Message-ID: <1414940236818-5961816.post@n5.nabble.com> In-Reply-To: <18F72354-0695-468F-8D39-C2563CC5CDAF@FreeBSD.org> References: <18F72354-0695-468F-8D39-C2563CC5CDAF@FreeBSD.org> Subject: Re: Ports Raspberry pi MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 14:57:19 -0000 See https://wiki.freebsd.org/QemuUserModeHowTo for information on how to cross compile ARM ports using "user mode" qemu. Regards, sson@ -- View this message in context: http://freebsd.1045724.n5.nabble.com/Ports-Raspberry-pi-tp5960993p5961816.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 16:32:14 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1FA2CB2 for ; Sun, 2 Nov 2014 16:32:14 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) by mx1.freebsd.org (Postfix) with ESMTP id B4DFF85C for ; Sun, 2 Nov 2014 16:32:14 +0000 (UTC) Received: from [75.187.32.8] ([75.187.32.8:36174] helo=raspberrypi.bildanet.com) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 6D/E9-06451-1DA56545; Sun, 02 Nov 2014 16:24:49 +0000 Received: from [192.168.1.25] (helo=desktop.bildanet.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1XkxxR-0003Fe-4F for freebsd-arm@freebsd.org; Sun, 02 Nov 2014 11:24:49 -0500 From: Baho Utot To: freebsd-arm@freebsd.org Subject: Re: FreeBSD on Raspberry PI Date: Sun, 02 Nov 2014 11:26:03 -0500 Message-ID: <2027705.a725itiJ0Q@desktop.bildanet.com> User-Agent: KMail/4.14.2 (Linux/3.17.1-1-ARCH; KDE/4.14.2; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 16:32:15 -0000 On Sunday 02 November 2014 1:39:47 PM Mario Sangiorgio wrote: > Hello, I am considering installing FreeBSD on my Raspberry Pi to use it a a > personal server. > > I read the documentation on the wiki but I still have some concerns. > > First, the wiki says: > As of January 2013, FreeBSD-CURRENT fully supports either a video console > (you'll need a USB keyboard and display connected) or it can be configured > to use a serial console (you'll need a serial adapter cable such as the one > sold by Adafruit.com). > I use hdmi with my three pi. > Does it mean that by default the access via the serial adapter is not > enabled by default and it needs to be configured in a special way? > > Second: I found links to a few unofficial packages repositories compatible > with the Raspberry Pi. Is there any official (or a recommended) repository? > I assume that compilation on the device would be quite slow, so I'd prefer > to avoid it. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/ ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/11.0 I am using version 11.0 with my Raspberry pi B models. I have a B+ but I have failed to get it to boot using the current images. > > Third: does FreeBSD have any special command to update Raspberry PI > firmware? Linux package managers have it and I am wondering if there is any > FreeBSD equivalent or what is the procedure to update the firmware. https://github.com/raspberrypi/firmware You have to do the update manually From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 17:15:56 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D920EBD0 for ; Sun, 2 Nov 2014 17:15:56 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62B32BBF for ; Sun, 2 Nov 2014 17:15:56 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id f15so9197001lbj.27 for ; Sun, 02 Nov 2014 09:15:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:from:date:message-id:subject:to:cc :content-type; bh=bAKD0WEDwDV44IxRtdBlvrU0kT5WMGK+DTN5YiDp6II=; b=k6mIvmEIdf5vldMgl4puT0Zf4UGR8ToykTDkj71dd/q92IfcYf+ff/GwpVhOfWf2If RUtJnjwkm5Ev3UWB9ElfexDSGMrRVW3HLF7o1CUH7/6074FVNYMD2ERV8UeqrNaBohgF VKwcSF2ltlfQ+PIDUq764ehxRSfKkfERG0BnHQhVatdYv6KhfhpPAT3IN4UaQ/NdiOqa UxZ9DuD3j6qoWNaQt8FIoG/fbmL3MDg1UGCh6BCHD8+bhx3eRVGfvcyy5eyhzKijgFTX /QVK21NfQQm1JqJfl4m79yPev4EYIaNEYzozQkTIo0yj/whpzjhoWWWbpWogsFnmrDVS wckA== X-Received: by 10.112.198.226 with SMTP id jf2mr44544934lbc.84.1414948554134; Sun, 02 Nov 2014 09:15:54 -0800 (PST) MIME-Version: 1.0 References: From: Mario Sangiorgio Date: Sun, 02 Nov 2014 17:15:53 +0000 Message-ID: Subject: Re: FreeBSD on Raspberry PI To: Tim Kientzle Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 17:15:57 -0000 Thank you all for your answers. As soon as I'll get a serial console usb cable I'll install FreeBSD on my Raspberry Pi. Regarding the update, is it just a matter of copying the new version of these files [1] in /boot? [1] https://github.com/raspberrypi/firmware/tree/master/boot On Sun Nov 02 2014 at 4:56:16 PM Tim Kientzle wrote: > > > On Nov 2, 2014, at 5:39 AM, Mario Sangiorgio > wrote: > > > > First, the wiki says: > > As of January 2013, FreeBSD-CURRENT fully supports either a video console > > (you'll need a USB keyboard and display connected) or it can be > configured > > to use a serial console (you'll need a serial adapter cable such as the > one > > sold by Adafruit.com). > > > > Does it mean that by default the access via the serial adapter is not > > enabled by default and it needs to be configured in a special way? > > The serial console is always enabled. > > Tim > > From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 17:17:41 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04011C29 for ; Sun, 2 Nov 2014 17:17:41 +0000 (UTC) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (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 C5597BD3 for ; Sun, 2 Nov 2014 17:17:40 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id sA2Gu85j023335; Sun, 2 Nov 2014 16:56:08 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.100] (gateway.kientzle.com [192.168.1.65]) by kientzle.com with SMTP id h9k3jyhwtc9i73r6tkxmaa8nzi; Sun, 02 Nov 2014 16:56:08 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: FreeBSD on Raspberry PI From: Tim Kientzle In-Reply-To: Date: Sun, 2 Nov 2014 08:56:07 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Mario Sangiorgio X-Mailer: Apple Mail (2.1990.1) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 17:17:41 -0000 > On Nov 2, 2014, at 5:39 AM, Mario Sangiorgio = wrote: >=20 > First, the wiki says: > As of January 2013, FreeBSD-CURRENT fully supports either a video = console > (you'll need a USB keyboard and display connected) or it can be = configured > to use a serial console (you'll need a serial adapter cable such as = the one > sold by Adafruit.com). >=20 > Does it mean that by default the access via the serial adapter is not > enabled by default and it needs to be configured in a special way? The serial console is always enabled. Tim From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 17:28:15 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D185148C for ; Sun, 2 Nov 2014 17:28:15 +0000 (UTC) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (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 AB553CB5 for ; Sun, 2 Nov 2014 17:28:15 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id sA2HSEsW023479; Sun, 2 Nov 2014 17:28:14 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.100] (gateway.kientzle.com [192.168.1.65]) by kientzle.com with SMTP id zvipcj3scdr4pwcupjq8xurhps; Sun, 02 Nov 2014 17:28:14 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: FreeBSD on Raspberry PI From: Tim Kientzle In-Reply-To: Date: Sun, 2 Nov 2014 09:28:14 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <032EAAEA-5E54-4F33-9F53-DC072DD749FA@kientzle.com> References: To: Mario Sangiorgio X-Mailer: Apple Mail (2.1990.1) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 17:28:15 -0000 > On Nov 2, 2014, at 9:15 AM, Mario Sangiorgio = wrote: >=20 > Thank you all for your answers. As soon as I'll get a serial console = usb cable I'll install FreeBSD on my Raspberry Pi. >=20 > Regarding the update, is it just a matter of copying the new version = of these files [1] in /boot? Yes. If you want to help, you could contribute a port that would do this so = people could update their systems in-place. Cheers, Tim From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 17:59:29 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 980193B8 for ; Sun, 2 Nov 2014 17:59:29 +0000 (UTC) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 201FFF40 for ; Sun, 2 Nov 2014 17:59:28 +0000 (UTC) Received: by mail-la0-f46.google.com with SMTP id hs14so8628342lab.33 for ; Sun, 02 Nov 2014 09:59:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:from:date:message-id:subject:to:cc :content-type; bh=8Wwt+Vc9KRjkPMVYAomIV/rjdpO2ELfoaAa+4/Y7NoI=; b=yRkiTPrmoHzAZvul6DwOfI4BY+nd17gfxPPi2pWoTc5pCNDDheKDOJPrMmzfypkZ7L Cz4k3HTZNhaHaR6eNvJeThKCKrSy9r7/S4cAc5odsLh4gt01mKa0hE4hQ5DOSt9mBFxr /ABG5GZDty/sxDmPxiYk6cxbiMcuiDS9PGd5IGQylxTicZINYMysYOUzxILewedXfXjg knnUGGFqL6GUT3SJgS9sSXQ2GmCI4eMXpqK2moqavaovDPfHTaBceSugJtOyxdlMiy3K F3fkFes/xBQb2kmfDlQddG2hLPiQ2mby3NwEokR7bo8s/bx02q8JHgau2Hs4RDeO3IRn XecQ== X-Received: by 10.152.19.37 with SMTP id b5mr44999914lae.80.1414951166950; Sun, 02 Nov 2014 09:59:26 -0800 (PST) MIME-Version: 1.0 References: <032EAAEA-5E54-4F33-9F53-DC072DD749FA@kientzle.com> From: Mario Sangiorgio Date: Sun, 02 Nov 2014 17:59:26 +0000 Message-ID: Subject: Re: FreeBSD on Raspberry PI To: Tim Kientzle Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 17:59:29 -0000 I'd be happy to contribute. I'm experienced with programming but I've never written a port. Is there any handbook/wiki page I can have a look at? On Sun Nov 02 2014 at 5:28:17 PM Tim Kientzle wrote: > > > On Nov 2, 2014, at 9:15 AM, Mario Sangiorgio > wrote: > > > > Thank you all for your answers. As soon as I'll get a serial console usb > cable I'll install FreeBSD on my Raspberry Pi. > > > > Regarding the update, is it just a matter of copying the new version of > these files [1] in /boot? > > Yes. > > If you want to help, you could contribute a port that would do this so > people could update their systems in-place. > > Cheers, > > Tim > > From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 18:40:12 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 317EDC09 for ; Sun, 2 Nov 2014 18:40:12 +0000 (UTC) Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 078E1341 for ; Sun, 2 Nov 2014 18:40:12 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id y10so10117725pdj.26 for ; Sun, 02 Nov 2014 10:40:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=guGLu2rJ25QSijc2K/YZc+YYG6CcHDwRd6kfLdEaGXk=; b=a3hBfS1+h4iqN9lOlvLFnpkbbmbi0m+M+YQX87bF/WRLVbc8SMcPrDLYgAtaBK0HJ6 h60Hu3UbvtecuEymf189BzTJ4G02bQ2I1VcEZBGnwrMR+k8RSd+zPqL3nL/F+YA3iJyM O3fSORaKtkizRXkVx86W3YwCVlzhJSJedLF7UA4KCM+oXcA2J6XkMvRt1SfgIIfvNkkP WssQMxumhOQMA2CUvhN7CyhqUCsZHUr05au6KfZJiZkqKp7ig8gpm771bAfpHUE02BMk wBWz+q+L22UjoPI15DnJuvkDM8OlC4wztfA8ytl5kam2vPSH9Xig7bYjf5a0lz7ackf9 ZGDA== MIME-Version: 1.0 X-Received: by 10.66.162.37 with SMTP id xx5mr23679244pab.10.1414953611367; Sun, 02 Nov 2014 10:40:11 -0800 (PST) Received: by 10.70.83.193 with HTTP; Sun, 2 Nov 2014 10:40:11 -0800 (PST) In-Reply-To: References: <032EAAEA-5E54-4F33-9F53-DC072DD749FA@kientzle.com> Date: Sun, 2 Nov 2014 19:40:11 +0100 Message-ID: Subject: Re: FreeBSD on Raspberry PI From: Zsolt Udvari To: Mario Sangiorgio Content-Type: text/plain; charset=UTF-8 Cc: Tim Kientzle , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 18:40:12 -0000 2014-11-02 18:59 GMT+01:00 Mario Sangiorgio : > I'm experienced with programming but I've never written a port. > Is there any handbook/wiki page I can have a look at? You should check Porter's Handbook [1] and the files in /usr/ports. Zsolt [1] https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 19:06:22 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 495FD1F8 for ; Sun, 2 Nov 2014 19:06:22 +0000 (UTC) Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E2B17E8 for ; Sun, 2 Nov 2014 19:06:21 +0000 (UTC) Received: by mail-ig0-f180.google.com with SMTP id h3so3580892igd.1 for ; Sun, 02 Nov 2014 11:06:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=P1dWZGgedWWX0H2TQ1L1GYVYtKtLk1ko1o+PTM2PHl4=; b=iNJVFfbnv8WqyEQBbnDX17UzoZe4i2QZsncZ3+4DrtalLbwllJIHfFC6Qc+QJGblEN yewKGc5ry+Zmx7snRuXojlJa7D0Scxdb4K8YaWmwtG0MFCqYDb7BsegZRTcexV12VvIu ZU5C2XeKkYqETxiw4Uvct+GrGNfHWfUe8nF1R1viDj5IVwKOXsDUogt/GilIUGepeg26 q7cgTDn/1AigNHPdpv1Ddl0SSeCfm9JEZ7F2Wan/36CggwxqAMh4F0zWx4yeKkiQQLd9 ZEWcGnTp788fs63FP8AL4vl5bompfyaXJwlc1OuvMZdJc+ONU0Tr7f1vbdoKunwwmFtZ /vYQ== X-Gm-Message-State: ALoCoQlhv8jWlWix5VlDiR8X+4YefmpoL3W8fF9VU6XbIrtfLhLLJaaw6lovJQnYmbSZfN1JSAjn X-Received: by 10.43.162.129 with SMTP id mk1mr18180226icc.20.1414955175760; Sun, 02 Nov 2014 11:06:15 -0800 (PST) Received: from netflix-mac.bsdimp.com ([50.253.99.174]) by mx.google.com with ESMTPSA id rj6sm2653479igc.0.2014.11.02.11.06.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Nov 2014 11:06:15 -0800 (PST) Sender: Warner Losh Content-Type: multipart/signed; boundary="Apple-Mail=_97E277DB-6ACC-4329-B612-93522313DC37"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: building cross-compiling tools on -CURRENT From: Warner Losh In-Reply-To: Date: Sun, 2 Nov 2014 12:06:12 -0700 Message-Id: References: <54527218.2090008@ceetonetechnology.com> To: Zsolt Udvari X-Mailer: Apple Mail (2.1878.6) Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 19:06:22 -0000 --Apple-Mail=_97E277DB-6ACC-4329-B612-93522313DC37 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I=92ve never had an issue building mips32 / arm on a amd64 host. On Nov 2, 2014, at 1:08 AM, Zsolt Udvari wrote: > I've tried similar about a one month ago and I ran into linker error > too. I've read this: > " For 64-bit targets (i.e. mips64) use an 64-bit host (i.e. amd64). > For 32-bit targets (i.e. armv6) use an 32-bit host (i.e. i386) or > compat-32. It may be possible to emulate 32-bit targets on a 64-bit > host in the future but currently that is not possible. " > https://wiki.freebsd.org/QemuUserModeHowTo > I don't find the url but as I remember it was written somewhere that > it maybe causes linker errors. >=20 > 2014-10-30 18:15 GMT+01:00 George Rosamond = : >> Using a new build box running head with r273764, and running into an >> issue building the cross compiler tools. Using source based in = /usr/src >> on an amd64 box. I do have devel/gperf installed as per = /usr/src/UPDATING. >>=20 >> Running this from /usr/src: >>=20 >> make TARGET=3Darm TARGET_ARCH=3Darmv6 WITH_GCC=3D1 = WITH_GCC_BOOTSTRAP=3D1 >> WITHOUT_CLANG=3D1 WITHOUT_CLANG_BOOTSTRAP=3D1 WITHOUT_CLANG_IS_CC=3D1 = xdev >>=20 >> I changed "XDEV" and "XDEV_ARCH to "TARGET" and "TARGET_ARCH" as per >> /usr/src/UPDATING from 20140723, but also tried "XDEV" "XDEV_ARCH". = If >> I'm reading this right, Crochet should take that into account. >>=20 >> I did clear out /usr/obj, updated and cleaned /usr/src... >>=20 >> Anyone else? Here's the relevant end of the failure AFAIK: >>=20 >> except.o: In function `nothrow_libfn_p': >> = /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/except.c:(.text= +0x10fb): >> undefined reference to `libc_name_p' >> cc: error: linker command failed with exit code 1 (use -v to see = invocation) >> *** Error code 1 >>=20 >> Stop. >> make[3]: stopped in /usr/src/gnu/usr.bin/cc/cc1plus >> *** Error code 1 >>=20 >> Stop. >> make[2]: stopped in /usr/src/gnu/usr.bin/cc >> *** Error code 1 >>=20 >> Stop. >> make[1]: stopped in /usr/src >> *** Error code 1 >>=20 >> Stop. >> make: stopped in /usr/src >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --Apple-Mail=_97E277DB-6ACC-4329-B612-93522313DC37 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUVoCkAAoJEGwc0Sh9sBEAP9cP/j8d0Uj+KuHRzO+3AH+1L4Ze ll0teVjJU4siEysto/nQkvq3cyimybmFiwnoSuWhrt1dmYwKx1gsDsqFOWlKPd4w AZ/hOCuSbQiDFB3t3lW7BpzugPBO2XAfDcuIiq69hlh4yQDL79U8IMY2t0NvYs69 zMVb7VRYTp2tyaYkvGGyKyyUJDXHaAZhmeYNvb43V4JhB8t7W3otj2L3wwqLs/rv Gf00Zl58qWpPGXwssy7vrOX+zUaCW2m9WcTkCot1Df8MeX1e7/AC2RrnKzCXIQSl YAaqB0um/gwIBU3SgswsC5B7lBV7L7EwGZ6etkC6TENfuxbXGbv3FJpE0bJn5fHC LyTfYYVTwJhdsjLd+3nHib3xmqXAQbro/Q+m6+7P64HfSKrp5jzrGBW+qj5HPXQD OV3o5X4HkcujIzYFQNASdiE54sfaRRrWewtPwsK+6vBY2ySumn+NoRkx54TL9lVG /tdpBnqt6b5XWwL2Fd2yRjK5pXUGXWuIRFE2ZhgKi2fxsfPM3UmtDoUtkeS9TZ0B CxA6KZ4OtwhaL7ECZsp+/qUSC2fttKcbQIke45vxsONWdOU9nNp7YyOB0V4F8j8U XOi4UjeN2iVzy4nB6oDq1VJldQzrWv1gt9aBrYmm7youHEf5lXZ5Sdk/tmikUpzv LiWehB74x1MvLWzSo9zb =t7wb -----END PGP SIGNATURE----- --Apple-Mail=_97E277DB-6ACC-4329-B612-93522313DC37-- From owner-freebsd-arm@FreeBSD.ORG Sun Nov 2 23:54:25 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 938EF8AC for ; Sun, 2 Nov 2014 23:54:25 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 673097A7 for ; Sun, 2 Nov 2014 23:54:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=Q7/TCOY32cXCZYhcv9qV+LmLxDwGJ0oy4Gt5EY+GzXg=; b=gLsQMpOSHuEzE6ls5wEcRefVGNv8C8MuYgB+qOjuFaLZsp4MilJbrb7fBXPeYH9CrBdr2GgOEnZZM9fd1OTY2vW50oGz6906FDnRiD/1yRbZiIF7hDpjfJlaSb6RLYYVnhwcIq6oRhLH7LACTSBwfano5TxL0CG6WFQ3m/4B15A=; Received: from [182.0.221.227] (port=12492 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpa (Exim 4.82) (envelope-from ) id 1Xl4yU-003PFk-UF; Sun, 02 Nov 2014 16:54:23 -0700 Date: Mon, 3 Nov 2014 07:54:17 +0800 From: Erich Dollansky To: Mario Sangiorgio Subject: Re: FreeBSD on Raspberry PI Message-ID: <20141103075417.7a402357@X220.alogt.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: Tim Kientzle , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 23:54:25 -0000 Hi, On Sun, 02 Nov 2014 17:15:53 +0000 Mario Sangiorgio wrote: > Thank you all for your answers. As soon as I'll get a serial console > usb cable I'll install FreeBSD on my Raspberry Pi. > don't you have a network at home? A RJ-45 cable and off you go. I did not connect keyboard or monitor to any of my Raspberries yet. SSH works from the images, telnet has to be enabled. > Regarding the update, is it just a matter of copying the new version > of these files [1] in /boot? Look at the archives for a conversation between YAMAMOTO Shigeru and me. YAMAMOTO explains it very well. And it works without flaws. Erich > > [1] https://github.com/raspberrypi/firmware/tree/master/boot > > On Sun Nov 02 2014 at 4:56:16 PM Tim Kientzle > wrote: > > > > > > On Nov 2, 2014, at 5:39 AM, Mario Sangiorgio > > > > > wrote: > > > > > > First, the wiki says: > > > As of January 2013, FreeBSD-CURRENT fully supports either a video > > > console (you'll need a USB keyboard and display connected) or it > > > can be > > configured > > > to use a serial console (you'll need a serial adapter cable such > > > as the > > one > > > sold by Adafruit.com). > > > > > > Does it mean that by default the access via the serial adapter is > > > not enabled by default and it needs to be configured in a special > > > way? > > > > The serial console is always enabled. > > > > Tim > > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 00:02:36 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EDA73999 for ; Mon, 3 Nov 2014 00:02:36 +0000 (UTC) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 74ADE863 for ; Mon, 3 Nov 2014 00:02:36 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id gd6so7375159lab.20 for ; Sun, 02 Nov 2014 16:02:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:from:date:message-id:subject:to:cc :content-type; bh=6TUGX0gChwEwS4OUiMChSpmk80nsgowe+OgfZW701oA=; b=kAoYq6g/iN/PuybyO5v56qT8LVYLt/rBaJ2znpJz9c5UruFHsjnGI2kA5LXYXnaQMU FPCdGGAU0kLfCzsZTgvhiEDGx0W8t0zViP85MYwP65F0AuOfDsHae4ZgSEjGhOuzJRCE ho7EhTN0v2Qgo2PvhZDQ7nO/iAtAFAut8AWo6FQ6NNE3MxtqsRNuawyVg3GRltsj9alg 9FB0ccmIvaaP7i4Orl211qyCQ/85p47X4qy65MFTgClbRmFHGFRGzSFTx656AGfSYfnD PttNaG8kwt0PkxQ6tCfK3hx/I52YnWY5mzGO/sh3hv0wr5KP23mLed+o4HwVmdYQqus1 FbOw== X-Received: by 10.112.125.106 with SMTP id mp10mr47370865lbb.50.1414972954296; Sun, 02 Nov 2014 16:02:34 -0800 (PST) MIME-Version: 1.0 References: <20141103075417.7a402357@X220.alogt.com> From: Mario Sangiorgio Date: Mon, 03 Nov 2014 00:02:33 +0000 Message-ID: Subject: Re: FreeBSD on Raspberry PI To: Erich Dollansky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tim Kientzle , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 00:02:37 -0000 I think I read on an online guide that ssh needed to be enabled. Maybe it was outdated. Tomorrow I'll give it a shot then. Should I try to connect as root with an empty password? On Sun, 2 Nov 2014 23:54 Erich Dollansky wrote: > Hi, > > On Sun, 02 Nov 2014 17:15:53 +0000 > Mario Sangiorgio wrote: > > > Thank you all for your answers. As soon as I'll get a serial console > > usb cable I'll install FreeBSD on my Raspberry Pi. > > > don't you have a network at home? A RJ-45 cable and off you go. I did > not connect keyboard or monitor to any of my Raspberries yet. SSH works > from the images, telnet has to be enabled. > > > Regarding the update, is it just a matter of copying the new version > > of these files [1] in /boot? > > Look at the archives for a conversation between YAMAMOTO Shigeru and > me. YAMAMOTO explains it very well. And it works without flaws. > > Erich > > > > > > [1] https://github.com/raspberrypi/firmware/tree/master/boot > > > > On Sun Nov 02 2014 at 4:56:16 PM Tim Kientzle > > wrote: > > > > > > > > > On Nov 2, 2014, at 5:39 AM, Mario Sangiorgio > > > > > > > wrote: > > > > > > > > First, the wiki says: > > > > As of January 2013, FreeBSD-CURRENT fully supports either a video > > > > console (you'll need a USB keyboard and display connected) or it > > > > can be > > > configured > > > > to use a serial console (you'll need a serial adapter cable such > > > > as the > > > one > > > > sold by Adafruit.com). > > > > > > > > Does it mean that by default the access via the serial adapter is > > > > not enabled by default and it needs to be configured in a special > > > > way? > > > > > > The serial console is always enabled. > > > > > > Tim > > > > > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 00:24:49 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9E21F42 for ; Mon, 3 Nov 2014 00:24:49 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 9EE0AA0D for ; Mon, 3 Nov 2014 00:24:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=D+x8Q1h4Elx11FtDbyrNrXrsYycI716xyL521xteQ4w=; b=MBPaUvLq+jznx6PTYzn+MYcb1+DaV4mQj1gtnY5DJef161gU99j68iQnkczLXxFgZaMGVQ0fs0/D9hFP2zo0zBAVBJEANtZU0SPHt+Dtxy93lH/xDGqn0z4BJ8jgFUXKTHVCmgQkZUyeWlaLFHinaOASUK3o0HlRYQ0gahggtCc=; Received: from [182.0.221.227] (port=21504 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpa (Exim 4.82) (envelope-from ) id 1Xl5Rv-003cUk-WE; Sun, 02 Nov 2014 17:24:48 -0700 Date: Mon, 3 Nov 2014 08:24:43 +0800 From: Erich Dollansky To: Mario Sangiorgio Subject: Re: FreeBSD on Raspberry PI Message-ID: <20141103082443.2db41632@X220.alogt.com> In-Reply-To: References: <20141103075417.7a402357@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: Tim Kientzle , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 00:24:50 -0000 Hi, On Mon, 03 Nov 2014 00:02:33 +0000 Mario Sangiorgio wrote: > I think I read on an online guide that ssh needed to be enabled. > Maybe it was outdated. > > Tomorrow I'll give it a shot then. Should I try to connect as root > with an empty password? > I do not even know. I copy my own configuration files and password database onto the image. This gives me the passwords of the other machine and all the settings as I expect it. Erich > On Sun, 2 Nov 2014 23:54 Erich Dollansky > wrote: > > > Hi, > > > > On Sun, 02 Nov 2014 17:15:53 +0000 > > Mario Sangiorgio wrote: > > > > > Thank you all for your answers. As soon as I'll get a serial > > > console usb cable I'll install FreeBSD on my Raspberry Pi. > > > > > don't you have a network at home? A RJ-45 cable and off you go. I > > did not connect keyboard or monitor to any of my Raspberries yet. > > SSH works from the images, telnet has to be enabled. > > > > > Regarding the update, is it just a matter of copying the new > > > version of these files [1] in /boot? > > > > Look at the archives for a conversation between YAMAMOTO Shigeru and > > me. YAMAMOTO explains it very well. And it works without flaws. > > > > Erich > > > > > > > > > > [1] https://github.com/raspberrypi/firmware/tree/master/boot > > > > > > On Sun Nov 02 2014 at 4:56:16 PM Tim Kientzle > > > wrote: > > > > > > > > > > > > On Nov 2, 2014, at 5:39 AM, Mario Sangiorgio > > > > > > > > > wrote: > > > > > > > > > > First, the wiki says: > > > > > As of January 2013, FreeBSD-CURRENT fully supports either a > > > > > video console (you'll need a USB keyboard and display > > > > > connected) or it can be > > > > configured > > > > > to use a serial console (you'll need a serial adapter cable > > > > > such as the > > > > one > > > > > sold by Adafruit.com). > > > > > > > > > > Does it mean that by default the access via the serial > > > > > adapter is not enabled by default and it needs to be > > > > > configured in a special way? > > > > > > > > The serial console is always enabled. > > > > > > > > Tim > > > > > > > > > > > _______________________________________________ > > > freebsd-arm@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > To unsubscribe, send any mail to > > > "freebsd-arm-unsubscribe@freebsd.org" > > > > From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 00:27:20 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC036F92 for ; Mon, 3 Nov 2014 00:27:20 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 609A8A1C for ; Mon, 3 Nov 2014 00:27:20 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id p9so2885640lbv.28 for ; Sun, 02 Nov 2014 16:27:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:from:date:message-id:subject:to:cc :content-type; bh=sa2KQt/DqJQjBV6QlfbwhMrype8mgrAxJkdgm/EM19U=; b=y8U+0kCxrd6nIIswCS4i4Pi0FKnJvg+cnL5W4HcVKZZOecl8waKYNzsLkBkcWtIvBI LCZOuKDKfIL24XeBuAT8RGXCUen7NCMBWmVeM6ts3296jUZtxcnaphQDkwQSA2LbsoZO fNSYiChKPRulRYhJ/hAF+0vpsbbri7CxKzdi13UbxmGxvkjLS2HpjYBrg+5ALBnvuVW2 NfbEQOUq3AxCC2jAx4JrBT0c8Lcs/+k12osrOzgYO7sB+8WpVU6KRPcx/vxshDXOpMlC VpCF8KoB3JGgdnFWkpWaW6iwVgK5krTZGVISWOwmFck+MsAfWcUwQIJzZZYdDjC/WMKh SHsA== X-Received: by 10.152.45.1 with SMTP id i1mr10402142lam.7.1414974438352; Sun, 02 Nov 2014 16:27:18 -0800 (PST) MIME-Version: 1.0 References: <20141103075417.7a402357@X220.alogt.com> <20141103082443.2db41632@X220.alogt.com> From: Mario Sangiorgio Date: Mon, 03 Nov 2014 00:27:17 +0000 Message-ID: Subject: Re: FreeBSD on Raspberry PI To: Erich Dollansky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tim Kientzle , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 00:27:21 -0000 I see. I think that the guide I followed was talking about a fresh install with no configuration customisations On Mon, 3 Nov 2014 00:24 Erich Dollansky wrote: > Hi, > > On Mon, 03 Nov 2014 00:02:33 +0000 > Mario Sangiorgio wrote: > > > I think I read on an online guide that ssh needed to be enabled. > > Maybe it was outdated. > > > > Tomorrow I'll give it a shot then. Should I try to connect as root > > with an empty password? > > > I do not even know. I copy my own configuration files and password > database onto the image. This gives me the passwords of the other > machine and all the settings as I expect it. > > Erich > > > > On Sun, 2 Nov 2014 23:54 Erich Dollansky > > wrote: > > > > > Hi, > > > > > > On Sun, 02 Nov 2014 17:15:53 +0000 > > > Mario Sangiorgio wrote: > > > > > > > Thank you all for your answers. As soon as I'll get a serial > > > > console usb cable I'll install FreeBSD on my Raspberry Pi. > > > > > > > don't you have a network at home? A RJ-45 cable and off you go. I > > > did not connect keyboard or monitor to any of my Raspberries yet. > > > SSH works from the images, telnet has to be enabled. > > > > > > > Regarding the update, is it just a matter of copying the new > > > > version of these files [1] in /boot? > > > > > > Look at the archives for a conversation between YAMAMOTO Shigeru and > > > me. YAMAMOTO explains it very well. And it works without flaws. > > > > > > Erich > > > > > > > > > > > > > > [1] https://github.com/raspberrypi/firmware/tree/master/boot > > > > > > > > On Sun Nov 02 2014 at 4:56:16 PM Tim Kientzle > > > > wrote: > > > > > > > > > > > > > > > On Nov 2, 2014, at 5:39 AM, Mario Sangiorgio > > > > > > > > > > > wrote: > > > > > > > > > > > > First, the wiki says: > > > > > > As of January 2013, FreeBSD-CURRENT fully supports either a > > > > > > video console (you'll need a USB keyboard and display > > > > > > connected) or it can be > > > > > configured > > > > > > to use a serial console (you'll need a serial adapter cable > > > > > > such as the > > > > > one > > > > > > sold by Adafruit.com). > > > > > > > > > > > > Does it mean that by default the access via the serial > > > > > > adapter is not enabled by default and it needs to be > > > > > > configured in a special way? > > > > > > > > > > The serial console is always enabled. > > > > > > > > > > Tim > > > > > > > > > > > > > > _______________________________________________ > > > > freebsd-arm@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > > To unsubscribe, send any mail to > > > > "freebsd-arm-unsubscribe@freebsd.org" > > > > > > > > From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 00:29:04 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8EA36FE8 for ; Mon, 3 Nov 2014 00:29:04 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) by mx1.freebsd.org (Postfix) with ESMTP id 50249A2C for ; Mon, 3 Nov 2014 00:29:03 +0000 (UTC) Received: from [75.187.32.8] ([75.187.32.8:36361] helo=raspberrypi.bildanet.com) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id FF/86-07476-E4CC6545; Mon, 03 Nov 2014 00:29:02 +0000 Received: from [192.168.1.25] (helo=desktop.bildanet.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1Xl5W2-0003Ox-Dl for freebsd-arm@freebsd.org; Sun, 02 Nov 2014 19:29:02 -0500 From: Baho Utot To: freebsd-arm@freebsd.org Subject: Re: FreeBSD on Raspberry PI Date: Sun, 02 Nov 2014 19:30:16 -0500 Message-ID: <5896289.HfUuql2DB6@desktop.bildanet.com> User-Agent: KMail/4.14.2 (Linux/3.17.1-1-ARCH; KDE/4.14.2; x86_64; ; ) In-Reply-To: References: <20141103075417.7a402357@X220.alogt.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 00:29:04 -0000 On Monday 03 November 2014 12:02:33 AM Mario Sangiorgio wrote: > I think I read on an online guide that ssh needed to be enabled. Maybe it > was outdated. > > Tomorrow I'll give it a shot then. Should I try to connect as root with an > empty password? > Won't work as root login to sshd is disabled. You will need to login as a user and su - to get root. Just connect an HDMI display and add a usb keyboard. Then boot it and after it is finished expanding the filesystem top use the whole sd card. Login and add a user. making sure the added user is also in the wheel group. I also use a static ipv4 address so when I try to ssh in I will know the ip. Now you can connect it on your network and ssh in and install ports and build whatever you need. One of the first things I build is screen so I can detach and log out ( break ssh connection ) and it will still build what ever package. If you are not using screen when you log out of your ssh connection your build will stop. Building ports can take a long time, some over nite. From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 05:51:26 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2105245F for ; Mon, 3 Nov 2014 05:51:26 +0000 (UTC) Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC78FB54 for ; Mon, 3 Nov 2014 05:51:25 +0000 (UTC) Received: by mail-pd0-f182.google.com with SMTP id fp1so10948457pdb.13 for ; Sun, 02 Nov 2014 21:51:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=NGa1q55KElCqA3ZR7YpnUY24UI9H4Qfw8iVR8F2Kkws=; b=ed7bY91+aIYbZngVvPqiYJ5s6jAHD9NCg76FeeZcSZ9LNeZTphn9qRtVJEHQ13ygKC +4NviupMLtVv7Ys3nLidp5lAsym13MMpQgqa4G+ss4/upt9FCR0q8wdqcVWBbLnmpfsj qLVXTT5vHe/p3gXo5jitq7ZE8TWLO/aEPDLjWImfFPk2Ky0c8IBtzrr2vDkP+nDGB/Ds T+/YXgTixsQAMY2yvqiva5Pxq3TpgkP5C/X2lqLAXDQGM6VP6bG+N2mBxPtkDIufwNhF +3w2F9AuWD2SEhShoLe0vjKtGh8jX419P6dXFoiOYL778d2MAz7WqVK/WvlSRl4rmUoT /pCQ== MIME-Version: 1.0 X-Received: by 10.70.95.198 with SMTP id dm6mr41050384pdb.58.1414993885461; Sun, 02 Nov 2014 21:51:25 -0800 (PST) Received: by 10.70.83.193 with HTTP; Sun, 2 Nov 2014 21:51:25 -0800 (PST) In-Reply-To: References: <54527218.2090008@ceetonetechnology.com> Date: Mon, 3 Nov 2014 06:51:25 +0100 Message-ID: Subject: Re: building cross-compiling tools on -CURRENT From: Zsolt Udvari To: Warner Losh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 05:51:26 -0000 2014-11-02 20:06 GMT+01:00 Warner Losh : > I=E2=80=99ve never had an issue building mips32 / arm on a amd64 host. You're lucky :) From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 12:32:36 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04F96EEF for ; Mon, 3 Nov 2014 12:32:36 +0000 (UTC) Received: from fallback7.mail.ru (fallback7.mail.ru [94.100.181.128]) by mx1.freebsd.org (Postfix) with ESMTP id B0233A59 for ; Mon, 3 Nov 2014 12:32:35 +0000 (UTC) Received: from smtp37.i.mail.ru (smtp37.i.mail.ru [94.100.177.97]) by fallback7.mail.ru (mPOP.Fallback_MX) with ESMTP id 61E7111C02942 for ; Mon, 3 Nov 2014 15:32:04 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=list.ru; s=mail; h=Date:Message-Id:Content-Type:MIME-Version:Subject:To:From; bh=UZKpPMuT0MwSwc//sA4YP0c7WEfqlNi4P8gtRWixcHw=; b=DhxmqkAP6RuK7uxo8M0shWDiluhSZool0bdU3ddOrNdYdfFVav1eN4m+nNfUx/pl75IRCF/hJ9VD2kRvuyQQ2zlTFSiAbAxL6zWkw08Cs9N44RTLOJ6AtKz7xug0FXuIgvjCiBNLdyJsZJ2qW+vWa740snYiudjAB1XsFm3UvR8=; Received: from [209.159.138.19] (port=10453 helo=localhost) by smtp37.i.mail.ru with esmtpa (envelope-from ) id 1XlGna-0002Ky-4L for freebsd-arm@FreeBSD.org; Mon, 03 Nov 2014 15:31:55 +0300 From: sig6247 To: freebsd-arm@FreeBSD.org Subject: dd /dev/random hangs on RPI-B+ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: Date: Mon, 03 Nov 2014 15:31:55 +0300 X-Spam: Not detected X-Mras: Ok X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 12:32:36 -0000 Hi, I'm running r273923, just noticed dd hangs with /dev/random, something like % dd if=/dev/random of=/dev/null bs=512K count=1 It never returns and takes all the CPU, and this process can't be killed. I also tried dd if=/dev/zero or dd if=/dev/mmcsd0, they both look fine. Any help would be appreciated. From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 14:01:48 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 45F274A9 for ; Mon, 3 Nov 2014 14:01:48 +0000 (UTC) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (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 086605E9 for ; Mon, 3 Nov 2014 14:01:47 +0000 (UTC) Received: from 127.0.0.1 (kaputte.li [194.150.168.95]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id sA3E5QBV066161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 3 Nov 2014 09:05:29 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <54578ABD.3010906@ceetonetechnology.com> Date: Mon, 03 Nov 2014 09:01:33 -0500 From: George Rosamond MIME-Version: 1.0 To: Zsolt Udvari , Warner Losh Subject: Re: building cross-compiling tools on -CURRENT References: <54527218.2090008@ceetonetechnology.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 14:01:48 -0000 Zsolt Udvari: > 2014-11-02 20:06 GMT+01:00 Warner Losh : >> I’ve never had an issue building mips32 / arm on a amd64 host. > You're lucky :) > Anyone who's built an RPi or BeagleBone image off an amd64 box is in the same boat... it's also just worked. I'm not using QEMU, VirtualBox, etc. But thanks for the input regardless. g From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 14:08:29 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9E4DB609 for ; Mon, 3 Nov 2014 14:08:29 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (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 72FE8645 for ; Mon, 3 Nov 2014 14:08:28 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XlIJ1-000Nng-CA; Mon, 03 Nov 2014 14:08:27 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id sA3E8Pqc091990; Mon, 3 Nov 2014 07:08:25 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18ORFfEyGFlen5G9h3NJ+B5 X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: dd /dev/random hangs on RPI-B+ From: Ian Lepore To: sig6247 In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Mon, 03 Nov 2014 07:08:24 -0700 Message-ID: <1415023704.1200.47.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 14:08:29 -0000 On Mon, 2014-11-03 at 15:31 +0300, sig6247 wrote: > Hi, > > I'm running r273923, just noticed dd hangs with /dev/random, > something like > > % dd if=/dev/random of=/dev/null bs=512K count=1 > > It never returns and takes all the CPU, and this process can't be > killed. I also tried dd if=/dev/zero or dd if=/dev/mmcsd0, they > both look fine. > > Any help would be appreciated. Please update to r273958 or later. /dev/random was briefly broken, it didn't get fully seeded before launching userland apps and they could get blocked waiting for more entropy. Making it a bit worse, it also didn't handle signals correctly so you couldn't cancel. Should be all fixed now. -- Ian From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 14:12:14 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E77756BB for ; Mon, 3 Nov 2014 14:12:14 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A8D6C751 for ; Mon, 3 Nov 2014 14:12:14 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XlIMX-0002lB-K0; Mon, 03 Nov 2014 15:12:11 +0100 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-arm@freebsd.org, sig6247 Subject: Re: dd /dev/random hangs on RPI-B+ References: Date: Mon, 03 Nov 2014 15:12:04 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.17 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, BAYES_20 autolearn=disabled version=3.3.2 X-Scan-Signature: c74461a82029b6293650421ecb57b64a X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 14:12:15 -0000 On Mon, 03 Nov 2014 13:31:55 +0100, sig6247 wrote: > > Hi, > > I'm running r273923, just noticed dd hangs with /dev/random, > something like > > % dd if=/dev/random of=/dev/null bs=512K count=1 > > It never returns and takes all the CPU, and this process can't be > killed. I also tried dd if=/dev/zero or dd if=/dev/mmcsd0, they > both look fine. > > Any help would be appreciated. Hi, There were some significant changes to the random device recently. There are fixes after r273923, so it is worth to try updating your source tree and building a new image. NB: I assume you run 11-CURRENT. Ronald. From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 14:22:12 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE6558D5 for ; Mon, 3 Nov 2014 14:22:12 +0000 (UTC) Received: from smtp69.iad3a.emailsrvr.com (smtp69.iad3a.emailsrvr.com [173.203.187.69]) (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 7DB2C84A for ; Mon, 3 Nov 2014 14:22:12 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp25.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id F073118034B for ; Mon, 3 Nov 2014 09:12:29 -0500 (EST) X-Virus-Scanned: OK Received: from app5.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp25.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id CD972180328 for ; Mon, 3 Nov 2014 09:12:29 -0500 (EST) X-Sender-Id: scott@jumpnowtek.com Received: from app5.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.3.2); Mon, 03 Nov 2014 14:12:29 GMT Received: from jumpnowtek.com (localhost.localdomain [127.0.0.1]) by app5.wa-webapps.iad3a (Postfix) with ESMTP id BB9A0180043 for ; Mon, 3 Nov 2014 09:12:29 -0500 (EST) Received: by apps.rackspace.com (Authenticated sender: scott@jumpnowtek.com, from: scott@jumpnowtek.com) with HTTP; Mon, 3 Nov 2014 09:12:29 -0500 (EST) Date: Mon, 3 Nov 2014 09:12:29 -0500 (EST) Subject: Wandboard Dual and Crochet-FreeBSD From: "Scott Ellis" To: freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Importance: Normal X-Priority: 3 (Normal) X-Type: plain X-Auth-ID: scott@jumpnowtek.com Message-ID: <1415023949.765217459@apps.rackspace.com> X-Mailer: webmail7.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 14:22:12 -0000 Wandboard-Quad crochet builds are working fine using the default=0Aconfig i= n freebsd-crochet/board/Wandboard using CURRENT r273961 =0Afor the source.= =0A=0AI tried creating a new freebsd-crochet/board/Wandboard-Dual config = =0Adirectory with the following changes=0A=0Ascott@fbsd:~/crochet-freebsd/b= oard % diff -r Wandboard Wandboard-Dual=0A=0Adiff -r Wandboard/files/boot.t= xt Wandboard-Dual/files/boot.txt=0A1c1=0A< setenv fdt_file wandboard-quad.d= tb;fatload mmc 0:1 88000000 ubldr;bootelf 88000000;=0A---=0A> setenv fdt_fi= le wandboard-dual.dtb;fatload mmc 0:1 88000000 ubldr;bootelf 88000000;=0A= =0Adiff -r Wandboard/setup.sh Wandboard-Dual/setup.sh=0A33c33=0A< strat= egy_add $PHASE_BUILD_OTHER uboot_configure $WANDBOARD_UBOOT_SRC wandboard_q= uad_config=0A---=0A> strategy_add $PHASE_BUILD_OTHER uboot_configure $W= ANDBOARD_UBOOT_SRC wandboard_dl_config=0A66,67c66,67=0A< freebsd_instal= l_fdt wandboard-quad.dts wandboard-quad.dts=0A< freebsd_install_fdt wan= dboard-quad.dts wandboard-quad.dtb=0A---=0A> freebsd_install_fdt wandbo= ard-dual.dts wandboard-dual.dts=0A> freebsd_install_fdt wandboard-dual.= dts wandboard-dual.dtb=0A76,77c76,77=0A< freebsd_install_fdt wandboard-= quad.dts boot/kernel/wandboard-quad.dts=0A< freebsd_install_fdt wandboa= rd-quad.dts boot/kernel/wandboard-quad.dtb=0A---=0A> freebsd_install_fd= t wandboard-dual.dts boot/kernel/wandboard-dual.dts=0A> freebsd_install= _fdt wandboard-dual.dts boot/kernel/wandboard-dual.dtb=0A=0A=0AWhen I try t= o boot the resulting image on a Wandboard-Dual it hangs here=0A=0A=0AU-Boot= 2014.07 (Nov 02 2014 - 13:03:34)=0A=0ACPU: Freescale i.MX6DL rev1.1 at 7= 92 MHz=0AReset cause: POR=0ABoard: Wandboard=0AI2C: ready=0ADRAM: 1 GiB= =0AWARNING: Caches not enabled=0AMMC: FSL_SDHC: 0, FSL_SDHC: 1=0A*** Warn= ing - bad CRC, using default environment=0A=0ANo panel detected: default to= HDMI=0ADisplay: HDMI (1024x768)=0AIn: serial=0AOut: serial=0AErr: s= erial=0ANet: FEC [PRIME]=0AHit any key to stop autoboot: 0=0Aswitch to p= artitions #0, OK=0Ammc0 is current device=0Areading boot.scr=0A157 bytes re= ad in 10 ms (14.6 KiB/s)=0ARunning bootscript from mmc ...=0A## Executing s= cript at 12000000=0Areading ubldr=0A251107 bytes read in 27 ms (8.9 MiB/s)= =0A(hang)=0A=0A=0AA Wandboard-Quad boot looks like this=0A=0A=0AU-Boot 2014= .07 (Nov 01 2014 - 16:31:42)=0A=0ACPU: Freescale i.MX6Q rev1.2 at 792 MHz= =0AReset cause: WDOG=0ABoard: Wandboard=0AI2C: ready=0ADRAM: 2 GiB=0AWAR= NING: Caches not enabled=0AMMC: FSL_SDHC: 0, FSL_SDHC: 1=0A*** Warning - = bad CRC, using default environment=0A=0ANo panel detected: default to HDMI= =0ADisplay: HDMI (1024x768)=0AIn: serial=0AOut: serial=0AErr: serial= =0ANet: FEC [PRIME]=0AHit any key to stop autoboot: 0=0Aswitch to partit= ions #0, OK=0Ammc0 is current device=0Areading boot.scr=0A157 bytes read in= 10 ms (14.6 KiB/s)=0ARunning bootscript from mmc ...=0A## Executing script= at 12000000=0Areading ubldr=0A251107 bytes read in 27 ms (8.9 MiB/s)=0A## = Starting application at 0x88000054 ...=0AConsoles: U-Boot console=0ACompati= ble U-Boot API signature found @8f5854a8=0A=0AFreeBSD/armv6 U-Boot loader, = Revision 1.2=0A(root@fbsd, Sun Nov 2 06:29:08 EST 2014)=0A=0A... kernel bo= ots=0A=0A=0ASo it looks to me like u-boot built okay, but maybe ubldr did n= ot.=0A=0AWhat is the correct way to setup crochet-freebsd to build for a = =0AWandboard-Dual or Solo?=0A=0A=0A From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 15:06:37 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 903912ED for ; Mon, 3 Nov 2014 15:06:37 +0000 (UTC) Received: from nibbler.fubar.geek.nz (nibbler.fubar.geek.nz [199.48.134.198]) by mx1.freebsd.org (Postfix) with ESMTP id 735FEC89 for ; Mon, 3 Nov 2014 15:06:37 +0000 (UTC) Received: from bender.lan (97e078e7.skybroadband.com [151.224.120.231]) by nibbler.fubar.geek.nz (Postfix) with ESMTPSA id 452E45C001; Mon, 3 Nov 2014 15:06:35 +0000 (UTC) Date: Mon, 3 Nov 2014 15:06:28 +0000 From: Andrew Turner To: Zsolt Udvari Subject: Re: building cross-compiling tools on -CURRENT Message-ID: <20141103150628.0b815182@bender.lan> In-Reply-To: References: <54527218.2090008@ceetonetechnology.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 15:06:37 -0000 On Sun, 2 Nov 2014 08:08:29 +0100 Zsolt Udvari wrote: > I've tried similar about a one month ago and I ran into linker error > too. I've read this: > " For 64-bit targets (i.e. mips64) use an 64-bit host (i.e. amd64). > For 32-bit targets (i.e. armv6) use an 32-bit host (i.e. i386) or > compat-32. It may be possible to emulate 32-bit targets on a 64-bit > host in the future but currently that is not possible. " > https://wiki.freebsd.org/QemuUserModeHowTo > I don't find the url but as I remember it was written somewhere that > it maybe causes linker errors. That page is taking about running applications under QEMU its usermode emulation. For cross-building world and the kernel there is no for QEMU. Cross building for arm on an amd64 host is supported, however it would appear the xdev target is under tested as it it quite often broken. Andrew From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 15:18:05 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 657FC42A for ; Mon, 3 Nov 2014 15:18:05 +0000 (UTC) Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 283E9D89 for ; Mon, 3 Nov 2014 15:18:04 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id rl12so5506373iec.10 for ; Mon, 03 Nov 2014 07:17:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=X5hiLe+NZvU6bBtx6J1HUDmn6ri0nhUouc7kZnYbVr0=; b=ZR71NH1E5PNBe50a8IFKmjgie01AE1JA4m1xjNvlhgyfMmfv4r1gkDrELbCUZWgtAS 7d+6zJ2AJHdpWWVWqnRqQ4nG0g1bRJgheodJjYmUsu87juGifyY6GkAh4kFnPbL3RbLS Y/26CBzROlwnUzPw9jCIf8yYod1aJ5UYPfzzI5tPivkerH1LJaxHqTO3zDJ5nk5wqf0i tpcg2LGFdadFdFiJKituKBR4i+JJR7IBiuhyuSROIq7xomXYjq6wLhvljPkVo8UGPp3U JLq89oZFTa1AhHxYJd/AySL6QDc/kwe4+KtoAwSM43bWz0dMDDB9QG2jXwSg4vLbjFCN /4MQ== X-Gm-Message-State: ALoCoQmTEzNVpUph58X+ysTXSWgiccbOkDWzZ5Vu2fCkEiXsP/sqD9ZQsqK59l89sCTrc3/NFKVW X-Received: by 10.42.142.201 with SMTP id t9mr2366536icu.60.1415027878570; Mon, 03 Nov 2014 07:17:58 -0800 (PST) Received: from netflix-mac.bsdimp.com ([50.253.99.174]) by mx.google.com with ESMTPSA id x9sm3772315igl.10.2014.11.03.07.17.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Nov 2014 07:17:57 -0800 (PST) Sender: Warner Losh Content-Type: multipart/signed; boundary="Apple-Mail=_48926A5C-51C1-4EEB-B1F7-2CA307E09464"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: building cross-compiling tools on -CURRENT From: Warner Losh In-Reply-To: Date: Mon, 3 Nov 2014 08:17:54 -0700 Message-Id: <73D2ECA4-FDDD-4843-BAC4-56D483E044A8@bsdimp.com> References: <54527218.2090008@ceetonetechnology.com> To: Zsolt Udvari X-Mailer: Apple Mail (2.1878.6) Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 15:18:05 -0000 --Apple-Mail=_48926A5C-51C1-4EEB-B1F7-2CA307E09464 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Nov 2, 2014, at 10:51 PM, Zsolt Udvari wrote: > 2014-11-02 20:06 GMT+01:00 Warner Losh : >> I=92ve never had an issue building mips32 / arm on a amd64 host. > You're lucky :) No. It works. And has for at least a decade, if not 15 years. Warner --Apple-Mail=_48926A5C-51C1-4EEB-B1F7-2CA307E09464 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUV5yjAAoJEGwc0Sh9sBEALQoP/2G+YnCm3GzEJMUvhqbTumUr Pr65fIH0MCWLcqQTIJ6z1bcPNuNQthN/pA3I70gn8eTqYiA+ScJBthbhqPKW2SfQ hfNGr6Zs8bpknoOG7pS5yK2mD5fEmGzRRMehe9rmLYYS+7nu3d40WX2G9/HBIvGx liodwp7G1BH6Nxm9nu51aMxvZJBJ2CNI0BGY4FypTuO/7Fhv9a/6mV8aHSerPIXG oPKkMICPsFipSP4h4i3nq8dXkOp99Z9GjoH2XKa7OC14m/vy7RS17J4SHwudH0oR UL7i4R8/8NlKpEF9i6Co9sSHY7Ir//EaGWbcMiXT7wIwWjDWKce6/FiZMz831kmN WZ9Q7zz+ywSeXBKVTW2PuofEf6GPGyG9MgAPPPUHIX2umA+p9fZq/5mIlj8cOQxd j1ZpFYLC46Xz7i7jPBgdPSE/pLVNav0qlnx2YA2aCMsk608bJjyIQ6Yf29q7SWnD 6G9+ngsR/E21bGFvK1VrPqSbnq7yyYbFJ70Tiphb3qeGb0T/UqzNsOhNaI4+epQB 5TVEjNs3mvkRWk8pUm0q39T0o7oxbunme5hTr9o3R11BC+cPpKW+faUps7mdVmw2 2302zhucyvBzXRkVcyz16p5kaaqNEKjxWLm1+0npCNm3AOPUl5chf4I/gCiEsoQb gvnbRB8T6sp+K/KFIyrF =EW4x -----END PGP SIGNATURE----- --Apple-Mail=_48926A5C-51C1-4EEB-B1F7-2CA307E09464-- From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 15:31:05 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5B53E875 for ; Mon, 3 Nov 2014 15:31:05 +0000 (UTC) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32207EA2 for ; Mon, 3 Nov 2014 15:31:05 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id r10so11669019pdi.16 for ; Mon, 03 Nov 2014 07:31:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZrJZPq6slNpc4Zph50vD8y2ymV3bCgiBHizpDVQ8Etw=; b=cbAaDsXx+rOY65O7VyNCjuR2MjLsv0eRUGGzXb32iU/tGxU3qNyWSNxyiLgZs2VsWm vfVw5fvrJ1W+WghR3BzYBpRREUjVsMjbMJj91vgfXMGF9Jyfav6fDyQIaSjMD7F8fRxl vXYJZ5KAIEAVLMV8CIzEG7mogOTf0Co+iXBXWswBSTkriWkp/sTb9ioLcY3ncIaUYH9z BqbpPuCo0AKUb5LWWVj7Tp0BOzmIDbrnOAoJlhw9xniN0eASBPY10G3ovYGNg+VxY6cN eUuemZ4uF9SvDgxUXyZ6otogzrYuWXOSCaEjtncbnajLQZ475TJFz9sIIDyN+9Q0++E+ Aicw== MIME-Version: 1.0 X-Received: by 10.70.44.99 with SMTP id d3mr44099987pdm.46.1415028664735; Mon, 03 Nov 2014 07:31:04 -0800 (PST) Received: by 10.70.83.193 with HTTP; Mon, 3 Nov 2014 07:31:04 -0800 (PST) In-Reply-To: <54578ABD.3010906@ceetonetechnology.com> References: <54527218.2090008@ceetonetechnology.com> <54578ABD.3010906@ceetonetechnology.com> Date: Mon, 3 Nov 2014 16:31:04 +0100 Message-ID: Subject: Re: building cross-compiling tools on -CURRENT From: Zsolt Udvari To: George Rosamond Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 15:31:05 -0000 2014-11-03 15:01 GMT+01:00 George Rosamond : > Anyone who's built an RPi or BeagleBone image off an amd64 box is in the > same boat... it's also just worked. I'm not using QEMU, VirtualBox, etc. First I've tried as you. And I've same error as you. I've read it somewhere (not in the linked article) that *maybe* (so not everytime) causes linker problems - the link: http://www.cruwe.de/?p=78 "Careful: Packages will not link properly when cross-compiling on amd64. ARMv6 is 32b, so linking in a 64b address space will fail!" But if it's a solution I want to know too :) Zsolt From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 15:59:41 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E014BDE8 for ; Mon, 3 Nov 2014 15:59:41 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (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 A29951E5 for ; Mon, 3 Nov 2014 15:59:41 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XlK2d-0008UY-FM; Mon, 03 Nov 2014 15:59:39 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id sA3FxcxN092136; Mon, 3 Nov 2014 08:59:38 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/1hc2CM4lJVFJXu46XoeR5 X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: Wandboard Dual and Crochet-FreeBSD From: Ian Lepore To: Scott Ellis In-Reply-To: <1415023949.765217459@apps.rackspace.com> References: <1415023949.765217459@apps.rackspace.com> Content-Type: text/plain; charset="us-ascii" Date: Mon, 03 Nov 2014 08:59:37 -0700 Message-ID: <1415030377.1200.56.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 15:59:42 -0000 On Mon, 2014-11-03 at 09:12 -0500, Scott Ellis wrote: > Wandboard-Quad crochet builds are working fine using the default > config in freebsd-crochet/board/Wandboard using CURRENT r273961 > for the source. > > I tried creating a new freebsd-crochet/board/Wandboard-Dual config > directory with the following changes > > scott@fbsd:~/crochet-freebsd/board % diff -r Wandboard Wandboard-Dual > > diff -r Wandboard/files/boot.txt Wandboard-Dual/files/boot.txt > 1c1 > < setenv fdt_file wandboard-quad.dtb;fatload mmc 0:1 88000000 ubldr;bootelf 88000000; > --- > > setenv fdt_file wandboard-dual.dtb;fatload mmc 0:1 88000000 ubldr;bootelf 88000000; > > diff -r Wandboard/setup.sh Wandboard-Dual/setup.sh > 33c33 > < strategy_add $PHASE_BUILD_OTHER uboot_configure $WANDBOARD_UBOOT_SRC wandboard_quad_config > --- > > strategy_add $PHASE_BUILD_OTHER uboot_configure $WANDBOARD_UBOOT_SRC wandboard_dl_config > 66,67c66,67 > < freebsd_install_fdt wandboard-quad.dts wandboard-quad.dts > < freebsd_install_fdt wandboard-quad.dts wandboard-quad.dtb > --- > > freebsd_install_fdt wandboard-dual.dts wandboard-dual.dts > > freebsd_install_fdt wandboard-dual.dts wandboard-dual.dtb > 76,77c76,77 > < freebsd_install_fdt wandboard-quad.dts boot/kernel/wandboard-quad.dts > < freebsd_install_fdt wandboard-quad.dts boot/kernel/wandboard-quad.dtb > --- > > freebsd_install_fdt wandboard-dual.dts boot/kernel/wandboard-dual.dts > > freebsd_install_fdt wandboard-dual.dts boot/kernel/wandboard-dual.dtb > > > When I try to boot the resulting image on a Wandboard-Dual it hangs here > > > U-Boot 2014.07 (Nov 02 2014 - 13:03:34) > > CPU: Freescale i.MX6DL rev1.1 at 792 MHz > Reset cause: POR > Board: Wandboard > I2C: ready > DRAM: 1 GiB > WARNING: Caches not enabled > MMC: FSL_SDHC: 0, FSL_SDHC: 1 > *** Warning - bad CRC, using default environment > > No panel detected: default to HDMI > Display: HDMI (1024x768) > In: serial > Out: serial > Err: serial > Net: FEC [PRIME] > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > reading boot.scr > 157 bytes read in 10 ms (14.6 KiB/s) > Running bootscript from mmc ... > ## Executing script at 12000000 > reading ubldr > 251107 bytes read in 27 ms (8.9 MiB/s) > (hang) > > > A Wandboard-Quad boot looks like this > > > U-Boot 2014.07 (Nov 01 2014 - 16:31:42) > > CPU: Freescale i.MX6Q rev1.2 at 792 MHz > Reset cause: WDOG > Board: Wandboard > I2C: ready > DRAM: 2 GiB > WARNING: Caches not enabled > MMC: FSL_SDHC: 0, FSL_SDHC: 1 > *** Warning - bad CRC, using default environment > > No panel detected: default to HDMI > Display: HDMI (1024x768) > In: serial > Out: serial > Err: serial > Net: FEC [PRIME] > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > reading boot.scr > 157 bytes read in 10 ms (14.6 KiB/s) > Running bootscript from mmc ... > ## Executing script at 12000000 > reading ubldr > 251107 bytes read in 27 ms (8.9 MiB/s) > ## Starting application at 0x88000054 ... > Consoles: U-Boot console > Compatible U-Boot API signature found @8f5854a8 > > FreeBSD/armv6 U-Boot loader, Revision 1.2 > (root@fbsd, Sun Nov 2 06:29:08 EST 2014) > > ... kernel boots > > > So it looks to me like u-boot built okay, but maybe ubldr did not. > > What is the correct way to setup crochet-freebsd to build for a > Wandboard-Dual or Solo? I think the problem is the 88000000 address. A dual board doesn't have that much ram. I load ubldr at 11000000 on all my wandboards (but I don't use crochet). I do know that it's important that ubldr be linked at the same address it's configured to load at, so you may have several places in crochet to adjust that 88000000 number. I just now booted a dual board (it's been a while) and it's working fine. Something I have not done for many months is boot a solo board, I guess I should check it sometime soon. -- Ian From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 16:13:31 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BADF31C for ; Mon, 3 Nov 2014 16:13:31 +0000 (UTC) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AAC35E0 for ; Mon, 3 Nov 2014 16:13:30 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id q5so6474551wiv.3 for ; Mon, 03 Nov 2014 08:13:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Z5OWTXo0zThIrC85ZTDnIsdtTLSeYpQgFTMXSfU/0Qc=; b=G0ueN0YhHM33yIQppM6f3rzUTkeRxzxli7tc7USK49C0vy5huXwGhRKezx7wW1OPKQ NNaycPuuaoIa8LjDfzUAdm5IPKSFlyHzR2uuY3fMAcsBfd3EtUM0etP1yUJTUH+Lppbz tBpQOwcxnegVIX+wPNlIbMQu/nO916d/pb0ligrmIiYkOENPsuSuyudeOqfd/ldGIadd SIlJCvagRXteLBkhpVR/KscUY92PSVsMBibHxV9Mh0Ejiq0bkx0V4DPaG52XJvmHwvWV 1fp/DETAcSwM/Hz2i1ziRsNAoydQCVDZ61Qmzooc5FXso0pP1jLSyW+ES/varNJY+B4N KufA== X-Gm-Message-State: ALoCoQk6+noiqPvbzc9j1VNmsgApjrOrnO/rEzn+WaA+3YvVm9w1yyEKG999qG5ZXUQIZKnbaFAf MIME-Version: 1.0 X-Received: by 10.181.29.105 with SMTP id jv9mr17643740wid.25.1415031202767; Mon, 03 Nov 2014 08:13:22 -0800 (PST) Received: by 10.217.182.133 with HTTP; Mon, 3 Nov 2014 08:13:22 -0800 (PST) In-Reply-To: <1415030377.1200.56.camel@revolution.hippie.lan> References: <1415023949.765217459@apps.rackspace.com> <1415030377.1200.56.camel@revolution.hippie.lan> Date: Mon, 3 Nov 2014 09:13:22 -0700 Message-ID: Subject: Re: Wandboard Dual and Crochet-FreeBSD From: Tom Everett To: Ian Lepore Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 16:13:31 -0000 Could I ask that you submit a bug here? https://github.com/kientzle/crochet-freebsd I only have a Quad, so that is what I built for. I am willing to make some fixes, if a tester will volunteer to verify them on the dual. On Mon, Nov 3, 2014 at 8:59 AM, Ian Lepore wrote: > On Mon, 2014-11-03 at 09:12 -0500, Scott Ellis wrote: > > Wandboard-Quad crochet builds are working fine using the default > > config in freebsd-crochet/board/Wandboard using CURRENT r273961 > > for the source. > > > > I tried creating a new freebsd-crochet/board/Wandboard-Dual config > > directory with the following changes > > > > scott@fbsd:~/crochet-freebsd/board % diff -r Wandboard Wandboard-Dual > > > > diff -r Wandboard/files/boot.txt Wandboard-Dual/files/boot.txt > > 1c1 > > < setenv fdt_file wandboard-quad.dtb;fatload mmc 0:1 88000000 > ubldr;bootelf 88000000; > > --- > > > setenv fdt_file wandboard-dual.dtb;fatload mmc 0:1 88000000 > ubldr;bootelf 88000000; > > > > diff -r Wandboard/setup.sh Wandboard-Dual/setup.sh > > 33c33 > > < strategy_add $PHASE_BUILD_OTHER uboot_configure > $WANDBOARD_UBOOT_SRC wandboard_quad_config > > --- > > > strategy_add $PHASE_BUILD_OTHER uboot_configure > $WANDBOARD_UBOOT_SRC wandboard_dl_config > > 66,67c66,67 > > < freebsd_install_fdt wandboard-quad.dts wandboard-quad.dts > > < freebsd_install_fdt wandboard-quad.dts wandboard-quad.dtb > > --- > > > freebsd_install_fdt wandboard-dual.dts wandboard-dual.dts > > > freebsd_install_fdt wandboard-dual.dts wandboard-dual.dtb > > 76,77c76,77 > > < freebsd_install_fdt wandboard-quad.dts > boot/kernel/wandboard-quad.dts > > < freebsd_install_fdt wandboard-quad.dts > boot/kernel/wandboard-quad.dtb > > --- > > > freebsd_install_fdt wandboard-dual.dts > boot/kernel/wandboard-dual.dts > > > freebsd_install_fdt wandboard-dual.dts > boot/kernel/wandboard-dual.dtb > > > > > > When I try to boot the resulting image on a Wandboard-Dual it hangs here > > > > > > U-Boot 2014.07 (Nov 02 2014 - 13:03:34) > > > > CPU: Freescale i.MX6DL rev1.1 at 792 MHz > > Reset cause: POR > > Board: Wandboard > > I2C: ready > > DRAM: 1 GiB > > WARNING: Caches not enabled > > MMC: FSL_SDHC: 0, FSL_SDHC: 1 > > *** Warning - bad CRC, using default environment > > > > No panel detected: default to HDMI > > Display: HDMI (1024x768) > > In: serial > > Out: serial > > Err: serial > > Net: FEC [PRIME] > > Hit any key to stop autoboot: 0 > > switch to partitions #0, OK > > mmc0 is current device > > reading boot.scr > > 157 bytes read in 10 ms (14.6 KiB/s) > > Running bootscript from mmc ... > > ## Executing script at 12000000 > > reading ubldr > > 251107 bytes read in 27 ms (8.9 MiB/s) > > (hang) > > > > > > A Wandboard-Quad boot looks like this > > > > > > U-Boot 2014.07 (Nov 01 2014 - 16:31:42) > > > > CPU: Freescale i.MX6Q rev1.2 at 792 MHz > > Reset cause: WDOG > > Board: Wandboard > > I2C: ready > > DRAM: 2 GiB > > WARNING: Caches not enabled > > MMC: FSL_SDHC: 0, FSL_SDHC: 1 > > *** Warning - bad CRC, using default environment > > > > No panel detected: default to HDMI > > Display: HDMI (1024x768) > > In: serial > > Out: serial > > Err: serial > > Net: FEC [PRIME] > > Hit any key to stop autoboot: 0 > > switch to partitions #0, OK > > mmc0 is current device > > reading boot.scr > > 157 bytes read in 10 ms (14.6 KiB/s) > > Running bootscript from mmc ... > > ## Executing script at 12000000 > > reading ubldr > > 251107 bytes read in 27 ms (8.9 MiB/s) > > ## Starting application at 0x88000054 ... > > Consoles: U-Boot console > > Compatible U-Boot API signature found @8f5854a8 > > > > FreeBSD/armv6 U-Boot loader, Revision 1.2 > > (root@fbsd, Sun Nov 2 06:29:08 EST 2014) > > > > ... kernel boots > > > > > > So it looks to me like u-boot built okay, but maybe ubldr did not. > > > > What is the correct way to setup crochet-freebsd to build for a > > Wandboard-Dual or Solo? > > I think the problem is the 88000000 address. A dual board doesn't have > that much ram. I load ubldr at 11000000 on all my wandboards (but I > don't use crochet). I do know that it's important that ubldr be linked > at the same address it's configured to load at, so you may have several > places in crochet to adjust that 88000000 number. > > I just now booted a dual board (it's been a while) and it's working > fine. Something I have not done for many months is boot a solo board, I > guess I should check it sometime soon. > > -- Ian > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > -- A better world shall emerge based on faith and understanding - Douglas MacArthur From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 16:37:07 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75BDA8D0 for ; Mon, 3 Nov 2014 16:37:07 +0000 (UTC) Received: from smtp77.iad3a.emailsrvr.com (smtp77.iad3a.emailsrvr.com [173.203.187.77]) (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 38702907 for ; Mon, 3 Nov 2014 16:37:06 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp18.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 793B92802B2; Mon, 3 Nov 2014 11:27:53 -0500 (EST) X-Virus-Scanned: OK Received: from app52.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp18.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 570512800EC; Mon, 3 Nov 2014 11:27:53 -0500 (EST) X-Sender-Id: scott@jumpnowtek.com Received: from app52.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.3.2); Mon, 03 Nov 2014 16:27:53 GMT Received: from jumpnowtek.com (localhost.localdomain [127.0.0.1]) by app52.wa-webapps.iad3a (Postfix) with ESMTP id 432D8380043; Mon, 3 Nov 2014 11:27:53 -0500 (EST) Received: by apps.rackspace.com (Authenticated sender: scott@jumpnowtek.com, from: scott@jumpnowtek.com) with HTTP; Mon, 3 Nov 2014 11:27:53 -0500 (EST) Date: Mon, 3 Nov 2014 11:27:53 -0500 (EST) Subject: Re: Wandboard Dual and Crochet-FreeBSD From: "Scott Ellis" To: "Tom Everett" MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Importance: Normal X-Priority: 3 (Normal) X-Type: plain In-Reply-To: References: <1415023949.765217459@apps.rackspace.com> <1415030377.1200.56.camel@revolution.hippie.lan> X-Auth-ID: scott@jumpnowtek.com Message-ID: <1415032073.272927972@apps.rackspace.com> X-Mailer: webmail7.0 Cc: "freebsd-arm@freebsd.org" , Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 16:37:07 -0000 I submitted a bug and I am volunteering to test. =0A=0AI only have Quads an= d Duals.=0A=0A-----Original Message-----=0AFrom: "Tom Everett" =0ASent: Monday, November 3, 2014 11:13am=0ATo: "Ian Lepore" =0ACc: "Scott Ellis" , "freebsd-arm@freebsd.or= g" =0ASubject: Re: Wandboard Dual and Crochet-Free= BSD=0A=0ACould I ask that you submit a bug here?=0A=0Ahttps://github.com/ki= entzle/crochet-freebsd=0A=0AI only have a Quad, so that is what I built for= . I am willing to make some=0Afixes, if a tester will volunteer to verify = them on the dual.=0A=0A=0AOn Mon, Nov 3, 2014 at 8:59 AM, Ian Lepore wrote:=0A=0A> On Mon, 2014-11-03 at 09:12 -0500, Scott Ellis wr= ote:=0A> > Wandboard-Quad crochet builds are working fine using the default= =0A> > config in freebsd-crochet/board/Wandboard using CURRENT r273961=0A> = > for the source.=0A> >=0A> > I tried creating a new freebsd-crochet/board/= Wandboard-Dual config=0A> > directory with the following changes=0A> >=0A> = > scott@fbsd:~/crochet-freebsd/board % diff -r Wandboard Wandboard-Dual=0A>= >=0A> > diff -r Wandboard/files/boot.txt Wandboard-Dual/files/boot.txt=0A>= > 1c1=0A> > < setenv fdt_file wandboard-quad.dtb;fatload mmc 0:1 88000000= =0A> ubldr;bootelf 88000000;=0A> > ---=0A> > > setenv fdt_file wandboard-du= al.dtb;fatload mmc 0:1 88000000=0A> ubldr;bootelf 88000000;=0A> >=0A> > dif= f -r Wandboard/setup.sh Wandboard-Dual/setup.sh=0A> > 33c33=0A> > < str= ategy_add $PHASE_BUILD_OTHER uboot_configure=0A> $WANDBOARD_UBOOT_SRC wandb= oard_quad_config=0A> > ---=0A> > > strategy_add $PHASE_BUILD_OTHER uboo= t_configure=0A> $WANDBOARD_UBOOT_SRC wandboard_dl_config=0A> > 66,67c66,67= =0A> > < freebsd_install_fdt wandboard-quad.dts wandboard-quad.dts=0A> = > < freebsd_install_fdt wandboard-quad.dts wandboard-quad.dtb=0A> > ---= =0A> > > freebsd_install_fdt wandboard-dual.dts wandboard-dual.dts=0A> = > > freebsd_install_fdt wandboard-dual.dts wandboard-dual.dtb=0A> > 76,= 77c76,77=0A> > < freebsd_install_fdt wandboard-quad.dts=0A> boot/kernel= /wandboard-quad.dts=0A> > < freebsd_install_fdt wandboard-quad.dts=0A> = boot/kernel/wandboard-quad.dtb=0A> > ---=0A> > > freebsd_install_fdt wa= ndboard-dual.dts=0A> boot/kernel/wandboard-dual.dts=0A> > > freebsd_ins= tall_fdt wandboard-dual.dts=0A> boot/kernel/wandboard-dual.dtb=0A> >=0A> >= =0A> > When I try to boot the resulting image on a Wandboard-Dual it hangs = here=0A> >=0A> >=0A> > U-Boot 2014.07 (Nov 02 2014 - 13:03:34)=0A> >=0A> > = CPU: Freescale i.MX6DL rev1.1 at 792 MHz=0A> > Reset cause: POR=0A> > Boa= rd: Wandboard=0A> > I2C: ready=0A> > DRAM: 1 GiB=0A> > WARNING: Caches n= ot enabled=0A> > MMC: FSL_SDHC: 0, FSL_SDHC: 1=0A> > *** Warning - bad CR= C, using default environment=0A> >=0A> > No panel detected: default to HDMI= =0A> > Display: HDMI (1024x768)=0A> > In: serial=0A> > Out: serial=0A>= > Err: serial=0A> > Net: FEC [PRIME]=0A> > Hit any key to stop autoboo= t: 0=0A> > switch to partitions #0, OK=0A> > mmc0 is current device=0A> > = reading boot.scr=0A> > 157 bytes read in 10 ms (14.6 KiB/s)=0A> > Running b= ootscript from mmc ...=0A> > ## Executing script at 12000000=0A> > reading = ubldr=0A> > 251107 bytes read in 27 ms (8.9 MiB/s)=0A> > (hang)=0A> >=0A> >= =0A> > A Wandboard-Quad boot looks like this=0A> >=0A> >=0A> > U-Boot 2014.= 07 (Nov 01 2014 - 16:31:42)=0A> >=0A> > CPU: Freescale i.MX6Q rev1.2 at 7= 92 MHz=0A> > Reset cause: WDOG=0A> > Board: Wandboard=0A> > I2C: ready=0A= > > DRAM: 2 GiB=0A> > WARNING: Caches not enabled=0A> > MMC: FSL_SDHC: 0= , FSL_SDHC: 1=0A> > *** Warning - bad CRC, using default environment=0A> >= =0A> > No panel detected: default to HDMI=0A> > Display: HDMI (1024x768)=0A= > > In: serial=0A> > Out: serial=0A> > Err: serial=0A> > Net: FEC = [PRIME]=0A> > Hit any key to stop autoboot: 0=0A> > switch to partitions #= 0, OK=0A> > mmc0 is current device=0A> > reading boot.scr=0A> > 157 bytes r= ead in 10 ms (14.6 KiB/s)=0A> > Running bootscript from mmc ...=0A> > ## Ex= ecuting script at 12000000=0A> > reading ubldr=0A> > 251107 bytes read in 2= 7 ms (8.9 MiB/s)=0A> > ## Starting application at 0x88000054 ...=0A> > Cons= oles: U-Boot console=0A> > Compatible U-Boot API signature found @8f5854a8= =0A> >=0A> > FreeBSD/armv6 U-Boot loader, Revision 1.2=0A> > (root@fbsd, Su= n Nov 2 06:29:08 EST 2014)=0A> >=0A> > ... kernel boots=0A> >=0A> >=0A> > = So it looks to me like u-boot built okay, but maybe ubldr did not.=0A> >=0A= > > What is the correct way to setup crochet-freebsd to build for a=0A> > W= andboard-Dual or Solo?=0A>=0A> I think the problem is the 88000000 address.= A dual board doesn't have=0A> that much ram. I load ubldr at 11000000 on= all my wandboards (but I=0A> don't use crochet). I do know that it's impo= rtant that ubldr be linked=0A> at the same address it's configured to load = at, so you may have several=0A> places in crochet to adjust that 88000000 n= umber.=0A>=0A> I just now booted a dual board (it's been a while) and it's = working=0A> fine. Something I have not done for many months is boot a solo= board, I=0A> guess I should check it sometime soon.=0A>=0A> -- Ian=0A>=0A>= =0A> _______________________________________________=0A> freebsd-arm@freebs= d.org mailing list=0A> http://lists.freebsd.org/mailman/listinfo/freebsd-ar= m=0A> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org= "=0A>=0A=0A=0A=0A-- =0AA better world shall emerge based on faith and under= standing - Douglas=0AMacArthur=0A From owner-freebsd-arm@FreeBSD.ORG Mon Nov 3 18:18:27 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F319CF6A for ; Mon, 3 Nov 2014 18:18:27 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D4B4D6A9 for ; Mon, 3 Nov 2014 18:18:27 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XlMCv-0004XD-OP for freebsd-arm@freebsd.org; Mon, 03 Nov 2014 10:18:25 -0800 Date: Mon, 3 Nov 2014 10:18:25 -0800 (PST) From: Scott Ellis To: freebsd-arm@freebsd.org Message-ID: <1415038705749-5962202.post@n5.nabble.com> In-Reply-To: <1415032073.272927972@apps.rackspace.com> References: <1415023949.765217459@apps.rackspace.com> <1415030377.1200.56.camel@revolution.hippie.lan> <1415032073.272927972@apps.rackspace.com> Subject: Re: Wandboard Dual and Crochet-FreeBSD MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 18:18:28 -0000 FYI, Ian's suggestion to change where ubldr gets loaded worked. I made the following two changes to the Wandboard-Dual configuration diff -r Wandboard/files/boot.txt Wandboard-Dual/files/boot.txt 1c1 < setenv fdt_file wandboard-quad.dtb;fatload mmc 0:1 88000000 ubldr;bootelf 88000000; --- > setenv fdt_file wandboard-dual.dtb;fatload mmc 0:1 44000000 ubldr;bootelf > 44000000; diff -r Wandboard/setup.sh Wandboard-Dual/setup.sh 49c49 < strategy_add $PHASE_BUILD_OTHER freebsd_ubldr_build UBLDR_LOADADDR=0x88000000 --- > strategy_add $PHASE_BUILD_OTHER freebsd_ubldr_build > UBLDR_LOADADDR=0x44000000 And the Wandboard-Dual board booted fine. Not suggesting that's the best place to stick ubldr, just a quick hack. Boot log here https://gist.github.com/scottellis/2c2416af428e05dc2aa1 -- View this message in context: http://freebsd.1045724.n5.nabble.com/Wandboard-Dual-and-Crochet-FreeBSD-tp5962144p5962202.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Tue Nov 4 01:04:11 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 473B2B82 for ; Tue, 4 Nov 2014 01:04:11 +0000 (UTC) Received: from frontend1.warwick.net (mail.warwick.net [204.255.24.102]) by mx1.freebsd.org (Postfix) with SMTP id F17AF6B3 for ; Tue, 4 Nov 2014 01:04:09 +0000 (UTC) Received: (qmail 2593 invoked from network); 4 Nov 2014 00:57:28 -0000 Received: from 70.44.113.89.res-cmts.sefg.ptd.net (HELO [70.44.113.89]) (egunther@warwick.net@70.44.113.89) by frontend1.warwick.net with SMTP (8c309722-63bd-11e4-bb8a-001e0b616b8e); Mon, 03 Nov 2014 19:57:28 -0500 Message-ID: <1415062647.7543.9.camel@res-cmts> Subject: Re: RPI, config.txt: overscan, not working From: ito To: freebsd-arm@freebsd.org Date: Mon, 03 Nov 2014 19:57:27 -0500 In-Reply-To: <1414917964.3427.2.camel@res-cmts> References: <1414774843.3499.18.camel@res-cmts> <1414917964.3427.2.camel@res-cmts> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-MagicMail-UUID: 8c309722-63bd-11e4-bb8a-001e0b616b8e X-MagicMail-Authenticated: egunther@warwick.net X-MagicMail-SourceIP: 70.44.113.89 X-MagicMail-EnvelopeFrom: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 01:04:11 -0000 Hi, I Discovered that the framebuffer_width and framebuffer_height sizes seem to work but the overscan_left, overscan_right, etc. not as much. I have settled on framebuffer_width=720 framebuffer_height=400 referenced a well commented config.txt although solely added the two framebuffer entries to the existing config.txt because the overscan did not seem to work. https://raw.githubusercontent.com/Evilpaul/RPi-config/master/config.txt Thanks for any advice, ito On Sun, 2014-11-02 at 03:46 -0500, ito wrote: > Is there anyone with an idea as to how I can stop the text from spilling > off the screen. > > The display is in excess of 1/2 an inch all around. > > Thanks, > > ito > > > > On Fri, 2014-10-31 at 13:00 -0400, ito wrote: > > Hello, > > > > I have a raspberry pi, > > > > Model B Revision 2.0 (512MB) > > which has the logo along with: > > Raspberry Pi > > (c)2011.12 > > written on it. > > > > I have obtained a image for freebsd to run from here: > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/10.0/ > > > > > > I uncompressed the image on a OpenSUSE system, and used, > > > > sudo dd if=FreeBSD-10.0-RELEASE-arm-armv6-RPI-B-20140131-r260789.img > > of=/dev/sdd > > > > to put the image on a micro SD... with that card and adapter I have > > successfully boot freebsd. > > > > The problem I am facing now is that I am using the yellow SVGA (RCA type > > plug) cables to use an old Television as a monitor, with this setup I > > have an issue with the text running off of the screen. > > > > I have tried the config.txt file with > > overscan_disable=0 > > overscan_left=20 > > overscan_right=20 > > overscan_top=20 > > overscan_bottom=20 > > > > > > added to the existing config.txt > > > > > > > > I have tried to load vesa: > > > > kldload vesa > > > > where I get a prompt that it does not exist. > > > > I looked in the kernel directory (/boot/kernel/) and there is no vesa, > > not sure what that means. > > > > > > I am assuming that there is something that is not happening with the > > config.txt. I saw mention of using the files here to replace the files > > on the pi; > > > > https://github.com/raspberrypi/firmware > > > > > > SO, essentially, how do I get the text to stop from spilling off of the > > screen (command prompt-no gui). > > > > > > Thank You, > > > > ito > From owner-freebsd-arm@FreeBSD.ORG Tue Nov 4 19:40:06 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8817BFF2 for ; Tue, 4 Nov 2014 19:40:06 +0000 (UTC) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (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 4F07723B for ; Tue, 4 Nov 2014 19:40:05 +0000 (UTC) Received: from 127.0.0.1 (politkovskaja.torservers.net [77.247.181.165]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id sA4Jhksn033718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 4 Nov 2014 14:43:52 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <54592B7B.5090908@ceetonetechnology.com> Date: Tue, 04 Nov 2014 14:39:39 -0500 From: George Rosamond MIME-Version: 1.0 To: "freebsd-arm@freebsd.org" Subject: crochet update to lib/freebsd_xdev.sh Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 19:40:06 -0000 Note this: https://github.com/kientzle/crochet-freebsd/commit/cdc90ae78a68edd576586cced453a3b282205772 Running: make XDEV=arm XDEV_ARCH=armv6 WITH_GCC=1 WITH_GCC_BOOTSTRAP=1 WITH_GNUCXX=1 WITHOUT_CLANG=1 WITHOUT_CLANG_BOOTSTRAP=1 WITHOUT_CLANG_IS_CC=1 WITHOUT_TESTS=1 xdev Same results for building xdev tools: usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/except.c:(.text+0x10fb): undefined reference to `libc_name_p' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[3]: stopped in /usr/src/gnu/usr.bin/cc/cc1plus *** Error code 1 Stop. make[2]: stopped in /usr/src/gnu/usr.bin/cc *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src g From owner-freebsd-arm@FreeBSD.ORG Tue Nov 4 19:43:27 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B640111C for ; Tue, 4 Nov 2014 19:43:27 +0000 (UTC) Received: from orange.myspectrum.nl (unknown [IPv6:2a01:7c8:aab2:19e:5054:ff:fe1e:7dad]) by mx1.freebsd.org (Postfix) with ESMTP id 79646324 for ; Tue, 4 Nov 2014 19:43:27 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by orange.myspectrum.nl (Postfix) with ESMTP id 0A6D684B5C; Tue, 4 Nov 2014 20:43:19 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at myspectrum.nl Received: from orange.myspectrum.nl ([127.0.0.1]) by localhost (orange.myspectrum.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2mU_9mkAqik; Tue, 4 Nov 2014 20:43:17 +0100 (CET) Received: from [10.0.0.105] (ip136-5-208-87.adsl2.static.versatel.nl [87.208.5.136]) (Authenticated sender: jeroen@myspectrum.nl) by orange.myspectrum.nl (Postfix) with ESMTPSA id 63B2D84B0F; Tue, 4 Nov 2014 20:43:17 +0100 (CET) Message-ID: <54592C54.7090805@myspectrum.nl> Date: Tue, 04 Nov 2014 20:43:16 +0100 From: Jeroen Hofstee User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: George Rosamond , "freebsd-arm@freebsd.org" Subject: Re: crochet update to lib/freebsd_xdev.sh References: <54592B7B.5090908@ceetonetechnology.com> In-Reply-To: <54592B7B.5090908@ceetonetechnology.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 19:43:27 -0000 Hello George, On 04-11-14 20:39, George Rosamond wrote: > Note this: > > https://github.com/kientzle/crochet-freebsd/commit/cdc90ae78a68edd576586cced453a3b282205772 > > Running: > > make XDEV=arm XDEV_ARCH=armv6 WITH_GCC=1 WITH_GCC_BOOTSTRAP=1 > WITH_GNUCXX=1 WITHOUT_CLANG=1 WITHOUT_CLANG_BOOTSTRAP=1 > WITHOUT_CLANG_IS_CC=1 WITHOUT_TESTS=1 xdev > > Same results for building xdev tools: > > usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/except.c:(.text+0x10fb): > undefined reference to `libc_name_p' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > *** Error code 1 > > Stop. > make[3]: stopped in /usr/src/gnu/usr.bin/cc/cc1plus > *** Error code 1 > > Stop. > make[2]: stopped in /usr/src/gnu/usr.bin/cc > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > which board are you trying to build? Regards, Jeroen From owner-freebsd-arm@FreeBSD.ORG Tue Nov 4 19:57:09 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25C0B992; Tue, 4 Nov 2014 19:57:09 +0000 (UTC) Date: Tue, 4 Nov 2014 19:57:06 +0000 From: Glen Barber To: Jeroen Hofstee Subject: Re: crochet update to lib/freebsd_xdev.sh Message-ID: <20141104195706.GB1138@hub.FreeBSD.org> References: <54592B7B.5090908@ceetonetechnology.com> <54592C54.7090805@myspectrum.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="eJnRUKwClWJh1Khz" Content-Disposition: inline In-Reply-To: <54592C54.7090805@myspectrum.nl> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 19:57:09 -0000 --eJnRUKwClWJh1Khz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 04, 2014 at 08:43:16PM +0100, Jeroen Hofstee wrote: > Hello George, >=20 > On 04-11-14 20:39, George Rosamond wrote: > >Note this: > > > >https://github.com/kientzle/crochet-freebsd/commit/cdc90ae78a68edd576586= cced453a3b282205772 > > > >Running: > > > >make XDEV=3Darm XDEV_ARCH=3Darmv6 WITH_GCC=3D1 WITH_GCC_BOOTSTRAP=3D1 > >WITH_GNUCXX=3D1 WITHOUT_CLANG=3D1 WITHOUT_CLANG_BOOTSTRAP=3D1 > >WITHOUT_CLANG_IS_CC=3D1 WITHOUT_TESTS=3D1 xdev > > > >Same results for building xdev tools: > > > >usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/except.c:(.tex= t+0x10fb): > >undefined reference to `libc_name_p' > >cc: error: linker command failed with exit code 1 (use -v to see invocat= ion) > >*** Error code 1 > > > >Stop. > >make[3]: stopped in /usr/src/gnu/usr.bin/cc/cc1plus > >*** Error code 1 > > > >Stop. > >make[2]: stopped in /usr/src/gnu/usr.bin/cc > >*** Error code 1 > > > >Stop. > >make[1]: stopped in /usr/src > >*** Error code 1 > > > >Stop. > >make: stopped in /usr/src > > >=20 > which board are you trying to build? >=20 It doesn't matter, this happens for all arm on head/. Glen --eJnRUKwClWJh1Khz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUWS+SAAoJEAMUWKVHj+KTpLwQAJK9iNPSZdHQ1y4N9wI6bBlL bDnFV8wW1Y+zRpnZMiyVU60EWddh2MdQ226Nn+/AcAArsNLujL5iJ3Z41v4v96rk fzjj/gdF4tZpzTt5jAPd/Luw1wkS+Y+9RdHO5l4ZUayi1Mqrrz5mIebIIq5e16IY qAmd1pukwlq7IXQhdtqSaCvtnK3I4QqITBxwoQ3QK0O+7CA4XA3oudkIpw0lOTXp yNWI3xpitfbUXAwZHbT5gvo4KZRCTJURJB3M7jCIwunLOT+x/4rhvzt+W1jw6l9u 01Hm0qIhOopxphgD52por7CNa/Fs7xeeTVw5s7iRbLpqZeSBVUPXzdcq22XicKVC 4aByjYnmjaVXV9CfDNBtyAHAlJf531+39+vKXPqugkdpGrmSnqBY5kKyegf2wjlK xkiHolI3hs+JMq0u9Ax1Aqxr4TxJ39RJbZS6VBR6Wx/2KIFkPKNP3c0ruvKRIIoQ qDdnqvUKjM+hhQX0IbVrVaQJ7fS2199rihOKtOWhGwJpLrNanBkFh4qEE2VWiPwQ iJGQx8uEofMt9ts3iEHfsxIC+bjx84P2Ayyxm2hak60s+FgvN/DCzwJ4qzzICODX pROYcipD9m9KAOgw9BhRn238Mp2o0SYgdEFJTi3ttbWRxGJlEo7Kc+AsLMzET50X yir7KAG7vv1MuccPWSVV =nMNy -----END PGP SIGNATURE----- --eJnRUKwClWJh1Khz-- From owner-freebsd-arm@FreeBSD.ORG Tue Nov 4 20:02:55 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D13FDAAB; Tue, 4 Nov 2014 20:02:55 +0000 (UTC) Received: from orange.myspectrum.nl (orange.myspectrum.nl [149.210.134.247]) by mx1.freebsd.org (Postfix) with ESMTP id 91FFC78B; Tue, 4 Nov 2014 20:02:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by orange.myspectrum.nl (Postfix) with ESMTP id BA3B084BE1; Tue, 4 Nov 2014 21:02:53 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at myspectrum.nl Received: from orange.myspectrum.nl ([127.0.0.1]) by localhost (orange.myspectrum.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fIxM1yd8Go2j; Tue, 4 Nov 2014 21:02:51 +0100 (CET) Received: from [10.0.0.105] (ip136-5-208-87.adsl2.static.versatel.nl [87.208.5.136]) (Authenticated sender: jeroen@myspectrum.nl) by orange.myspectrum.nl (Postfix) with ESMTPSA id 7FCB684BCF; Tue, 4 Nov 2014 21:02:51 +0100 (CET) Message-ID: <545930EB.6050701@myspectrum.nl> Date: Tue, 04 Nov 2014 21:02:51 +0100 From: Jeroen Hofstee User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Glen Barber Subject: Re: crochet update to lib/freebsd_xdev.sh References: <54592B7B.5090908@ceetonetechnology.com> <54592C54.7090805@myspectrum.nl> <20141104195706.GB1138@hub.FreeBSD.org> In-Reply-To: <20141104195706.GB1138@hub.FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 20:02:55 -0000 Hi Glen, On 04-11-14 20:57, Glen Barber wrote: > On Tue, Nov 04, 2014 at 08:43:16PM +0100, Jeroen Hofstee wrote: >> Hello George, >> >> On 04-11-14 20:39, George Rosamond wrote: >>> Note this: >>> >>> https://github.com/kientzle/crochet-freebsd/commit/cdc90ae78a68edd576586cced453a3b282205772 >>> >>> Running: >>> >>> make XDEV=arm XDEV_ARCH=armv6 WITH_GCC=1 WITH_GCC_BOOTSTRAP=1 >>> WITH_GNUCXX=1 WITHOUT_CLANG=1 WITHOUT_CLANG_BOOTSTRAP=1 >>> WITHOUT_CLANG_IS_CC=1 WITHOUT_TESTS=1 xdev >>> >>> Same results for building xdev tools: >>> >>> usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/except.c:(.text+0x10fb): >>> undefined reference to `libc_name_p' >>> cc: error: linker command failed with exit code 1 (use -v to see invocation) >>> *** Error code 1 >>> >>> Stop. >>> make[3]: stopped in /usr/src/gnu/usr.bin/cc/cc1plus >>> *** Error code 1 >>> >>> Stop. >>> make[2]: stopped in /usr/src/gnu/usr.bin/cc >>> *** Error code 1 >>> >>> Stop. >>> make[1]: stopped in /usr/src >>> *** Error code 1 >>> >>> Stop. >>> make: stopped in /usr/src >>> >> which board are you trying to build? >> > It doesn't matter, this happens for all arm on head/. likely, but I am asking it since the clang xdev might be able to compile u-boot, so gcc xdev doesn't need to be compiled at all. Jeroen From owner-freebsd-arm@FreeBSD.ORG Tue Nov 4 22:58:18 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A1D1EA; Tue, 4 Nov 2014 22:58:17 +0000 (UTC) Date: Tue, 4 Nov 2014 22:58:13 +0000 From: Glen Barber To: Jeroen Hofstee Subject: Re: crochet update to lib/freebsd_xdev.sh Message-ID: <20141104225813.GD1138@hub.FreeBSD.org> References: <54592B7B.5090908@ceetonetechnology.com> <54592C54.7090805@myspectrum.nl> <20141104195706.GB1138@hub.FreeBSD.org> <545930EB.6050701@myspectrum.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1sNVjLsmu1MXqwQ/" Content-Disposition: inline In-Reply-To: <545930EB.6050701@myspectrum.nl> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 22:58:18 -0000 --1sNVjLsmu1MXqwQ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 04, 2014 at 09:02:51PM +0100, Jeroen Hofstee wrote: > Hi Glen, >=20 > On 04-11-14 20:57, Glen Barber wrote: > >On Tue, Nov 04, 2014 at 08:43:16PM +0100, Jeroen Hofstee wrote: > >>Hello George, > >> > >>On 04-11-14 20:39, George Rosamond wrote: > >>>Note this: > >>> > >>>https://github.com/kientzle/crochet-freebsd/commit/cdc90ae78a68edd5765= 86cced453a3b282205772 > >>> > >>>Running: > >>> > >>>make XDEV=3Darm XDEV_ARCH=3Darmv6 WITH_GCC=3D1 WITH_GCC_BOOTSTRAP=3D1 > >>>WITH_GNUCXX=3D1 WITHOUT_CLANG=3D1 WITHOUT_CLANG_BOOTSTRAP=3D1 > >>>WITHOUT_CLANG_IS_CC=3D1 WITHOUT_TESTS=3D1 xdev > >>> > >>>Same results for building xdev tools: > >>> > >>>usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/except.c:(.t= ext+0x10fb): > >>>undefined reference to `libc_name_p' > >>>cc: error: linker command failed with exit code 1 (use -v to see invoc= ation) > >>>*** Error code 1 > >>> > >>>Stop. > >>>make[3]: stopped in /usr/src/gnu/usr.bin/cc/cc1plus > >>>*** Error code 1 > >>> > >>>Stop. > >>>make[2]: stopped in /usr/src/gnu/usr.bin/cc > >>>*** Error code 1 > >>> > >>>Stop. > >>>make[1]: stopped in /usr/src > >>>*** Error code 1 > >>> > >>>Stop. > >>>make: stopped in /usr/src > >>> > >>which board are you trying to build? > >> > >It doesn't matter, this happens for all arm on head/. >=20 > likely, but I am asking it since the clang xdev might be able to compile > u-boot, so gcc xdev doesn't need to be compiled at all. >=20 Honestly, the larger issue is that gcc xdev build for arm is broken on head/, and this is exactly why we have not had arm snapshots for the past few weeks. While, yes, it *may* be something that can be built with clang, since not all u-boot versions build with clang, this is still a very big problem. Glen --1sNVjLsmu1MXqwQ/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUWVoFAAoJEAMUWKVHj+KTXfgP/2rqyw3icAhD9zwxvScPRYfp NMRZFnPcGKAoxXh/5GBNBZAyBQSoCe19zXa17ODWh8BWqH2YKYWng7LZS9kgGr5M Zi9XiEaj1Izd5dmbB7GiBWHeB8LIVUTL5KKsqWVjHc9BleFoscusw4BD+wJZ2RDg T/Hl1GTsvuYxc3IuT6cw9rZo3W0LK96nPVjnQhGkGhHEmjAo0k9kxtkWcCGwLobl bu8Dmuvsn2Qmg8FGcyA86a2NUaIQjdTqrvFIh7EJzPqUTcsRkvGeAdy19XYF6hGZ uXfYW87TjVEClAlJIjLs586SPH5XjEQNdnZpJThjVz4KnbkhyQoNYtZCXERGfPZR TfF9nkUtFko6sDdxEEDMulmnRNlbhwN7eGzHXu/Jtdx+ziDK22RtYlyln/9zbnZE N2bYi2b5hOWfqDk5d7q5+KK1aNvtMCybuAw42xPG8rK/Q0SD+0uqpsMLy5brrhIg hFHKUgXXt3APyI+8F0INWgizzDwKawcX3PJoeRLGXdNNd2mJZIZ1ckQ4KER4JiU2 Xc8QkvEMgFMfbobwsDnJN4BWsCBQHX2k97hrlgCRf9pT3KAr6CLecpAKWsuvmCYB NdaXyfb4OzXejcPM+wsPqtIwVcgU2FFEmJWG0pBXd8uRk34rVMZ3Tubo8NVMRmMW fRL0w58YXkWgA3twooax =jm/1 -----END PGP SIGNATURE----- --1sNVjLsmu1MXqwQ/-- From owner-freebsd-arm@FreeBSD.ORG Thu Nov 6 12:51:05 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 208B0B81 for ; Thu, 6 Nov 2014 12:51:05 +0000 (UTC) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E3ECCA82 for ; Thu, 6 Nov 2014 12:51:04 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id AAA0339D0A for ; Thu, 6 Nov 2014 21:50:55 +0900 (JST) Received: from artemis (unknown [172.18.0.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id 8862439D09 for ; Thu, 6 Nov 2014 21:50:55 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: References: <0A8390C3FC2B444B9AA8AC934B79DCD6@ad.peach.ne.jp> In-Reply-To: <0A8390C3FC2B444B9AA8AC934B79DCD6@ad.peach.ne.jp> Subject: Re: FreeBSD 11-CURRENT on Raspberry Pi 512MB Date: Thu, 6 Nov 2014 21:50:49 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2014 12:51:05 -0000 Hello, I've updated the image to SVN r274088 and cpufreq-20141106. It can be downloaded from: http://www.peach.ne.jp/archives/rpi/FreeBSD-armv6-11.0-RPI-B-test20-r274088-20141106.img.gz include temperature in dev.cpu node add 256MB swap by default use tmpfs as /tmp and /var/tmp new tunable parameters in /boot/loader.conf: hw.bcm2835.cpufreq.verbose=1 hw.bcm2835.cpufreq.lowest_freq=300 Try it yourself. Thank you, -- Daisuke Aoyama From owner-freebsd-arm@FreeBSD.ORG Thu Nov 6 22:57:15 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D570160 for ; Thu, 6 Nov 2014 22:57:15 +0000 (UTC) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (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 66F49A0E for ; Thu, 6 Nov 2014 22:57:14 +0000 (UTC) Received: from 127.0.0.1 (euve19412.vserver.de [62.75.168.144]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id sA6N0wYt074046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 6 Nov 2014 18:01:02 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <545BFCB8.4030604@ceetonetechnology.com> Date: Thu, 06 Nov 2014 17:56:56 -0500 From: George Rosamond MIME-Version: 1.0 To: "freebsd-arm@freebsd.org" Subject: A current BB Black issues Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2014 22:57:15 -0000 BeagleBone Black with: FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r274186: Thu Nov 6 14:51:29 EST 2014 root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/BEAGLEBONE arm First, I tried to run copy-to-emmc.sh but noticed this is the dmesg: sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci_ti1-slot0: ============== REGISTER DUMP ============== sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 sdhci_ti1-slot0: =========================================== sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci_ti1-slot0: ============== REGISTER DUMP ============== sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 sdhci_ti1-slot0: =========================================== am335x_pmic0: TPS65217C ver 1.2 powered by USB and mmcsd1 isn't showing up in /dev/, the boot process, etc. It will boot from eMMC if I don't hold down the button by the microSD card. Anything I should be aware of? g From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 01:17:06 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 254266AF for ; Fri, 7 Nov 2014 01:17:06 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 F3234DF5 for ; Fri, 7 Nov 2014 01:17:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Subject:To:From:Date; bh=Pty0Y6H5m/4enGS6F86d4zpl6ETFlKjhA6JmKZM/iTs=; b=v0pLdk2SqLU12fvp76dZkqTg9Fqw62t4rthLXeQXCqeib8/pPbrqOKKQ2R6A9yoUiFa+RNb8e38bS8THa1ZZSuy+HL4CGb6NvbWYE7geTqv36WJacZHJ/5xf2igUSd2Pp7IcpHJuLiUexKrMmOS0VQIj8MM0+3EXTlevEFBs+jE=; Received: from [182.10.35.123] (port=56653 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpa (Exim 4.82) (envelope-from ) id 1XmYAc-003B0Z-Ly for freebsd-arm@freebsd.org; Thu, 06 Nov 2014 18:16:59 -0700 Date: Fri, 7 Nov 2014 09:16:54 +0800 From: Erich Dollansky To: "freebsd-arm@freebsd.org" Subject: Raspberry Pi B+ as a thin client Message-ID: <20141107091654.14fa9980@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 01:17:06 -0000 Hi, as we use the Raspberry for other things, I thought, why not have it tested as a thin client. Ok, it works. X can be installed. I then used blackbox as the local window manager. It is not a problem to run programs via telnet but the moment X comes into the game, things will get slow. The most anoying thing is the mouse which drags behind and then suddenly jumps. I am a bit surprised as I used to use a Transmeta Crusoe machine as a thin client for years without these problems and thought that the little Raspberry is just fast enough to do this. Does anybody here has some positive experience with other ARM-based machines runnning as thin clients? Erich From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 01:51:59 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B9FB1F0 for ; Fri, 7 Nov 2014 01:51:59 +0000 (UTC) Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F25F82BF for ; Fri, 7 Nov 2014 01:51:58 +0000 (UTC) Received: by mail-pd0-f172.google.com with SMTP id r10so2288876pdi.31 for ; Thu, 06 Nov 2014 17:51:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=xRUGLCWXy32a52bkA3vgwi7Hj0WVg9ss+uI9oShq7RU=; b=dLPA+EroXbEAvHmRDbGXCX9DuLAvXIlJGmXDWm4OSu8A+q7U2fNV7ZkZy4zUxlYu3Q HfJM0HF1bGklN0DpMsy6bWIDciKUlaGCcKXPqzu2Vfg0nFb+s6lb82NBDOLayjG0aCB3 wy4ojT/Cgw+p5qq7bzBp8GJRSRPB9Cpr1ZjbYcYVQd8LItlNT1EQIJY4h3vl4E/SEWRD +xLfuhO2HwNkgyS51EaNoCrIGtGXtUlUfUxWruBDo/WL4RZPsjiDL7Cgq8oFYiQvVsEb kO1zYeaW5XXxoQq19Q7N4AgfaZjn5x+CpweJqKYQpLXYSCgiTmaFB2jfmhGQDLARzgG2 t/Ag== X-Gm-Message-State: ALoCoQlh9Caj0NRB73ToTxNGlqbfAbYUUdC/t+G2tGqPDoBVqXooU/ed4aK81tWxr4VHBYABZHDE X-Received: by 10.69.13.196 with SMTP id fa4mr8528267pbd.65.1415325117203; Thu, 06 Nov 2014 17:51:57 -0800 (PST) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id il5sm5442506pbb.56.2014.11.06.17.51.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Nov 2014 17:51:56 -0800 (PST) Subject: Re: FreeBSD 11-CURRENT on Raspberry Pi 512MB Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle X-Priority: 3 In-Reply-To: Date: Thu, 6 Nov 2014 17:51:03 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <70AFE35A-31F4-462E-897E-F2FCA44BFB7D@kientzle.com> References: <0A8390C3FC2B444B9AA8AC934B79DCD6@ad.peach.ne.jp> To: Daisuke Aoyama X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 01:51:59 -0000 On Nov 6, 2014, at 4:50 AM, Daisuke Aoyama wrote: > Hello, >=20 > I've updated the image to SVN r274088 and cpufreq-20141106. >=20 > It can be downloaded from: > = http://www.peach.ne.jp/archives/rpi/FreeBSD-armv6-11.0-RPI-B-test20-r27408= 8-20141106.img.gz >=20 > include temperature in dev.cpu node > add 256MB swap by default You=92ll need a lot more swap than this if you want to support native = buildworld. I=92m using 768MB on my Beaglebones. At one time, I experimented with startup scripts that would create the = swap file on first boot if there was sufficient free disk space. This = is nice with growable images: You can put a 2GB image onto a 32GB SD = card and have the image automatically grow and allocate swap when it = first boots. > use tmpfs as /tmp and /var/tmp I keep meaning to experiment and find a good setup for this. Crochet=92s = Beaglebone images use tmpfs for /var/tmp and I keep running out of = inodes when using mergemaster. >=20 > new tunable parameters in /boot/loader.conf: > hw.bcm2835.cpufreq.verbose=3D1 > hw.bcm2835.cpufreq.lowest_freq=3D300 >=20 > Try it yourself. > Thank you, > --=20 > Daisuke Aoyama _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 03:18:32 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 653EE161 for ; Fri, 7 Nov 2014 03:18:32 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 3C915CBF for ; Fri, 7 Nov 2014 03:18:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=sTFw8rMzBMvnQAgUweO3JiYnf23Vm9FQpaDHgGIiThM=; b=KP1Cih4o0D9V9WbaMc5OmLTki2WKLb1aJR8/3QETc7NQye9J14CebQHChLH8DDzreFtjNH4SxV8iythmb+75gKkOJqTMxXwOxfRX9eJBoAzUnQ+xFW0Fz+NQHXzUny2DM6v9OX2/toHhe2f/YGdWiN+zxg24mnSvvB26bNY911c=; Received: from [182.10.35.123] (port=32172 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpa (Exim 4.82) (envelope-from ) id 1Xma4D-0042Yf-8d; Thu, 06 Nov 2014 20:18:29 -0700 Date: Fri, 7 Nov 2014 11:18:25 +0800 From: Erich Dollansky To: Tim Kientzle Subject: Re: FreeBSD 11-CURRENT on Raspberry Pi 512MB Message-ID: <20141107111825.2b5bf643@X220.alogt.com> In-Reply-To: <70AFE35A-31F4-462E-897E-F2FCA44BFB7D@kientzle.com> References: <0A8390C3FC2B444B9AA8AC934B79DCD6@ad.peach.ne.jp> <70AFE35A-31F4-462E-897E-F2FCA44BFB7D@kientzle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 03:18:32 -0000 Hi, On Thu, 6 Nov 2014 17:51:03 -0800 Tim Kientzle wrote: > On Nov 6, 2014, at 4:50 AM, Daisuke Aoyama wrote: > > > I've updated the image to SVN r274088 and cpufreq-20141106. > > > > It can be downloaded from: > > http://www.peach.ne.jp/archives/rpi/FreeBSD-armv6-11.0-RPI-B-test20-r274088-20141106.img.gz > > > > include temperature in dev.cpu node > > add 256MB swap by default > > You’ll need a lot more swap than this if you want to support native > buildworld. I’m using 768MB on my Beaglebones. > > > use tmpfs as /tmp and /var/tmp > > I keep meaning to experiment and find a good setup for this. > Crochet’s Beaglebone images use tmpfs for /var/tmp and I keep running > out of inodes when using mergemaster. > do you really run a small machine like this alone? I use NFS to create whatever is needed on a normal FreeBSD machine. Swap is off by default but can be added whenever required and NFS is available. > Erich From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 05:46:51 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C5B0821 for ; Fri, 7 Nov 2014 05:46:51 +0000 (UTC) Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DBECB96 for ; Fri, 7 Nov 2014 05:46:50 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id bj1so2853486pad.29 for ; Thu, 06 Nov 2014 21:46:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=sruc2x183/J/1op8ovhtJpCgIVK0hSVZ39LbVPTp1xA=; b=QDc1Vn/1gkLuM9y6BLJ8FCWp4Pv84ShUOS9ZnFqxsMTXz6mS7Ap4cqq+j06ssR1s3D 2e0UvD5SexmyHzF8u8c3Ebw5G3rMP45ECv6d+JleuFfcdhow6IkJl9DOsiDr/useoA9P qgnIVbOJVdqXNu9qqM4iMh47toVOqi1GeoP7v9LRgc95AhZ/MfApKRtHZs0B7tOyc4X6 P2Bez9VzL4Cq9SYVbKB7mNI8dZoMh3fKXr4OXj97NmJPsoJaDQhEY/HljTlbA3UwNV54 1nDPws1p5DZVPZmBgTwipeyLCh3zilvKHRtCnN6ZfX0HXcHy0YpsIOV22U/PxeFGLnoh McSQ== X-Gm-Message-State: ALoCoQlSGjlYrKLwlLaky3uweDJ7853BQazFE3yA19jZt1bbFs/sy+UZnFtYHxs7oKufArsjXwgr X-Received: by 10.66.246.196 with SMTP id xy4mr9805146pac.29.1415338773590; Thu, 06 Nov 2014 21:39:33 -0800 (PST) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id j14sm7434976pbq.85.2014.11.06.21.39.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Nov 2014 21:39:32 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: FreeBSD 11-CURRENT on Raspberry Pi 512MB From: Tim Kientzle In-Reply-To: <20141107111825.2b5bf643@X220.alogt.com> Date: Thu, 6 Nov 2014 21:38:39 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0A8390C3FC2B444B9AA8AC934B79DCD6@ad.peach.ne.jp> <70AFE35A-31F4-462E-897E-F2FCA44BFB7D@kientzle.com> <20141107111825.2b5bf643@X220.alogt.com> To: Erich Dollansky X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 05:46:51 -0000 On Nov 6, 2014, at 7:18 PM, Erich Dollansky = wrote: > Hi, >=20 > On Thu, 6 Nov 2014 17:51:03 -0800 > Tim Kientzle wrote: >=20 >> On Nov 6, 2014, at 4:50 AM, Daisuke Aoyama = wrote: >>=20 >>> I've updated the image to SVN r274088 and cpufreq-20141106. >>>=20 >>> It can be downloaded from: >>> = http://www.peach.ne.jp/archives/rpi/FreeBSD-armv6-11.0-RPI-B-test20-r27408= 8-20141106.img.gz >>>=20 >>> include temperature in dev.cpu node >>> add 256MB swap by default >>=20 >> You=92ll need a lot more swap than this if you want to support native >> buildworld. I=92m using 768MB on my Beaglebones. >>=20 >>> use tmpfs as /tmp and /var/tmp >>=20 >> I keep meaning to experiment and find a good setup for this. >> Crochet=92s Beaglebone images use tmpfs for /var/tmp and I keep = running >> out of inodes when using mergemaster. >>=20 > do you really run a small machine like this alone? Not alone, no. I have three of them. ;-) I=92ve been doing native source upgrades (including port upgrades) on = each of my BeagleBones about once a week for quite a while now. I=92m = currently trying to get the upgrade process fully automated so I can run = two or three upgrades a week instead of just one. Tim From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 06:41:40 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5CCD01F0; Fri, 7 Nov 2014 06:41:40 +0000 (UTC) Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtp001.mac.com [17.172.220.236]) (using TLSv1 with cipher DES-CBC3-SHA (112/168 bits)) (Client CN "smtp.me.com", Issuer "VeriSign Class 3 Extended Validation SSL SGC CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33021FE3; Fri, 7 Nov 2014 06:41:37 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (unknown [73.162.13.215]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit (built Jun 6 2014)) with ESMTPSA id <0NEN00KRCP8OAU50@st11p02mm-asmtp001.mac.com>; Fri, 07 Nov 2014 06:41:15 +0000 (GMT) From: Rui Paulo Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Subject: libgpio Message-id: Date: Thu, 06 Nov 2014 22:41:12 -0800 To: embedded@freebsd.org, arm@freebsd.org MIME-version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) X-Mailer: Apple Mail (2.1990.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.28,0.0.0000 definitions=2014-11-07_04:2014-11-07,2014-11-07,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1408290000 definitions=main-1411070063 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 06:41:40 -0000 Hi, Some time ago, I wrote a gpio library as a way to interact with the = kernel gpio driver in a more sensible way (hiding the details of opening = a /dev file, handling all the ioctls, etc.). Here's the project code: https://bitbucket.org/rpaulo/libgpio/src Here's the header file: = https://bitbucket.org/rpaulo/libgpio/src/1dfe793d0b0cd6caff2e196cf667a5c06= bbade8d/libgpio.h?at=3Ddefault It looks like some people started using the library and I was wondering = if it would be a good candidate for the base system. I would rewrite = gpioctl to use it and I'm open to changing the library API. Any comments? -- Rui Paulo From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 07:31:48 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44B22554 for ; Fri, 7 Nov 2014 07:31:48 +0000 (UTC) Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtp001.mac.com [17.172.220.236]) (using TLSv1 with cipher DES-CBC3-SHA (112/168 bits)) (Client CN "smtp.me.com", Issuer "VeriSign Class 3 Extended Validation SSL SGC CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 190CB75C for ; Fri, 7 Nov 2014 07:31:47 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (unknown [73.162.13.215]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit (built Jun 6 2014)) with ESMTPSA id <0NEN002H7RJV7B20@st11p02mm-asmtp001.mac.com> for freebsd-arm@freebsd.org; Fri, 07 Nov 2014 07:31:10 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.28,0.0.0000 definitions=2014-11-07_04:2014-11-07,2014-11-07,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1408290000 definitions=main-1411070069 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: A current BB Black issues From: Rui Paulo In-reply-to: <545BFCB8.4030604@ceetonetechnology.com> Date: Thu, 06 Nov 2014 23:31:07 -0800 Content-transfer-encoding: quoted-printable Message-id: References: <545BFCB8.4030604@ceetonetechnology.com> To: George Rosamond X-Mailer: Apple Mail (2.1990.1) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 07:31:48 -0000 On Nov 6, 2014, at 14:56, George Rosamond = wrote: > BeagleBone Black with: >=20 > FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r274186: = Thu > Nov 6 14:51:29 EST 2014 > = root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/= BEAGLEBONE > arm >=20 >=20 > First, I tried to run copy-to-emmc.sh but noticed this is the dmesg: >=20 > sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no active > command. > sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REGISTER = DUMP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 > sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 > sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b > sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 > sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 > sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 > sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 > sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb > sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 > sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 > sdhci_ti1-slot0: =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 > sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no active > command. > sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REGISTER = DUMP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 > sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 > sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b > sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 > sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 > sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 > sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 > sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb > sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 > sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 > sdhci_ti1-slot0: =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 > am335x_pmic0: TPS65217C ver 1.2 powered by USB >=20 > and mmcsd1 isn't showing up in /dev/, the boot process, etc. It will > boot from eMMC if I don't hold down the button by the microSD card. >=20 > Anything I should be aware of? My speculation is that the newer U-Boot breaks the eMMC support in = FreeBSD. An U-Boot from 2013.4 seems to work fine while the U-Boot from = 2014.3 doesn't work for me. -- Rui Paulo From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 07:49:47 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 868296B0; Fri, 7 Nov 2014 07:49:47 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 60B18875; Fri, 7 Nov 2014 07:49:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=xNSuxj3M3cNgwnq1eA7Vl7BE/hzTSnx+LwltMoYBs7I=; b=sytGKNRtFkk224wgDy+FpfFjO3svyy7cJhEi69k/6kyJ3tB69XrpIYT2MdX8YE5OAFDk8F/wlJu31bcixfL2zAUIVNViAAWcibQVhjG/aLC31p2Xdya15vcLxWFV1xt5wscPBLP9/0CKEvUgDN1AIVLlwAMNkRndCC2LMJc10Fk=; Received: from [182.10.35.123] (port=28832 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpa (Exim 4.82) (envelope-from ) id 1XmeIj-001R94-M9; Fri, 07 Nov 2014 00:49:46 -0700 Date: Fri, 7 Nov 2014 15:49:41 +0800 From: Erich Dollansky To: Rui Paulo Subject: Re: libgpio Message-ID: <20141107154941.3694a9c9@X220.alogt.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: arm@freebsd.org, embedded@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 07:49:47 -0000 Hi, On Thu, 06 Nov 2014 22:41:12 -0800 Rui Paulo wrote: > Some time ago, I wrote a gpio library as a way to interact with the > kernel gpio driver in a more sensible way (hiding the details of > opening a /dev file, handling all the ioctls, etc.). > > Here's the project code: > > https://bitbucket.org/rpaulo/libgpio/src > > Here's the header file: > > https://bitbucket.org/rpaulo/libgpio/src/1dfe793d0b0cd6caff2e196cf667a5c06bbade8d/libgpio.h?at=default > > It looks like some people started using the library and I was I am one of them. > wondering if it would be a good candidate for the base system. I It would. > would rewrite gpioctl to use it and I'm open to changing the library > API. > > Any comments? The only thing I would really change is to add functions which include the opening and closing of the port. With other words, the application only calls something like gpio_pin_write (Name, Pin, value) or gpio_pin_write (Pin, value) and gpio_pin_write opens and closes the device. Plus a function to set the device name to be used for all later calls. Erich From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 11:24:34 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B9C5375A; Fri, 7 Nov 2014 11:24:34 +0000 (UTC) Received: from mx0.deglitch.com (unknown [IPv6:2001:16d8:ff00:19d::2]) by mx1.freebsd.org (Postfix) with ESMTP id 745CC1D9; Fri, 7 Nov 2014 11:24:34 +0000 (UTC) Received: from [192.168.11.2] (unknown [98.248.95.7]) by mx0.deglitch.com (Postfix) with ESMTPSA id A67708FC27; Fri, 7 Nov 2014 15:24:21 +0400 (MSK) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: libgpio From: Stanislav Sedov In-Reply-To: Date: Fri, 7 Nov 2014 03:24:16 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <2F8338D7-083E-4C3A-84A4-C197D071CA24@freebsd.org> References: To: Rui Paulo X-Mailer: Apple Mail (2.1990.1) Cc: arm@freebsd.org, embedded@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 11:24:34 -0000 > On Nov 6, 2014, at 10:41 PM, Rui Paulo wrote: >=20 > Hi, >=20 > Some time ago, I wrote a gpio library as a way to interact with the = kernel gpio driver in a more sensible way (hiding the details of opening = a /dev file, handling all the ioctls, etc.). >=20 > Here's the project code: >=20 > https://bitbucket.org/rpaulo/libgpio/src >=20 > Here's the header file: >=20 > = https://bitbucket.org/rpaulo/libgpio/src/1dfe793d0b0cd6caff2e196cf667a5c06= bbade8d/libgpio.h?at=3Ddefault >=20 > It looks like some people started using the library and I was = wondering if it would be a good candidate for the base system. I would = rewrite gpioctl to use it and I'm open to changing the library API. >=20 > Any comments? In my opinion it is an excellent idea to import the library into the base system. It is really useful and will facilitate 3rd party applications development. I=E2=80=99d say go for it. -- ST4096-RIPE From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 14:02:27 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BA8819E3 for ; Fri, 7 Nov 2014 14:02:27 +0000 (UTC) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (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 6297E934 for ; Fri, 7 Nov 2014 14:02:26 +0000 (UTC) Received: from 127.0.0.1 (tor31.anonymizer.ccc.de [217.115.10.131]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id sA7E6Kv1040085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 7 Nov 2014 09:06:23 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <545CD0E8.1070402@ceetonetechnology.com> Date: Fri, 07 Nov 2014 09:02:16 -0500 From: George Rosamond MIME-Version: 1.0 To: Rui Paulo Subject: Re: A current BB Black issues References: <545BFCB8.4030604@ceetonetechnology.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 14:02:27 -0000 Rui Paulo: > On Nov 6, 2014, at 14:56, George Rosamond > wrote: >> BeagleBone Black with: >> >> FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 >> r274186: Thu Nov 6 14:51:29 EST 2014 >> root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/BEAGLEBONE >> >> arm >> >> >> First, I tried to run copy-to-emmc.sh but noticed this is the >> dmesg: >> >> sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no >> active command. sdhci_ti1-slot0: ============== REGISTER DUMP >> ============== sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: >> 0x00003101 sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: >> 0x00000001 sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: >> 0x0000071b sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: >> 0x00000000 sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: >> 0x00000000 sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: >> 0x00008007 sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: >> 0x00000000 sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: >> 0x017f00fb sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: >> 0x00000000 sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: >> 0x00000000 sdhci_ti1-slot0: >> =========================================== sdhci_ti1-slot0: Got >> data interrupt 0x00000002, but there is no active command. >> sdhci_ti1-slot0: ============== REGISTER DUMP ============== >> sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 >> sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 >> sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b >> sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 >> sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 >> sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 >> sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 >> sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb >> sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 >> sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 >> sdhci_ti1-slot0: =========================================== >> am335x_pmic0: TPS65217C ver 1.2 powered by USB >> >> and mmcsd1 isn't showing up in /dev/, the boot process, etc. It >> will boot from eMMC if I don't hold down the button by the microSD >> card. >> >> Anything I should be aware of? > > My speculation is that the newer U-Boot breaks the eMMC support in > FreeBSD. An U-Boot from 2013.4 seems to work fine while the U-Boot > from 2014.3 doesn't work for me. > That didn't even cross my mind. I'll definitely try that. Thanks. g From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 14:38:29 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 261E1686; Fri, 7 Nov 2014 14:38:29 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 194E2CCE; Fri, 7 Nov 2014 14:38:27 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id sA7Eb9bs042651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 7 Nov 2014 22:37:10 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id sA7Eb9TR042650; Fri, 7 Nov 2014 22:37:09 +0800 (CST) (envelope-from kevlo) Date: Fri, 7 Nov 2014 22:37:09 +0800 From: Kevin Lo To: Stanislav Sedov Subject: Re: libgpio Message-ID: <20141107143709.GA42643@ns.kevlo.org> References: <2F8338D7-083E-4C3A-84A4-C197D071CA24@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2F8338D7-083E-4C3A-84A4-C197D071CA24@freebsd.org> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: arm@freebsd.org, embedded@freebsd.org, Rui Paulo X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 14:38:29 -0000 On Fri, Nov 07, 2014 at 03:24:16AM -0800, Stanislav Sedov wrote: > > > > On Nov 6, 2014, at 10:41 PM, Rui Paulo wrote: > > > > Hi, > > > > Some time ago, I wrote a gpio library as a way to interact with the kernel gpio driver in a more sensible way (hiding the details of opening a /dev file, handling all the ioctls, etc.). > > > > Here's the project code: > > > > https://bitbucket.org/rpaulo/libgpio/src > > > > Here's the header file: > > > > https://bitbucket.org/rpaulo/libgpio/src/1dfe793d0b0cd6caff2e196cf667a5c06bbade8d/libgpio.h?at=default > > > > It looks like some people started using the library and I was wondering if it would be a good candidate for the base system. I would rewrite gpioctl to use it and I'm open to changing the library API. > > > > Any comments? > > In my opinion it is an excellent idea to import the library into > the base system. It is really useful and will facilitate 3rd > party applications development. Indeed. I've used libgpio for one of my projects. > I’d say go for it. +1 :-) > -- > ST4096-RIPE Kevin From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 15:44:47 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27B404A9 for ; Fri, 7 Nov 2014 15:44:47 +0000 (UTC) Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E3CD7788 for ; Fri, 7 Nov 2014 15:44:46 +0000 (UTC) Received: by mail-ig0-f182.google.com with SMTP id hn18so5597643igb.3 for ; Fri, 07 Nov 2014 07:44:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=khTZ/wQPe6JVGuwnEovKV2pg8VMtN14KCQId0C2EBq8=; b=GOdze8nmKhx0xLBkKXhLnGC2Tl72W9f3A5CN9//drV51Am8JVOi/AwhUmz5EZYVbSI z5EGfTsBC2Q21pP0ZukU4ZRwhgzeEZ/E1xyIWhGMClMJzYoEnaq8YtH+OeDea3zlVd1f YN5BrlrpLqrRBXD1WepKjI9ZzXNT29r/l9r0XHZ6OW23HRMdJtP0JzZABy8UEJaB4ykp 0t6wP6aPWGhQO4PRIbYK3VA7ntzH0KvJmHU9Sk1L76NZ+i7jDrWqlHNCsYmt+d9WzXg2 B3WxniSqLd7ZPrp31J08WqUmIXscoI7qHYMKsFysvLR9BDxwHfjxbwTGX/gaKRP39qnW zOGg== X-Gm-Message-State: ALoCoQm/XAmU0kKWZFi+FoeBL9SGQUM7Hn1L8V3g96wgO+NTaIpPgQmo5T9kd8t/cjjKCzMIjgZj X-Received: by 10.50.43.197 with SMTP id y5mr4680485igl.33.1415375073961; Fri, 07 Nov 2014 07:44:33 -0800 (PST) Received: from bsdimp.bsdimp.com ([50.253.99.174]) by mx.google.com with ESMTPSA id n29sm4407815ioe.19.2014.11.07.07.44.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Nov 2014 07:44:33 -0800 (PST) Sender: Warner Losh Content-Type: multipart/signed; boundary="Apple-Mail=_E873F49E-869E-44FD-8979-473D22DE02FD"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: libgpio From: Warner Losh In-Reply-To: Date: Fri, 7 Nov 2014 08:44:30 -0700 Message-Id: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> References: To: Rui Paulo X-Mailer: Apple Mail (2.1878.6) Cc: arm@freebsd.org, embedded@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 15:44:47 -0000 --Apple-Mail=_E873F49E-869E-44FD-8979-473D22DE02FD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Nov 6, 2014, at 11:41 PM, Rui Paulo wrote: > Hi, >=20 > Some time ago, I wrote a gpio library as a way to interact with the = kernel gpio driver in a more sensible way (hiding the details of opening = a /dev file, handling all the ioctls, etc.). >=20 > Here's the project code: >=20 > https://bitbucket.org/rpaulo/libgpio/src >=20 > Here's the header file: >=20 > = https://bitbucket.org/rpaulo/libgpio/src/1dfe793d0b0cd6caff2e196cf667a5c06= bbade8d/libgpio.h?at=3Ddefault >=20 > It looks like some people started using the library and I was = wondering if it would be a good candidate for the base system. I would = rewrite gpioctl to use it and I'm open to changing the library API. >=20 > Any comments? I generally like it. Here=92s some suggestions, though many may be hard = given that our gpio interface is a bit weak. First, there=92s no way to set multiple pins at the same time. That=92s = likely a reflection of our GPIO system, I know, but it is a deficiency. = Fortunately, most devices can tolerate multiple pins changing at = different times before a =91clock=92 or =91enable=92 pin forces them to = latch their state. What the heck is g_caps? There=92s nothing at all to describe it. Not = even an indirection to look at sys/gpio.h For systems that have multiple GPIO devices (some have a few hundred I/O = lines that can be addressed), how do you handle that? Do you just kinda have to know these details? There=92s no facilities for interrupts (usually you=92d like to say = =93wait for this line to change and let me know=94). I know that the = Atmel gpio stuff did this, but I don=92t think that made it into the = generalization that was later done. I=92m not sure that I like the gpio_pin_* helper functions causing the = thing to change, rather than operating on a gpio_config_t. But since you = don=92t normally change a bunch at a time, that=92s not so bad. Finally a question: What does Linux do here? Is there a standard = interface that we could use to leverage off applications written for = Linux? Perhaps beyond the scope of what you=92re trying to do, but any = discussion about pushing things into the base should ask the question = =93Is this the right, most useful interface?=94 Warner --Apple-Mail=_E873F49E-869E-44FD-8979-473D22DE02FD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUXOjeAAoJEGwc0Sh9sBEA1RoP/2piAIsGxJ32VaI2x3Bj5p2A hzg8VpRsYSdJmLfaHbcVoSWY0h/HAJiKqSIvEnFE+1D97s91nNU7VhiYSayvGc6R NRKfZqugAzPSZUDACx6dY6huYpva4JlVdDHnQgoG6Wxdlcy565NlJVXTLuu5yeB4 OzQzX7upJUNUckFIWReTJmWAwYuGMQqSHQmWBEW0Hrg/94zemaCBXpekb4rOyiOx cVjvxr204KWfCk5iUVmo/MIKPOwMSBschUx+oyQQLAaE2ROnPQzYwmHKBN16NaMG SuzaO9TNKerGJxRaMGc5KyRAcprJ4C2I6A0HQUCZEcE0/d59D14FGi3zAqHffXCp qmYN7hmWBoYlb2ctlKhDcWmB2QrZ4z6V0E0ZI2RAkeoR2bmFfNmmbeUUWR8IjeRq roKjJfJj+Zvk52Du9OoNLPXd+YM6MdZCYQumbRRufVdK/+zKUgseGZzqwa8l+ivt knXVDPUa71v1703iHz1oFknuc2fpnPogKZFH2KW/LfRAXDtMpFtqYxd0UcCJgyZR 0rFKiwjKyZPu0X9lnYLbL98DYmVhB6eKOdLXQIudLs+QCuc9FyEgPTU6o1jjb+lb Io/+DTwO9tKrO9WFrrIoQwA1qTp7Y+ukG8/4VivcQTPmJvhhGcQ+IlT/Xa6j16vh eQrsQLn3nuJC4VxxBgQg =7WX+ -----END PGP SIGNATURE----- --Apple-Mail=_E873F49E-869E-44FD-8979-473D22DE02FD-- From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 16:33:35 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75A6EC3D; Fri, 7 Nov 2014 16:33:35 +0000 (UTC) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AC56CDF; Fri, 7 Nov 2014 16:33:35 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id n3so5129803wiv.0 for ; Fri, 07 Nov 2014 08:33:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=nPebHxOI+7J+V/qHpCi0rWTmwQk+G36U05NHYj5gXRE=; b=G32om1ZoPYROi0v/LgF78S/xseOc8cTEiHwZmDxg7kENh5+LFH+4IDcPvklaWG4pin HuORDuq9HBkBmzq3KPkADu7LCR4jKHOs9bo7qaIJ1Svxq1r8B0ROfKzI4hcUO1A0DO7H LK+TdOKpXFLvnf4Zw6bo7eGWiJT2iayFgad4DeMdIWczD5oepbGoL4pWod7E8YB9OcTS 71UK01opBWy9t3Eflh05rb3PZ++5sBP+x0j7xuodSvTQSgPk3QlPGmLI9+aYoGgkUKWt yT7y+WdUvvhbVYaABcq86VSwq4cBz6J8E/JLQuILcK7RtI9Dkp1utNAxAV1U1HGR3IlA e+YQ== MIME-Version: 1.0 X-Received: by 10.180.188.41 with SMTP id fx9mr6445118wic.59.1415378013470; Fri, 07 Nov 2014 08:33:33 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Fri, 7 Nov 2014 08:33:33 -0800 (PST) In-Reply-To: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> References: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> Date: Fri, 7 Nov 2014 08:33:33 -0800 X-Google-Sender-Auth: fyRA3o2ytBd428oP2CtZj4ml5PE Message-ID: Subject: Re: libgpio From: Adrian Chadd To: Warner Losh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-arm@freebsd.org" , "freebsd-embedded@freebsd.org" , Rui Paulo X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 16:33:35 -0000 Hi, Yes, it'd be nice to (later) add an API call that takes multiple pin updates (and reads multiple pin updates.) That way higher speed, time critical stuff can be done for drivers that grow this feature and can do batched/timestamped GPIO events. -adrian On 7 November 2014 07:44, Warner Losh wrote: > > On Nov 6, 2014, at 11:41 PM, Rui Paulo wrote: > >> Hi, >> >> Some time ago, I wrote a gpio library as a way to interact with the kern= el gpio driver in a more sensible way (hiding the details of opening a /dev= file, handling all the ioctls, etc.). >> >> Here's the project code: >> >> https://bitbucket.org/rpaulo/libgpio/src >> >> Here's the header file: >> >> https://bitbucket.org/rpaulo/libgpio/src/1dfe793d0b0cd6caff2e196cf= 667a5c06bbade8d/libgpio.h?at=3Ddefault >> >> It looks like some people started using the library and I was wondering = if it would be a good candidate for the base system. I would rewrite gpioc= tl to use it and I'm open to changing the library API. >> >> Any comments? > > I generally like it. Here=E2=80=99s some suggestions, though many may be = hard given that our gpio interface is a bit weak. > > First, there=E2=80=99s no way to set multiple pins at the same time. That= =E2=80=99s likely a reflection of our GPIO system, I know, but it is a defi= ciency. Fortunately, most devices can tolerate multiple pins changing at di= fferent times before a =E2=80=98clock=E2=80=99 or =E2=80=98enable=E2=80=99 = pin forces them to latch their state. > > What the heck is g_caps? There=E2=80=99s nothing at all to describe it. N= ot even an indirection to look at sys/gpio.h > > For systems that have multiple GPIO devices (some have a few hundred I/O = lines that can be addressed), how > do you handle that? Do you just kinda have to know these details? > > There=E2=80=99s no facilities for interrupts (usually you=E2=80=99d like = to say =E2=80=9Cwait for this line to change and let me know=E2=80=9D). I k= now that the Atmel gpio stuff did this, but I don=E2=80=99t think that made= it into the generalization that was later done. > > I=E2=80=99m not sure that I like the gpio_pin_* helper functions causing = the thing to change, rather than operating on a gpio_config_t. But since yo= u don=E2=80=99t normally change a bunch at a time, that=E2=80=99s not so ba= d. > > Finally a question: What does Linux do here? Is there a standard interfac= e that we could use to leverage off applications written for Linux? Perhaps= beyond the scope of what you=E2=80=99re trying to do, but any discussion a= bout pushing things into the base should ask the question =E2=80=9CIs this = the right, most useful interface?=E2=80=9D > > Warner From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 16:49:26 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88B20250 for ; Fri, 7 Nov 2014 16:49:26 +0000 (UTC) Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A3EAE01 for ; Fri, 7 Nov 2014 16:49:25 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id lj1so3797629pab.8 for ; Fri, 07 Nov 2014 08:49:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=NRhJPj67AXe9I1ETYCmXPqHqV8qT28DkK6h/tCJxvRk=; b=EwrnDc+yGr3Yd3OeLjpFXj6403IV9NXOtsVocPDORsu6GHTOdrT4U/c8PPMZedzkCO 8ylFpfuHFISe8f7/IjaHA8IS/ta4V0Gno0VbSMK2vcu7jNG8ZLuPCYRMAnBr+4LFLfhh TcGk+70YxnbDINYnUJhwBYo/tjqGRKuhq9YxjemD15CvolOAWy4zGdB69H4zPRlCnjCa RQM7NQrMAqZRh4p7UarM7Fua4eKO//coRMbRlUsbKUxUYHRXra6inL9Wngk5SV9EXYPO cVqjTSyaubh+rp7G9NNDQ76P7cC62VA+E37Hh6URJqTPfEKLGnZ1tVS2ibBBlTBQL8G8 F/TA== X-Gm-Message-State: ALoCoQnWSyeuBmljbnP+cJ0LJpo7ObeXnQBUpInrIKvoXdL2/qJcB9vrCF70P93DraDEC6KKvItI X-Received: by 10.68.197.170 with SMTP id iv10mr13356280pbc.135.1415378540785; Fri, 07 Nov 2014 08:42:20 -0800 (PST) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id dk5sm9177926pbc.61.2014.11.07.08.42.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Nov 2014 08:42:19 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: A current BB Black issues From: Tim Kientzle In-Reply-To: <545CD0E8.1070402@ceetonetechnology.com> Date: Fri, 7 Nov 2014 08:41:22 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com> References: <545BFCB8.4030604@ceetonetechnology.com> <545CD0E8.1070402@ceetonetechnology.com> To: George Rosamond X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-arm@freebsd.org" , Rui Paulo X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 16:49:26 -0000 Patrick Kelsey contributed the patches for U-Boot 2013.04 to support = eMMC booting. They have not yet been reworked to apply to 2014.04. I=92ve looked at = it only briefly. Tim On Nov 7, 2014, at 6:02 AM, George Rosamond = wrote: > Rui Paulo: >> On Nov 6, 2014, at 14:56, George Rosamond >> wrote: >>> BeagleBone Black with: >>>=20 >>> FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 >>> r274186: Thu Nov 6 14:51:29 EST 2014=20 >>> = root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/= BEAGLEBONE >>>=20 >>>=20 > arm >>>=20 >>>=20 >>> First, I tried to run copy-to-emmc.sh but noticed this is the >>> dmesg: >>>=20 >>> sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no >>> active command. sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D REGISTER DUMP >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D sdhci_ti1-slot0: Sys = addr: 0x00000000 | Version: >>> 0x00003101 sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: >>> 0x00000001 sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: >>> 0x0000071b sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: >>> 0x00000000 sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: >>> 0x00000000 sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: >>> 0x00008007 sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: >>> 0x00000000 sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: >>> 0x017f00fb sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: >>> 0x00000000 sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: >>> 0x00000000 sdhci_ti1-slot0: >>> =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 = sdhci_ti1-slot0: Got >>> data interrupt 0x00000002, but there is no active command.=20 >>> sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REGISTER = DUMP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 >>> sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101=20 >>> sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001=20 >>> sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b=20 >>> sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000=20 >>> sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000=20 >>> sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007=20 >>> sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000=20 >>> sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb=20 >>> sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000=20 >>> sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000=20 >>> sdhci_ti1-slot0: =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= =20 >>> am335x_pmic0: TPS65217C ver 1.2 powered by USB >>>=20 >>> and mmcsd1 isn't showing up in /dev/, the boot process, etc. It >>> will boot from eMMC if I don't hold down the button by the microSD >>> card. >>>=20 >>> Anything I should be aware of? >>=20 >> My speculation is that the newer U-Boot breaks the eMMC support in >> FreeBSD. An U-Boot from 2013.4 seems to work fine while the U-Boot >> from 2014.3 doesn't work for me. >>=20 >=20 > That didn't even cross my mind. I'll definitely try that. >=20 > Thanks. >=20 > g > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 16:57:27 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2799543D; Fri, 7 Nov 2014 16:57:27 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (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 D98DCEEB; Fri, 7 Nov 2014 16:57:26 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Xmmqi-000CSR-Vz; Fri, 07 Nov 2014 16:57:25 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id sA7GvNWh001353; Fri, 7 Nov 2014 09:57:23 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+dta4syf2PtEywCHtMdSqy X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: libgpio From: Ian Lepore To: Adrian Chadd In-Reply-To: References: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> Content-Type: text/plain; charset="windows-1251" Date: Fri, 07 Nov 2014 09:57:23 -0700 Message-ID: <1415379443.1200.215.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ilsoft.org id sA7GvNWh001353 Cc: "freebsd-arm@freebsd.org" , "freebsd-embedded@freebsd.org" , Rui Paulo X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 16:57:27 -0000 On Fri, 2014-11-07 at 08:33 -0800, Adrian Chadd wrote: > Hi, >=20 > Yes, it'd be nice to (later) add an API call that takes multiple pin > updates (and reads multiple pin updates.) That way higher speed, time > critical stuff can be done for drivers that grow this feature and can > do batched/timestamped GPIO events. >=20 >=20 >=20 > -adrian >=20 mixed bottom/top posting. grrrr. comments below, where they belong. >=20 > On 7 November 2014 07:44, Warner Losh wrote: > > > > On Nov 6, 2014, at 11:41 PM, Rui Paulo wrote: > > > >> Hi, > >> > >> Some time ago, I wrote a gpio library as a way to interact with the = kernel gpio driver in a more sensible way (hiding the details of opening = a /dev file, handling all the ioctls, etc.). > >> > >> Here's the project code: > >> > >> https://bitbucket.org/rpaulo/libgpio/src > >> > >> Here's the header file: > >> > >> https://bitbucket.org/rpaulo/libgpio/src/1dfe793d0b0cd6caff2e1= 96cf667a5c06bbade8d/libgpio.h?at=3Ddefault > >> > >> It looks like some people started using the library and I was wonder= ing if it would be a good candidate for the base system. I would rewrite= gpioctl to use it and I'm open to changing the library API. > >> > >> Any comments? > > > > I generally like it. Here=92s some suggestions, though many may be ha= rd given that our gpio interface is a bit weak. > > > > First, there=92s no way to set multiple pins at the same time. That=92= s likely a reflection of our GPIO system, I know, but it is a deficiency.= Fortunately, most devices can tolerate multiple pins changing at differe= nt times before a =91clock=92 or =91enable=92 pin forces them to latch th= eir state. > > > > What the heck is g_caps? There=92s nothing at all to describe it. Not= even an indirection to look at sys/gpio.h > > > > For systems that have multiple GPIO devices (some have a few hundred = I/O lines that can be addressed), how > > do you handle that? Do you just kinda have to know these details? > > > > There=92s no facilities for interrupts (usually you=92d like to say =93= wait for this line to change and let me know=94). I know that the Atmel g= pio stuff did this, but I don=92t think that made it into the generalizat= ion that was later done. > > > > I=92m not sure that I like the gpio_pin_* helper functions causing th= e thing to change, rather than operating on a gpio_config_t. But since yo= u don=92t normally change a bunch at a time, that=92s not so bad. > > > > Finally a question: What does Linux do here? Is there a standard inte= rface that we could use to leverage off applications written for Linux? P= erhaps beyond the scope of what you=92re trying to do, but any discussion= about pushing things into the base should ask the question =93Is this th= e right, most useful interface?=94 > > > > Warner Multiple-pin read/write is really required for anything other than trivial "turn on this led" type stuff. A restriction that all the pins have to be on the same /dev/gpiocN device is fine. Routines to do simple bit-banging (so that multiple bits can be banged out with a single call) are also good to have. It's good for a driver to support an api for that at the lowest level to get reasonable speed for things like programming an fpga. (The at91 gpio drivers do this now.) -- Ian From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 17:00:57 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DF9F55ED for ; Fri, 7 Nov 2014 17:00:56 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AD94FA2 for ; Fri, 7 Nov 2014 17:00:55 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id sA7GvGe1045080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 7 Nov 2014 17:57:17 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 sA7Gv3u1081733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Nov 2014 17:57:03 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id sA7Gv3fQ021916; Fri, 7 Nov 2014 17:57:03 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id sA7Gv3Zx021915; Fri, 7 Nov 2014 17:57:03 +0100 (CET) (envelope-from ticso) Date: Fri, 7 Nov 2014 17:57:03 +0100 From: Bernd Walter To: Rui Paulo Subject: Re: A current BB Black issues Message-ID: <20141107165703.GA21868@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <545BFCB8.4030604@ceetonetechnology.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: George Rosamond , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 17:00:57 -0000 On Thu, Nov 06, 2014 at 11:31:07PM -0800, Rui Paulo wrote: > On Nov 6, 2014, at 14:56, George Rosamond wrote: > > BeagleBone Black with: > > > > FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r274186: Thu > > Nov 6 14:51:29 EST 2014 > > root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/BEAGLEBONE > > arm > > > > > > First, I tried to run copy-to-emmc.sh but noticed this is the dmesg: > > > > sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no active > > command. > > sdhci_ti1-slot0: ============== REGISTER DUMP ============== > > sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 > > sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 > > sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b > > sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 > > sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 > > sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 > > sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 > > sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb > > sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 > > sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 > > sdhci_ti1-slot0: =========================================== > > sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no active > > command. > > sdhci_ti1-slot0: ============== REGISTER DUMP ============== > > sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 > > sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 > > sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b > > sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 > > sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 > > sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 > > sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 > > sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb > > sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 > > sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 > > sdhci_ti1-slot0: =========================================== > > am335x_pmic0: TPS65217C ver 1.2 powered by USB > > > > and mmcsd1 isn't showing up in /dev/, the boot process, etc. It will > > boot from eMMC if I don't hold down the button by the microSD card. > > > > Anything I should be aware of? > > My speculation is that the newer U-Boot breaks the eMMC support in FreeBSD. An U-Boot from 2013.4 seems to work fine while the U-Boot from 2014.3 doesn't work for me. Just a few weeks ago I tried copy-to-emmc.sh. A couple reverse order messages later it completed, but my BBBs ROM code didn't find anything bootable on it and failed back to xmodem. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 22:45:00 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 294E01A4 for ; Fri, 7 Nov 2014 22:45:00 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6D37897 for ; Fri, 7 Nov 2014 22:44:59 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id d1so5880025wiv.15 for ; Fri, 07 Nov 2014 14:44:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=S7+A26NLGS0YwbLd2D+qTtW3c6KDnFRZNgRdGqxebNM=; b=lPphEisVOCVSRKbdtCrrslttGANVo8ROsnPmRK1s3ugF2b3XU16NxGSV3dEXGS90e5 n/kQrAEGJVPrhewHpfobBVI5ImzRirMjj4lEzJTVtu8mIFd8j3IgVer1mvz05I1TXwrA EXpfT34+Zyu1qG56Q2dyGVBZGSduc+imqthXsrMoUqU/0FIMmgCI7WmlXlnE5dS8u31U fxhpwhNxabtu0LF73e6RSFtLkbtjVGPGjsCWpjYhUW3aKhZ3p38QDNTKKVjucKbkQg3H SiAOCEwe5tJYHpJVutP6ziRIv+Z8H7kYhKoX3qiN8koy9KCpxBp8ruMh4C/ED4qOkkBs 7wtA== X-Received: by 10.180.20.167 with SMTP id o7mr8978096wie.49.1415400298024; Fri, 07 Nov 2014 14:44:58 -0800 (PST) Received: from ketas-laptop.mydomain (ketas-laptop6.si.pri.ee. [2001:ad0:91f:0:21a:6bff:fe66:2ad3]) by mx.google.com with ESMTPSA id wl1sm13445452wjb.4.2014.11.07.14.44.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Nov 2014 14:44:57 -0800 (PST) Sender: Sulev-Madis Silber Message-ID: <545D4B61.2020209@hot.ee> Date: Sat, 08 Nov 2014 00:44:49 +0200 From: "Sulev-Madis Silber (ketas)" User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Tim Kientzle Subject: Re: A current BB Black issues References: <545BFCB8.4030604@ceetonetechnology.com> <545CD0E8.1070402@ceetonetechnology.com> <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com> In-Reply-To: <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com> X-TagToolbar-Keys: D20141108004449264 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: George Rosamond , "freebsd-arm@freebsd.org" , Rui Paulo X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 22:45:00 -0000 I've been using 2014.04 for a quite some time now. With eMMC. No SD connected. I think I should make a port. It feels like only me and one other user have those patches, others just complain that things don't work. And I got almost all of them from crochet repo or freebsd-arm@. However, I don't like those patches. It's wrong way, but I don't know how to do it in right way. Maybe ubldr needs change. If you use these and find that eMMC sometimes fails to detect properly, that's known issue too. I should also mention that I use hardware watchdog, which now works. All patches I currently use with uboot are here: http://ketas.si.pri.ee/bbb/uboot-patches/ On 2014-11-07 18:41, Tim Kientzle wrote: > Patrick Kelsey contributed the patches for U-Boot 2013.04 to support eMMC booting. > > They have not yet been reworked to apply to 2014.04. I’ve looked at it only briefly. > > Tim > > > On Nov 7, 2014, at 6:02 AM, George Rosamond wrote: > >> Rui Paulo: >>> On Nov 6, 2014, at 14:56, George Rosamond >>> wrote: >>>> BeagleBone Black with: >>>> >>>> FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 >>>> r274186: Thu Nov 6 14:51:29 EST 2014 >>>> root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/BEAGLEBONE >>>> >>>> >> arm >>>> >>>> >>>> First, I tried to run copy-to-emmc.sh but noticed this is the >>>> dmesg: >>>> >>>> sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no >>>> active command. sdhci_ti1-slot0: ============== REGISTER DUMP >>>> ============== sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: >>>> 0x00003101 sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: >>>> 0x00000001 sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: >>>> 0x0000071b sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: >>>> 0x00000000 sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: >>>> 0x00000000 sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: >>>> 0x00008007 sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: >>>> 0x00000000 sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: >>>> 0x017f00fb sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: >>>> 0x00000000 sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: >>>> 0x00000000 sdhci_ti1-slot0: >>>> =========================================== sdhci_ti1-slot0: Got >>>> data interrupt 0x00000002, but there is no active command. >>>> sdhci_ti1-slot0: ============== REGISTER DUMP ============== >>>> sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101 >>>> sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001 >>>> sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b >>>> sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000 >>>> sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000 >>>> sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007 >>>> sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000 >>>> sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb >>>> sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 >>>> sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000 >>>> sdhci_ti1-slot0: =========================================== >>>> am335x_pmic0: TPS65217C ver 1.2 powered by USB >>>> >>>> and mmcsd1 isn't showing up in /dev/, the boot process, etc. It >>>> will boot from eMMC if I don't hold down the button by the microSD >>>> card. >>>> >>>> Anything I should be aware of? >>> >>> My speculation is that the newer U-Boot breaks the eMMC support in >>> FreeBSD. An U-Boot from 2013.4 seems to work fine while the U-Boot >>> from 2014.3 doesn't work for me. >>> >> >> That didn't even cross my mind. I'll definitely try that. >> >> Thanks. >> >> g >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://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 Nov 8 02:01:10 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 707A46B8; Sat, 8 Nov 2014 02:01:10 +0000 (UTC) Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A90DBEF; Sat, 8 Nov 2014 02:01:10 +0000 (UTC) Received: by mail-vc0-f180.google.com with SMTP id hy10so2381025vcb.25 for ; Fri, 07 Nov 2014 18:01:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=cBESePNobtBycFlq/KEHatA5ey5wUqNrwvlun3CBliE=; b=tlzG45NUvLIBzj7SQGcIfJN63i2CDvWbcHsFF1tfwHtxPJKiz56nLKWBp+W6wFUNHw H96/CpelcLLWtfbYf9q054PqiAVzIqQfYxOBk7JSIGFe0j5mClCuLuVBTH7ueRnNGH+c bM7BGq1gKWt3LpQGafR+i9sAVf8a6izsJnQBO/CpofOdjLt4BC4ojXggGBmgKikwrixa o20zdt+KUEjEYHWfIXa9RIR0OdUolMKFHnRoPe+7zvIiBAKLizVinz/B6hSywbue31jn CoyCCeQ+wbGUu+w5XmpaeMjIkE5eMER8mkArZCKKGLldDHC0Un8iMFrHJSuy31rsygi+ 92sg== MIME-Version: 1.0 X-Received: by 10.52.64.180 with SMTP id p20mr7587554vds.8.1415412068963; Fri, 07 Nov 2014 18:01:08 -0800 (PST) Sender: johny.mattsson@gmail.com Received: by 10.220.71.136 with HTTP; Fri, 7 Nov 2014 18:01:08 -0800 (PST) In-Reply-To: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> References: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> Date: Sat, 8 Nov 2014 13:01:08 +1100 X-Google-Sender-Auth: FIOtr6M6hryJCCCFesJbmiMzsgI Message-ID: Subject: Re: libgpio From: Johny Mattsson To: Warner Losh Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: arm@freebsd.org, embedded@freebsd.org, Rui Paulo X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 02:01:10 -0000 On 8 November 2014 02:44, Warner Losh wrote:On Nov 6, 2014, at 11:41 PM, Rui Paulo wrote: > Finally a question: What does Linux do here? Is there a standard interface > that we could use to leverage off applications written for Linux? On Linux, userspace GPIO is typically* used through the GPIO SysFS module which provides entries under /sys/class/gpio (or wherever you've mounted your sysfs). Individual pins are transferred to userspace control by writing the pin number to the "export" file, which when successful then adds a virtual directory for that GPIO line, with entries for direction, value, edge and whether it's active-low. Depending on the backing kernel driver and hardware, interrupt support may or may not be available. When available it's enabled by writing "rising", "falling" or "both" (again subject to hw/driver) to the "edge" file, and then select(2)ing on the "value" file return when said edge is triggered. Changing the output on a line is as simple as writing "0" or "1" to the "value" file. Example (drive gpio #32 high): echo 32 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio32/direction # this annoyingly/reassuringly clears this pin - i.e. cat value gives 0 echo 1 > /sys/class/gpio/gpio32/value # some time later, maybe echo 32 > /sys/class/gpio/unexport There is no support for synchronously setting multiple pins through this interface. Even if there was, it would have to be limited to within the one controller/bank. Also, if I remember the i.MX25 correctly, there was no hardware support for doing more than one line at a time anyway due to the register layout. While such a feature would be nice, I wouldn't stress too much about getting it in. At best, support for it will be sporadic depending on hardware. The (limited) documentation for GPIO SysFS on Linux, other than the source itself, can be found here: https://www.kernel.org/doc/Documentation/gpio/sysfs.txt Cheers, /Johny *) Based on personal experience at $work, and the companies we work with, doing various embedded micro and embedded Linux things. From owner-freebsd-arm@FreeBSD.ORG Sat Nov 8 04:09:07 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CEC5C9BA; Sat, 8 Nov 2014 04:09:07 +0000 (UTC) Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtp001.mac.com [17.172.220.236]) (using TLSv1 with cipher DES-CBC3-SHA (112/168 bits)) (Client CN "smtp.me.com", Issuer "VeriSign Class 3 Extended Validation SSL SGC CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2F4D907; Sat, 8 Nov 2014 04:09:07 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (unknown [73.162.13.215]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit (built Jun 6 2014)) with ESMTPSA id <0NEP00707CUH2S70@st11p02mm-asmtp001.mac.com>; Sat, 08 Nov 2014 04:08:43 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.28,0.0.0000 definitions=2014-11-08_01:2014-11-07,2014-11-07,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1408290000 definitions=main-1411080043 Content-type: text/plain; charset=windows-1252 MIME-version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: libgpio From: Rui Paulo In-reply-to: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> Date: Fri, 07 Nov 2014 20:08:40 -0800 Content-transfer-encoding: quoted-printable Message-id: <7B37033A-A7DC-4328-90E0-F33A2A008D68@me.com> References: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.1990.1) Cc: arm@freebsd.org, embedded@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 04:09:07 -0000 On Nov 7, 2014, at 07:44, Warner Losh wrote: > I generally like it. Here=92s some suggestions, though many may be = hard given that our gpio interface is a bit weak. >=20 > First, there=92s no way to set multiple pins at the same time. That=92s = likely a reflection of our GPIO system, I know, but it is a deficiency. = Fortunately, most devices can tolerate multiple pins changing at = different times before a =91clock=92 or =91enable=92 pin forces them to = latch their state. OK; I'll work on an API that does this even if it's just a for loop = setting multiple pins to their state. > What the heck is g_caps? There=92s nothing at all to describe it. Not = even an indirection to look at sys/gpio.h It's what describes the pin: input/output/pullup/etc. I'll add some = documentation. I need to write a man page anyway. > For systems that have multiple GPIO devices (some have a few hundred = I/O lines that can be addressed), how > do you handle that? Do you just kinda have to know these details? Right now you have to work with each individually. We could change it = so that it opens all gpio devices and provides a structure that includes = all pins. > There=92s no facilities for interrupts (usually you=92d like to say = =93wait for this line to change and let me know=94). I know that the = Atmel gpio stuff did this, but I don=92t think that made it into the = generalization that was later done. There's no kernel support for it, but the library could create a thread = to poll the pin to see if it has changed. It's wasteful, but I don't = see any better way until we have GPIO interrupts. > I=92m not sure that I like the gpio_pin_* helper functions causing the = thing to change, rather than operating on a gpio_config_t. But since you = don=92t normally change a bunch at a time, that=92s not so bad. I just added those to make it easy to configure pins in one shot. > Finally a question: What does Linux do here? Is there a standard = interface that we could use to leverage off applications written for = Linux? Perhaps beyond the scope of what you=92re trying to do, but any = discussion about pushing things into the base should ask the question = =93Is this the right, most useful interface?=94 That was correctly answered by Johny. -- Rui Paulo From owner-freebsd-arm@FreeBSD.ORG Sat Nov 8 04:37:03 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55F3258B; Sat, 8 Nov 2014 04:37:03 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (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 15D9EC7D; Sat, 8 Nov 2014 04:37:02 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Xmxlk-0003fD-QQ; Sat, 08 Nov 2014 04:37:01 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id sA84axMh002540; Fri, 7 Nov 2014 21:36:59 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX185YLfL3hOH80v5go8QAP1I X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: libgpio From: Ian Lepore To: Rui Paulo In-Reply-To: <7B37033A-A7DC-4328-90E0-F33A2A008D68@me.com> References: <58908C87-6046-4873-87B1-74995EFA72D1@bsdimp.com> <7B37033A-A7DC-4328-90E0-F33A2A008D68@me.com> Content-Type: text/plain; charset="windows-1251" Date: Fri, 07 Nov 2014 21:36:58 -0700 Message-ID: <1415421418.1200.278.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ilsoft.org id sA84axMh002540 Cc: arm@freebsd.org, embedded@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 04:37:03 -0000 On Fri, 2014-11-07 at 20:08 -0800, Rui Paulo wrote: > On Nov 7, 2014, at 07:44, Warner Losh wrote: > > I generally like it. Here=92s some suggestions, though many may be ha= rd given that our gpio interface is a bit weak. > >=20 > > First, there=92s no way to set multiple pins at the same time. That=92= s likely a reflection of our GPIO system, I know, but it is a deficiency.= Fortunately, most devices can tolerate multiple pins changing at differe= nt times before a =91clock=92 or =91enable=92 pin forces them to latch th= eir state. >=20 > OK; I'll work on an API that does this even if it's just a for loop se= tting multiple pins to their state. >=20 A loop would default the purpose of the feature. Sometimes you need to create a bus out of a collection of pins, and it only works if you can manipulate the pin states atomically as a group. If the underlying device doesn't support it, then you wouldn't be trying to do it in the first place. The current at91 gpio interface supports this in a fairly simple way, but not a way that would necessarily map to every device (it assumes 32 pins per /dev/gpiocN for example). > > What the heck is g_caps? There=92s nothing at all to describe it. Not= even an indirection to look at sys/gpio.h >=20 > It's what describes the pin: input/output/pullup/etc. I'll add some do= cumentation. I need to write a man page anyway. >=20 > > For systems that have multiple GPIO devices (some have a few hundred = I/O lines that can be addressed), how > > do you handle that? Do you just kinda have to know these details? >=20 > Right now you have to work with each individually. We could change it = so that it opens all gpio devices and provides a structure that includes = all pins. >=20 That's probably not a good idea, because gpio devices can come and go. For example, at work we have hot-pluggable expansion cards with an i2c bus that runs to each expansion slot, and there are i2c devices that provide gpio. FTDI usb<->serial chips also provide gpio pins and can come and go. I think userland software working with gpios is generally purpose- specific and targeted at a particular piece of hardware, and just knows what device and pin numbers to work with, as opposed to knowing some abstraction like "pin 147". -- Ian > > There=92s no facilities for interrupts (usually you=92d like to say =93= wait for this line to change and let me know=94). I know that the Atmel g= pio stuff did this, but I don=92t think that made it into the generalizat= ion that was later done. >=20 > There's no kernel support for it, but the library could create a thread= to poll the pin to see if it has changed. It's wasteful, but I don't se= e any better way until we have GPIO interrupts. >=20 > > I=92m not sure that I like the gpio_pin_* helper functions causing th= e thing to change, rather than operating on a gpio_config_t. But since yo= u don=92t normally change a bunch at a time, that=92s not so bad. >=20 > I just added those to make it easy to configure pins in one shot. >=20 > > Finally a question: What does Linux do here? Is there a standard inte= rface that we could use to leverage off applications written for Linux? P= erhaps beyond the scope of what you=92re trying to do, but any discussion= about pushing things into the base should ask the question =93Is this th= e right, most useful interface?=94 >=20 > That was correctly answered by Johny. >=20 > -- > Rui Paulo >=20 >=20 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20 From owner-freebsd-arm@FreeBSD.ORG Sat Nov 8 16:58:35 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B23223C6 for ; Sat, 8 Nov 2014 16:58:35 +0000 (UTC) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 810AD315 for ; Sat, 8 Nov 2014 16:58:34 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id 7AA0939D0A for ; Sun, 9 Nov 2014 01:58:26 +0900 (JST) Received: from artemis (unknown [172.18.0.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id 616FB39D09 for ; Sun, 9 Nov 2014 01:58:26 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: Subject: swap_pager_reserve bug (not arm depend and any version of FreeBSD) Date: Sun, 9 Nov 2014 01:58:21 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 16:58:35 -0000 Hello, In short, I get a bug of kernel code. swap_pager_reserve never free unused area. Because of this, you can't clean up correctly by vm_object_deallocate. The part of my code in the kernel module is like this: vm_object_t obj; obj = vm_pager_allocate(OBJT_SWAP, NULL, 32768, VM_PROT_DEFAULT, 0, NULL); swap_pager_reserve(obj, 0, OFF_TO_IDX(32768)); (using...) vm_object_deallocate(obj); Allocate 32KB as swap object, then reserve all and deallocate it after using. In this case, swap_pager_reserve take 128KB(32xPAGE_SIZE) swap on it, but vm_object_deallocate will free only 32KB. Probably, left 96KB will cause a kernel panic when you remove(swapoff) the swap device (including shutdown). I think this is a rare case but don't want get a panic... Here is my test patch. If you have more better code, please help me. Currently, I've tested on 9.3 amd64 and 11-current arm RPi. Index: swap_pager.c =================================================================== --- swap_pager.c (revision 274088) +++ swap_pager.c (working copy) @@ -858,7 +858,7 @@ VM_OBJECT_WLOCK(object); while (size) { if (n == 0) { - n = BLIST_MAX_ALLOC; + n = min(BLIST_MAX_ALLOC, size); /* happy with small size */ while ((blk = swp_pager_getswapspace(n)) == SWAPBLK_NONE) { n >>= 1; if (n == 0) { Thanks, -- Daisuke Aoyama