From owner-freebsd-arm@freebsd.org Sun Oct 9 22:22:02 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BECF8C0BB38; Sun, 9 Oct 2016 22:22:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81F10B81; Sun, 9 Oct 2016 22:22:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x236.google.com with SMTP id z65so54930320itc.0; Sun, 09 Oct 2016 15:22:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=B7EPTlsI4G18YWl8Gqv99gHK6oJWO1ja8qOG598UxMQ=; b=YQk2c3ruPWNpzkUWm3MD6WfGZTkIqNe0Co16TOEWq7RUXF/sgvfQxALWB9vCY5S3TH VT90T0M3vjHfNr/0qWhewry+5wnOJYLw/5eDLPUZ8MURYfIln1PayPKRAlJqZX6fOv9g cl/hOurwi/mvWq3C4ta3D6Dw3vWyh9S1vIShXwvbqpwYI0UggjspH5pmLJDj5FB7rZRw 6EXhbeuXTB/UpfbPv143QeoSy3Ype5WDH0FyjjjRxPXaBHllOjw7rJ7K+LP4d5wmGKI6 STQ2CqK20khyGG9WqhpDBhgifB7fHdSlt8MeeGTYxmSBXuQHOPd5VIXagqDGXcJY8VIU HUZg== 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:from:date :message-id:subject:to:cc; bh=B7EPTlsI4G18YWl8Gqv99gHK6oJWO1ja8qOG598UxMQ=; b=kG+ucCXXqnprW6RQGb6L0Yw66E5f5e/Owcrx1JZaHX3YlTLSIu3y8ONaJIdn7RCGt7 XcZARn+K1th+ipqOaUps3ekE6FTt6DSerY9TDsPT9owH5QxYN5KLgACAYWBw27ZaTuUA 6U8wYAwDGs9iQjq2HSkbIyh76pL0lMo1W+UMhxoYvcKbZNop2d5J/dwgEaop70cNNf9B mmqFx26z/Wd/FgUZDJxMdE32hwMkQdL0HlVEEZQZ46W5iWddwMs+n7iSj3NLJlaHpFGZ FlOtaYLfhSZ5o7I0y2j1VY18Wu7c8ak2PCyVeJD10F9kVXzfdzUpekszjk4S2po/91Hp pkCA== X-Gm-Message-State: AA6/9RkjlnMs5r4vfnT/8IIB7KLVG9nqHgrmu5NpBZTwvxaMS+TdwrsQ5ClsDO+nC401g72Zi0rDV+y36EeYRA== X-Received: by 10.36.228.195 with SMTP id o186mr7128882ith.39.1476051721818; Sun, 09 Oct 2016 15:22:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Sun, 9 Oct 2016 15:22:00 -0700 (PDT) In-Reply-To: <13052a1c-db9b-6e08-eb1a-d75b93c67c33@ambient-md.com> References: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> <13052a1c-db9b-6e08-eb1a-d75b93c67c33@ambient-md.com> From: Adrian Chadd Date: Sun, 9 Oct 2016 15:22:00 -0700 Message-ID: Subject: Re: RPI2 AP To: Peter Garshtja , "freebsd-wireless@freebsd.org" Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Oct 2016 22:22:02 -0000 hiya, ok. We'll need some more debugging from the driver and net80211. Andriy? Any ideas? -a On 8 October 2016 at 08:11, Peter Garshtja wrote: > Good Morning Adrian, > > I added and rebooted RPI2, but the result is the same > > wlan_amrr_load="YES" to /boot/loader.conf > > ifconfig wlan0 list sta > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 50:55:27:ff:dc:04 1 5 54M 20.5 0 2482 38240 EPS AQE RSN > WME > 00:13:ef:66:18:49 2 5 1M 14.0 0 7130 27104 EPS AQE RSN > WME > > After ~ 5 minutes all the stations were disconnected > > 10:43 # ifconfig wlan0 list sta > 10:43 # ifconfig wlan0 list sta > 10:43 # > > WLAN interface details > ------------------------------ > ifconfig wlan0 list caps > drivercaps=591c541 > cryptocaps=b > htcaps=6000c<> > ------------------------------ > > Kernel modules loaded > > Id Refs Address Size Name > 1 31 0xc0100000 9bfaec kernel > 2 1 0xc0ac0000 a168 wlan_amrr.ko > 3 7 0xc0acb000 59a18 wlan.ko > 4 1 0xc46d2000 11000 if_bridge.ko > 5 1 0xc46e3000 e000 bridgestp.ko > 6 1 0xc4731000 d000 if_vlan.ko > 7 1 0xc484c000 27000 if_urtwn.ko > 8 1 0xc4774000 b000 firmware.ko > 9 1 0xc46bf000 a000 pflog.ko > 10 1 0xc4b2c000 3a000 pf.ko > 11 1 0xc4e25000 9000 wlan_xauth.ko > 12 1 0xc4888000 a000 wlan_wep.ko > 13 1 0xc4ef9000 b000 wlan_tkip.ko > 14 1 0xc4f0c000 e000 wlan_ccmp.ko > > I have 2 different wifi dongles with the same chipset and the behavior is > the same. > > Also here is the dmesg after reboot > > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 > ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM > 3.8.0) > VT: init without driver. > sema_sysinit > CPU: Cortex A7 rev 5 (Cortex-A core) > Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext > WB enabled LABT branch prediction disabled > LoUU:2 LoC:3 LoUIS:2 > Cache level 1: > 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc > 32KB/32B 2-way instruction cache Read-Alloc > Cache level 2: > 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc > real memory = 989851648 (943 MB) > avail memory = 955379712 (911 MB) > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > random: entropy device external interface > kbd0 at kbdmux0 > ofwbus0: > simplebus0: mem 0x3f000000-0x3fffffff on > ofwbus0 > local_intc0: mem 0x40000000-0x400000ff on > simplebus0 > generic_timer0: on ofwbus0 > Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 > Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 > intc0: mem 0xb200-0xb3ff on simplebus0 > bcmwd0: mem 0x10001c-0x100027 on simplebus0 > gpio0: mem 0x200000-0x2000af on simplebus0 > gpio0: read-only pins: 46,48-53. > gpio0: reserved pins: 48-53. > gpiobus0: on gpio0 > gpioled0: at pin 35 on gpiobus0 > gpioled1: at pin 47 on gpiobus0 > gpioc0: on gpio0 > iichb0: mem 0x205000-0x20501f on simplebus0 > iicbus0: on iichb0 > iic0: on iicbus0 > iichb1: mem 0x804000-0x80401f on simplebus0 > iicbus1: on iichb1 > iic1: on iicbus1 > spi0: mem 0x204000-0x20401f on simplebus0 > spibus0: on spi0 > bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on > simplebus0 > mbox0: mem 0xb880-0xb8bf on simplebus0 > sdhci_bcm0: mem 0x300000-0x3000ff on > simplebus0 > mmc0: on sdhci_bcm0 > uart0: mem 0x201000-0x201fff on simplebus0 > uart0: console (115200,n,8,1) > vchiq0: mem 0xb800-0xb84f on simplebus0 > vchiq: local ver 8 (min 3), remote ver 8. > pcm0: on vchiq0 > bcm283x_dwcotg0: mem > 0x980000-0x99ffff on simplebus0 > usbus0 on bcm283x_dwcotg0 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > bcm2835_cpufreq0: on cpu0 > cpu1: on cpulist0 > cpu2: on cpulist0 > cpu3: on cpulist0 > fb0: on ofwbus0 > fbd0 on fb0 > VT: initialize with new VT driver "fb". > fb0: 1680x1050(1680x1050@0,0) 24bpp > fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 > cryptosoft0: > Timecounters tick every 10.000 msec > usbus0: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > mmcsd0: 8GB at mmc0 > 41.6MHz/4bit/65535-block > bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF > Release APs > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... > warning: no time-of-day clock registered, system time will not be set > accurately > uhub0: 1 port with 1 removable, self powered > ugen0.2: at usbus0 > uhub1: on > usbus0 > uhub1: MTT enabled > random: unblocking device. > uhub1: 5 ports with 4 removable, self powered > ugen0.3: at usbus0 > smsc0: on usbus0 > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > ukphy0: PHY 1 on miibus0 > ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: Ethernet address: b8:27:eb:f2:8e:4e > ugen0.4: at usbus0 > bridge0: Ethernet address: 02:fd:a6:82:73:00 > ue0: changing name to 'mgmt' > smsc0: chip 0xec00, rev. 0002 > mgmt: link state changed to DOWN > vlan0: changing name to 'wan' > vlan1: changing name to 'lan' > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > urtwn0: on usbus0 > urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R > urtwn0: enabling 11n > wlan0: Ethernet address: 00:c6:d2:21:c9:34 > wlan0: promiscuous mode enabled > bridge0: link state changed to UP > pflog0: promiscuous mode enabled > mgmt: promiscuous mode enabled > lan: promiscuous mode enabled > > > Thanks, > Peter > > > On 10/8/2016 12:51 AM, Adrian Chadd wrote: > > heh, try adding wlan_amrr_load="YES" to /boot/loader.conf and rebooting? > > > -a > > > On 7 October 2016 at 18:59, Peter Garshtja > wrote: > > Greetings, > > Here is uname - 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306544M > > > Below is dmesg > > > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 > ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM > 3.8.0) > VT: init without driver. > sema_sysinit > CPU: Cortex A7 rev 5 (Cortex-A core) > Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext > WB enabled LABT branch prediction disabled > LoUU:2 LoC:3 LoUIS:2 > Cache level 1: > 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc > 32KB/32B 2-way instruction cache Read-Alloc > Cache level 2: > 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc > real memory = 989851648 (943 MB) > avail memory = 956411904 (912 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > random: entropy device external interface > kbd0 at kbdmux0 > ofwbus0: > simplebus0: mem 0x3f000000-0x3fffffff on > ofwbus0 > local_intc0: mem 0x40000000-0x400000ff on > simplebus0 > generic_timer0: on ofwbus0 > Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 > Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 > intc0: mem 0xb200-0xb3ff on simplebus0 > bcmwd0: mem 0x10001c-0x100027 on simplebus0 > gpio0: mem 0x200000-0x2000af on simplebus0 > gpio0: read-only pins: 46,48-53. > gpio0: reserved pins: 48-53. > gpiobus0: on gpio0 > gpioled0: at pin 35 on gpiobus0 > gpioled1: at pin 47 on gpiobus0 > gpioc0: on gpio0 > iichb0: mem 0x205000-0x20501f on simplebus0 > iicbus0: on iichb0 > iic0: on iicbus0 > iichb1: mem 0x804000-0x80401f on simplebus0 > iicbus1: on iichb1 > iic1: on iicbus1 > spi0: mem 0x204000-0x20401f on simplebus0 > spibus0: on spi0 > bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on > simplebus0 > mbox0: mem 0xb880-0xb8bf on simplebus0 > sdhci_bcm0: mem 0x300000-0x3000ff on > simplebus0 > mmc0: on sdhci_bcm0 > uart0: mem 0x201000-0x201fff on simplebus0 > uart0: console (115200,n,8,1) > vchiq0: mem 0xb800-0xb84f on simplebus0 > vchiq: local ver 8 (min 3), remote ver 8. > pcm0: on vchiq0 > bcm283x_dwcotg0: mem > 0x980000-0x99ffff on simplebus0 > usbus0 on bcm283x_dwcotg0 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > bcm2835_cpufreq0: on cpu0 > cpu1: on cpulist0 > cpu2: on cpulist0 > cpu3: on cpulist0 > fb0: on ofwbus0 > fbd0 on fb0 > VT: initialize with new VT driver "fb". > fb0: 1680x1050(1680x1050@0,0) 24bpp > fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 > cryptosoft0: > Timecounters tick every 10.000 msec > usbus0: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > mmcsd0: 8GB at mmc0 > 41.6MHz/4bit/65535-block > bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF > Release APs > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... > WARNING: / was not properly dismounted > warning: no time-of-day clock registered, system time will not be set > accurately > uhub0: 1 port with 1 removable, self powered > ugen0.2: at usbus0 > uhub1: on > usbus0 > uhub1: MTT enabled > uhub1: 5 ports with 4 removable, self powered > random: unblocking device. > ugen0.3: at usbus0 > smsc0: on usbus0 > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > ukphy0: PHY 1 on miibus0 > ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: Ethernet address: b8:27:eb:f2:8e:4e > ugen0.4: at usbus0 > bridge0: Ethernet address: 02:fd:a6:82:73:00 > ue0: changing name to 'mgmt' > smsc0: chip 0xec00, rev. 0002 > mgmt: link state changed to DOWN > vlan0: changing name to 'wan' > vlan1: changing name to 'lan' > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > urtwn0: on usbus0 > > *urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R > > *urtwn0: enabling 11n > mgmt: link state changed to DOWN > lan: link state changed to DOWN > wan: link state changed to DOWN > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > ieee80211_load_module: load the wlan_amrr module by hand for now. > wlan0: Ethernet address: 00:c6:d2:21:c9:34 > wlan0: promiscuous mode enabled > bridge0: link state changed to UP > pflog0: promiscuous mode enabled > mgmt: promiscuous mode enabled > lan: promiscuous mode enabled > > Thanks in advance, > > Peter > > On 10/7/2016 4:36 PM, Adrian Chadd wrote: > > + freebsd-wireless > > can you post a 'dmesg' output? That way we can see which urtwn NIC it > is and whether it logged anything. > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > From owner-freebsd-arm@freebsd.org Sun Oct 9 22:24:23 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A881C0BBC0; Sun, 9 Oct 2016 22:24:23 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7230C7D; Sun, 9 Oct 2016 22:24:22 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f49.google.com with SMTP id b81so93812780lfe.1; Sun, 09 Oct 2016 15:24:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=NVH/5Ta2qEMQVL/dObZ9uNxT0ArF/pk7n7IgdywfD+I=; b=mnYU+sAls4/fq6abt5MfG27lQxwUzKHt6+lG06/LWyZINu0SouiH/N8hYfE9tKCgHO oMxxMDDkLisFI5i8r92rbbs6mBZIriBGVWwnNasMwQ/dmfKkxpLmmkyXDv+KPyYBjy6x 6c7PKyRi1PjDE2Eu9vogpgFFI3jA5SSP/SstIcvzfnXghkq6ovay8iXCyuMVdOxsdfTe +KzIPLW307FHMpoJfeUz+03ioFporRJFyaQLPUVaVWZNd+jB+800RfuTX40F5nhpvFaN 0gef25j5bR0vPsdNb8ZGNzjnrs4bWUKuB5+biu3xwf9EFdYXcCi/PPsXCQfH6yXMUTzD sRiw== X-Gm-Message-State: AA6/9Rk9M2LW5N8/MldGiZBdP9ezZkXUr6EgCwy2/mW+lmDco4GhpQSaRRxTggxcFa0Xlw== X-Received: by 10.25.18.97 with SMTP id h94mr12710701lfi.106.1476051854499; Sun, 09 Oct 2016 15:24:14 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id b71sm5466842lfb.42.2016.10.09.15.24.13 (version=TLS1 cipher=AES128-SHA bits=128/128); Sun, 09 Oct 2016 15:24:14 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Peter Garshtja" , "freebsd-wireless@freebsd.org" , "Adrian Chadd" Cc: "freebsd-arm@freebsd.org" Subject: Re: RPI2 AP References: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> <13052a1c-db9b-6e08-eb1a-d75b93c67c33@ambient-md.com> Date: Mon, 10 Oct 2016 01:24:14 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Oct 2016 22:24:23 -0000 Mon, 10 Oct 2016 01:22:00 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Adrian Chadd = : Have you tried to use the driver from https://github.com/s3erios/rtwn ? > hiya, > > ok. We'll need some more debugging from the driver and net80211. > > Andriy? Any ideas? > > > -a > > > On 8 October 2016 at 08:11, Peter Garshtja > wrote: >> Good Morning Adrian, >> >> I added and rebooted RPI2, but the result is the same >> >> wlan_amrr_load=3D"YES" to /boot/loader.conf >> >> ifconfig wlan0 list sta >> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> 50:55:27:ff:dc:04 1 5 54M 20.5 0 2482 38240 EPS AQE = = >> RSN >> WME >> 00:13:ef:66:18:49 2 5 1M 14.0 0 7130 27104 EPS AQE = = >> RSN >> WME >> >> After ~ 5 minutes all the stations were disconnected >> >> 10:43 # ifconfig wlan0 list sta >> 10:43 # ifconfig wlan0 list sta >> 10:43 # >> >> WLAN interface details >> ------------------------------ >> ifconfig wlan0 list caps >> drivercaps=3D591c541 >> cryptocaps=3Db >> htcaps=3D6000c<> >> ------------------------------ >> >> Kernel modules loaded >> >> Id Refs Address Size Name >> 1 31 0xc0100000 9bfaec kernel >> 2 1 0xc0ac0000 a168 wlan_amrr.ko >> 3 7 0xc0acb000 59a18 wlan.ko >> 4 1 0xc46d2000 11000 if_bridge.ko >> 5 1 0xc46e3000 e000 bridgestp.ko >> 6 1 0xc4731000 d000 if_vlan.ko >> 7 1 0xc484c000 27000 if_urtwn.ko >> 8 1 0xc4774000 b000 firmware.ko >> 9 1 0xc46bf000 a000 pflog.ko >> 10 1 0xc4b2c000 3a000 pf.ko >> 11 1 0xc4e25000 9000 wlan_xauth.ko >> 12 1 0xc4888000 a000 wlan_wep.ko >> 13 1 0xc4ef9000 b000 wlan_tkip.ko >> 14 1 0xc4f0c000 e000 wlan_ccmp.ko >> >> I have 2 different wifi dongles with the same chipset and the behavio= r = >> is >> the same. >> >> Also here is the dmesg after reboot >> >> Copyright (c) 1992-2016 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1= 994 >> The Regents of the University of California. All rights = >> reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 >> ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm >> FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on= = >> LLVM >> 3.8.0) >> VT: init without driver. >> sema_sysinit >> CPU: Cortex A7 rev 5 (Cortex-A core) >> Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ex= t >> WB enabled LABT branch prediction disabled >> LoUU:2 LoC:3 LoUIS:2 >> Cache level 1: >> 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc >> 32KB/32B 2-way instruction cache Read-Alloc >> Cache level 2: >> 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc >> real memory =3D 989851648 (943 MB) >> avail memory =3D 955379712 (911 MB) >> >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> random: entropy device external interface >> kbd0 at kbdmux0 >> ofwbus0: >> simplebus0: mem = >> 0x3f000000-0x3fffffff on >> ofwbus0 >> local_intc0: mem 0x40000000-0x400000ff= on >> simplebus0 >> generic_timer0: on ofwbus0 >> Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 10= 00 >> Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 100= 0 >> intc0: mem 0xb200-0xb3ff on simplebus0= >> bcmwd0: mem 0x10001c-0x100027 on simplebus0 >> gpio0: mem 0x200000-0x2000af on = >> simplebus0 >> gpio0: read-only pins: 46,48-53. >> gpio0: reserved pins: 48-53. >> gpiobus0: on gpio0 >> gpioled0: at pin 35 on gpiobus0 >> gpioled1: at pin 47 on gpiobus0 >> gpioc0: on gpio0 >> iichb0: mem 0x205000-0x20501f on = >> simplebus0 >> iicbus0: on iichb0 >> iic0: on iicbus0 >> iichb1: mem 0x804000-0x80401f on = >> simplebus0 >> iicbus1: on iichb1 >> iic1: on iicbus1 >> spi0: mem 0x204000-0x20401f on simplebu= s0 >> spibus0: on spi0 >> bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05ff= f = >> on >> simplebus0 >> mbox0: mem 0xb880-0xb8bf on simplebus0 >> sdhci_bcm0: mem 0x300000-0x3000ff on= >> simplebus0 >> mmc0: on sdhci_bcm0 >> uart0: mem 0x201000-0x201fff on simplebus0 >> uart0: console (115200,n,8,1) >> vchiq0: mem 0xb800-0xb84f on simplebus0 >> vchiq: local ver 8 (min 3), remote ver 8. >> pcm0: on vchiq0 >> bcm283x_dwcotg0: me= m >> 0x980000-0x99ffff on simplebus0 >> usbus0 on bcm283x_dwcotg0 >> cpulist0: on ofwbus0 >> cpu0: on cpulist0 >> bcm2835_cpufreq0: on cpu0 >> cpu1: on cpulist0 >> cpu2: on cpulist0 >> cpu3: on cpulist0 >> fb0: on ofwbus0 >> fbd0 on fb0 >> VT: initialize with new VT driver "fb". >> fb0: 1680x1050(1680x1050@0,0) 24bpp >> fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 >> cryptosoft0: >> Timecounters tick every 10.000 msec >> usbus0: 480Mbps High Speed USB v2.0 >> ugen0.1: at usbus0 >> uhub0: on usb= us0 >> mmcsd0: 8GB at mmc0 >> 41.6MHz/4bit/65535-block >> bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF >> Release APs >> Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... >> warning: no time-of-day clock registered, system time will not be set= >> accurately >> uhub0: 1 port with 1 removable, self powered >> ugen0.2: at usbus0 >> uhub1: = >> on >> usbus0 >> uhub1: MTT enabled >> random: unblocking device. >> uhub1: 5 ports with 4 removable, self powered >> ugen0.3: at usbus0 >> smsc0: on usbus= 0 >> smsc0: chip 0xec00, rev. 0002 >> miibus0: on smsc0 >> ukphy0: PHY 1 on miibus0 >> ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: on smsc0 >> ue0: Ethernet address: b8:27:eb:f2:8e:4e >> ugen0.4: at usbus0 >> bridge0: Ethernet address: 02:fd:a6:82:73:00 >> ue0: changing name to 'mgmt' >> smsc0: chip 0xec00, rev. 0002 >> mgmt: link state changed to DOWN >> vlan0: changing name to 'wan' >> vlan1: changing name to 'lan' >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> urtwn0: on = >> usbus0 >> urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R >> urtwn0: enabling 11n >> wlan0: Ethernet address: 00:c6:d2:21:c9:34 >> wlan0: promiscuous mode enabled >> bridge0: link state changed to UP >> pflog0: promiscuous mode enabled >> mgmt: promiscuous mode enabled >> lan: promiscuous mode enabled >> >> >> Thanks, >> Peter >> >> >> On 10/8/2016 12:51 AM, Adrian Chadd wrote: >> >> heh, try adding wlan_amrr_load=3D"YES" to /boot/loader.conf and reboo= ting? >> >> >> -a >> >> >> On 7 October 2016 at 18:59, Peter Garshtja >> wrote: >> >> Greetings, >> >> Here is uname - 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r30654= 4M >> >> >> Below is dmesg >> >> >> Copyright (c) 1992-2016 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1= 994 >> The Regents of the University of California. All rights = >> reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 >> ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm >> FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on= = >> LLVM >> 3.8.0) >> VT: init without driver. >> sema_sysinit >> CPU: Cortex A7 rev 5 (Cortex-A core) >> Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ex= t >> WB enabled LABT branch prediction disabled >> LoUU:2 LoC:3 LoUIS:2 >> Cache level 1: >> 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc >> 32KB/32B 2-way instruction cache Read-Alloc >> Cache level 2: >> 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc >> real memory =3D 989851648 (943 MB) >> avail memory =3D 956411904 (912 MB) >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> random: entropy device external interface >> kbd0 at kbdmux0 >> ofwbus0: >> simplebus0: mem = >> 0x3f000000-0x3fffffff on >> ofwbus0 >> local_intc0: mem 0x40000000-0x400000ff= on >> simplebus0 >> generic_timer0: on ofwbus0 >> Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 10= 00 >> Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 100= 0 >> intc0: mem 0xb200-0xb3ff on simplebus0= >> bcmwd0: mem 0x10001c-0x100027 on simplebus0 >> gpio0: mem 0x200000-0x2000af on = >> simplebus0 >> gpio0: read-only pins: 46,48-53. >> gpio0: reserved pins: 48-53. >> gpiobus0: on gpio0 >> gpioled0: at pin 35 on gpiobus0 >> gpioled1: at pin 47 on gpiobus0 >> gpioc0: on gpio0 >> iichb0: mem 0x205000-0x20501f on = >> simplebus0 >> iicbus0: on iichb0 >> iic0: on iicbus0 >> iichb1: mem 0x804000-0x80401f on = >> simplebus0 >> iicbus1: on iichb1 >> iic1: on iicbus1 >> spi0: mem 0x204000-0x20401f on simplebu= s0 >> spibus0: on spi0 >> bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05ff= f = >> on >> simplebus0 >> mbox0: mem 0xb880-0xb8bf on simplebus0 >> sdhci_bcm0: mem 0x300000-0x3000ff on= >> simplebus0 >> mmc0: on sdhci_bcm0 >> uart0: mem 0x201000-0x201fff on simplebus0 >> uart0: console (115200,n,8,1) >> vchiq0: mem 0xb800-0xb84f on simplebus0 >> vchiq: local ver 8 (min 3), remote ver 8. >> pcm0: on vchiq0 >> bcm283x_dwcotg0: me= m >> 0x980000-0x99ffff on simplebus0 >> usbus0 on bcm283x_dwcotg0 >> cpulist0: on ofwbus0 >> cpu0: on cpulist0 >> bcm2835_cpufreq0: on cpu0 >> cpu1: on cpulist0 >> cpu2: on cpulist0 >> cpu3: on cpulist0 >> fb0: on ofwbus0 >> fbd0 on fb0 >> VT: initialize with new VT driver "fb". >> fb0: 1680x1050(1680x1050@0,0) 24bpp >> fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 >> cryptosoft0: >> Timecounters tick every 10.000 msec >> usbus0: 480Mbps High Speed USB v2.0 >> ugen0.1: at usbus0 >> uhub0: on usb= us0 >> mmcsd0: 8GB at mmc0 >> 41.6MHz/4bit/65535-block >> bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF >> Release APs >> Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... >> WARNING: / was not properly dismounted >> warning: no time-of-day clock registered, system time will not be set= >> accurately >> uhub0: 1 port with 1 removable, self powered >> ugen0.2: at usbus0 >> uhub1: = >> on >> usbus0 >> uhub1: MTT enabled >> uhub1: 5 ports with 4 removable, self powered >> random: unblocking device. >> ugen0.3: at usbus0 >> smsc0: on usbus= 0 >> smsc0: chip 0xec00, rev. 0002 >> miibus0: on smsc0 >> ukphy0: PHY 1 on miibus0 >> ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: on smsc0 >> ue0: Ethernet address: b8:27:eb:f2:8e:4e >> ugen0.4: at usbus0 >> bridge0: Ethernet address: 02:fd:a6:82:73:00 >> ue0: changing name to 'mgmt' >> smsc0: chip 0xec00, rev. 0002 >> mgmt: link state changed to DOWN >> vlan0: changing name to 'wan' >> vlan1: changing name to 'lan' >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> urtwn0: on = >> usbus0 >> >> *urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R >> >> *urtwn0: enabling 11n >> mgmt: link state changed to DOWN >> lan: link state changed to DOWN >> wan: link state changed to DOWN >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> ieee80211_load_module: load the wlan_amrr module by hand for now. >> wlan0: Ethernet address: 00:c6:d2:21:c9:34 >> wlan0: promiscuous mode enabled >> bridge0: link state changed to UP >> pflog0: promiscuous mode enabled >> mgmt: promiscuous mode enabled >> lan: promiscuous mode enabled >> >> Thanks in advance, >> >> Peter >> >> On 10/7/2016 4:36 PM, Adrian Chadd wrote: >> >> + freebsd-wireless >> >> can you post a 'dmesg' output? That way we can see which urtwn NIC it= >> is and whether it logged anything. >> >> >> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org= " >> >> > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Mon Oct 10 00:58:46 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 064F5C07D9B for ; Mon, 10 Oct 2016 00:58:46 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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 CAF7DEF1 for ; Mon, 10 Oct 2016 00:58:45 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=6+2GdBbdXjbVmO6sLwrpJS4gAbri9L1YjrjNMb9ig9I=; b=X3NraiHUKb/fpOiZyYw2dHuG+X AWAnEZtCAdABR6tYOeAcjykz0fSGaRw7ywZapkn9mtEq0ACuOFQokGX3akbwKbdLRlGrhChXg45oQ 2QRsinIOQUswmd9vH4wh90pSUvAKuvSw5P5UYi+oxGWWtY3Fz6t208v+XPja9JFUrd1g=; Received: from [114.120.232.105] (port=46638 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1btOvO-002EGf-2d for freebsd-arm@freebsd.org; Sun, 09 Oct 2016 18:58:38 -0600 Date: Mon, 10 Oct 2016 08:58:32 +0800 From: Erich Dollansky To: "freebsd-arm@freebsd.org" Subject: Where is makeinfo gone Message-ID: <20161010085832.311ac350@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-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 00:58:46 -0000 Hi, I was a bit surprised that makeinfo seems to be gone from my newer Raspberries. The installation dated 20.11.15 still has it in /usr/bin but the installation dated 01.12.15 and all newer do not have it anymore. I am running 10.x, 11 and 12 on different Raspberries. At least http://www.unix.com/man-page/freebsd/1/makeinfo/ tells me that it should be part of 11. The installations come from a mix of downloaded images and compiled from source. Can somebody confirm that makeinfo should be there or tell me what I missed? Thanks! Erich From owner-freebsd-arm@freebsd.org Mon Oct 10 03:27:43 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCB9EC07E7B for ; Mon, 10 Oct 2016 03:27:43 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mx1.mailbox.org (mx1.mailbox.org [80.241.60.212]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D9303BB for ; Mon, 10 Oct 2016 03:27:43 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id C2A1743E5A for ; Mon, 10 Oct 2016 05:22:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mailbox.org; h= content-transfer-encoding:content-type:content-type:mime-version :references:in-reply-to:subject:subject:from:from:message-id :date:date:received; s=mail20150812; t=1476069746; bh=c++abjP8iZ f0h6FlLmeZe+eAD9h1Ic7RpD8au2aQeOg=; b=ecFKGWl+iVRSZbUCTx1gx76DlI 6ec4T5pVa9c7swow1n2ZdfPk51vHrMxBk9mALYbzTYsasOxh/TmvgnH+z5jzvqkl Q/4+uqFWfbljEoq/W9FIzoCZFi4fV0Za2sSMEvqdrOhjPpl4jyOMI6+DNLc5gf/t AcVVtiMSWxXdhOCan6PEcHaMyhZs2uqbwSZF3Na9ZC/ZgyYd/yvxU8j3EWZiieZr ZO8Xj1axoMgNDOs5fV9EBk5noMMXZeXPUCV2qx/GErg9YDUy+Aago74ZlF8idTXK vDZrZ7zGEVzxW7DL6VWM85wBs24K3cxAOsgOIqhxx2eMbb7LlSkaxHKgI8lA== X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by hefe.heinlein-support.de (hefe.heinlein-support.de [91.198.250.172]) (amavisd-new, port 10030) with ESMTP id mU2QpOdJlHBE for ; Mon, 10 Oct 2016 05:22:26 +0200 (CEST) Date: Mon, 10 Oct 2016 05:22:25 +0200 Message-ID: <86bmys99ce.wl-herbert@mailbox.org> From: "Herbert J. Skuhra" To: freebsd-arm@freebsd.org Subject: Re: Where is makeinfo gone In-Reply-To: <20161010085832.311ac350@X220.alogt.com> References: <20161010085832.311ac350@X220.alogt.com> MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 03:27:44 -0000 Erich Dollansky skrev: > = > Hi, > I was a bit surprised that makeinfo seems to be gone from my newer > Raspberries. > = > The installation dated 20.11.15 still has it in /usr/bin but the > installation dated 01.12.15 and all newer do not have it anymore. > = > I am running 10.x, 11 and 12 on different Raspberries. > = > At least > = > http://www.unix.com/man-page/freebsd/1/makeinfo/ > = > tells me that it should be part of 11. Try https://www.freebsd.org/cgi/man.cgi > The installations come from a mix of downloaded images and compiled > from source. > = > Can somebody confirm that makeinfo should be there or tell me what I > missed? From=20/usr/src/UPDATING: 20150102: The GNU texinfo and GNU info pages have been removed. To be able to view GNU info pages please install texinfo from ports. -- Herbert From owner-freebsd-arm@freebsd.org Mon Oct 10 06:49:28 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9034C0BEA1 for ; Mon, 10 Oct 2016 06:49:28 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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 890C4EEA for ; Mon, 10 Oct 2016 06:49:28 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=n5azqpgG14RcAFOc8ijzN7JNRYQ1X7H34Gh45p7ZCzg=; b=p+RyMfJZlNzKYpYya0uDTT4EE/ Zha+0C2gCVOi6G/r8UZ0FDQQEW/iQL9JbLrMvx+yRkpi295t06j5Qlet3P+Ut9GHdfA4YnxWkFh3D YFICuAyyZU3iy52oOzNcjW5+YfVMe8S4YodeDt/sxd8IEFEvj55it9TQEsj0zzJ3yrYQ=; Received: from [114.120.237.132] (port=45033 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1btUOs-003eis-2L; Mon, 10 Oct 2016 00:49:26 -0600 Date: Mon, 10 Oct 2016 14:49:15 +0800 From: Erich Dollansky To: "Herbert J. Skuhra" Cc: freebsd-arm@freebsd.org Subject: Re: Where is makeinfo gone Message-ID: <20161010144915.58566c4c@X220.alogt.com> In-Reply-To: <86bmys99ce.wl-herbert@mailbox.org> References: <20161010085832.311ac350@X220.alogt.com> <86bmys99ce.wl-herbert@mailbox.org> 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-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 06:49:28 -0000 Hi, On Mon, 10 Oct 2016 05:22:25 +0200 "Herbert J. Skuhra" wrote: > Erich Dollansky skrev: > > > > Hi, > > I was a bit surprised that makeinfo seems to be gone from my newer > > Raspberries. > > > > The installation dated 20.11.15 still has it in /usr/bin but the > > installation dated 01.12.15 and all newer do not have it anymore. > > > > I am running 10.x, 11 and 12 on different Raspberries. > > > > At least > > > > http://www.unix.com/man-page/freebsd/1/makeinfo/ > > > > tells me that it should be part of 11. > > Try https://www.freebsd.org/cgi/man.cgi > > > The installations come from a mix of downloaded images and compiled > > from source. > > > > Can somebody confirm that makeinfo should be there or tell me what I > > missed? > > From /usr/src/UPDATING: > > 20150102: > The GNU texinfo and GNU info pages have been removed. > To be able to view GNU info pages please install texinfo from > ports. > the problem is then in the ports tree: [raspberry2]...devel/autoconf (root) > make ===> autoconf-2.69_1 depends on executable: gm4 - not found ===> m4-1.4.17_1,1 depends on executable: makeinfo - not found ===> m4-1.4.17_1,1 depends on executable: makeinfo - not found *** Error code 1 Stop. make[2]: stopped in /usr/ports/devel/m4 *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/m4 *** Error code 1 Stop. make: stopped in /usr/ports/devel/autoconf The ports tree on this machine is a month old. Do you know if this got fixed recently? Erich From owner-freebsd-arm@freebsd.org Mon Oct 10 07:01:54 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8F40AF7234 for ; Mon, 10 Oct 2016 07:01:54 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 53824861 for ; Mon, 10 Oct 2016 07:01:53 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 115aeb8a; Mon, 10 Oct 2016 09:01:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=owXjEOdHpmb6zQ4mGBCsVtDrwko=; b=mXtmip56+UuX70OhHHUyw8jkkz9u v2zPJGGLMAI8NMlXgd2tW8nIuMzS+rtZP96rSwVkvXgwpDg1bb0lHynR6aAzp59s XBlOCakH59Ua1uF77oZJrriINqztGLyddmC76V0gAFhFPGeP9R/v9JelMiLuLr+i BGuIP4pVPdDToyE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=kYuF5EO7Ga+HVooZ5nLaVwJMO4If9R7CrS0netbAOTlaii5JZ2mDrdqJ rVjd7Goio7eT28XCQK5TlY+o5A2EBrhii1tfjFHznXM+diqWslmarTrAvi3sOKC6 FTZkzGNNfI8CltglyyNzVnoT89T7oDnpIDDDIP0c18g3AGLyDqs= Received: from arcadia.staff.bocal.org (163.5.251.128 [163.5.251.128]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 791cb7a7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 10 Oct 2016 09:01:44 +0200 (CEST) Date: Mon, 10 Oct 2016 09:01:43 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Da Rock , "freebsd-arm@freebsd.org" Subject: Re: u-boot efi option Message-Id: <20161010090143.ddd35f7ad7518de8e2a4110e@bidouilliste.com> In-Reply-To: References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> <20161006181000.b52d8a27d32dd25c31853948@bidouilliste.com> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) 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.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 07:01:54 -0000 I don't know much about nanobsd but I'll look at it. What I will probably do is : 1) Fix the release scripts so partitioning is done right 2) Add loader.efi into the arm images as boot/bootarm.efi 3) Make release.sh copy every dtb in the /dtb/ directory on the fat partition 4) Make two options in the u-boot ports, one for U-Boot API, one for EFI. The later being selected by default for 12 5) Once we know that everything is ok MFC every bits in 11 6) Make the EFI option default for 11 The only way it could fail is if FreeBSD 11 is used for building the 12 snapshot ... On Thu, 6 Oct 2016 11:53:45 -0600 Warner Losh wrote: > I'd really like to merge the release and nanobsd (and crochet if they > want to use it) building methods if at all possible. > > Warner > > On Thu, Oct 6, 2016 at 10:10 AM, Emmanuel Vadot wrote: > > > > Good news, everyone! > > > > I've just tested without alignment and it works. > > What doesn't work is taking the snapshot or release image and doing > > EFI with it. > > I did nothing special when creating the sd card : > > > > gpart create -s mbr da0 > > gpart add -t fat16 -s 50m -a 1m da0 > > gpart show da0 > > gpart add -t freebsd da0 > > gpart create -s bsd da0s2 > > gpart add -t freebsd-ufs da0s2 > > newfs /dev/da0s2a > > newfs_msdos -F16 /dev/da0s1 > > > > Now that I know everything works I'll look at the release scripts to > > see how to adapt them for EFI. > > > > On Mon, 3 Oct 2016 07:55:37 -0600 > > Warner Losh wrote: > > > >> Sounds like we should target 12 to be EFI only then, or at least EFI > >> preferred with our infrastructure setup to cope. > >> > >> Why is there a 512k alignment requirement? Or is that just the typical > >> 512k at the start of the disk is needed for uboot issue? > >> > >> Warner > >> > >> On Mon, Oct 3, 2016 at 4:23 AM, Emmanuel Vadot wrote: > >> > On Mon, 3 Oct 2016 19:01:30 +1000 > >> > Da Rock wrote: > >> > > >> >> A few points that I'd like clarification on: > >> >> > >> >> 1. I'm not having much success on rpi3 with any images, but I'm working > >> >> on my own 64bit anyway. I'm also trying to get a handle on what the > >> >> process of running the system on the rpi3 actually is as well. Fun... :) > >> >> So the 512kb alignment, why is that an issue? Perhaps I'm a little > >> >> foggy, but isn't that simply a case of partitioning correctly? > >> > > >> > I don't know exactly to be honest, I have to read a lot of code. > >> > > >> >> 2. I should have mentioned this initially (which is why I was checking > >> >> efi status to see if I was banging on for no reason), but I'm having > >> >> trouble (still) compiling u-boot version that has the efi capability > >> >> (2016.09) - can't find . I've tried with clang (x18 error) > >> >> and gcc to no avail. I tried leveraging ports, but it is not exactly > >> >> cooperating either (I'll have to try some more diags on that). Anyone > >> >> have a clue on how to get past this? -I doesn't work, or linking to > >> >> /usr/local/include. > >> > > >> > - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} > >> > - cd uboot-src > >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > >> > XXX_defconfig > >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > >> > > >> > I've never tried with clang. > >> > > >> >> 3. My other query was on the EFI boot process on arm. As I understood, > >> >> the u-boot is equivalent to boot0? So that means boot1 should then be in > >> >> the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or > >> >> doesn't it need to be? > >> > > >> > U-Boot can be seen as BIOS/boot0 combined. > >> > Yes boot1.efi MUST be on the fat partition and by default an EFI > >> > firmware will load /efi/boot/boot${ARCH}.efi > >> > > >> >> Apologies if I sound like a complete goose, but I'm still new to all > >> >> things arm yet - but learning fast :) > >> > > >> > Don't worry, this motivate me more to do a page on the wiki about UEFI > >> > on arm :) > >> > > >> >> On 03/10/2016 18:32, Emmanuel Vadot wrote: > >> >> > I've never had any problem with it (I know it doesn't really answer to > >> >> > your question). > >> >> > SuSe have switch to EFI (the main developer for U-Boot > >> >> > EFI is from SuSe), OpenBSD too. > >> >> > > >> >> > The main problem right now for people to test is that the partition > >> >> > on the arm images that we provide aren't aligned for it to work. > >> >> > > >> >> > I either need to fix the bug for non 512kb-aligned partition or > >> >> > aligned them in the release scripts. > >> >> > > >> >> > Also I don't know which ports-tree re@ is using for snapshots. I think > >> >> > that they use the latest quarterly for release and stable. > >> >> > So we have to be carefull when we will switch the ports to UEFI. > >> >> > > >> >> > In the meantime don't hesitate to test with my patch. > >> >> > > >> >> > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load > >> >> > it. > >> >> > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi > >> >> > > >> >> > On Sun, 2 Oct 2016 16:06:37 -0600 > >> >> > Warner Losh wrote: > >> >> > > >> >> >> How long do you think until this is mature enough we can cut over to it? > >> >> >> There's issues with ubldr on newer u-boot version on some of the platforms > >> >> >> we support. If we could cut over to this, that would be great. > >> >> >> > >> >> >> Warner > >> >> >> > >> >> >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: > >> >> >>> Hello, > >> >> >>> > >> >> >>> I've commited every needed change on our side, for uboot side you will > >> >> >>> need this patch : > >> >> >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff > >> >> >>> > >> >> >>> The only drawback is that you will need to have your partition aligned > >> >> >>> on 512kb boundaries on the mmc. > >> >> >>> > >> >> >>> I've successfully booted my beaglebone black and most of my Allwinner > >> >> >>> boards with UEFI. > >> >> >>> > >> >> >>> Some part of the uboot patch have started to be upstreamed, for > >> >> >>> the others I need to rework on some part before I upstream them. > >> >> >>> > >> >> >>> Cheers, > >> >> >>> > >> >> >>> On Sun, 2 Oct 2016 19:56:54 +1000 > >> >> >>> Da Rock wrote: > >> >> >>> > >> >> >>>> Has anyone tried this option yet? I've heard someone got it going for > >> >> >>>> slack, but I thought it sounded like it might make it easier for running > >> >> >>>> freebsd. > >> >> >>>> > >> >> >>>> I'm currently trying to build a more current u-boot to test it. > >> >> >>>> > >> >> >>>> _______________________________________________ > >> >> >>>> freebsd-arm@freebsd.org mailing list > >> >> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> >> >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >> >> >>> > >> >> >>> -- > >> >> >>> Emmanuel Vadot > >> >> >>> _______________________________________________ > >> >> >>> freebsd-arm@freebsd.org mailing list > >> >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> >> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >> >> > > >> > > >> > > >> > -- > >> > Emmanuel Vadot > > > > > > -- > > Emmanuel Vadot -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 10 09:16:52 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0D7DC0BAA6 for ; Mon, 10 Oct 2016 09:16:52 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mx1.mailbox.org (mx1.mailbox.org [80.241.60.212]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 61C9A3BA for ; Mon, 10 Oct 2016 09:16:51 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id 6199644C40; Mon, 10 Oct 2016 11:16:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mailbox.org; h= content-type:content-type:mime-version:references:in-reply-to :subject:subject:from:from:message-id:date:date:received; s= mail20150812; t=1476090998; bh=ZdhZVTLBUmQ609orLCBN/KWzBJtZ06tuX a8DJuqbujs=; b=PAzR9tf5ew1Y+OupgC6nSmJkpYQS5IFR+oQmfSaxxC0zDkK5I Y4wvqpy7Rcq5c71Aql8wpTrpSTBekyaqgrmcB7qVNuL+Kx54Uqqx0sL/RILSx+Fx aeFsIP54wvsFtr/JAy15Iydb4VKi9kavKalMeckSLFNWe15HZZa367EINFYnd5yI 8czLB0JhPyyjpwHtxSG4qqq150iUyI3p7mTPzAlVbaoz0e9TeTgMg/2ToRZRxBqG +Q5v76wl3AKDp1lbQlZBVFirp7A/x4FLNEO+Cd9VyqZ950zMVhZfyXIs2hJlfn+S 7qjfSUBn7V1lwfY+5FSjRNogyttR61jj952HA== X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by gerste.heinlein-support.de (gerste.heinlein-support.de [91.198.250.173]) (amavisd-new, port 10030) with ESMTP id WfAbSteVmbNj; Mon, 10 Oct 2016 11:16:38 +0200 (CEST) Date: Mon, 10 Oct 2016 11:16:37 +0200 Message-ID: <86a8ecd0ne.wl-herbert@mailbox.org> From: "Herbert J. Skuhra" To: Erich Dollansky Cc: freebsd-arm@freebsd.org Subject: Re: Where is makeinfo gone In-Reply-To: <20161010144915.58566c4c@X220.alogt.com> References: <20161010085832.311ac350@X220.alogt.com> <86bmys99ce.wl-herbert@mailbox.org> <20161010144915.58566c4c@X220.alogt.com> MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 09:16:52 -0000 Erich Dollansky skrev: > > Hi, > On Mon, 10 Oct 2016 05:22:25 +0200 > "Herbert J. Skuhra" wrote: > >> Erich Dollansky skrev: >> > >> > Hi, >> > I was a bit surprised that makeinfo seems to be gone from my newer >> > Raspberries. >> > >> > The installation dated 20.11.15 still has it in /usr/bin but the >> > installation dated 01.12.15 and all newer do not have it anymore. >> > >> > I am running 10.x, 11 and 12 on different Raspberries. >> > >> > At least >> > >> > http://www.unix.com/man-page/freebsd/1/makeinfo/ >> > >> > tells me that it should be part of 11. >> >> Try https://www.freebsd.org/cgi/man.cgi >> >> > The installations come from a mix of downloaded images and compiled >> > from source. >> > >> > Can somebody confirm that makeinfo should be there or tell me what I >> > missed? >> >> From /usr/src/UPDATING: >> >> 20150102: >> The GNU texinfo and GNU info pages have been removed. >> To be able to view GNU info pages please install texinfo from >> ports. >> > the problem is then in the ports tree: > > [raspberry2]...devel/autoconf (root) > make > ===> autoconf-2.69_1 depends on executable: gm4 - not found > ===> m4-1.4.17_1,1 depends on executable: makeinfo - not found > ===> m4-1.4.17_1,1 depends on executable: makeinfo - not found > *** Error code 1 > > Stop. > make[2]: stopped in /usr/ports/devel/m4 > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/devel/m4 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/autoconf > > The ports tree on this machine is a month old. Do you know if this got > fixed recently? First run make clean in /usr/ports/print/texinfo and then try to build devel/autoconf. -- Herbert From owner-freebsd-arm@freebsd.org Mon Oct 10 09:57:17 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7729DC064C8 for ; Mon, 10 Oct 2016 09:57:17 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mx2.mailbox.org (mx2.mailbox.org [80.241.60.215]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 38934977 for ; Mon, 10 Oct 2016 09:57:16 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id DE76943116; Mon, 10 Oct 2016 11:57:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mailbox.org; h= content-type:content-type:mime-version:references:in-reply-to :subject:subject:from:from:message-id:date:date:received; s= mail20150812; t=1476093417; bh=RQ6+d0xq0MLKB0O5XnGWn3kfDqDXYiIKD AcIrmfidD8=; b=A/2aLPHq5aQPYJy2LOJYeZhd61oAK9lSND8gT0p/2E7c+pfXn SV4UuJqoGMbtho92kc7clqkfIYDgPSOLLNR8lvQ/RXY0DDEoKskEQD/g53DN1tbp cAak5Hctgbe5PARnctcIYtChmsjolO8UQfogIwFwZWPfieKBgzMZe5Zk0XXHMzDK b0+q+xL0/Pctv18gZ+kWKCs+k18zS0fVW9yNWb5eAr62qTnrwYT96jxwbkgfpuwb fj6Wu5hEArP3MvhvR6iqdqm9YevNybwvY18SdmljulGZK9lsKPv6gCstiREQN5/P k0fxFRjuw9vr9SK7T3kHv611zSf7wBBISG2Vw== X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by gerste.heinlein-support.de (gerste.heinlein-support.de [91.198.250.173]) (amavisd-new, port 10030) with ESMTP id nRIj0Clg-tYd; Mon, 10 Oct 2016 11:56:57 +0200 (CEST) Date: Mon, 10 Oct 2016 11:56:55 +0200 Message-ID: <868ttwcys8.wl-herbert@mailbox.org> From: "Herbert J. Skuhra" To: Erich Dollansky Cc: freebsd-arm@freebsd.org Subject: Re: Where is makeinfo gone In-Reply-To: <86a8ecd0ne.wl-herbert@mailbox.org> References: <20161010085832.311ac350@X220.alogt.com> <86bmys99ce.wl-herbert@mailbox.org> <20161010144915.58566c4c@X220.alogt.com> <86a8ecd0ne.wl-herbert@mailbox.org> MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 09:57:17 -0000 Herbert J Skuhra skrev: > > Erich Dollansky skrev: >> >> Hi, >> On Mon, 10 Oct 2016 05:22:25 +0200 >> "Herbert J. Skuhra" wrote: >> >>> Erich Dollansky skrev: >>> > >>> > Hi, >>> > I was a bit surprised that makeinfo seems to be gone from my newer >>> > Raspberries. >>> > >>> > The installation dated 20.11.15 still has it in /usr/bin but the >>> > installation dated 01.12.15 and all newer do not have it anymore. >>> > >>> > I am running 10.x, 11 and 12 on different Raspberries. >>> > >>> > At least >>> > >>> > http://www.unix.com/man-page/freebsd/1/makeinfo/ >>> > >>> > tells me that it should be part of 11. >>> >>> Try https://www.freebsd.org/cgi/man.cgi >>> >>> > The installations come from a mix of downloaded images and compiled >>> > from source. >>> > >>> > Can somebody confirm that makeinfo should be there or tell me what I >>> > missed? >>> >>> From /usr/src/UPDATING: >>> >>> 20150102: >>> The GNU texinfo and GNU info pages have been removed. >>> To be able to view GNU info pages please install texinfo from >>> ports. >>> >> the problem is then in the ports tree: >> >> [raspberry2]...devel/autoconf (root) > make >> ===> autoconf-2.69_1 depends on executable: gm4 - not found >> ===> m4-1.4.17_1,1 depends on executable: makeinfo - not found >> ===> m4-1.4.17_1,1 depends on executable: makeinfo - not found >> *** Error code 1 >> >> Stop. >> make[2]: stopped in /usr/ports/devel/m4 >> *** Error code 1 >> >> Stop. >> make[1]: stopped in /usr/ports/devel/m4 >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/devel/autoconf >> >> The ports tree on this machine is a month old. Do you know if this got >> fixed recently? > > First run make clean in /usr/ports/print/texinfo and then try to build > devel/autoconf. Or run 'make clean-depends' in devel/autoconf first. -- Herbert From owner-freebsd-arm@freebsd.org Mon Oct 10 14:33:38 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85DAAC0B4BC for ; Mon, 10 Oct 2016 14:33:38 +0000 (UTC) (envelope-from freebsd-arm@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (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 AA7FF812 for ; Mon, 10 Oct 2016 14:33:37 +0000 (UTC) (envelope-from freebsd-arm@herveybayaustralia.com.au) Received: from [192.168.0.177] (laptop3.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 5A7C962053; Tue, 11 Oct 2016 00:33:23 +1000 (EST) Subject: Re: u-boot efi option To: Warner Losh , Emmanuel Vadot References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> <20161006181000.b52d8a27d32dd25c31853948@bidouilliste.com> Cc: "freebsd-arm@freebsd.org" From: Da Rock Message-ID: <49e08194-d029-1156-dc5c-dee1471f9463@herveybayaustralia.com.au> Date: Tue, 11 Oct 2016 00:33:21 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 14:33:38 -0000 Ok, so I'm so close to getting this I can smell it! However, it seems to hang up on the boot1.efi - maybe can't find the loader/partition? No messages at all. So I've tried copying loader.efi (works for cd's apparently, so hey why not give it a shot?) and it comes up with "FreeBSD..." (yay!) then application fails with "r=-22"; no beastie or boot query. Given that loader expects itself to be in the partition booted thats fair enough - but that narrows it squarely down to boot1. I've gone back over my knowledge (using google and handbook) to check if I missed something, but I don't think so. My partitions are mbr based so all good for uboot to _not_ hang up on. The only thing I can think of is using a GPT hybrid but I'm not 100% sure of the necessity at this stage given the info available. GPT itself fails (tried) as the uboot/rpi system can't read it. So damn frustrating - I know this could work... On 07/10/2016 03:53, Warner Losh wrote: > I'd really like to merge the release and nanobsd (and crochet if they > want to use it) building methods if at all possible. > > Warner > > On Thu, Oct 6, 2016 at 10:10 AM, Emmanuel Vadot wrote: >> Good news, everyone! >> >> I've just tested without alignment and it works. >> What doesn't work is taking the snapshot or release image and doing >> EFI with it. >> I did nothing special when creating the sd card : >> >> gpart create -s mbr da0 >> gpart add -t fat16 -s 50m -a 1m da0 >> gpart show da0 >> gpart add -t freebsd da0 >> gpart create -s bsd da0s2 >> gpart add -t freebsd-ufs da0s2 >> newfs /dev/da0s2a >> newfs_msdos -F16 /dev/da0s1 >> >> Now that I know everything works I'll look at the release scripts to >> see how to adapt them for EFI. >> >> On Mon, 3 Oct 2016 07:55:37 -0600 >> Warner Losh wrote: >> >>> Sounds like we should target 12 to be EFI only then, or at least EFI >>> preferred with our infrastructure setup to cope. >>> >>> Why is there a 512k alignment requirement? Or is that just the typical >>> 512k at the start of the disk is needed for uboot issue? >>> >>> Warner >>> >>> On Mon, Oct 3, 2016 at 4:23 AM, Emmanuel Vadot wrote: >>>> On Mon, 3 Oct 2016 19:01:30 +1000 >>>> Da Rock wrote: >>>> >>>>> A few points that I'd like clarification on: >>>>> >>>>> 1. I'm not having much success on rpi3 with any images, but I'm working >>>>> on my own 64bit anyway. I'm also trying to get a handle on what the >>>>> process of running the system on the rpi3 actually is as well. Fun... :) >>>>> So the 512kb alignment, why is that an issue? Perhaps I'm a little >>>>> foggy, but isn't that simply a case of partitioning correctly? >>>> I don't know exactly to be honest, I have to read a lot of code. >>>> >>>>> 2. I should have mentioned this initially (which is why I was checking >>>>> efi status to see if I was banging on for no reason), but I'm having >>>>> trouble (still) compiling u-boot version that has the efi capability >>>>> (2016.09) - can't find . I've tried with clang (x18 error) >>>>> and gcc to no avail. I tried leveraging ports, but it is not exactly >>>>> cooperating either (I'll have to try some more diags on that). Anyone >>>>> have a clue on how to get past this? -I doesn't work, or linking to >>>>> /usr/local/include. >>>> - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} >>>> - cd uboot-src >>>> - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- >>>> XXX_defconfig >>>> - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- >>>> >>>> I've never tried with clang. >>>> >>>>> 3. My other query was on the EFI boot process on arm. As I understood, >>>>> the u-boot is equivalent to boot0? So that means boot1 should then be in >>>>> the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or >>>>> doesn't it need to be? >>>> U-Boot can be seen as BIOS/boot0 combined. >>>> Yes boot1.efi MUST be on the fat partition and by default an EFI >>>> firmware will load /efi/boot/boot${ARCH}.efi >>>> >>>>> Apologies if I sound like a complete goose, but I'm still new to all >>>>> things arm yet - but learning fast :) >>>> Don't worry, this motivate me more to do a page on the wiki about UEFI >>>> on arm :) >>>> >>>>> On 03/10/2016 18:32, Emmanuel Vadot wrote: >>>>>> I've never had any problem with it (I know it doesn't really answer to >>>>>> your question). >>>>>> SuSe have switch to EFI (the main developer for U-Boot >>>>>> EFI is from SuSe), OpenBSD too. >>>>>> >>>>>> The main problem right now for people to test is that the partition >>>>>> on the arm images that we provide aren't aligned for it to work. >>>>>> >>>>>> I either need to fix the bug for non 512kb-aligned partition or >>>>>> aligned them in the release scripts. >>>>>> >>>>>> Also I don't know which ports-tree re@ is using for snapshots. I think >>>>>> that they use the latest quarterly for release and stable. >>>>>> So we have to be carefull when we will switch the ports to UEFI. >>>>>> >>>>>> In the meantime don't hesitate to test with my patch. >>>>>> >>>>>> If you have the correct dtb in /dtb/ on the msdos part U-Boot will load >>>>>> it. >>>>>> For booting automatically just put boot1.efi as /efi/boot/bootarm.efi >>>>>> >>>>>> On Sun, 2 Oct 2016 16:06:37 -0600 >>>>>> Warner Losh wrote: >>>>>> >>>>>>> How long do you think until this is mature enough we can cut over to it? >>>>>>> There's issues with ubldr on newer u-boot version on some of the platforms >>>>>>> we support. If we could cut over to this, that would be great. >>>>>>> >>>>>>> Warner >>>>>>> >>>>>>> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> I've commited every needed change on our side, for uboot side you will >>>>>>>> need this patch : >>>>>>>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff >>>>>>>> >>>>>>>> The only drawback is that you will need to have your partition aligned >>>>>>>> on 512kb boundaries on the mmc. >>>>>>>> >>>>>>>> I've successfully booted my beaglebone black and most of my Allwinner >>>>>>>> boards with UEFI. >>>>>>>> >>>>>>>> Some part of the uboot patch have started to be upstreamed, for >>>>>>>> the others I need to rework on some part before I upstream them. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> On Sun, 2 Oct 2016 19:56:54 +1000 >>>>>>>> Da Rock wrote: >>>>>>>> >>>>>>>>> Has anyone tried this option yet? I've heard someone got it going for >>>>>>>>> slack, but I thought it sounded like it might make it easier for running >>>>>>>>> freebsd. >>>>>>>>> >>>>>>>>> I'm currently trying to build a more current u-boot to test it. >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> freebsd-arm@freebsd.org mailing list >>>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>>>>>>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>>>>>>> -- >>>>>>>> Emmanuel Vadot >>>>>>>> _______________________________________________ >>>>>>>> freebsd-arm@freebsd.org mailing list >>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>>>>>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>>> >>>> -- >>>> Emmanuel Vadot >> >> -- >> Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 10 15:07:37 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D676CC075BB for ; Mon, 10 Oct 2016 15:07:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A5383A69 for ; Mon, 10 Oct 2016 15:07:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x244.google.com with SMTP id m138so1339541itm.0 for ; Mon, 10 Oct 2016 08:07:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=W8ETm/b2U4yEouqzznhHoZgGwrjkHjtI9sgLgkroazw=; b=awboXf+d2Ud1blxDe0orZP73oXCXJ7GiorkP2KQ0VhGHjFgn9gydviHRzMTQhMMmhW TktYFxsYh6yLQX7YlsBq5XzV46q7mLKi4a8NRjB9Q+8S6ZoMCxE+bHc7O6Bz1zcC2bh1 ePzV0l6UxjgPsTdY4DEgCVeaKGTAv6CNB5vAD44PPR3/38/DLXBnmU9zSWTWRCse/0YC nbEIk0wu3nZF506tMYuOrj4nh2GoF1xMzm0+V4nGwiN9jR4Gl/ZZyxbuEpJMCXpt8LNn nGn6kFPEdYhvSqkLj1vYKJNIkXp7Fd5gSTfq80/4Ccdv+TlqtyLlpmybTdYryDczwCCM eNhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=W8ETm/b2U4yEouqzznhHoZgGwrjkHjtI9sgLgkroazw=; b=RW+xgR7rm+JoRq6dUiret01F8/27SRImGlsJ5+4Av1XG/Ct3EgTwqaF6U6Ag1Fwkld BayRnuozz1KH72h2YMc367Q9nXces/SMcAsWhiqtnTl4lrvKGsgVjQitVWFODxXidFTx OmyjgEEbehTiJnRLeBi6l1ifD1yXvBq4RjfpuwtEzHJFNmrLKP+Zjf8Ai0cqJP0EHMkN 6bK3aLR59Ic+D94nDzgc8VcEG8wq8cAlUiNHD4SgIw9pn1z82qLAnmcdi5Kyf+6oR0fB 8C/xx1HU0ZX8S7KvnlwNu2qjoMRPdFralmUqazmm7/bQAiOcYq/nQAj3dQJePuKoCr6v anvg== X-Gm-Message-State: AA6/9Rm5E+BFZmBCveSg3h4vDYqg0V5oLbtdIRyR1flH1499LobPT47xFF9X1yYT+2f4qcLj1ycgY08QB3gWcA== X-Received: by 10.36.43.82 with SMTP id h79mr12278457ita.60.1476112056856; Mon, 10 Oct 2016 08:07:36 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.77.85 with HTTP; Mon, 10 Oct 2016 08:07:36 -0700 (PDT) X-Originating-IP: [50.205.115.50] In-Reply-To: <20161010090143.ddd35f7ad7518de8e2a4110e@bidouilliste.com> References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> <20161006181000.b52d8a27d32dd25c31853948@bidouilliste.com> <20161010090143.ddd35f7ad7518de8e2a4110e@bidouilliste.com> From: Warner Losh Date: Mon, 10 Oct 2016 09:07:36 -0600 X-Google-Sender-Auth: jZeiDSiPcqx1WdvxuMXNu3T9q1s Message-ID: Subject: Re: u-boot efi option To: Emmanuel Vadot Cc: Da Rock , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 15:07:37 -0000 On Mon, Oct 10, 2016 at 1:01 AM, Emmanuel Vadot wrote: > > I don't know much about nanobsd but I'll look at it. > What I will probably do is : > > 1) Fix the release scripts so partitioning is done right Already done. See the embedded stuff I added. > 2) Add loader.efi into the arm images as boot/bootarm.efi Already done for x86, should be trivial to adapt. > 3) Make release.sh copy every dtb in the /dtb/ directory on the fat > partition We already install everything into /boot/dtb. But this would be needed if we don't use the UFS EFI driver inside of uboot to read them off /boot/dtb. > 4) Make two options in the u-boot ports, one for U-Boot API, one for > EFI. The later being selected by default for 12 Good luck with that. The u-boot ports are an absolute mess right now. I have a cleanup for that, but my experience so far tells me that you'll need the absolute latest u-boot to successfully boot with EFI. But the latest u-boot doesn't work on all the boards we support. > 5) Once we know that everything is ok MFC every bits in 11 > 6) Make the EFI option default for 11 Unlikely to happen, since this violates the ABI stability rules for stable branches. > The only way it could fail is if FreeBSD 11 is used for building the > 12 snapshot ... Which it often is... Warner > On Thu, 6 Oct 2016 11:53:45 -0600 > Warner Losh wrote: > >> I'd really like to merge the release and nanobsd (and crochet if they >> want to use it) building methods if at all possible. >> >> Warner >> >> On Thu, Oct 6, 2016 at 10:10 AM, Emmanuel Vadot wrote: >> > >> > Good news, everyone! >> > >> > I've just tested without alignment and it works. >> > What doesn't work is taking the snapshot or release image and doing >> > EFI with it. >> > I did nothing special when creating the sd card : >> > >> > gpart create -s mbr da0 >> > gpart add -t fat16 -s 50m -a 1m da0 >> > gpart show da0 >> > gpart add -t freebsd da0 >> > gpart create -s bsd da0s2 >> > gpart add -t freebsd-ufs da0s2 >> > newfs /dev/da0s2a >> > newfs_msdos -F16 /dev/da0s1 >> > >> > Now that I know everything works I'll look at the release scripts to >> > see how to adapt them for EFI. >> > >> > On Mon, 3 Oct 2016 07:55:37 -0600 >> > Warner Losh wrote: >> > >> >> Sounds like we should target 12 to be EFI only then, or at least EFI >> >> preferred with our infrastructure setup to cope. >> >> >> >> Why is there a 512k alignment requirement? Or is that just the typical >> >> 512k at the start of the disk is needed for uboot issue? >> >> >> >> Warner >> >> >> >> On Mon, Oct 3, 2016 at 4:23 AM, Emmanuel Vadot wrote: >> >> > On Mon, 3 Oct 2016 19:01:30 +1000 >> >> > Da Rock wrote: >> >> > >> >> >> A few points that I'd like clarification on: >> >> >> >> >> >> 1. I'm not having much success on rpi3 with any images, but I'm working >> >> >> on my own 64bit anyway. I'm also trying to get a handle on what the >> >> >> process of running the system on the rpi3 actually is as well. Fun... :) >> >> >> So the 512kb alignment, why is that an issue? Perhaps I'm a little >> >> >> foggy, but isn't that simply a case of partitioning correctly? >> >> > >> >> > I don't know exactly to be honest, I have to read a lot of code. >> >> > >> >> >> 2. I should have mentioned this initially (which is why I was checking >> >> >> efi status to see if I was banging on for no reason), but I'm having >> >> >> trouble (still) compiling u-boot version that has the efi capability >> >> >> (2016.09) - can't find . I've tried with clang (x18 error) >> >> >> and gcc to no avail. I tried leveraging ports, but it is not exactly >> >> >> cooperating either (I'll have to try some more diags on that). Anyone >> >> >> have a clue on how to get past this? -I doesn't work, or linking to >> >> >> /usr/local/include. >> >> > >> >> > - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} >> >> > - cd uboot-src >> >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- >> >> > XXX_defconfig >> >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- >> >> > >> >> > I've never tried with clang. >> >> > >> >> >> 3. My other query was on the EFI boot process on arm. As I understood, >> >> >> the u-boot is equivalent to boot0? So that means boot1 should then be in >> >> >> the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or >> >> >> doesn't it need to be? >> >> > >> >> > U-Boot can be seen as BIOS/boot0 combined. >> >> > Yes boot1.efi MUST be on the fat partition and by default an EFI >> >> > firmware will load /efi/boot/boot${ARCH}.efi >> >> > >> >> >> Apologies if I sound like a complete goose, but I'm still new to all >> >> >> things arm yet - but learning fast :) >> >> > >> >> > Don't worry, this motivate me more to do a page on the wiki about UEFI >> >> > on arm :) >> >> > >> >> >> On 03/10/2016 18:32, Emmanuel Vadot wrote: >> >> >> > I've never had any problem with it (I know it doesn't really answer to >> >> >> > your question). >> >> >> > SuSe have switch to EFI (the main developer for U-Boot >> >> >> > EFI is from SuSe), OpenBSD too. >> >> >> > >> >> >> > The main problem right now for people to test is that the partition >> >> >> > on the arm images that we provide aren't aligned for it to work. >> >> >> > >> >> >> > I either need to fix the bug for non 512kb-aligned partition or >> >> >> > aligned them in the release scripts. >> >> >> > >> >> >> > Also I don't know which ports-tree re@ is using for snapshots. I think >> >> >> > that they use the latest quarterly for release and stable. >> >> >> > So we have to be carefull when we will switch the ports to UEFI. >> >> >> > >> >> >> > In the meantime don't hesitate to test with my patch. >> >> >> > >> >> >> > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load >> >> >> > it. >> >> >> > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi >> >> >> > >> >> >> > On Sun, 2 Oct 2016 16:06:37 -0600 >> >> >> > Warner Losh wrote: >> >> >> > >> >> >> >> How long do you think until this is mature enough we can cut over to it? >> >> >> >> There's issues with ubldr on newer u-boot version on some of the platforms >> >> >> >> we support. If we could cut over to this, that would be great. >> >> >> >> >> >> >> >> Warner >> >> >> >> >> >> >> >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: >> >> >> >>> Hello, >> >> >> >>> >> >> >> >>> I've commited every needed change on our side, for uboot side you will >> >> >> >>> need this patch : >> >> >> >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff >> >> >> >>> >> >> >> >>> The only drawback is that you will need to have your partition aligned >> >> >> >>> on 512kb boundaries on the mmc. >> >> >> >>> >> >> >> >>> I've successfully booted my beaglebone black and most of my Allwinner >> >> >> >>> boards with UEFI. >> >> >> >>> >> >> >> >>> Some part of the uboot patch have started to be upstreamed, for >> >> >> >>> the others I need to rework on some part before I upstream them. >> >> >> >>> >> >> >> >>> Cheers, >> >> >> >>> >> >> >> >>> On Sun, 2 Oct 2016 19:56:54 +1000 >> >> >> >>> Da Rock wrote: >> >> >> >>> >> >> >> >>>> Has anyone tried this option yet? I've heard someone got it going for >> >> >> >>>> slack, but I thought it sounded like it might make it easier for running >> >> >> >>>> freebsd. >> >> >> >>>> >> >> >> >>>> I'm currently trying to build a more current u-boot to test it. >> >> >> >>>> >> >> >> >>>> _______________________________________________ >> >> >> >>>> freebsd-arm@freebsd.org mailing list >> >> >> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> >> >> >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >> >> >>> >> >> >> >>> -- >> >> >> >>> Emmanuel Vadot >> >> >> >>> _______________________________________________ >> >> >> >>> freebsd-arm@freebsd.org mailing list >> >> >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> >> >> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Emmanuel Vadot >> > >> > >> > -- >> > Emmanuel Vadot > > > -- > Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 10 22:30:32 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FABCC0C34D for ; Mon, 10 Oct 2016 22:30:32 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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 6F497824 for ; Mon, 10 Oct 2016 22:30:32 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=zuB+YNfvAhs19yRioL8grumN0wdPE/tsZ3kh/q/RahI=; b=J1cjpHqnwb/TwxEICAOqJUpNqo R2MxaE93FvrVE8CM9/J5eCoXQej4AHzDgPx2XlW7h/xu0qEkpZW8GNjwruAerVplWJ1M9swMIKHHR oRigyOIiicu55pV03TZK5y4Z1dNAMEnexVkr+kAYhO5sMuqq0TaSCYsxn8nT/+g33ekQ=; Received: from [114.120.239.25] (port=21947 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1btj5a-001Q0N-45; Mon, 10 Oct 2016 16:30:30 -0600 Date: Tue, 11 Oct 2016 06:30:25 +0800 From: Erich Dollansky To: "Herbert J. Skuhra" Cc: freebsd-arm@freebsd.org Subject: Re: Where is makeinfo gone Message-ID: <20161011063025.1d817ede@X220.alogt.com> In-Reply-To: <86a8ecd0ne.wl-herbert@mailbox.org> References: <20161010085832.311ac350@X220.alogt.com> <86bmys99ce.wl-herbert@mailbox.org> <20161010144915.58566c4c@X220.alogt.com> <86a8ecd0ne.wl-herbert@mailbox.org> 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-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 22:30:32 -0000 Hi, On Mon, 10 Oct 2016 11:16:37 +0200 "Herbert J. Skuhra" wrote: > Erich Dollansky skrev: > > > > > > The ports tree on this machine is a month old. Do you know if this > > got fixed recently? > > First run make clean in /usr/ports/print/texinfo and then try to build > devel/autoconf. > how could I forget this? Yes, this helped. It just got stuck a bit later. I will update my ports tree and restart then. Thanks for your help. Erich From owner-freebsd-arm@freebsd.org Tue Oct 11 09:10:18 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15362C0CE67 for ; Tue, 11 Oct 2016 09:10:18 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 70F82C63 for ; Tue, 11 Oct 2016 09:10:16 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 315ca6fb; Tue, 11 Oct 2016 11:10:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=LUtrOhFegp+ki2nwmrSPJq9rwPU=; b=c5wgf60pe+BiXGYurj4f5iK/MRdc 8BJCTxtCsxDJCyt9V13Qc8X7B3Bf2sQKTsr6pxlBo76qLGM/i4C55UTM0UWUSqo2 JEQpfPZl5YdRrysapFN7rcCmBiIwz1loMJcSVf/swSgvhwLLAK4J/RqMXq+WphKv ZEOpJkmVsR9tDlU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=jttI2s1QV0ZyalqRqw/pfP8DZYXNGFVeD2A8TxvtLJRTnJ7GiyqVzfBJ Q2/aTco8UtX9q3ZVF6iNG+on5bHqjBSMDRUPdT5LU2/+ahk65iIf40dKSs42KHtA zpeVy9uqEsfSPVYxeGMdVBGa+xP4Lptqb1aupkH6Osm3Ce4RUbg= Received: from arcadia.staff.bocal.org (163.5.250.3 [163.5.250.3]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 3ef71e28 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 11 Oct 2016 11:10:09 +0200 (CEST) Date: Tue, 11 Oct 2016 11:10:08 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Da Rock , "freebsd-arm@freebsd.org" Subject: Re: u-boot efi option Message-Id: <20161011111008.ffac2428aeee6cbd8111861e@bidouilliste.com> In-Reply-To: References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> <20161006181000.b52d8a27d32dd25c31853948@bidouilliste.com> <20161010090143.ddd35f7ad7518de8e2a4110e@bidouilliste.com> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) 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.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2016 09:10:18 -0000 On Mon, 10 Oct 2016 09:07:36 -0600 Warner Losh wrote: > On Mon, Oct 10, 2016 at 1:01 AM, Emmanuel Vadot wrote: > > > > I don't know much about nanobsd but I'll look at it. > > What I will probably do is : > > > > 1) Fix the release scripts so partitioning is done right > > Already done. See the embedded stuff I added. Yeah, and I might know what the problem is/was for efi to work. On the release images the ufs partition is added on the 'freebsd' slice with 64k alignment so the UFS magic is not somewhere boot1.efi looks. My knowledge on this subject is not very good but should we align the slice and not the ufs partition ? > > 2) Add loader.efi into the arm images as boot/bootarm.efi > > Already done for x86, should be trivial to adapt. > > > 3) Make release.sh copy every dtb in the /dtb/ directory on the fat > > partition > > We already install everything into /boot/dtb. But this would be needed > if we don't use the UFS EFI driver inside of uboot to read them off > /boot/dtb. Yes, having uboot load the dtb for us is easier, especially if we want at one point support for simplefb as it patches the dtb for the memory used by the framebuffer. > > 4) Make two options in the u-boot ports, one for U-Boot API, one for > > EFI. The later being selected by default for 12 > > Good luck with that. The u-boot ports are an absolute mess right now. > I have a cleanup for that, but my experience so far tells me that > you'll need the absolute latest u-boot to successfully boot with EFI. > But the latest u-boot doesn't work on all the boards we support. I'll start with Allwinner as this is the easiest. Do you have a list of board which doesn't work with latest upstream uboot ? > > 5) Once we know that everything is ok MFC every bits in 11 > > 6) Make the EFI option default for 11 > > Unlikely to happen, since this violates the ABI stability rules for > stable branches. So we're stuck with U-Boot api for 11 ? That sucks. > > The only way it could fail is if FreeBSD 11 is used for building the > > 12 snapshot ... > > Which it often is... Well ... crap ... > Warner > > > On Thu, 6 Oct 2016 11:53:45 -0600 > > Warner Losh wrote: > > > >> I'd really like to merge the release and nanobsd (and crochet if they > >> want to use it) building methods if at all possible. > >> > >> Warner > >> > >> On Thu, Oct 6, 2016 at 10:10 AM, Emmanuel Vadot wrote: > >> > > >> > Good news, everyone! > >> > > >> > I've just tested without alignment and it works. > >> > What doesn't work is taking the snapshot or release image and doing > >> > EFI with it. > >> > I did nothing special when creating the sd card : > >> > > >> > gpart create -s mbr da0 > >> > gpart add -t fat16 -s 50m -a 1m da0 > >> > gpart show da0 > >> > gpart add -t freebsd da0 > >> > gpart create -s bsd da0s2 > >> > gpart add -t freebsd-ufs da0s2 > >> > newfs /dev/da0s2a > >> > newfs_msdos -F16 /dev/da0s1 > >> > > >> > Now that I know everything works I'll look at the release scripts to > >> > see how to adapt them for EFI. > >> > > >> > On Mon, 3 Oct 2016 07:55:37 -0600 > >> > Warner Losh wrote: > >> > > >> >> Sounds like we should target 12 to be EFI only then, or at least EFI > >> >> preferred with our infrastructure setup to cope. > >> >> > >> >> Why is there a 512k alignment requirement? Or is that just the typical > >> >> 512k at the start of the disk is needed for uboot issue? > >> >> > >> >> Warner > >> >> > >> >> On Mon, Oct 3, 2016 at 4:23 AM, Emmanuel Vadot wrote: > >> >> > On Mon, 3 Oct 2016 19:01:30 +1000 > >> >> > Da Rock wrote: > >> >> > > >> >> >> A few points that I'd like clarification on: > >> >> >> > >> >> >> 1. I'm not having much success on rpi3 with any images, but I'm working > >> >> >> on my own 64bit anyway. I'm also trying to get a handle on what the > >> >> >> process of running the system on the rpi3 actually is as well. Fun... :) > >> >> >> So the 512kb alignment, why is that an issue? Perhaps I'm a little > >> >> >> foggy, but isn't that simply a case of partitioning correctly? > >> >> > > >> >> > I don't know exactly to be honest, I have to read a lot of code. > >> >> > > >> >> >> 2. I should have mentioned this initially (which is why I was checking > >> >> >> efi status to see if I was banging on for no reason), but I'm having > >> >> >> trouble (still) compiling u-boot version that has the efi capability > >> >> >> (2016.09) - can't find . I've tried with clang (x18 error) > >> >> >> and gcc to no avail. I tried leveraging ports, but it is not exactly > >> >> >> cooperating either (I'll have to try some more diags on that). Anyone > >> >> >> have a clue on how to get past this? -I doesn't work, or linking to > >> >> >> /usr/local/include. > >> >> > > >> >> > - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} > >> >> > - cd uboot-src > >> >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > >> >> > XXX_defconfig > >> >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > >> >> > > >> >> > I've never tried with clang. > >> >> > > >> >> >> 3. My other query was on the EFI boot process on arm. As I understood, > >> >> >> the u-boot is equivalent to boot0? So that means boot1 should then be in > >> >> >> the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or > >> >> >> doesn't it need to be? > >> >> > > >> >> > U-Boot can be seen as BIOS/boot0 combined. > >> >> > Yes boot1.efi MUST be on the fat partition and by default an EFI > >> >> > firmware will load /efi/boot/boot${ARCH}.efi > >> >> > > >> >> >> Apologies if I sound like a complete goose, but I'm still new to all > >> >> >> things arm yet - but learning fast :) > >> >> > > >> >> > Don't worry, this motivate me more to do a page on the wiki about UEFI > >> >> > on arm :) > >> >> > > >> >> >> On 03/10/2016 18:32, Emmanuel Vadot wrote: > >> >> >> > I've never had any problem with it (I know it doesn't really answer to > >> >> >> > your question). > >> >> >> > SuSe have switch to EFI (the main developer for U-Boot > >> >> >> > EFI is from SuSe), OpenBSD too. > >> >> >> > > >> >> >> > The main problem right now for people to test is that the partition > >> >> >> > on the arm images that we provide aren't aligned for it to work. > >> >> >> > > >> >> >> > I either need to fix the bug for non 512kb-aligned partition or > >> >> >> > aligned them in the release scripts. > >> >> >> > > >> >> >> > Also I don't know which ports-tree re@ is using for snapshots. I think > >> >> >> > that they use the latest quarterly for release and stable. > >> >> >> > So we have to be carefull when we will switch the ports to UEFI. > >> >> >> > > >> >> >> > In the meantime don't hesitate to test with my patch. > >> >> >> > > >> >> >> > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load > >> >> >> > it. > >> >> >> > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi > >> >> >> > > >> >> >> > On Sun, 2 Oct 2016 16:06:37 -0600 > >> >> >> > Warner Losh wrote: > >> >> >> > > >> >> >> >> How long do you think until this is mature enough we can cut over to it? > >> >> >> >> There's issues with ubldr on newer u-boot version on some of the platforms > >> >> >> >> we support. If we could cut over to this, that would be great. > >> >> >> >> > >> >> >> >> Warner > >> >> >> >> > >> >> >> >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: > >> >> >> >>> Hello, > >> >> >> >>> > >> >> >> >>> I've commited every needed change on our side, for uboot side you will > >> >> >> >>> need this patch : > >> >> >> >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff > >> >> >> >>> > >> >> >> >>> The only drawback is that you will need to have your partition aligned > >> >> >> >>> on 512kb boundaries on the mmc. > >> >> >> >>> > >> >> >> >>> I've successfully booted my beaglebone black and most of my Allwinner > >> >> >> >>> boards with UEFI. > >> >> >> >>> > >> >> >> >>> Some part of the uboot patch have started to be upstreamed, for > >> >> >> >>> the others I need to rework on some part before I upstream them. > >> >> >> >>> > >> >> >> >>> Cheers, > >> >> >> >>> > >> >> >> >>> On Sun, 2 Oct 2016 19:56:54 +1000 > >> >> >> >>> Da Rock wrote: > >> >> >> >>> > >> >> >> >>>> Has anyone tried this option yet? I've heard someone got it going for > >> >> >> >>>> slack, but I thought it sounded like it might make it easier for running > >> >> >> >>>> freebsd. > >> >> >> >>>> > >> >> >> >>>> I'm currently trying to build a more current u-boot to test it. > >> >> >> >>>> > >> >> >> >>>> _______________________________________________ > >> >> >> >>>> freebsd-arm@freebsd.org mailing list > >> >> >> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> >> >> >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >> >> >> >>> > >> >> >> >>> -- > >> >> >> >>> Emmanuel Vadot > >> >> >> >>> _______________________________________________ > >> >> >> >>> freebsd-arm@freebsd.org mailing list > >> >> >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> >> >> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >> >> >> > > >> >> > > >> >> > > >> >> > -- > >> >> > Emmanuel Vadot > >> > > >> > > >> > -- > >> > Emmanuel Vadot > > > > > > -- > > Emmanuel Vadot -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Oct 12 06:22:26 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E03FC0E1BB for ; Wed, 12 Oct 2016 06:22:26 +0000 (UTC) (envelope-from tobiaskilb@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B6BBE92 for ; Wed, 12 Oct 2016 06:22:25 +0000 (UTC) (envelope-from tobiaskilb@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id b81so63011735lfe.1 for ; Tue, 11 Oct 2016 23:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=V+DPS0586ca43dXCs/GTrE7j7oEmkRSez/fsoG++fbc=; b=DR4dDM0qDIKlCsVnwriIaMFK+w/gsfLZZB7rMqkMM0tog6WGii/q2ExMUOtcUPIUWk yv+qRFh6pD0a65XEqsZqGzbqo6YTcMJ+pd6Fjo2Giw0efFXs0D0wkUH/yN76uAHmYNgH l/H9LCpHo4TADyJpo4SfXJvCXdlSiKJnYHYQ0rgJvECN3ftzxii7joCTMY0gvOoN1Et1 AqwN1YimXbQ172NxknRMEs3YoJzyWRZ4zgHOVKHlOUwJr5Oud5ZxPIj4jwaxg2bu+vS6 /j3TXsRoZ8LD54HxxASgK4w1+ZUAOtup/FksZBxOsGz9T3vQ4I3I5DSQ+fBoQoL6bx3f xGiA== 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:from:date :message-id:subject:to; bh=V+DPS0586ca43dXCs/GTrE7j7oEmkRSez/fsoG++fbc=; b=KEYJscYq6LkqmJ0ywqsTzgZLHCUmwaayrQ8O5/rVv2wROOSQ0UpErjELkaa28icigX FpZR37ADSo4mQuHnVCK3TreYpQHHVK4ZdfAwL73iSi1qqW/MvjErLFZ3TarC29RPQFle ZbGBS/t2Ah/p8yCH9/oiikhnobwxBYt013QmvYUGSdYaHllf1X2ws4NVH1yUvuU8TCuD A6MAOmUq29T3vdu38RTNthewKFLANqUBuP3RawmmI0k89rbDwFM7w3cIIZW6vJ6d8N9h DXvpTJqbFa1WAkjgYPU3CCpcKmPuoksviyKsEJ/FVvyF9VG4TjctKT9PgGeFHL8XxaCQ ripA== X-Gm-Message-State: AA6/9RnElO3rdNvyHX++SmUv8f4Wb7Dz73ftmadwQuIxdY2l6ArGcfEnNqBq+Hdmmzw66wPJb/nrcqI17c9CUw== X-Received: by 10.25.75.216 with SMTP id y207mr6098417lfa.100.1476253343799; Tue, 11 Oct 2016 23:22:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.163.211 with HTTP; Tue, 11 Oct 2016 23:22:23 -0700 (PDT) Received: by 10.25.163.211 with HTTP; Tue, 11 Oct 2016 23:22:23 -0700 (PDT) In-Reply-To: References: From: tobias kilb Date: Wed, 12 Oct 2016 08:22:23 +0200 Message-ID: Subject: DTS files for Orange Pi One (H3) SoC To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2016 06:22:26 -0000 Hi, Does anybody know where I can find suitable DTS files for the Orange Pi One? And maybe a kernel/SD card build instruction? Regards, Tobias From owner-freebsd-arm@freebsd.org Fri Oct 14 05:44:04 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3968AC11185 for ; Fri, 14 Oct 2016 05:44:04 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 24B91F76 for ; Fri, 14 Oct 2016 05:44:03 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from [136.179.10.143] (helo=[10.140.230.85]) by id.bluezbox.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86_2 (FreeBSD)) (envelope-from ) id 1buvHl-0004FM-6u for freebsd-arm@freebsd.org; Thu, 13 Oct 2016 22:44:01 -0700 From: Oleksandr Tymoshenko Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\)) Subject: Raspberry Pi 3 support Message-Id: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> Date: Thu, 13 Oct 2016 22:43:31 -0700 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3226) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Hello, Limited support for Raspberry Pi 3 has just landed in HEAD. No SMP and no 3D yet. And no BT/WiFi drivers. If you would like to give it a spin read this info, it may save you some googling time: [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 05:44:04 -0000 Hello, Limited support for Raspberry Pi 3 has just landed in HEAD. No SMP and no 3D yet. And no BT/WiFi drivers. If you would like to give it a = spin read this info, it may save you some googling time: - SD card layout is the same as for RPi or RPi 2 - Firmware and DTB files can be downloaded from official repo: https://github.com/raspberrypi/firmware/tree/master/boot Just copy them as-is to FAT partition on SD. There are plans to import latest .dts files and provide rpi3.dtb just like for Raspberry Pi and Raspberry Pi 2 - boot mode on RPi 3 is controlled by arm_control parameter in = config.txt, set it to 0x200 to boot in 64-bit mode - To reduce mess with consoles for now only PL01x UART is used (old one,=20= not miniUART) in all boot component: firmware, U-Boot, kernel. - On RPi 3 firmware defaults to miniUART, use = "dtoverlay=3Dpi3-disable-bt=E2=80=9D in config.txt to revert to old behaviour - A lot of peripherals are disabled in default dtb, to enable them add = this line to config.txt before any dtoverlay line: dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don - MMC is not included in dtb, add "dtoverlay=3Dmmc=E2=80=9D to = config.txt to enable it - Stock U-Boot uses miniUART as console so manual patching of include/configs/rpi.h required. Just search for = CONFIG_BCM283X_MU_SERIAL or CONFIG_PL01X_SERIAL - ubldr was switched for loader.efi, hence CONFIG_EFI is required for = U-Boot. Patch include/configs/rpi.h or pass CONFIG_EFI=3Dy to gmake when = building u-boot. Diane Bruce works on u-boot-rpi3 port that addresses all = these issues. - No crochet config for RPi 3 yet - To save you hassle, here are u-boot.bin, loader.efi, config.txt: https://people.freebsd.org/~gonzo/arm/rpi3/ Copy these files to FAT partition along with firmware mentioned = above - bootcmd for EFI would look like: fatload mmc 0 ${loadaddr} loader.efi; bootefi ${loadaddr} 0x100 where 0x100 is FDT blob address matching the value of = device_tree_address parameter in config.txt =E2=80=94=20 gonzo= From owner-freebsd-arm@freebsd.org Fri Oct 14 06:11:53 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 207DFC11686 for ; Fri, 14 Oct 2016 06:11:53 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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 ECE98D92 for ; Fri, 14 Oct 2016 06:11:52 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=eVnoLj0JDJEh8CtRS4USvj9v6LhQkua8cz4t+imLXPs=; b=jTz7wTtpPcUS6s4B2nRzitkPZ2 PIUs0BElC6tTKbhNM1GESMByITdi7SQU0EIulw+8s0b64FJ6deEKebb2E4kWIeqw5/GRqKlZtj1u8 uFhTYfCwylxCIaU3yblcQzqjGXnSNmSRw+H40bmfe9HLXLdL7A+gs+Wyc42jVuKShs9E=; Received: from subs12-223-255-228-102.three.co.id ([223.255.228.102]:44630 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1buvia-00350l-Sy; Fri, 14 Oct 2016 00:11:45 -0600 Date: Fri, 14 Oct 2016 14:11:38 +0800 From: Erich Dollansky To: Oleksandr Tymoshenko Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 3 support Message-ID: <20161014141138.20673299@X220.alogt.com> In-Reply-To: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> References: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.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-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 06:11:53 -0000 Hi, On Thu, 13 Oct 2016 22:43:31 -0700 Oleksandr Tymoshenko wrote: > Raspberry Pi 3 support thanks! This is the best news of the day. Erich From owner-freebsd-arm@freebsd.org Fri Oct 14 10:49:24 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7ACD9C117AB for ; Fri, 14 Oct 2016 10:49:24 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6BA9D295 for ; Fri, 14 Oct 2016 10:49:24 +0000 (UTC) (envelope-from db@db.net) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 149412AA597; Fri, 14 Oct 2016 04:48:31 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 79D5B1CDE4; Fri, 14 Oct 2016 06:49:20 -0400 (EDT) Date: Fri, 14 Oct 2016 06:49:20 -0400 From: Diane Bruce To: Oleksandr Tymoshenko Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 3 support Message-ID: <20161014104920.GA61973@night.db.net> References: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 10:49:24 -0000 On Thu, Oct 13, 2016 at 10:43:31PM -0700, Oleksandr Tymoshenko wrote: > Hello, > ... > > - ubldr was switched for loader.efi, hence CONFIG_EFI is required for U-Boot. > Patch include/configs/rpi.h or pass CONFIG_EFI=y to gmake when building > u-boot. Diane Bruce works on u-boot-rpi3 port that addresses all these > issues. A very preliminary port is at fetch http://people.FreeBSD.org/~db/u-boot-rpi3.tgz Please note there is ongoing work and this is not the final port but will get you going. > > - No crochet config for RPi 3 yet I have a preliminary crotchet setup here. I'll tarball that up later today. > — > gonzo Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-arm@freebsd.org Fri Oct 14 11:10:56 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 442C5C11D64 for ; Fri, 14 Oct 2016 11:10:56 +0000 (UTC) (envelope-from mattia.rossi.mailinglists@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2ACFE9E for ; Fri, 14 Oct 2016 11:10:55 +0000 (UTC) (envelope-from mattia.rossi.mailinglists@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id b81so187712472lfe.1 for ; Fri, 14 Oct 2016 04:10:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:subject:references:to:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ZIuM5+3SBPzB0hOhghqOG871QYBbajNRIIhIcRBohMk=; b=NyTsVNC3pgC4tUO5viaQWza87yV9mA2dZTP0gA82+IacW5ShRy6523SKmtoMhvda1v 0alh3PaC4O/WjcGVM5VxzEcD9nWibZJCINS0hfvENP+vcrC4MTN8WD0C+t7zuId7+2dI O+bLd1zPSZsIzIZD3Lpdc2NuUzlDroklsWmhPlVxa+ViqaRVssxntqTWzZdLedu659Ve uJq1sTiEABhtBAj1c1CgjlzgUoRVG6A7f8/KJFGyDxca9zE+oBvv1zAy8oNrk99c4wGx jxTmgXgKtJZ+cn74Y9yxwwGRrmg5k2EwJip3r+vleEMyi/eFskELauzpcMGJ1Tbu1hYP 3T5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ZIuM5+3SBPzB0hOhghqOG871QYBbajNRIIhIcRBohMk=; b=MNT0ESlUdOIe13LKOSQnk0NWv2FHnl8CzMlliWwoETxQetXCuhzMsZFEhq/Dl2860C CHzvBImbsQN/D7cXR2MSauN+f3xzTrMKZr5HykVrcvxvSTCn4W8jF6sxh54vGo50zNzA GunUtcb5Tm7tE5+45cs9EOZ/38COTGrZdplFhhXXN8Op0DA8Eek+6Eek/4RxUXXpXPUm WZARy7ri4YhYu2a2mXxn4Ont1TnFI+yjtUD3f5GsJkY0Kj/y/IMExnrdJrcIa+KwM86j 6mOL8suP/PYovzfZ1RxoshIYNtyt3wLfgdmEFK1HMUmPJfqAQvUTggW+G+yLsne30sQ9 cHJg== X-Gm-Message-State: AA6/9RlPxurxBhRecdQ+xFRtzd/TtSr04MFhCm0BDfpTqbHfGNt/suPqmRtlv9B8m4XTAw== X-Received: by 10.25.151.212 with SMTP id z203mr2961736lfd.79.1476443453410; Fri, 14 Oct 2016 04:10:53 -0700 (PDT) Received: from [172.20.10.2] (241.228.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch. [178.197.228.241]) by smtp.gmail.com with ESMTPSA id n14sm4988144lfn.7.2016.10.14.04.10.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Oct 2016 04:10:52 -0700 (PDT) Reply-To: mattia.rossi.mailinglists@gmail.com Subject: Re: DTS files for Orange Pi One (H3) SoC References: To: tobias kilb , freebsd-arm@freebsd.org, Daniel Braniss From: Mattia Rossi Message-ID: <8f3839ac-8684-0479-e131-39828c775b40@gmail.com> Date: Fri, 14 Oct 2016 13:10:51 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 11:10:56 -0000 Hi Tobias, I'm using build instructions and a .dtb that I got from Daniel Braniss... Given that it was a link to his page, I'm not sure I'm allowed to share it on the list.. Cheers, Mat Am 12.10.2016 um 08:22 schrieb tobias kilb: > Hi, > > Does anybody know where I can find suitable DTS files for the Orange Pi > One? And maybe a kernel/SD card build instruction? > > Regards, > > Tobias > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Fri Oct 14 12:54:39 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E232C1141A for ; Fri, 14 Oct 2016 12:54:39 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D8C39D5C for ; Fri, 14 Oct 2016 12:54:38 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from imac.bs.cs.huji.ac.il ([132.65.179.42]) by kabab.cs.huji.ac.il with esmtp id 1bv1nR-000Be2-Mm; Fri, 14 Oct 2016 15:41:09 +0300 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: DTS files for Orange Pi One (H3) SoC From: Daniel Braniss In-Reply-To: <8f3839ac-8684-0479-e131-39828c775b40@gmail.com> Date: Fri, 14 Oct 2016 15:41:09 +0300 Cc: tobias kilb , freebsd-arm@freebsd.org Message-Id: References: <8f3839ac-8684-0479-e131-39828c775b40@gmail.com> To: mattia.rossi.mailinglists@gmail.com X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 12:54:39 -0000 > On 14 Oct 2016, at 2:10 PM, Mattia Rossi = wrote: >=20 > Hi Tobias, >=20 > I'm using build instructions and a .dtb that I got from Daniel = Braniss... >=20 > Given that it was a link to his page, I'm not sure I'm allowed to = share it on the list.. of course you can share it. www.cs.huji.ac .il/~danny danny >=20 > Cheers, >=20 > Mat >=20 > Am 12.10.2016 um 08:22 schrieb tobias kilb: >> Hi, >>=20 >> Does anybody know where I can find suitable DTS files for the Orange = Pi >> One? And maybe a kernel/SD card build instruction? >>=20 >> Regards, >>=20 >> Tobias >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" >=20 From owner-freebsd-arm@freebsd.org Fri Oct 14 16:04:47 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F38C5C107C6 for ; Fri, 14 Oct 2016 16:04:47 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABD4AA5F for ; Fri, 14 Oct 2016 16:04:47 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qk0-x22b.google.com with SMTP id z190so155623714qkc.2 for ; Fri, 14 Oct 2016 09:04:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=g4pi7PRS22/Ya6FZmu1d/l636narglzNSJVDHYOG2ZM=; b=fl7t9V2mSG4BtkFBOABHDZqSFwBLx+nttNe0wF+izcjFA5iVqU2DaB90kPzb0Bp5Nl Kdk70ZsGsXpOVTTiNRefylgQ8OCTJw7RaXBC0dES5hJDtcS01u5cz4KFHlxXGNz2Akra HDrnl56hTUTPKsluWx3MweWQLsHO/H4L1kTg427cVBMDCxggIWMQllmj8Qk8k3Y8rTCq DL5fdOYgYzk76qifzkM5LYig6UaJlXnD6z6Kq5jeprmrQ5kWthObAi6vjQlLauRqwqkJ rlXp2mR29DYsk4vGRIr90b0DdzZSZZWlC57DuR70PG0NK/He/Mpbl4l7tpQiDRPTJ5Lh nw/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=g4pi7PRS22/Ya6FZmu1d/l636narglzNSJVDHYOG2ZM=; b=kFPzBGqHAXBzgu92ULhIMUZWpyfaZT5zJhIBVKenOWbYNCDNFGb6XZY0OuZYQesSSh a8qif6dJVBe2s+RYl9R/HGJxw/QZMAV3TNdQ2GXBmBx45WPiCcs6ZM3Y/AuADQLV54m6 0ukZXVL3hcbdDdtzORvFZ+BZj1fG2MJhZB7M+dg83PXsdVmqS6v10TtYT2jp/Ccf853q KExN9/xy1mzqO5ZWiqI1vgjXSnPdx9GLO8WfqcgMHkwauVwM4es7RKQwbhtQRssAP82x 98KDYxRn7QngNDP/ZqMw2s+WbejsGk8t8tKbCR44adN+6gCH2fuycflBVmA56n4Mdbu+ IjvQ== X-Gm-Message-State: AA6/9Rn8DkGCcpVLb1QFkMgH67R7Ag+LumID7PerBo7q2tLHV7Kub3hO/+BWXMCsytrC+kwq X-Received: by 10.55.113.69 with SMTP id m66mr14147230qkc.229.1476461086611; Fri, 14 Oct 2016 09:04:46 -0700 (PDT) Received: from mutt-hardenedbsd ([63.88.83.66]) by smtp.gmail.com with ESMTPSA id 22sm7841598qkj.15.2016.10.14.09.04.44 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 14 Oct 2016 09:04:44 -0700 (PDT) Date: Fri, 14 Oct 2016 12:04:42 -0400 From: Shawn Webb To: Oleksandr Tymoshenko Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 3 support Message-ID: <20161014160442.GA5906@mutt-hardenedbsd> References: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> X-Operating-System: FreeBSD mutt-hardenedbsd 12.0-CURRENT-HBSD FreeBSD 12.0-CURRENT-HBSD X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 16:04:48 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 13, 2016 at 10:43:31PM -0700, Oleksandr Tymoshenko wrote: > Hello, >=20 > Limited support for Raspberry Pi 3 has just landed in HEAD. No SMP > and no 3D yet. And no BT/WiFi drivers. If you would like to give it a spin > read this info, it may save you some googling time: >=20 > - SD card layout is the same as for RPi or RPi 2 >=20 > - Firmware and DTB files can be downloaded from official repo: > https://github.com/raspberrypi/firmware/tree/master/boot > Just copy them as-is to FAT partition on SD. There are plans to > import latest .dts files and provide rpi3.dtb just like for > Raspberry Pi and Raspberry Pi 2 >=20 > - boot mode on RPi 3 is controlled by arm_control parameter in config.txt, > set it to 0x200 to boot in 64-bit mode >=20 > - To reduce mess with consoles for now only PL01x UART is used (old one,= =20 > not miniUART) in all boot component: firmware, U-Boot, kernel. >=20 > - On RPi 3 firmware defaults to miniUART, use "dtoverlay=3Dpi3-disable-bt= ??? in > config.txt to revert to old behaviour >=20 > - A lot of peripherals are disabled in default dtb, to enable them add th= is > line to config.txt before any dtoverlay line: > dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don >=20 > - MMC is not included in dtb, add "dtoverlay=3Dmmc??? to config.txt to en= able it >=20 > - Stock U-Boot uses miniUART as console so manual patching of > include/configs/rpi.h required. Just search for CONFIG_BCM283X_MU_SER= IAL > or CONFIG_PL01X_SERIAL >=20 > - ubldr was switched for loader.efi, hence CONFIG_EFI is required for U-B= oot. > Patch include/configs/rpi.h or pass CONFIG_EFI=3Dy to gmake when buil= ding > u-boot. Diane Bruce works on u-boot-rpi3 port that addresses all these > issues. >=20 > - No crochet config for RPi 3 yet >=20 > - To save you hassle, here are u-boot.bin, loader.efi, config.txt: > https://people.freebsd.org/~gonzo/arm/rpi3/ > Copy these files to FAT partition along with firmware mentioned above >=20 > - bootcmd for EFI would look like: > fatload mmc 0 ${loadaddr} loader.efi; bootefi ${loadaddr} 0x100 > where 0x100 is FDT blob address matching the value of device_tree_add= ress > parameter in config.txt Thank you so much for the hard work! It's great to see the progress being made and I'm so excited! If I were to set up an sdcard manually. What kind of partition layout would I need? How would I install U-Boot to it? Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYAQIYAAoJEGqEZY9SRW7uXyUP/j1Cwor42XBUkh/yJTINaiej 9pnO6viIdxgY964lu5skQmuGWY+6HnBYs4476dKGh/3EWoehJUSIb8xhnBqeFHZT AwP7Y04AsgRQaFppt+9KmKkWSaFo5kICy0ruLiYy3NdlOs1rzRVdFnVSBkD94N8s 9dzZ65aGpzexrNcOIVCr6rNu+WpNffRi7DpGdoJOJ4sPoWhKH40Ys3GEx5qlyZM/ C0Z+CGFr2IdMstm8gqGxcTXWT95tp1uwrst4odBxkBCKT3t5eHHQdaWm2GtG9Ng3 vsCl6G/oBQZyK5kSWGfae5Brb2a7YLLoP5zsg4LWhjNOXJmyhJu8yEKXa5gzt5zD z2kVmQpx+qR/2wZyjETgYncprZR0oach7VrUDhiNhH4Th+guW/wUyrw4psC1DOiq //FbNfbj/ucbhkSnnSR5QK63nDh++g8g20v1IitbHZSsSNw4VLkkmjN1rvlZVafM rGpo0He1FzOU9+wZOx/FXMAM50IWfZT2/SsRsZ7vj/zCemmFetVKEL+vJ8vaIHTr tPKu+0qdpBdq5n3HafpLhs7TxjFW8rVfqxJ446IQ96iXlnQyaj2O7CyPlBhH9JBD gYsGfliFAdS8bLcTY76CPA7XpcPtGD0xv1EB8dO9A7aCILyGpFpf59QEBObNvYYe Tfb5iIqC9K/5Gt56yege =ZYkg -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf-- From owner-freebsd-arm@freebsd.org Fri Oct 14 16:42:50 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6637C117DE for ; Fri, 14 Oct 2016 16:42:50 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 B9C71B1D for ; Fri, 14 Oct 2016 16:42:50 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from [76.102.118.237] (helo=[10.0.1.5]) by id.bluezbox.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86_2 (FreeBSD)) (envelope-from ) id 1bv5ZH-0005Rb-B2; Fri, 14 Oct 2016 09:42:48 -0700 From: Oleksandr Tymoshenko Message-Id: <761781BA-6EDE-4C09-978C-6D312E6F1FAB@bluezbox.com> Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\)) Subject: Re: Raspberry Pi 3 support Date: Fri, 14 Oct 2016 09:42:47 -0700 In-Reply-To: <20161014160442.GA5906@mutt-hardenedbsd> Cc: freebsd-arm@freebsd.org To: Shawn Webb References: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> <20161014160442.GA5906@mutt-hardenedbsd> X-Mailer: Apple Mail (2.3226) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: > On Oct 14, 2016, at 9:04 AM, Shawn Webb wrote: > > On Thu, Oct 13, 2016 at 10:43:31PM -0700, Oleksandr Tymoshenko wrote: >> Hello, >> >> Limited support for Raspberry Pi 3 has just landed in HEAD. No SMP >> and no 3D yet. And no BT/WiFi drivers. If you would like to give it a spin >> read this info, it may save you some googling time: >> >> - SD card layout is the same as for RPi or RPi 2 >> >> - Firmware and DTB files can be downloaded from official repo: >> https://github.com/raspberrypi/firmware/tree/master/boot >> Just copy them as-is to FAT partition on SD. There are plans to >> import latest .dts files and provide rpi3.dtb just like for >> Raspberry Pi and Raspberry Pi 2 >> >> - boot mode on RPi 3 is controlled by arm_control parameter in config.txt, >> set it to 0x200 to boot in 64-bit mode >> >> - To reduce mess with consoles for now only PL01x UART is used (old one, >> not miniUART) in all boot component: firmware, U-Boot, kernel. >> >> - On RPi 3 firmware defaults to miniUART, use "dtoverlay=pi3-disable-bt??? in >> config.txt to revert to old behaviour >> >> - A lot of peripherals are disabled in default dtb, to enable them add this >> line to config.txt before any dtoverlay line: >> dtparam=audio=on,i2c_arm=on,spi=on >> >> - MMC is not included in dtb, add "dtoverlay=mmc??? to config.txt to enable it >> >> - Stock U-Boot uses miniUART as console so manual patching of >> include/configs/rpi.h required. Just search for CONFIG_BCM283X_MU_SERIAL >> or CONFIG_PL01X_SERIAL >> >> - ubldr was switched for loader.efi, hence CONFIG_EFI is required for U-Boot. >> Patch include/configs/rpi.h or pass CONFIG_EFI=y to gmake when building >> u-boot. Diane Bruce works on u-boot-rpi3 port that addresses all these >> issues. >> >> - No crochet config for RPi 3 yet >> >> - To save you hassle, here are u-boot.bin, loader.efi, config.txt: >> https://people.freebsd.org/~gonzo/arm/rpi3/ >> Copy these files to FAT partition along with firmware mentioned above >> >> - bootcmd for EFI would look [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 HTML_MESSAGE BODY: HTML included in message Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 16:42:51 -0000 > On Oct 14, 2016, at 9:04 AM, Shawn Webb = wrote: >=20 > On Thu, Oct 13, 2016 at 10:43:31PM -0700, Oleksandr Tymoshenko wrote: >> Hello, >>=20 >> Limited support for Raspberry Pi 3 has just landed in HEAD. No SMP >> and no 3D yet. And no BT/WiFi drivers. If you would like to give it a = spin >> read this info, it may save you some googling time: >>=20 >> - SD card layout is the same as for RPi or RPi 2 >>=20 >> - Firmware and DTB files can be downloaded from official repo: >> https://github.com/raspberrypi/firmware/tree/master/boot >> Just copy them as-is to FAT partition on SD. There are plans to >> import latest .dts files and provide rpi3.dtb just like for >> Raspberry Pi and Raspberry Pi 2 >>=20 >> - boot mode on RPi 3 is controlled by arm_control parameter in = config.txt, >> set it to 0x200 to boot in 64-bit mode >>=20 >> - To reduce mess with consoles for now only PL01x UART is used (old = one,=20 >> not miniUART) in all boot component: firmware, U-Boot, kernel. >>=20 >> - On RPi 3 firmware defaults to miniUART, use = "dtoverlay=3Dpi3-disable-bt??? in >> config.txt to revert to old behaviour >>=20 >> - A lot of peripherals are disabled in default dtb, to enable them = add this >> line to config.txt before any dtoverlay line: >> dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don >>=20 >> - MMC is not included in dtb, add "dtoverlay=3Dmmc??? to config.txt = to enable it >>=20 >> - Stock U-Boot uses miniUART as console so manual patching of >> include/configs/rpi.h required. Just search for = CONFIG_BCM283X_MU_SERIAL >> or CONFIG_PL01X_SERIAL >>=20 >> - ubldr was switched for loader.efi, hence CONFIG_EFI is required for = U-Boot. >> Patch include/configs/rpi.h or pass CONFIG_EFI=3Dy to gmake when = building >> u-boot. Diane Bruce works on u-boot-rpi3 port that addresses all = these >> issues. >>=20 >> - No crochet config for RPi 3 yet >>=20 >> - To save you hassle, here are u-boot.bin, loader.efi, config.txt: >> https://people.freebsd.org/~gonzo/arm/rpi3/ >> Copy these files to FAT partition along with firmware mentioned = above >>=20 >> - bootcmd for EFI would look like: >> fatload mmc 0 ${loadaddr} loader.efi; bootefi ${loadaddr} 0x100 >> where 0x100 is FDT blob address matching the value of = device_tree_address >> parameter in config.txt >=20 > Thank you so much for the hard work! It's great to see the progress > being made and I'm so excited! >=20 > If I were to set up an sdcard manually. What kind of partition layout > would I need? How would I install U-Boot to it? SD card layout is: one FAT partition for firmware/u-boot, one large = partition for BSD. Something like: # gpart create -s MBR da0 # gpart add -t '\!12' -a 63 -s 50m da0 # gpart set -a active -i 1 da0 # newfs_msdos -F 16 /dev/da0s1 # gpart add -t freebsd -a 4m da0 # gpart create -s BSD da0s2 # gpart add -t freebsd-ufs da0s2 # newfs -U da0s2a (source: https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi%202%20image = ) To install U-Boot just copy firmware files from github, u-boot.bin, = loader.efi, config.txt to FAT partition.= From owner-freebsd-arm@freebsd.org Fri Oct 14 16:50:45 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7599BC11AF0 for ; Fri, 14 Oct 2016 16:50:45 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0635CEB4; Fri, 14 Oct 2016 16:50:44 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id u9EGoYNY094602 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 14 Oct 2016 16:50:35 GMT (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 u9EGoMev066887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Oct 2016 18:50:22 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id u9EGoMhd032735; Fri, 14 Oct 2016 18:50:22 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id u9EGoLYV032734; Fri, 14 Oct 2016 18:50:21 +0200 (CEST) (envelope-from ticso) Date: Fri, 14 Oct 2016 18:50:21 +0200 From: Bernd Walter To: freebsd-arm@freebsd.org Cc: jbeich@freebsd.org, Bernd Walter Subject: libx264 fails to build on a raspberry pi2 Message-ID: <20161014165021.GN99217@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 10.2-RELEASE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-1.507 autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 16:50:45 -0000 This seems to be a new problem, as I've installed the port before on another Pi2 System (11-RC1): libx264-0.144.2533_1 H.264/MPEG-4 AVC Video Encoding (Library) System is the official FreeBSD 11-RELEASE image for Pi2. FreeBSD rpi2 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 13:01:42 UTC 2016 root@releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/RPI2 arm [61]cicely1# svn info /usr/ports/multimedia/libx264 Path: multimedia/libx264 Working Copy Root Path: /usr/ports URL: file:///data/freebsd-svn/ports/head/multimedia/libx264 Relative URL: ^/head/multimedia/libx264 Repository Root: file:///data/freebsd-svn/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 423971 Node Kind: directory Schedule: normal Last Changed Author: jbeich Last Changed Rev: 422675 Last Changed Date: 2016-09-23 15:15:06 +0200 (Fri, 23 Sep 2016) ... cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o encoder/encoder.o encoder/encoder.c cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o encoder/lookahead.o encoder/lookahead.c cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o common/threadpool.o common/threadpool.c cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o common/arm/mc-c.o common/arm/mc-c.c cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o common/arm/predict-c.o common/arm/predict-c.c cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o common/opencl.o common/opencl.c cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o encoder/slicetype-cl.o encoder/slicetype-cl.c cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/cpu-a.o common/arm/cpu-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/pixel-a.o common/arm/pixel-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/mc-a.o common/arm/mc-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/dct-a.o common/arm/dct-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/quant-a.o common/arm/quant-a.S :29:5: error: instruction requires: armv6t2 rbit r1, r1 ^ common/arm/quant-a.S:362:1: note: while in macro instantiation decimate_score_1x 15 ^ :29:5: error: instruction requires: armv6t2 rbit r1, r1 ^ /tmp/quant-a-6e019c.s:515:1: note: while in macro instantiation decimate_score_1x 16 ^ cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/deblock-a.o common/arm/deblock-a.S gmake[4]: *** [Makefile:217: common/arm/quant-a.o] Error 1 gmake[4]: *** Waiting for unfinished jobs.... gmake[4]: Leaving directory '/usr/obj/usr/ports/multimedia/libx264/work/x264-snapshot-20160921-2245-stable' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[3]: stopped in /usr/ports/multimedia/libx264 *** Error code 1 Stop. make[2]: stopped in /usr/ports/multimedia/libx264 *** Error code 1 Stop. make[1]: stopped in /usr/ports/multimedia/ffmpeg *** Error code 1 Stop. make: stopped in /usr/ports/multimedia/ffmpeg 377.491u 24.840s 2:59.62 223.9% 47346+407k 1+72io 17pf+0w Exit 1 -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Oct 14 21:13:30 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA129C12DD3 for ; Fri, 14 Oct 2016 21:13:30 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 C31B233D for ; Fri, 14 Oct 2016 21:13:30 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from [208.184.220.60] (helo=limiting-factor.dolby.net) by id.bluezbox.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86_2 (FreeBSD)) (envelope-from ) id 1bv9nD-0005po-Rw for freebsd-arm@freebsd.org; Fri, 14 Oct 2016 14:13:28 -0700 From: Oleksandr Tymoshenko Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\)) Subject: Re: Raspberry Pi 3 support Date: Fri, 14 Oct 2016 14:12:58 -0700 References: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> To: freebsd-arm@freebsd.org In-Reply-To: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> Message-Id: <815A1DB5-1592-4E4F-A12C-99EAAC4684C0@bluezbox.com> X-Mailer: Apple Mail (2.3226) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: > On Oct 13, 2016, at 10:43 PM, Oleksandr Tymoshenko wrote: > > Hello, > > > - bootcmd for EFI would look like: > fatload mmc 0 ${loadaddr} loader.efi; bootefi ${loadaddr} 0x100 > where 0x100 is FDT blob address matching the value of device_tree_address > parameter in config.txt [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 21:13:30 -0000 > On Oct 13, 2016, at 10:43 PM, Oleksandr Tymoshenko = wrote: >=20 > Hello, >=20 >=20 > - bootcmd for EFI would look like: > fatload mmc 0 ${loadaddr} loader.efi; bootefi ${loadaddr} 0x100 > where 0x100 is FDT blob address matching the value of = device_tree_address > parameter in config.txt I stand corrected. boot1.efi should be placed on FAT partition and used = in this command, not loader.efi Actually the right way to do this is to copy boot1.efi to = EFI/BOOT/bootaa64.efi Then no custom boot command is required. Board will just boot.= From owner-freebsd-arm@freebsd.org Fri Oct 14 22:10:56 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3421DC11A1B for ; Fri, 14 Oct 2016 22:10:56 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF0A7BF9 for ; Fri, 14 Oct 2016 22:10:55 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qk0-x229.google.com with SMTP id z190so166700630qkc.2 for ; Fri, 14 Oct 2016 15:10:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=W1VdFjMyKzQF/HF2uEPEfUWYJQLgeaJjTjXOMQkwVQ8=; b=RrXMjrwFwPrOMvVFQarzjrELM4d5CzxvSSU0cXC0CBzBw1tFCDAhTC/Pumc07iAJQj SZELGU1lYPhANyrbcg1FOqUQ01a2jZCAcvtjo437WIJ0IyPccvBAOHtFgJpK9TIKwWuB aKCw7k6kSb/8DlboRUSi7dWlsh0S01gvFS9JBvdoU/+u8rmtj6GNX+FTcZQPHudPe0w6 ROl5sH/Ims7f+DXoIxfEl4g8Y6vcza+ebDrfvDCmbhYThSrtrdRsmqF6iF4cviiH1rK4 KirWOqIPUJoKy6AulqCW3YMUm1bkvJL1iSFBR1GHKd4KefmRpTB+AmFWaeX0hl4yhf+u YGSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=W1VdFjMyKzQF/HF2uEPEfUWYJQLgeaJjTjXOMQkwVQ8=; b=ZAfD+jdxV8EqP1bN28mkbMKcdfpWqas6DcelooHSxcODYXfiT7W2zelbuz2Gcr3a1e OfhR/bQlAp6la4Cc/iT4Le7xl9zvbA09j5D2GbuweC+lyVSdKWqH0GdtWuP09F3O7ARS RM52jsOoKLc5CGLEzNMjPyHrtdZIL1WbCZ7oBs7XhgO3TE84aKyRmcleO9q8JT+N1iaE y2Kz4Oj9WYrcKQqMn941q2aCrcEXLdd2DII9LbN+pTRHZaAb9OMpq+26cVSUDPMGS+Xl vhQ4pGZ4U6TBnBqoSizJSzPEf9aNgicnYOBjIPr+32dqfkvJVbx99dB7F38/lmwZJWut duNg== X-Gm-Message-State: AA6/9RkJtuEpCLxud1gzEuDZISm3ETF4Ui25KHiXp8ljmF0gaviafD0RkbIEPtb/nZt6LvQ+ X-Received: by 10.55.107.198 with SMTP id g189mr13106053qkc.287.1476483054882; Fri, 14 Oct 2016 15:10:54 -0700 (PDT) Received: from mutt-hardenedbsd ([63.88.83.66]) by smtp.gmail.com with ESMTPSA id x25sm8634891qtx.9.2016.10.14.15.10.52 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 14 Oct 2016 15:10:52 -0700 (PDT) Date: Fri, 14 Oct 2016 18:10:50 -0400 From: Shawn Webb To: Oleksandr Tymoshenko Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 3 support Message-ID: <20161014221050.GB5906@mutt-hardenedbsd> References: <5F2E0B05-0A54-4BD6-9CFE-4DFF5FEF07DC@bluezbox.com> <815A1DB5-1592-4E4F-A12C-99EAAC4684C0@bluezbox.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/WwmFnJnmDyWGHa4" Content-Disposition: inline In-Reply-To: <815A1DB5-1592-4E4F-A12C-99EAAC4684C0@bluezbox.com> X-Operating-System: FreeBSD mutt-hardenedbsd 12.0-CURRENT-HBSD FreeBSD 12.0-CURRENT-HBSD X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 22:10:56 -0000 --/WwmFnJnmDyWGHa4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 14, 2016 at 02:12:58PM -0700, Oleksandr Tymoshenko wrote: >=20 > > On Oct 13, 2016, at 10:43 PM, Oleksandr Tymoshenko = wrote: > >=20 > > Hello, > >=20 > >=20 > > - bootcmd for EFI would look like: > > fatload mmc 0 ${loadaddr} loader.efi; bootefi ${loadaddr} 0x100 > > where 0x100 is FDT blob address matching the value of device_tree_ad= dress > > parameter in config.txt >=20 > I stand corrected. boot1.efi should be placed on FAT partition and used i= n this command, > not loader.efi >=20 > Actually the right way to do this is to copy boot1.efi to EFI/BOOT/bootaa= 64.efi > Then no custom boot command is required. Board will just boot. I've documented the steps I took to install FreeBSD on my RPI3: https://wiki.freebsd.org/arm64 I hope I didn't miss anything. It's a wiki, so if I did, feel free to correct it (or let me know and I can correct it, too). Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --/WwmFnJnmDyWGHa4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYAVfoAAoJEGqEZY9SRW7uA1MQAI82WE2as6LxvvtHQHmBNe7P oTlFfgqpw6bLdzSUZ2cfH8rWrWZd8qNYMyFnG3nhjl8iloh+ru9jZh5Ux+nbkR1k fOVh9B4VeETF7v1XR2PCdlt5faGt2crvfNYS59pBy33dKcYbkZjU+2OzMD8qTGWY G8e5z/WVkh0MpT7L+AqeYqFHfR2onU3q5tu9e/UUduXGy56W2KtZE28xhzgXGd+T 9QoLAlE66kOSsLS+iNWgrezB7HnBBtpxxRvwafCjNiNLjs/GoYyie6hociJU8nt+ 4RO03D6W2GkTU67LsIhLpZUrOuOp1D9BpHctHlni/KShu47gTL5GK7arjbTddFSm 1V7cEeBfhTFsdcSh85oJ4WYr89tAg8e/9junAMP2jImgM/vlXzBZnpVpsb0AJl99 5YLb/7OE+7kCH2CzuE7cRrcPCP95UimLe8bn/AEid9Yt1zzpOxaoPnyn5lXRgY+O NdLlRIRss+7e9FUt0awbTxN+iiX4l2Xr+GuZMHvyn0BTtowvYhPgQys5yjNHqGo+ XmgMAtckJmMTaeMYY9mADhbfMTY3KV7LyufbLgobwjaEMBABber86QpotGg8rFCH q3saR1RRaCHUA/A6bccBsgOZnxGItgFfCGLKC5+ZDRC0XsTC99k07g2BviIetAvv 7A2xYBgYKK9scZINw3WK =nUt+ -----END PGP SIGNATURE----- --/WwmFnJnmDyWGHa4-- From owner-freebsd-arm@freebsd.org Sat Oct 15 06:55:25 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28DC1C11CD3 for ; Sat, 15 Oct 2016 06:55:25 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-38.reflexion.net [208.70.210.38]) (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 DD3C137D for ; Sat, 15 Oct 2016 06:55:24 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 20551 invoked from network); 15 Oct 2016 06:48:37 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 15 Oct 2016 06:48:37 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.10.0) with SMTP; Sat, 15 Oct 2016 02:48:49 -0400 (EDT) Received: (qmail 9960 invoked from network); 15 Oct 2016 06:48:49 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 15 Oct 2016 06:48:49 -0000 Received: from [192.168.0.104] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id 56B37EC8FFD; Fri, 14 Oct 2016 23:48:41 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: libx264 fails to build on a raspberry pi2 From: Mark Millard In-Reply-To: <20161014165021.GN99217@cicely7.cicely.de> Date: Fri, 14 Oct 2016 23:48:40 -0700 Cc: freebsd-arm , jbeich@freebsd.org, ticso@cicely.de Content-Transfer-Encoding: quoted-printable Message-Id: References: <20161014165021.GN99217@cicely7.cicely.de> To: Bernd Walter X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Oct 2016 06:55:25 -0000 On 2016-Oct-14, at 9:50 AM, Bernd Walter = wrote: > This seems to be a new problem, as I've installed the port before > on another Pi2 System (11-RC1): > libx264-0.144.2533_1 H.264/MPEG-4 AVC Video Encoding = (Library) >=20 > System is the official FreeBSD 11-RELEASE image for Pi2. > FreeBSD rpi2 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu = Sep 29 13:01:42 UTC 2016 = root@releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/RPI2 arm >=20 > [61]cicely1# svn info /usr/ports/multimedia/libx264=20 > Path: multimedia/libx264 > Working Copy Root Path: /usr/ports > URL: file:///data/freebsd-svn/ports/head/multimedia/libx264 > Relative URL: ^/head/multimedia/libx264 > Repository Root: file:///data/freebsd-svn/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 423971 > Node Kind: directory > Schedule: normal > Last Changed Author: jbeich > Last Changed Rev: 422675 > Last Changed Date: 2016-09-23 15:15:06 +0200 (Fri, 23 Sep 2016) >=20 > ... > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -Wall -I. -I. -isystem = /usr/local/include -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -std=3Dgnu99 -D_GNU_SOURCE = -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem = /usr/local/include -c -o encoder/encoder.o encoder/encoder.c Above (and later below) -mcpu=3Darm1136jf-s is odd for an rpi2b. Is = "36jf" right for any raspberry pi version? "76jzf" I'm aware of for = older rpi's (if I remember right). -mcpu=3Dcortex-a7 would match an rpi2b as I understand. For rpi2b I by default use: # more /etc/make.conf DEFAULT_VERSIONS+=3Dperl5=3D5.22 WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D WITH_DEBUG_FILES=3D MALLOC_PRODUCTION=3D CFLAGS+=3D -mcpu=3Dcortex-a7 CXXFLAGS+=3D -mcpu=3Dcortex-a7 CPPFLAGS+=3D -mcpu=3Dcortex-a7 (and similarly for buildworld and buildkernel as well, not just ports). But figuring out why -mcpu=3Darm1136jf-s is in use for your rpi2b = targeted build would seem to be a direction to go for what you were = building. > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -Wall -I. -I. -isystem = /usr/local/include -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -std=3Dgnu99 -D_GNU_SOURCE = -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem = /usr/local/include -c -o encoder/lookahead.o encoder/lookahead.c > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -Wall -I. -I. -isystem = /usr/local/include -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -std=3Dgnu99 -D_GNU_SOURCE = -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem = /usr/local/include -c -o common/threadpool.o common/threadpool.c > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -Wall -I. -I. -isystem = /usr/local/include -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -std=3Dgnu99 -D_GNU_SOURCE = -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem = /usr/local/include -c -o common/arm/mc-c.o common/arm/mc-c.c > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -Wall -I. -I. -isystem = /usr/local/include -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -std=3Dgnu99 -D_GNU_SOURCE = -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem = /usr/local/include -c -o common/arm/predict-c.o common/arm/predict-c.c > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -Wall -I. -I. -isystem = /usr/local/include -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -std=3Dgnu99 -D_GNU_SOURCE = -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem = /usr/local/include -c -o common/opencl.o common/opencl.c > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -Wall -I. -I. -isystem = /usr/local/include -O -pipe -isystem /usr/local/include = -fno-strict-aliasing -mcpu=3Darm1136jf-s -std=3Dgnu99 -D_GNU_SOURCE = -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem = /usr/local/include -c -o encoder/slicetype-cl.o encoder/slicetype-cl.c > cc -I. -I. -c -DSTACK_ALIGNMENT=3D4 -DPIC -DHIGH_BIT_DEPTH=3D0 = -DBIT_DEPTH=3D8 -o common/arm/cpu-a.o common/arm/cpu-a.S > cc -I. -I. -c -DSTACK_ALIGNMENT=3D4 -DPIC -DHIGH_BIT_DEPTH=3D0 = -DBIT_DEPTH=3D8 -o common/arm/pixel-a.o common/arm/pixel-a.S > cc -I. -I. -c -DSTACK_ALIGNMENT=3D4 -DPIC -DHIGH_BIT_DEPTH=3D0 = -DBIT_DEPTH=3D8 -o common/arm/mc-a.o common/arm/mc-a.S > cc -I. -I. -c -DSTACK_ALIGNMENT=3D4 -DPIC -DHIGH_BIT_DEPTH=3D0 = -DBIT_DEPTH=3D8 -o common/arm/dct-a.o common/arm/dct-a.S > cc -I. -I. -c -DSTACK_ALIGNMENT=3D4 -DPIC -DHIGH_BIT_DEPTH=3D0 = -DBIT_DEPTH=3D8 -o common/arm/quant-a.o common/arm/quant-a.S > :29:5: error: instruction requires: armv6t2 > rbit r1, r1 > ^ > common/arm/quant-a.S:362:1: note: while in macro instantiation > decimate_score_1x 15 > ^ > :29:5: error: instruction requires: armv6t2 > rbit r1, r1 > ^ > /tmp/quant-a-6e019c.s:515:1: note: while in macro instantiation > decimate_score_1x 16 > ^ Whatever caused the -mcpu=3Darm1136jf-s usage earlier above might also = cause misclassification here as well, so it is not even targeting an = armv6t2 (armv6 with Thumb-2 if I understand right), much less a armv-7a = (march)? "ARM1136 does not support Neon or Thumb-2 instructions from the = Cortex-A series": see = https://www.arm.com/products/processors/classic/arm11/arm1136.php ). > cc -I. -I. -c -DSTACK_ALIGNMENT=3D4 -DPIC -DHIGH_BIT_DEPTH=3D0 = -DBIT_DEPTH=3D8 -o common/arm/deblock-a.o common/arm/deblock-a.S > gmake[4]: *** [Makefile:217: common/arm/quant-a.o] Error 1 > gmake[4]: *** Waiting for unfinished jobs.... > gmake[4]: Leaving directory = '/usr/obj/usr/ports/multimedia/libx264/work/x264-snapshot-20160921-2245-st= able' > =3D=3D=3D> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the = failure to > the maintainer. > *** Error code 1 >=20 > Stop. > make[3]: stopped in /usr/ports/multimedia/libx264 > *** Error code 1 >=20 > Stop. > make[2]: stopped in /usr/ports/multimedia/libx264 > *** Error code 1 >=20 > Stop. > make[1]: stopped in /usr/ports/multimedia/ffmpeg > *** Error code 1 >=20 > Stop. > make: stopped in /usr/ports/multimedia/ffmpeg > 377.491u 24.840s 2:59.62 223.9% 47346+407k 1+72io 17pf+0w > Exit 1 >=20 > --=20 > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Oct 15 07:04:00 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 927E4C11EB2 for ; Sat, 15 Oct 2016 07:04:00 +0000 (UTC) (envelope-from tobiaskilb@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 161E0980 for ; Sat, 15 Oct 2016 07:04:00 +0000 (UTC) (envelope-from tobiaskilb@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id b81so210170756lfe.1 for ; Sat, 15 Oct 2016 00:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=q5r1QayN88Nd1OnspgKjwCKz8Bzik1Nggnp04E65T70=; b=xog0cdUJv13A2e3u4BYU9HEfPbxcwaYt7dY2v0V3Hjct3JWQa2yDD1cJkosOIh/Zjd /lPQevO4Dp3TiPFDaD5Gssva5OEUg1kX+R0AfQZ+bBEG+Gv3k8ea+6LmOt6oK66YpRR4 Ku+uSG9uFtMQFiQDdXd26r8P4mumwyvY2y6H9R1ttphwExwr2qmNqQuFW8M4f3XQrcER pgO5VFc2GaqPR1rhHthi2CsUraVfqubYkAj5bwn1p9hYe74oUHxncDwRncIUVhNBIDCB QxxmrjeiGmRnrvfGeHqMRHxeapeMFRknBzjArmmyYN0FVYUKQPQVRp8zwZvHVic8gNYf SmCg== 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:from:date :message-id:subject:to:cc; bh=q5r1QayN88Nd1OnspgKjwCKz8Bzik1Nggnp04E65T70=; b=M7GI+iPrWPmcWueodqniLRgT0BXXSvWMe5reSXFPIBqvxPo5ejMr8DmSrgDIoJLheh HYUlCovpnWzxIJFbBcRX1F2t5M2KXrg3dO6RMRwj09RXrGbgc+6lCQoDkYhQpBLIHMbI BunrAsDGN/1q4rTgNiJlB/F/srRxEQZwwSwaWgEZGQAh67Cie4Uf1wzDKzVQMlD1apN5 cKP03Ndicdu/GpCeqijd0+Ev/NMuBKNIUEwBobWpRk4JPtcq9/JfnRuKA74lWBM7GK5B 9GYJy6CL8opszsl1IKp0v9p8Gntr6MWe3RDjxkIB5tRd4FCyTGPqKAJX/AtjS0HzIjOA KMvQ== X-Gm-Message-State: AA6/9RlVn9OScClxyTYTPEstaw1eVRnBfmojJ6SS8ENRARm8UA54j+EgEvYOVEcfRLSmGAEuUQvIgT0lgP3cFA== X-Received: by 10.25.137.68 with SMTP id l65mr6143452lfd.115.1476515038088; Sat, 15 Oct 2016 00:03:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.163.211 with HTTP; Sat, 15 Oct 2016 00:03:57 -0700 (PDT) In-Reply-To: References: <8f3839ac-8684-0479-e131-39828c775b40@gmail.com> From: tobias kilb Date: Sat, 15 Oct 2016 09:03:57 +0200 Message-ID: Subject: Re: DTS files for Orange Pi One (H3) SoC To: Daniel Braniss Cc: mattia.rossi.mailinglists@gmail.com, freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Oct 2016 07:04:00 -0000 On Fri, Oct 14, 2016 at 2:41 PM, Daniel Braniss wrote: > > On 14 Oct 2016, at 2:10 PM, Mattia Rossi > wrote: > > Hi Tobias, > > I'm using build instructions and a .dtb that I got from Daniel Braniss... > > Given that it was a link to his page, I'm not sure I'm allowed to share it > on the list.. > > > of course you can share it. > > www.cs.huji.ac.il/~danny Thank you very much! When the hardware arrives I will try to build a FreeBSD image. > danny > > > Cheers, > > Mat Regards Tobias > > Am 12.10.2016 um 08:22 schrieb tobias kilb: > > Hi, > > Does anybody know where I can find suitable DTS files for the Orange Pi > One? And maybe a kernel/SD card build instruction? > > Regards, > > Tobias > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > From owner-freebsd-arm@freebsd.org Sat Oct 15 23:02:07 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71262C13D45 for ; Sat, 15 Oct 2016 23:02:07 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 194A4224; Sat, 15 Oct 2016 23:02:06 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id u9FN1s2k037582 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 15 Oct 2016 23:01:55 GMT (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 u9FN1oXC098718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Oct 2016 01:01:50 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id u9FN1nBY038284; Sun, 16 Oct 2016 01:01:49 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id u9FN1m51038283; Sun, 16 Oct 2016 01:01:48 +0200 (CEST) (envelope-from ticso) Date: Sun, 16 Oct 2016 01:01:48 +0200 From: Bernd Walter To: Mark Millard Cc: Bernd Walter , freebsd-arm , jbeich@freebsd.org, ticso@cicely.de Subject: Re: libx264 fails to build on a raspberry pi2 Message-ID: <20161015230148.GR99217@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20161014165021.GN99217@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 10.2-RELEASE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-1.507 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Oct 2016 23:02:07 -0000 On Fri, Oct 14, 2016 at 11:48:40PM -0700, Mark Millard wrote: > On 2016-Oct-14, at 9:50 AM, Bernd Walter wrote: > > > This seems to be a new problem, as I've installed the port before > > on another Pi2 System (11-RC1): > > libx264-0.144.2533_1 H.264/MPEG-4 AVC Video Encoding (Library) > > > > System is the official FreeBSD 11-RELEASE image for Pi2. > > FreeBSD rpi2 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 13:01:42 UTC 2016 root@releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/RPI2 arm > > > > [61]cicely1# svn info /usr/ports/multimedia/libx264 > > Path: multimedia/libx264 > > Working Copy Root Path: /usr/ports > > URL: file:///data/freebsd-svn/ports/head/multimedia/libx264 > > Relative URL: ^/head/multimedia/libx264 > > Repository Root: file:///data/freebsd-svn/ports > > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > > Revision: 423971 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: jbeich > > Last Changed Rev: 422675 > > Last Changed Date: 2016-09-23 15:15:06 +0200 (Fri, 23 Sep 2016) > > > > ... > > cc -Wshadow -O3 -ffast-math -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -isystem /usr/local/include -O -pipe -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -isystem /usr/local/include -c -o encoder/encoder.o encoder/encoder.c > > Above (and later below) -mcpu=arm1136jf-s is odd for an rpi2b. Is "36jf" right for any raspberry pi version? "76jzf" I'm aware of for older rpi's (if I remember right). > > -mcpu=cortex-a7 would match an rpi2b as I understand. > > For rpi2b I by default use: > > # more /etc/make.conf > DEFAULT_VERSIONS+=perl5=5.22 > WRKDIRPREFIX=/usr/obj/portswork > WITH_DEBUG= > WITH_DEBUG_FILES= > MALLOC_PRODUCTION= > CFLAGS+= -mcpu=cortex-a7 > CXXFLAGS+= -mcpu=cortex-a7 > CPPFLAGS+= -mcpu=cortex-a7 > > (and similarly for buildworld and buildkernel as well, not just ports). > > > But figuring out why -mcpu=arm1136jf-s is in use for your rpi2b targeted build would seem to be a direction to go for what you were building. I havn't touched make.conf beside adding WRKDIRPREFIX. After adding all *FLAGS: cc -Wshadow -O3 -ffast-math -O -pipe -mcpu=cortex-a7 -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -mcpu=cortex-a7 -isystem /usr/local/include -O -pipe -mcpu=cortex-a7 -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -mcpu=cortex-a7 -isystem /usr/local/include -c -o common/opencl.o common/opencl.c cc -Wshadow -O3 -ffast-math -O -pipe -mcpu=cortex-a7 -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -Wall -I. -I. -mcpu=cortex-a7 -isystem /usr/local/include -O -pipe -mcpu=cortex-a7 -isystem /usr/local/include -fno-strict-aliasing -mcpu=arm1136jf-s -std=gnu99 -D_GNU_SOURCE -fPIC -fomit-frame-pointer -fno-tree-vectorize -mcpu=cortex-a7 -isystem /usr/local/include -c -o encoder/slicetype-cl.o encoder/slicetype-cl.c cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/cpu-a.o common/arm/cpu-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/pixel-a.o common/arm/pixel-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/mc-a.o common/arm/mc-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/dct-a.o common/arm/dct-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/quant-a.o common/arm/quant-a.S cc -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/deblock-a.o common/arm/deblock-a.S :29:5: error: instruction requires: armv6t2 rbit r1, r1 ^ common/arm/quant-a.S:362:1: note: while in macro instantiation decimate_score_1x 15 ^ :29:5: error: instruction requires: armv6t2 rbit r1, r1 ^ /tmp/quant-a-967f0b.s:515:1: note: while in macro instantiation decimate_score_1x 16 ^ gmake[2]: *** [Makefile:217: common/arm/quant-a.o] Error 1 gmake[2]: *** Waiting for unfinished jobs.... gmake[2]: Leaving directory '/usr/obj/usr/ports/multimedia/libx264/work/x264-snapshot-20160921-2245-stable' ===> Compilation failed unexpectedly. That -mcpu=arm1136jf-s is something from the multimedia/x264/Makefile, on which the libx264 port is based on. 413179 jbeich CFLAGS_armv6+= -mcpu=arm1136jf-s However the problem is at least with one of the assembly files, which don't get those args at all. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.