From owner-freebsd-ppc@freebsd.org Sun Dec 20 08:33:48 2015 Return-Path: Delivered-To: freebsd-ppc@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 B5D45A4B8F8 for ; Sun, 20 Dec 2015 08:33:48 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (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 6AEF818B1 for ; Sun, 20 Dec 2015 08:33:47 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 7714 invoked from network); 20 Dec 2015 08:33:47 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Dec 2015 08:33:47 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sun, 20 Dec 2015 03:33:43 -0500 (EST) Received: (qmail 22083 invoked from network); 20 Dec 2015 08:33:42 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 20 Dec 2015 08:33:42 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 21319B1E002; Sun, 20 Dec 2015 00:33:16 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: bug 205453: another buildworld failure that shows up for powerpc64 lib32 contexts From: Mark Millard In-Reply-To: <5671D5DD.9090808@fgznet.ch> Date: Sun, 20 Dec 2015 00:33:15 -0800 Cc: FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <4E5F2AD9-180D-4800-98D7-774F40808FB6@dsl-only.net> References: <894D2513-6DE7-4E31-87A5-0529ECDF336C@dsl-only.net> <20151215123640.GG3625@kib.kiev.ua> <5671D5DD.9090808@fgznet.ch> To: Andreas Tobler , Konstantin Belousov X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 08:33:48 -0000 I have submitted bug 205453: another buildworld failure that shows up = for powerpc64 lib32 contexts. But in this case I submitted against the Base System for sys/cdefs.h = and/or libcxxrt/guard.cc problems in using/handling C11's = _Static_assert. You may want to look and see if you expect it should instead be = attributed to the various g++ compilers (g++49, g++5, = powerpc64-portbld-freebsd11.0-g++, . . .). A simple 6 line program = source shows the g++ syntax error issue with a direct use of = _Static_assert. (See the bug.) As I understand C++ the rejections are = valid/allowed. gcc49, gcc5, powerpc64-portbld-freebsd11.0-gcc, . . . accept the same = C11 _Static_assert notation fine when compiling the same source file = content as C code. clang++ (3.7) accepts the C11 _Static_assert syntax = in C++ compiles. But: # clang++ -Wall -pedantic main.cc main.cc:2:1: warning: _Static_assert is a C11-specific feature = [-Wc11-extensions] _Static_assert(1,"Test"); ^ 1 warning generated. In the buildworld case the reason for lib32's -m32 compiles being = involved is #if/#elif/. . . structure for = non-__arm__/non-_LP64/non-__LITTLE_ENDIAN__ contexts being the only ones = to attempt to use C11's _Static_assert in libcxxrt/guard.cc's C++ source = code: #ifdef __arm__ . . . #elif defined(_LP64) . . . #else typedef uint32_t guard_lock_t; # if defined(__LITTLE_ENDIAN__) . . . # else typedef struct { uint32_t init_half; uint32_t lock_half; } guard_t; _Static_assert(sizeof(guard_t) =3D=3D sizeof(uint64_t), ""); . . . # endif . . . #endif =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sun Dec 20 10:16:15 2015 Return-Path: Delivered-To: freebsd-ppc@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 7505D9C97F7 for ; Sun, 20 Dec 2015 10:16:15 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::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 13E4710C7 for ; Sun, 20 Dec 2015 10:16:15 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id l126so35810687wml.1 for ; Sun, 20 Dec 2015 02:16:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-type; bh=I6/FzelGVIPqbkr/iUNhv0vPYfxPN+PQyfyDScErqTo=; b=hK5tJp+ej32N6dDiuZzqNylR490355ITIDh1arPPUn8dnApaWtWe+hL0uSP09p8apU DfRHd7OePzwgaVASwHmU1zQYtqJibMqqqU5mbP8oC5aGIZrJPln7NdqpH/1AWWPOaSvd az2EBRvylL48+FF9uHZO+xqrK7jWePLbRGrxsDAoBnt/B/92hLIC/nWBN1NQ7mQdj+KQ Mg45tNPb19T5zzjIzMx6Qrq7eF75zUy6w4CpjYkmtowo6qRHP8gU8K6OVNz5agLulYdU QohIpkRVT9QkM+FZ4WNQroJrTIy85rAtEOcNbpG5E4ON2gXsbvHrhi+82BM3qJEkFlNe TQuw== X-Received: by 10.194.114.1 with SMTP id jc1mr14038821wjb.78.1450606573114; Sun, 20 Dec 2015 02:16:13 -0800 (PST) Received: from [192.168.1.131] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.googlemail.com with ESMTPSA id wl10sm13040777wjb.27.2015.12.20.02.16.12 for (version=TLSv1/SSLv3 cipher=OTHER); Sun, 20 Dec 2015 02:16:12 -0800 (PST) To: FreeBSD PowerPC ML From: Jukka Ukkonen Subject: gcc5 caused an unexpected error for 128 bit floating point numbers X-Enigmail-Draft-Status: N1110 Message-ID: <56767FEB.1080303@gmail.com> Date: Sun, 20 Dec 2015 12:16:11 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------020900010507010209090701" X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 10:16:15 -0000 This is a multi-part message in MIME format. --------------020900010507010209090701 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello all, I installed gcc5 from ports (gcc5-5.3.0) expecting it to be able to handle 128 bit floating point numbers on ppc64. It turns out, this does not work quite right. Apparently gcc5 tries to compile any basic 128 bit floating point operations to calls to functions like __gcc_qmul, _gcc_qdiv, etc. If such function wrappers are used at all, I guess they should be implemented as inline assebler wrappers or something instead of genuine functions, right? --jau --------------020900010507010209090701 Content-Type: text/plain; charset=UTF-8; name="Bugs.ppc64-float128" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Bugs.ppc64-float128" L3RtcC8vY2NVbnFFSnMubzogSW4gZnVuY3Rpb24gYHBwYzY0X2Zsb2F0MTI4X3Rlc3QnOgpw cGM2NF9mbG9hdDEyOF90ZXN0LmM6KC50ZXh0KzB4YTgpOiB1bmRlZmluZWQgcmVmZXJlbmNl IHRvIGBfX2djY19xbXVsJwpwcGM2NF9mbG9hdDEyOF90ZXN0LmM6KC50ZXh0KzB4ZGMpOiB1 bmRlZmluZWQgcmVmZXJlbmNlIHRvIGBfX2djY19xYWRkJwpwcGM2NF9mbG9hdDEyOF90ZXN0 LmM6KC50ZXh0KzB4MTAwKTogdW5kZWZpbmVkIHJlZmVyZW5jZSB0byBgX19nY2NfcW11bCcK cHBjNjRfZmxvYXQxMjhfdGVzdC5jOigudGV4dCsweDE4MCk6IHVuZGVmaW5lZCByZWZlcmVu Y2UgdG8gYF9fZ2NjX3FkaXYnCnBwYzY0X2Zsb2F0MTI4X3Rlc3QuYzooLnRleHQrMHgxOTAp OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRvIGBfX2djY19xYWRkJwovdG1wLy9jY1VucUVKcy5v OiBJbiBmdW5jdGlvbiBgbWFpbic6CnBwYzY0X2Zsb2F0MTI4X3Rlc3QuYzooLnRleHQuc3Rh cnR1cCsweGQ4KTogdW5kZWZpbmVkIHJlZmVyZW5jZSB0byBgX19nY2NfcW11bCcKcHBjNjRf ZmxvYXQxMjhfdGVzdC5jOigudGV4dC5zdGFydHVwKzB4MTA4KTogdW5kZWZpbmVkIHJlZmVy ZW5jZSB0byBgX19nY2NfcWFkZCcKcHBjNjRfZmxvYXQxMjhfdGVzdC5jOigudGV4dC5zdGFy dHVwKzB4MTJjKTogdW5kZWZpbmVkIHJlZmVyZW5jZSB0byBgX19nY2NfcW11bCcKcHBjNjRf ZmxvYXQxMjhfdGVzdC5jOigudGV4dC5zdGFydHVwKzB4MWFjKTogdW5kZWZpbmVkIHJlZmVy ZW5jZSB0byBgX19nY2NfcWRpdicKcHBjNjRfZmxvYXQxMjhfdGVzdC5jOigudGV4dC5zdGFy dHVwKzB4MWJjKTogdW5kZWZpbmVkIHJlZmVyZW5jZSB0byBgX19nY2NfcWFkZCcKY29sbGVj dDI6IGVycm9yOiBsZCByZXR1cm5lZCAxIGV4aXQgc3RhdHVzCg== --------------020900010507010209090701-- From owner-freebsd-ppc@freebsd.org Sun Dec 20 14:08:04 2015 Return-Path: Delivered-To: freebsd-ppc@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 E7673A14D10 for ; Sun, 20 Dec 2015 14:08:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7A4F1BF0 for ; Sun, 20 Dec 2015 14:08:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBKE84vO009063 for ; Sun, 20 Dec 2015 14:08:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205458] 11.0-CURRENT/10-STABLE powerpc64: a PowerMac G5 specific sys/powerpc/ofw/ofw_machdep.c change for reliable PowerMac G5 booting (with lots of RAM) Date: Sun, 20 Dec 2015 14:08:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 14:08:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205458 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-ppc@FreeBSD.org Keywords| |patch -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-ppc@freebsd.org Sun Dec 20 14:08:31 2015 Return-Path: Delivered-To: freebsd-ppc@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 6B89CA14DA8 for ; Sun, 20 Dec 2015 14:08:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C1A71C6A for ; Sun, 20 Dec 2015 14:08:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBKE8VaS009569 for ; Sun, 20 Dec 2015 14:08:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205455] 11.0-CURRENT sys/boot/ofw/Makfile.inc , powerpc/Makefile , and uboot/Makefile.inc LDFLAGS patches for powerpc64: use -Wl, Date: Sun, 20 Dec 2015 14:08:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 14:08:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205455 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-ppc@FreeBSD.org Keywords| |patch -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-ppc@freebsd.org Sun Dec 20 14:09:56 2015 Return-Path: Delivered-To: freebsd-ppc@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 9A061A14E9C for ; Sun, 20 Dec 2015 14:09:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8A3151D26 for ; Sun, 20 Dec 2015 14:09:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBKE9udL011288 for ; Sun, 20 Dec 2015 14:09:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205453] 11.0-CURRENT libcxxrt/guard.cc uses C11's _Static_assert in conditionally-compiled C++ code and when it is used buildworld fails for syntax errors in g++ compilers Date: Sun, 20 Dec 2015 14:09:56 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 14:09:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205453 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-toolchain@FreeBSD.o | |rg CC| |freebsd-ppc@FreeBSD.org -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-ppc@freebsd.org Sun Dec 20 16:29:47 2015 Return-Path: Delivered-To: freebsd-ppc@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 B9735A4D60E for ; Sun, 20 Dec 2015 16:29:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 90D421758 for ; Sun, 20 Dec 2015 16:29:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBKGTlG3085940 for ; Sun, 20 Dec 2015 16:29:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205453] 11.0-CURRENT libcxxrt/guard.cc uses C11's _Static_assert in conditionally-compiled C++ code and when it is used buildworld fails for syntax errors in g++ compilers Date: Sun, 20 Dec 2015 16:29:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dim@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 16:29:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205453 Dimitry Andric changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bapt@FreeBSD.org, | |dim@FreeBSD.org, | |theraven@FreeBSD.org --- Comment #2 from Dimitry Andric --- Hm, this _Static_assert has an interesting history. The original review from Baptiste, https://reviews.freebsd.org/D1390, used static_assert(), but this required -std=c++11 to compile, otherwise you would get: contrib/libcxxrt/guard.cc:104:1: error: C++ requires a type specifier for all declarations static_assert(sizeof(guard_t) == sizeof(uint64_t), ""); ^~~~~~~~~~~~~ This is the version upstream eventually also used, since they apparently assume C++11 there. David suggested changing it to _Static_assert(): "This should work if you change it to _Static_assert, which I think we support for all C/C++ versions." Now that I look at the code again, I am not entirely sure why the static assertion is only for the big endian #ifdef block. It would seem more useful to put it a few lines lower, for the !_LP64 case. That said, even when moving the _Static_assert() like that, it compiles fine for me, both with base gcc, and several versions of ports gcc (I tried gcc 4.8, 4.9 and 5.2). On the other hand, your sample program indeed does not compile with the ports versions of gcc. I'm not sure where those versions are getting their version of _Static_assert() from, though... -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-ppc@freebsd.org Sun Dec 20 16:56:40 2015 Return-Path: Delivered-To: freebsd-ppc@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 6F2FAA4E86E for ; Sun, 20 Dec 2015 16:56:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5FA171A1E for ; Sun, 20 Dec 2015 16:56:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBKGue5u037112 for ; Sun, 20 Dec 2015 16:56:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205453] 11.0-CURRENT libcxxrt/guard.cc uses C11's _Static_assert in conditionally-compiled C++ code and when it is used buildworld fails for syntax errors in g++ compilers Date: Sun, 20 Dec 2015 16:56:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 16:56:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205453 --- Comment #3 from Mark Millard --- As for where _Static_assert and static_assert are gotten from: _Static_assert in C11 and static_assert in C++11 exist even for free-standing implementations. As I understand it is even stronger: no explicit headers should be required unless the notation from one language is being used in the other (ignoring simulating for older versions of languages). The handling should be automatic/built-in even for source with no #includes involved. -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-ppc@freebsd.org Sun Dec 20 18:03:13 2015 Return-Path: Delivered-To: freebsd-ppc@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 0D048A4E575 for ; Sun, 20 Dec 2015 18:03:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F16AD1423 for ; Sun, 20 Dec 2015 18:03:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBKI3CnS005915 for ; Sun, 20 Dec 2015 18:03:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205453] 11.0-CURRENT libcxxrt/guard.cc uses C11's _Static_assert in conditionally-compiled C++ code and when it is used buildworld fails for syntax errors in g++ compilers Date: Sun, 20 Dec 2015 18:03:12 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2015 18:03:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205453 --- Comment #4 from Mark Millard --- FYI: My src.conf in use for the failing powerpc64-gcc "X" toolchain based buildworld and buildkernel (with gcc49 acting as the host toolchain) was: # more ~/src.configs/src.conf.powerpc64-xtoolchain.powerpc64-host KERNCONF=GENERIC64vtsc-NODEBUG TARGET=powerpc .if ${.MAKE.LEVEL} == 0 TARGET_ARCH=powerpc64 .export TARGET_ARCH .endif WITHOUT_CROSS_COMPILER= WITHOUT_CLANG_EXTRAS= WITH_FAST_DEPEND= WITH_LIBCPLUSPLUS= WITH_LIB32= WITH_BOOT= WITH_CLANG= WITH_CLANG_IS_CC= WITH_CLANG_FULL= WITH_LLDB= WITHOUT_GCC= WITHOUT_GNUCXX= NO_WERROR= MALLOC_PRODUCTION= WITH_DEBUG= WITH_DEBUG_FILES= CROSS_TOOLCHAIN=powerpc64-gcc .if ${.MAKE.LEVEL} == 0 CC=/usr/local/bin/gcc49 CXX=/usr/local/bin/g++49 CPP=/usr/local/bin/cpp49 .export CC .export CXX .export CPP .endif So WITH_LIBCPLUSPLUS. make.conf was empty. gcc49/g++49 had been built without 32 bit (lib32) support. gcc49 built powerpc64-gcc's update; the older powerpc64-gcc built gcc49. gcc 4.2.1 is/was not present. The kernel configuration turns on both vt and sc and turns off ps3. -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-ppc@freebsd.org Mon Dec 21 22:41:00 2015 Return-Path: Delivered-To: freebsd-ppc@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 D4D4DA4EB04 for ; Mon, 21 Dec 2015 22:41:00 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (unknown [IPv6:2001:4060:1:1001::14:54]) (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 9E5A919C3 for ; Mon, 21 Dec 2015 22:41:00 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from [192.168.225.14] (dhclient-91-190-14-19.flashcable.ch [91.190.14.19]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by fgznet.ch (Postfix) with ESMTPS id 4C9C1CEC75; Mon, 21 Dec 2015 23:40:49 +0100 (CET) Subject: Re: gcc5 caused an unexpected error for 128 bit floating point numbers To: Jukka Ukkonen , FreeBSD PowerPC ML References: <56767FEB.1080303@gmail.com> From: Andreas Tobler Message-ID: <56787FF0.40102@fgznet.ch> Date: Mon, 21 Dec 2015 23:40:48 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <56767FEB.1080303@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 127.0.1.1 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2015 22:41:00 -0000 On 20.12.15 11:16, Jukka Ukkonen wrote: > > Hello all, > > I installed gcc5 from ports (gcc5-5.3.0) expecting it to be > able to handle 128 bit floating point numbers on ppc64. > It turns out, this does not work quite right. Apparently gcc5 > tries to compile any basic 128 bit floating point operations > to calls to functions like __gcc_qmul, _gcc_qdiv, etc. > If such function wrappers are used at all, I guess they should > be implemented as inline assebler wrappers or something instead > of genuine functions, right? The support for soft float128 is not implemented yet. I excluded the functionality at the time I did the port. I'll revisit. Real float128 support requires a VSX capable cpu, power7+ and up. And this is work in progress on the gcc side. In theory it might be possible to tweak altivec to achive the same but this is not on my top list until reality has settled down, iow until real float128 has entered gcc land and this will happen earliest with gcc-7. Andreas From owner-freebsd-ppc@freebsd.org Tue Dec 22 10:50:34 2015 Return-Path: Delivered-To: freebsd-ppc@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 E8AF7A4F46E for ; Tue, 22 Dec 2015 10:50:33 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9253F1A65 for ; Tue, 22 Dec 2015 10:50:32 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3pPvR74VzQz1cXL0 for ; Tue, 22 Dec 2015 11:43:47 +0100 (CET) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id cc58KPKeLyG7 for ; Tue, 22 Dec 2015 11:43:47 +0100 (CET) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3pPvR73fpRz1cXKx for ; Tue, 22 Dec 2015 11:43:47 +0100 (CET) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 2F26D1B7483 for ; Tue, 22 Dec 2015 11:43:46 +0100 (CET) Date: Tue, 22 Dec 2015 11:36:07 +0100 From: Luciano Mannucci To: FreeBSD PowerPC ML Subject: IBM KVM on Power 8 again - tried 11 20151217-r292413 X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3pPvR73fpRz1cXKx@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2015 10:50:34 -0000 I'm still trying to install a freebsd on my Power 8 under quemu. The last snapshot gives me: SCSI: Looking for devices 8001000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.3." 8000000000000000 DISK : "QEMU QEMU HARDDISK 2.3." Populating /vdevice/vty@30000000 Populating /vdevice/nvram@71000000 Populating /pci@800000020000000 00 1800 (D) : 1af4 1002 unknown-legacy-device* 00 1000 (D) : 106b 003f serial bus [ usb-ohci ] 00 0800 (D) : 10ec 8139 network [ ethernet ] No NVRAM common partition, re-initializing... Scanning USB OHCI: initializing USB Keyboard USB mouse Using default console: /vdevice/vty@30000000 Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /vdevice/v-scsi@2000/disk@8001000000000000 ... Successfully loaded Consoles: Open Firmware console FreeBSD/powerpc64 Open Firmware loader, Revision 0.1 (root@releng2.nyi.freebsd.org, Fri Dec 18 03:58:11 UTC 2015) Memory: 1048576KB Booted from: /vdevice/v-scsi@2000/disk@8001000000000000 Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0xe49048+0x41ab78 syms=[0x8+0x143700+0x8+0x1402cb] \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Kernel entry at 0x102590 ... KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2015 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-CURRENT #0 r292413: Fri Dec 18 04:07:25 UTC 2015 root@releng2.nyi.freebsd.org:/usr/obj/powerpc.powerpc64/usr/src/sys/GENERIC64 powerpc gcc version 4.2.1 20070831 patched [FreeBSD] WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. cpu0: IBM POWER8E revision 2.1, 3425.00 MHz cpu0: Features dc000080 real memory = 1036713984 (988 MB) avail memory = 945573888 (901 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0: dev=3e5e0070 (BSP) random: entropy device external interface kbd0 at kbdmux0 ofwbus0: on nexus0 xicp0: on ofwbus0 cpulist0: on ofwbus0 cpu0: on cpulist0 cpu1: on cpulist0 pcib0: on ofwbus0 pci0: on pcib0 pci0: at device 3.0 (no driver attached) ohci0: mem 0xc0000000-0xc00000ff irq 4100 at device 2.0 on pci0 usbus0 on ohci0 re0: port 0x100-0x1ff mem 0xc0000100-0xc00001ff irq 4099 at device 1.0 on pci0 re0: Chip rev. 0x74800000 re0: MAC rev. 0x00000000 miibus0: on re0 rlphy0: PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow re0: Using defaults for TSO: 65518/35/2048 re0: Ethernet address: 52:54:00:b7:48:dc rtas0: on ofwbus0 vdevice0: on ofwbus0 vscsi0: irq 16781319 on vdevice0 vscsi0: Queue depth 22 commands uart0: irq 16781320 on vdevice0 Timecounter "timebase" frequency 512000000 Hz quality 0 Event timer "decrementer" frequency 512000000 Hz quality 1000 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 cd0 at vscsi0 bus 0 scbus0 target 0 lun 1 cugen0.1: at usbus0 uhub0: on usbus0 d0: Removable CD-ROM SPC-3 SCSI device cd0: 150.000MB/s transfers cd0: 643MB (329505 2048 byte sectors) da0 at vscsi0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SPC-3 SCSI device da0: 150.000MB/s transfers da0: 20480MB (41943040 512 byte sectors) SMP: AP CPU #8 launched WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from cd9660:/dev/iso9660/11_0_CURRENT_POWERPC64_CD [ro]... lock order reversal: 1st 0xc000000000055e40 bufwait (bufwait) @ /usr/src/sys/vm/vm_pager.c:380 2nd 0x47139a0 isofs (isofs) @ /usr/src/sys/kern/imgact_elf.c:877 stack backtrace: #0 0x5c5f10 at ??+0 #1 0x529784 at ??+0 #2 0x617264 at ??+0 #3 0x8a968c at ??+0 #4 0x63e3c8 at ??+0 #5 0x4df950 at ??+0 #6 0x50b810 at ??+0 #7 0x50c900 at ??+0 #8 0x4e499c at ??+0 #9 0x510be4 at ??+0 #10 0x88c650 at ??+0 #11 0x88c524 at ??+0 userret: returning with the following locks held: exclusive lockmgr bufwait (bufwait) r = 0 (0xc0000000000557b0) locked @ /usr/src/sys/vm/vm_pager.c:380 exclusive lockmgr bufwait (bufwait) r = 0 (0xc0000000000559e0) locked @ /usr/src/sys/vm/vm_pager.c:380 exclusive lockmgr bufwait (bufwait) r =uhub0: 3 ports with 3 removable, self powered 0 (0xc000000000055c10) locked @ /usr/src/sys/vm/vm_pager.c:380 exclusive lockmgr bufwait (bufwait) r = 0 (0xc000000000055e40) locked @ /usr/src/sys/vm/vm_pager.c:380 timeout stopping cpus panic: witness_warn cpuid = 0 KDB: stack backtrace: 0xc00000002458b110: at .kdb_backtrace+0x5c 0xc00000002458b240: at .vpanic+0x190 0xc00000002458b300: at .kassert_panic+0x8c 0xc00000002458b3a0: at .witness_warn+0x25c 0xc00000002458b470: at .userret+0xe8 0xc00000002458b500: at .trap+0xe70 0xc00000002458b770: at .powerpc_interrupt+0x1e0 0xc00000002458b810: user DSI read trap @ 0x1011c810 by 0x100001f0: srr1=0x800000000000d032 r1=0xffffffffffffddb0 cr=0 xer=0 ctr=0 r2=0x10124810 sr=0x40000000 KDB: enter: panic [ thread pid 1 tid 100002 ] Stopped at .kdb_enter+0x60: ld r2, r1, 0x28, db> Where am I wrong? Thanks to everybody, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Tue Dec 22 15:31:18 2015 Return-Path: Delivered-To: freebsd-ppc@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 2F8F1A4F6AA for ; Tue, 22 Dec 2015 15:31:18 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1FED91948 for ; Tue, 22 Dec 2015 15:31:17 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net ([32.210.31.157]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id tBMFVDIM005590 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 22 Dec 2015 07:31:14 -0800 Subject: Re: IBM KVM on Power 8 again - tried 11 20151217-r292413 To: Luciano Mannucci , FreeBSD PowerPC ML References: <3pPvR73fpRz1cXKx@baobab.bilink.it> From: Nathan Whitehorn Message-ID: <56796CC0.8050103@freebsd.org> Date: Tue, 22 Dec 2015 07:31:12 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <3pPvR73fpRz1cXKx@baobab.bilink.it> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVYi1DR1kGgKC2m5go1QLxjoAeYGDGgYW5HWLFy1KySdh7XmNPTQShEoglAwSZ8J6zwuBeKB/MtcMYrnk1phtAjbBUUmJXKRAXU= X-Sonic-ID: C;Wr27CMGo5RGG4v8vZz0oYQ== M;AopVCcGo5RGG4v8vZz0oYQ== X-Spam-Flag: No X-Sonic-Spam-Details: 1.6/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2015 15:31:18 -0000 That's quite odd. Maybe that particular kernel had a regression? I just successfully installed the 20151130 snapshot. Have you tried that one? -Nathan On 12/22/15 02:36, Luciano Mannucci wrote: > I'm still trying to install a freebsd on my Power 8 under quemu. The > last snapshot gives me: > > SCSI: Looking for devices > 8001000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.3." > 8000000000000000 DISK : "QEMU QEMU HARDDISK 2.3." > Populating /vdevice/vty@30000000 > Populating /vdevice/nvram@71000000 > Populating /pci@800000020000000 > 00 1800 (D) : 1af4 1002 unknown-legacy-device* > 00 1000 (D) : 106b 003f serial bus [ usb-ohci ] > 00 0800 (D) : 10ec 8139 network [ ethernet ] > No NVRAM common partition, re-initializing... > Scanning USB > OHCI: initializing > USB Keyboard > USB mouse > Using default console: /vdevice/vty@30000000 > > Welcome to Open Firmware > > Copyright (c) 2004, 2011 IBM Corporation All rights reserved. > This program and the accompanying materials are made available > under the terms of the BSD License available at > http://www.opensource.org/licenses/bsd-license.php > > > Trying to load: from: /vdevice/v-scsi@2000/disk@8001000000000000 ... Successfully loaded > Consoles: Open Firmware console > > FreeBSD/powerpc64 Open Firmware loader, Revision 0.1 > (root@releng2.nyi.freebsd.org, Fri Dec 18 03:58:11 UTC 2015) > Memory: 1048576KB > Booted from: /vdevice/v-scsi@2000/disk@8001000000000000 > > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=0xe49048+0x41ab78 syms=[0x8+0x143700+0x8+0x1402cb] > \ > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Kernel entry at 0x102590 ... > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2015 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-CURRENT #0 r292413: Fri Dec 18 04:07:25 UTC 2015 > root@releng2.nyi.freebsd.org:/usr/obj/powerpc.powerpc64/usr/src/sys/GENERIC64 powerpc > gcc version 4.2.1 20070831 patched [FreeBSD] > WARNING: WITNESS option enabled, expect reduced performance. > VT: init without driver. > cpu0: IBM POWER8E revision 2.1, 3425.00 MHz > cpu0: Features dc000080 > real memory = 1036713984 (988 MB) > avail memory = 945573888 (901 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0: dev=3e5e0070 (BSP) > random: entropy device external interface > kbd0 at kbdmux0 > ofwbus0: on nexus0 > xicp0: on ofwbus0 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > cpu1: on cpulist0 > pcib0: on ofwbus0 > pci0: on pcib0 > pci0: at device 3.0 (no driver attached) > ohci0: mem 0xc0000000-0xc00000ff irq 4100 at device 2.0 on pci0 > usbus0 on ohci0 > re0: port 0x100-0x1ff mem 0xc0000100-0xc00001ff irq 4099 at device 1.0 on pci0 > re0: Chip rev. 0x74800000 > re0: MAC rev. 0x00000000 > miibus0: on re0 > rlphy0: PHY 0 on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > re0: Using defaults for TSO: 65518/35/2048 > re0: Ethernet address: 52:54:00:b7:48:dc > rtas0: on ofwbus0 > vdevice0: on ofwbus0 > vscsi0: irq 16781319 on vdevice0 > vscsi0: Queue depth 22 commands > uart0: irq 16781320 on vdevice0 > Timecounter "timebase" frequency 512000000 Hz quality 0 > Event timer "decrementer" frequency 512000000 Hz quality 1000 > Timecounters tick every 1.000 msec > usbus0: 12Mbps Full Speed USB v1.0 > cd0 at vscsi0 bus 0 scbus0 target 0 lun 1 > cugen0.1: at usbus0 > uhub0: on usbus0 > d0: Removable CD-ROM SPC-3 SCSI device > cd0: 150.000MB/s transfers > cd0: 643MB (329505 2048 byte sectors) > da0 at vscsi0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SPC-3 SCSI device > da0: 150.000MB/s transfers > da0: 20480MB (41943040 512 byte sectors) > SMP: AP CPU #8 launched > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from cd9660:/dev/iso9660/11_0_CURRENT_POWERPC64_CD [ro]... > lock order reversal: > 1st 0xc000000000055e40 bufwait (bufwait) @ /usr/src/sys/vm/vm_pager.c:380 > 2nd 0x47139a0 isofs (isofs) @ /usr/src/sys/kern/imgact_elf.c:877 > stack backtrace: > #0 0x5c5f10 at ??+0 > #1 0x529784 at ??+0 > #2 0x617264 at ??+0 > #3 0x8a968c at ??+0 > #4 0x63e3c8 at ??+0 > #5 0x4df950 at ??+0 > #6 0x50b810 at ??+0 > #7 0x50c900 at ??+0 > #8 0x4e499c at ??+0 > #9 0x510be4 at ??+0 > #10 0x88c650 at ??+0 > #11 0x88c524 at ??+0 > userret: returning with the following locks held: > exclusive lockmgr bufwait (bufwait) r = 0 (0xc0000000000557b0) locked @ /usr/src/sys/vm/vm_pager.c:380 > exclusive lockmgr bufwait (bufwait) r = 0 (0xc0000000000559e0) locked @ /usr/src/sys/vm/vm_pager.c:380 > exclusive lockmgr bufwait (bufwait) r =uhub0: 3 ports with 3 removable, self powered > 0 (0xc000000000055c10) locked @ /usr/src/sys/vm/vm_pager.c:380 > exclusive lockmgr bufwait (bufwait) r = 0 (0xc000000000055e40) locked @ /usr/src/sys/vm/vm_pager.c:380 > timeout stopping cpus > panic: witness_warn > cpuid = 0 > KDB: stack backtrace: > 0xc00000002458b110: at .kdb_backtrace+0x5c > 0xc00000002458b240: at .vpanic+0x190 > 0xc00000002458b300: at .kassert_panic+0x8c > 0xc00000002458b3a0: at .witness_warn+0x25c > 0xc00000002458b470: at .userret+0xe8 > 0xc00000002458b500: at .trap+0xe70 > 0xc00000002458b770: at .powerpc_interrupt+0x1e0 > 0xc00000002458b810: user DSI read trap @ 0x1011c810 by 0x100001f0: srr1=0x800000000000d032 > r1=0xffffffffffffddb0 cr=0 xer=0 ctr=0 r2=0x10124810 sr=0x40000000 > KDB: enter: panic > [ thread pid 1 tid 100002 ] > Stopped at .kdb_enter+0x60: ld r2, r1, 0x28, > db> > > Where am I wrong? > > Thanks to everybody, > > Luciano. From owner-freebsd-ppc@freebsd.org Tue Dec 22 16:44:33 2015 Return-Path: Delivered-To: freebsd-ppc@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 9C16BA4E04E for ; Tue, 22 Dec 2015 16:44:33 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 6133C14BB; Tue, 22 Dec 2015 16:44:33 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3pQ3RP0zqQzRRry; Tue, 22 Dec 2015 17:44:33 +0100 (CET) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id owtasSQrIRHS; Tue, 22 Dec 2015 17:44:33 +0100 (CET) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3pQ3RP0JrrzRRrx; Tue, 22 Dec 2015 17:44:33 +0100 (CET) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id C01F11B7580; Tue, 22 Dec 2015 17:44:31 +0100 (CET) Date: Tue, 22 Dec 2015 17:36:53 +0100 From: Luciano Mannucci To: Nathan Whitehorn Cc: FreeBSD PowerPC ML Subject: Re: IBM KVM on Power 8 again - tried 11 20151217-r292413 In-Reply-To: <56796CC0.8050103@freebsd.org> References: <3pPvR73fpRz1cXKx@baobab.bilink.it> <56796CC0.8050103@freebsd.org> X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3pQ3RP0JrrzRRrx@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2015 16:44:33 -0000 On Tue, 22 Dec 2015 07:31:12 -0800 Nathan Whitehorn wrote: > That's quite odd. Maybe that particular kernel had a regression? I just > successfully installed the 20151130 snapshot. Have you tried that one? Yes. This one installs flawlessly. After that, the next boot gives me: Trying to load: from: /vdevice/v-scsi@2000/disk@8000000000000000 ... E3404: Not a bootable device! Well, I don'nt know which format scheme I should use (MBR? GPT?...) Or maybe there is a problem with the qcow2 format... Any hints? Thanks again, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Tue Dec 22 17:47:58 2015 Return-Path: Delivered-To: freebsd-ppc@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 5F4F7A4F79E for ; Tue, 22 Dec 2015 17:47:58 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ED031284 for ; Tue, 22 Dec 2015 17:47:58 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net ([32.210.31.157]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id tBMHlsOb017708 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 22 Dec 2015 09:47:55 -0800 Subject: Re: IBM KVM on Power 8 again - tried 11 20151217-r292413 To: Luciano Mannucci References: <3pPvR73fpRz1cXKx@baobab.bilink.it> <56796CC0.8050103@freebsd.org> <3pQ3RP0JrrzRRrx@baobab.bilink.it> Cc: FreeBSD PowerPC ML From: Nathan Whitehorn Message-ID: <56798CCA.5080308@freebsd.org> Date: Tue, 22 Dec 2015 09:47:54 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <3pQ3RP0JrrzRRrx@baobab.bilink.it> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVb6hZhYJI0C+q1CZKGoYKM63uKJHdpPMLhlPDQRZIdZKml2fOnjaVHTw8XaAo63JiVDJsSH2GBx5TJWKdM/mB4xchZLSwIKCE0= X-Sonic-ID: C;HpA6IdSo5RGoNP8vZz0oYQ== M;pibLIdSo5RGoNP8vZz0oYQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2015 17:47:58 -0000 On 12/22/15 08:36, Luciano Mannucci wrote: > On Tue, 22 Dec 2015 07:31:12 -0800 > Nathan Whitehorn wrote: > >> That's quite odd. Maybe that particular kernel had a regression? I just >> successfully installed the 20151130 snapshot. Have you tried that one? > Yes. > This one installs flawlessly. After that, the next boot gives me: Interesting. I'll try to see what happened with the 1215 one. The most recent -CURRENT from source also seems to work, so perhaps the snapshot builds had the misfortune of catching a transient problem. > Trying to load: from: /vdevice/v-scsi@2000/disk@8000000000000000 ... > E3404: Not a bootable device! > > Well, I don'nt know which format scheme I should use (MBR? GPT?...) > Or maybe there is a problem with the qcow2 format... Interesting. You should use the default MBR formatting in the installer. That will create a prep-boot partition and a bsdlabel in a subsequent partition, in which / must be first. This error indicates that the firmware could not locate the prep-boot partition. -Nathan > Any hints? > > Thanks again, > > Luciano. From owner-freebsd-ppc@freebsd.org Tue Dec 22 19:51:21 2015 Return-Path: Delivered-To: freebsd-ppc@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 1B9B9A4FD49 for ; Tue, 22 Dec 2015 19:51:21 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id D200D1596 for ; Tue, 22 Dec 2015 19:51:20 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 48E0B20B4B55 for ; Wed, 23 Dec 2015 05:51:18 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 423B12811A4 for ; Wed, 23 Dec 2015 05:51:18 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gD4g0V7g1uUg for ; Wed, 23 Dec 2015 05:51:18 +1000 (AEST) Received: from Peters-MacBook-Pro.local (unknown [101.165.8.192]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id A6807280F61; Wed, 23 Dec 2015 05:51:15 +1000 (AEST) Subject: Re: IBM KVM on Power 8 again - tried 11 20151217-r292413 To: Nathan Whitehorn , Luciano Mannucci References: <3pPvR73fpRz1cXKx@baobab.bilink.it> <56796CC0.8050103@freebsd.org> <3pQ3RP0JrrzRRrx@baobab.bilink.it> <56798CCA.5080308@freebsd.org> Cc: FreeBSD PowerPC ML From: Peter Grehan Message-ID: <5679A9B3.7050705@freebsd.org> Date: Wed, 23 Dec 2015 05:51:15 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <56798CCA.5080308@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=B9IZqLZM c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=cruUJTHX6diKK6SHAlbU8Q==:17 a=3FMX7HLxAAAA:8 a=6I5d2MoRAAAA:8 a=N659UExz7-8A:10 a=wUQvQvOEmiQA:10 a=wh7CRmdp3c3lKdbTG_UA:9 a=pILNOxqGKmIA:10 a=AFPkJ8gyYzwA:10 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2015 19:51:21 -0000 > Interesting. I'll try to see what happened with the 1215 one. The most > recent -CURRENT from source also seems to work, so perhaps the snapshot > builds had the misfortune of catching a transient problem. Yes - same issue with the amd64 snapshot. later, Peter. From owner-freebsd-ppc@freebsd.org Mon Dec 21 17:30:58 2015 Return-Path: Delivered-To: freebsd-ppc@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 CDCA1A4EC95; Mon, 21 Dec 2015 17:30:58 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x244.google.com (mail-vk0-x244.google.com [IPv6:2607:f8b0:400c:c05::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 8F01E182D; Mon, 21 Dec 2015 17:30:58 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by mail-vk0-x244.google.com with SMTP id a185so5817766vkb.3; Mon, 21 Dec 2015 09:30:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=79QS0nvNWkx/1hvauOOYRkzEMpfKdHyXk2vDS9eZpwc=; b=0Aeo7HSWh3jL/9AvU4W54QldTdxcrRecAJ4aX7svkMZ41tt4ubU0O4AG2DIz9y4XEU sqE3EzXz3C8rPpHemV+9VL4u++Prk2bF7UekcSIoyzyfyptaClRk1srK6Mm/up+pm3rf veFVajTD6kdlZADYEVJRCTk46QVCsA/vfq5g/Q2tBCkw03gyssDTLB4qbgCq6K6y4YOF ZXMRA736KHCQJ7rTonLtKHEVeUvQ6rLqa9dU3Rst36VFvJomYlBd5zUO7WRkRrW7nbfC ptUZ5UFRBxEp+UWZ7bn6S96b6PUNMutm9QpompGxYUtQnosemxNriCrCYNtcSwD+UVah XNIw== MIME-Version: 1.0 X-Received: by 10.31.132.140 with SMTP id g134mr12980449vkd.94.1450719057500; Mon, 21 Dec 2015 09:30:57 -0800 (PST) Received: by 10.103.9.195 with HTTP; Mon, 21 Dec 2015 09:30:57 -0800 (PST) Date: Mon, 21 Dec 2015 12:30:57 -0500 Message-ID: Subject: Pardon the interruption. From: Joe Nosay To: NGie Cooper , NGie Cooper , Dru Lavigne , dru@freebsd.org, team@powerpc-notebook.org, Debian powerpc Mailinglist , FreeBSD PowerPC ML , FreeBSD Hackers , Nathan Whitehorn , Tomasz CEDRO , freebsd-current X-Mailman-Approved-At: Tue, 22 Dec 2015 21:28:47 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2015 17:30:58 -0000 Let's find out exactly what the laptop project needs and work from there. I have some ideas on using it for accessibility and creativity. There needs to be a working prototype - a few actually - for developers to build the systems. Have someone put together a model and we can work from there. From owner-freebsd-ppc@freebsd.org Mon Dec 21 17:49:14 2015 Return-Path: Delivered-To: freebsd-ppc@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 398A2A4D948; Mon, 21 Dec 2015 17:49:14 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x244.google.com (mail-vk0-x244.google.com [IPv6:2607:f8b0:400c:c05::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 ECA3A112A; Mon, 21 Dec 2015 17:49:13 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by mail-vk0-x244.google.com with SMTP id a188so9239535vkc.1; Mon, 21 Dec 2015 09:49:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Kyx2Ws9mlCmruFb15KUb7Gm9fYdCgMiT2OYWatzMal8=; b=PdgJa56eAKMowR001maeRebIz6lw7ABuYZ18HUjzgQctnfpFHqBQYaBRKyP9sbHwTH KQlFZaTF+lEjzC84WHVVV2QIj7Q1Io69kXLGMB3oGq3mKYK1i+FK/JjouCktOlLQPtd2 SuuxozlEqwcy1km7GXzOGKsXeypGOjqGBMl4ZUbV7MLbzXBoZ1AeK4rvsce08mazhngI aOxVsWEzxlDFR+T5UHRMoe14r0K+woTuH1jpubYQI9D/txWD/4iv8yh4UNx8LJdNGzn9 jALrrdQHBBzbZ3aI8FI6dG6STzXM+4S3bfaXd93gEXpVJWVWrXNoztoAAH/myASeXyiR nsJA== MIME-Version: 1.0 X-Received: by 10.31.132.140 with SMTP id g134mr13033520vkd.94.1450720153039; Mon, 21 Dec 2015 09:49:13 -0800 (PST) Received: by 10.103.9.195 with HTTP; Mon, 21 Dec 2015 09:49:12 -0800 (PST) In-Reply-To: References: Date: Mon, 21 Dec 2015 12:49:12 -0500 Message-ID: Subject: Re: Pardon the interruption. From: Joe Nosay To: NGie Cooper , NGie Cooper , Dru Lavigne , dru@freebsd.org, team@powerpc-notebook.org, Debian powerpc Mailinglist , FreeBSD PowerPC ML , FreeBSD Hackers , Nathan Whitehorn , Tomasz CEDRO , freebsd-current X-Mailman-Approved-At: Tue, 22 Dec 2015 21:28:47 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2015 17:49:14 -0000 Okay. Somebody needs to get a board and start building the actual laptop. www.nxp.com Since this is a crowd funding effort, it should be easy to have support. On Mon, Dec 21, 2015 at 12:30 PM, Joe Nosay wrote: > Let's find out exactly what the laptop project needs and work from there. > I have some ideas on using it for accessibility and creativity. There needs > to be a working prototype - a few actually - for developers to build the > systems. > Have someone put together a model and we can work from there. > From owner-freebsd-ppc@freebsd.org Wed Dec 23 08:13:29 2015 Return-Path: Delivered-To: freebsd-ppc@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 25ED7A4F5FA for ; Wed, 23 Dec 2015 08:13:29 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) (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 C100C1185 for ; Wed, 23 Dec 2015 08:13:28 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) X-MSFBL: eyJiIjoiNzRfOTFfODVfMjM4IiwiciI6ImZyZWVic2QtcHBjQGZyZWVic2Qub3Jn IiwiZyI6IlNuc3RlbGVjb21fZGVkaWNhdGVkX3Bvb2wifQ== Received: from [192.168.80.11] ([192.168.80.11:35025] helo=rs-ord-mta01-1.smtp.com) by rs-ord-mta04-3.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTP id 60/5C-03821-7A75A765; Wed, 23 Dec 2015 08:13:27 +0000 X-MSFBL: eyJyIjoiZnJlZWJzZC1wcGNAZnJlZWJzZC5vcmciLCJiIjoiU25zdGVsZWNvbV9k ZWRpY2F0ZWRfcG9vbCIsImciOiJTbnN0ZWxlY29tX2RlZGljYXRlZF9wb29sIn0= DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple; q=dns/txt; i=@smtp.com; t=1450858407; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=n8eCxJzkq2gu/xO+Q9TwqSrKrpdve/JvJF2mUI57DDM=; b=f5GeAfs1AsweBu+ONiMQuFyiXsLnx2Z9h6SEXi268d+8VKVax2h/KNQWLYBJppSU dFEGZj9+tjic3VZVJAb26yts+aSky3+NqG3P4u/cqyhHjVMmF+y851WyP+jnUMit r148CRfE0+JOfnYZjAeLqlZqorx2Ger6tLGZPHxafdI=; Received: from [154.20.125.37] ([154.20.125.37:41618] helo=d154-20-125-37.bchsia.telus.net) by rs-ord-mta01-1.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id D6/32-23888-7A75A765; Wed, 23 Dec 2015 08:13:27 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snscommunication.com To: freebsd-ppc@freebsd.org Subject: The mHealth (Mobile Healthcare) Ecosystem: 2015 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Wed, 23 Dec 2015 00:13:22 -0800 Message-ID: <802041672653688001919@Ankur> X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com X-SMTPCOM-Tracking-Number: 17c2e76a-9e0b-4582-969c-f9069e5e4fbf X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2015 08:13:29 -0000 The LPWA (Low Power Wide Area) Networks Ecosystem: 2015 =96 2030 =96 Opport= unities, Challenges, Strategies, Industry Verticals & Forecasts Hello=20 Hope you are doing well.=20 I wanted to bring to your attention the latest SNS Research report in which= you might be interested, " The mHealth (Mobile Healthcare) Ecosystem: 2015= =96 2030 =96 Opportunities, Challenges, Strategies & Forecasts."=20 I believe this report will be highly applicable for you. If you would like = to see the report sample or have any questions, please let me know. =20 Report Information: Release Date: September 2015 Number of Pages: 359 Number of Tables and Figures: 105 Report Overview: With more than 7 Billion mobile network subscriptions worldwide, the mobile= communications sector is rapidly gaining traction from a diverse range of = vertical sectors. Healthcare is no exception to this trend.=20 As healthcare providers seek to maximize their patient outreach while minim= izing costs, many view mobile healthcare (or mHealth) as the solution to im= prove healthcare cost=96efficiency.mHealth refers to the usage of mobile co= mmunications technology & devices to enhance access to healthcare informati= on, improve distribution of routine and emergency health services and provi= de diagnostic services. Mobile network operators also view mHealth as a lucrative opportunity for t= he monetization of their mobile connectivity services as a growing proporti= on of their subscribers adopt healthcare centric wearables. Given that mos= t operators have established themselves as reputable consumer brands, they = are also eyeing on opportunities to offer services beyond simple connectivi= ty. Many operators already offer branded or co-branded end-to-end mHealth s= olutions to their customer bases.=20 In addition, mHealth offers a multitude to opportunities to the pharmaceuti= cal industry ranging from R&D activities to securing the supply chain and, = in the battle against counterfeit drugs. Driven by the thriving ecosystem, SNS Research estimates that the mHealth m= arket will account for nearly $18 Billion in 2016 alone. Despite barriers r= elating to regulation, patient acceptance and privacy concerns, SNS Researc= h estimates further growth at a CAGR of 40% over the next 5 years. The =93mHealth (Mobile Healthcare) Ecosystem: 2015 =96 2030 =96 Opportuniti= es, Challenges, Strategies & Forecasts=93 report presents an in=96depth as= sessment of the global mHealth market. In addition to covering key market d= rivers, challenges, future roadmap, value chain analysis, deployment case s= tudies, service/product strategies and strategic recommendations, the repor= t also presents comprehensive forecasts for the mHealth market from 2015 ti= ll 2030. The forecasts and historical revenue figures are individually segm= ented for 5 individual submarkets, 29 use case categories, 5 ecosystem play= er categories, 6 geographical regions and 34 countries. The report comes with an associated Excel datasheet suite covering quantita= tive data from all numeric forecasts presented in the report. =20 Key Findings: The report has the following key findings Driven by the thriving ecosystem, SNS Research estimates that the mHealth m= arket will account for over $18 Billion in 2016 alone Despite barriers relating to regulation, patient acceptance and privacy con= cerns, SNS Research estimates further growth at a CAGR of 40% over the next= 5 years SNS Research estimates that mHealth centric wearable devices will account f= or over 130 Million unit shipments by the end of 2020. In order to gain val= uable insights from the data generated by these devices, healthcare provide= rs and other stakeholders are increasingly investing in Big Data and analyt= ics technology SNS Research estimates that Big Data and analytics technology investments i= n the healthcare sector will account for over $4 Billion by 2020, following= a CAGR of over 14% between 2015 and 2020 In a bid to reduce error rates and enhance patient monitoring, pharmaceutic= al companies are increasingly incorporating smartphone and tablet based mon= itoring apps in their clinical trials mHealth has the potential to dramatically reduce the costs of healthcare op= erations, while improving the quality of healthcare. SNS Research estimates= that by the end of 2016, mHealth could represent up to $340 Billion in ann= ual healthcare cost savings worldwide Topics Covered: The report covers the following topics: The scope and implementation of mHealth across the globe mHealth technology Market drivers and key benefits of mHealth Challenges and inhibitors to the mHealth ecosystem mHealth standardization and regulatory initiatives mHealth opportunities, use cases and applications mHealth deployment case studies Value chain analysis of the mHealth ecosystem and the recognition of key pl= ayers in each segment of the value chain mHealth industry roadmap: 2015 =96 2030 Key trends in the mHealth ecosystem; mHealth regulation & security, adoptio= n of cloud based mHealth services, alliances for ecosystem fortification, a= nd the impact of LTE deployments The role of M2M and wearable technology in the mHealth ecosystem =20 Profiles and strategies of over 200 ecosystem players Strategic recommendations for mobile network operators, wireless infrastruc= ture/device OEMs, application developers, healthcare service providers & ph= armaceutical companies to capitalize on the mHealth opportunity In-depth analysis for 5 individual submarkets and their associated mHealth = application use cases:=20 Pharmaceutical Applications Medical Information & Healthcare Management Healthcare & Fitness Remote Consultation/Diagnostic Services M2M, Wearable Technology, Sensor & Monitoring Applications=20 Historical revenue figures and forecasts till 2030 Forecast Segmentation: Market forecasts and historical revenue figures are provided for each of th= e following 5 submarkets and their 23 use case categories: Pharmaceutical Applications Safety Data Collection Consumer Education Medical Education Post=96Market Monitoring Drug Authentication Social Media Patient Compliance & Retention: Clinical Trials Information & Healthcare Management Electronic Health/Medical Records & Tracking Tools Diagnostic Tools & Medical Reference Continuing Medical Education Awareness Through Alerts Logistical & Payment Support Healthcare & Fitness Medical Compliance Fitness & Nutrition Apps Clinical Decision Support Systems Prescribable Mobile Apps Remote Consultation/Diagnostic Services Mobile Video Consultations, Collaboration & Surgery Non-Video Consultations & Collaboration Remote Collaboration in Emergency Situations M2M, Wearable Technology, Sensor & Monitoring Applications Health and Wellness Monitoring Disease Surveillance/Remote Monitoring Diagnostic Tools Technical Logistics Revenue is also split by ecosystem player: Ecosystem Player Mobile Network Operators/Connectivity Providers Mobile & mHealth Device OEMs Content & Application Providers Healthcare Service Providers Pharmaceutical Industry The following regional and country markets are also covered: Regional Markets Asia Pacific Eastern Europe Latin & Central America Middle East & Africa North America Western Europe Country Markets Argentina, Australia, Brazil, Canada, China, Czech Republic, Denmark, Finla= nd, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mex= ico, Norway, Pakistan, Philippines, Poland, Qatar, Russia, Saudi Arabia, Si= ngapore, South Africa, South Korea, Spain, Sweden, Taiwan, Thailand, UAE, U= K, USA Additional forecasts are provided for the following: Wireless M2M connections for the mHealth vertical mHealth centric wearable device shipments Mobile video calling users Annual throughput of mobile network data traffic Smartphone, feature phone, tablet, desktop PC and notebook shipments Mobile network subscriptions by region Cost saving potential of mHealth by region Big Data & analytics technology investments in the healthcare sector Key Questions Answered: The report provides answers to the following key questions: What are the key market drivers and challenges for the mHealth ecosystem=3F What are the key applications of mHealth=3F How is the mHealth value chain structured and how will it evolve overtime=3F What opportunities does mHealth offer to mobile network operators, healthca= re service providers, pharmaceutical companies and other players in the val= ue chain=3F What strategies should mobile network operators, wireless infrastructure & = device OEMs, healthcare service providers, pharmaceutical companies and app= lication developers adopt to capitalize on the mHealth opportunity=3F How big is the mHealth market, and how much revenue will it generate in 202= 0=3F What will be the installed base of mHealth M2M connections in 2020=3F How many mHealth centric wearable devices will be shipped in 2020=3F What particular submarkets does the mHealth ecosystem constitute=3F What geographical regions, countries and submarkets offer the greatest grow= th potential for mHealth=3F Who are the key players in the mHealth market=3F What level of cost savings can mHealth facilitate for healthcare service pr= oviders in each region=3F What are the key applications of LTE in the mHealth market=3F What considerations should be taken into account to devise a successful mHe= althstrategy for a hospital=3F Report Pricing: Single User License: USD 2,500 Company Wide License: USD 3,500 Ordering Process: Please contact Andy Silva on andy.silva@snscommunication.com Provide the following information: 1. Report Title - 2. Report License - (Single User/Company Wide) 3. Name - 4. Email - 5. Job Title - 6. Company - 7. Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents and List of figures mentioned below for your better inside. I look forward to hearing from you. Kind Regards Andy Silva Marketing Executive Signals and Systems Telecom Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 ___________________________________________________________________________= __________________________________________________________________________ =20 Table of Content =20 1.1 Topics Covered 1.2 Forecast Segmentation 1.3 Key Questions Answered 1.4 Key Findings 1.5 Methodology 1.6 Target Audience 1.7 Companies & Organizations Mentioned =20 Chapter 2: An Overview of mHealth 2.1 What is mHealth=3F 2.2 The Evolution from eHealth to mHealth 2.3 Telemedicine 2.4 Health Informatics 2.5 The mHealth Business Case 2.6 Key Market Drivers 2.6.1 Increasing Penetration of Smartphones, Tablets & Wearables 2.6.2 Proliferation of Mobile Broadband Networks 2.6.3 The Rise of Chronic Diseases 2.6.4 Growing mHealth Applications: Reduction in Lead Time 2.6.5 Government & Regulatory Initiatives 2.6.6 Physicians at Forefront of Mobility Adoption 2.6.7 The Cost Saving Potential of mHealth 2.6.8 Increasing Adoption of Open Source Software 2.6.9 The Role of Developed Economies 2.6.10 The Role of Emerging Economies 2.7 Barriers to Growth 2.7.1 Security/Privacy Concerns & Absence of Legal Guidelines 2.7.2 Regulation & Efficacy of Applications 2.7.3 Operational Maintenance & Control 2.7.4 Human Behavior: Disbelief among Patients 2.7.5 Lack of Clear mHealth Strategies 2.7.6 Funding Challenges 2.8 mHealth Technologies 2.8.1 Smartphones & Tablets 2.8.2 Mobile Apps 2.8.3 Mobile Broadband: The LTE Era 2.8.4 Wearable Body Sensors 2.8.5 M2M Technology 2.8.6 Mobile Video Calling 2.9 mHealth Use Case Categories 2.9.1 Pharmaceutical Applications 2.9.2 Medical Information & Healthcare Management 2.9.3 Healthcare & Fitness 2.9.4 Remote Consultation/Diagnostic Services 2.9.5 M2M, Wearable Technology, Sensor & Monitoring Applications =20 Chapter 3: mHealth Value Chain and Industry Roadmap 3.1 The mHealth Value Chain 3.1.1 Mobile/mHealth Device, Chipset & Infrastructure OEMs 3.1.2 Mobile Network Operators 3.1.3 Healthcare Professionals & Providers 3.1.4 Insurers and Government Health Systems 3.1.5 The Pharmaceutical Industry 3.1.6 Application Developers & Integrators 3.1.7 Patients 3.2 The mHealth Industry Roadmap: 2015 =96 2030 3.2.1 2015 =96 2020: Commercialization of Consumer Centric mHealth Apps &= Devices 3.2.2 2020 =96 2025: Large Scale Proliferation of Remote Video Consultati= ons & Advanced Apps 3.2.3 2025 =96 2030: The Era of mHealth Analytics =20 Chapter 4: mHealth Use Cases 4.1 Pharmaceutical Applications 4.1.1 Safety Data Collection 4.1.2 Consumer Education 4.1.3 Medical Education 4.1.4 Post=96Market Monitoring 4.1.5 Drug Authentication 4.1.6 Social Media 4.1.7 Patient Compliance & Retention: Clinical Trials 4.2 Medical Information & Healthcare Management 4.2.1 Electronic Health/Medical Records & Tracking Tools 4.2.2 Diagnostic Tools & Medical Reference 4.2.3 Continuing Medical Education 4.2.4 Awareness through Alerts 4.2.5 Logistical & Payment Support 4.3 Healthcare & Fitness 4.3.1 Medical Compliance 4.3.2 Fitness & Nutrition Apps 4.3.3 Clinical Decision Support Systems 4.3.4 Prescribable Mobile Apps 4.4 Remote Consultation/Diagnostics Services 4.4.1 Mobile Video Consultations, Collaboration & Surgery 4.4.2 Non=96Video Consultations & Collaboration 4.4.3 Remote Collaboration in Emergency Situations 4.5 M2M, Wearable Technology, Sensor & Monitoring Applications 4.5.1 Health & Wellness Monitoring 4.5.2 Disease Surveillance/Remote Monitoring 4.5.3 Diagnostic Tools 4.5.4 Technical Logistics =20 Chapter 5: mHealth Deployment Case Studies 5.1 Apollo Hospitals Group: Enabling mHealth for the Masses 5.2 AT&T: Connected Healthcare Monitoring for the Elderly 5.3 London Air Ambulance: Utilizing EE=92s 4G LTE Network to Power Navigati= on 5.4 Novartis: Clinical Trials of the Future 5.5 Orange Healthcare: Fighting Counterfeit Drugs using SMS Technology 5.6 Praekelt Foundation: HIV/AIDS Awareness Campaign 5.7 Qualcomm: 3G=96Enabled Kit for Monitoring Asthmatic Children 5.8 Roche: Powering Clinical Trials with Smartphones 5.9 Verizon: Cloud Based Healthcare Management 5.10 WellDoc: Managing Chronic Diseases using Mobile Apps =20 Chapter 6: mHealth Solution Provider Profiles 6.1 270 Vision 6.2 3L Labs 6.3 3M 6.4 4DForce 6.5 4iii Innovations 6.6 Adidas 6.7 Aerotel Medical Systems 6.8 Aetna 6.9 AGFA Healthcare 6.10 AirStrip Technologies 6.11 Alego Health 6.12 Alivecor 6.13 AllScripts Healthcare Solutions 6.14 AMD Global Telemedicine 6.15 Amiigo 6.16 Apple 6.17 Asics 6.18 AT&T 6.19 Atlas Wearables 6.20 AthenaHealth 6.21 Augmendix 6.22 BettrLife 6.23 Bionym 6.24 Biosensics 6.25 Boston Scientific 6.26 Breakthrough Technologies 6.27 Broadcom 6.28 BSX Athletics 6.29 BlackBerry 6.30 BTS Bioengineering 6.31 Cambridge Consultants 6.32 Cambridge Temperature Concepts 6.33 CardioComm Solutions 6.34 CardioNet 6.35 Carre Technologies 6.36 Catapult 6.37 CellTrust Corporation 6.38 Cerner Corporation 6.39 Chetu 6.40 Cisco Systems 6.41 Cityzen Sciences 6.42 Codoon 6.43 Cyberdyne 6.44 DELTA 6.45 DT (Deutsche Telekom) 6.46 DocbookMD 6.47 DorsaVi (ASX) 6.48 Diversinet Corporation 6.49 Dreamtrap Commercials 6.50 EB Sport Group (Sync) 6.51 E=96Clinical Works 6.52 e=96Cycle 6.53 EdanSafe 6.54 Ekso Bionics 6.55 Emotiv Systems 6.56 Epic Systems Corporation 6.57 Epion Health 6.58 Epocrates (Part of Athena Health) 6.59 Ericsson 6.60 European Medical Network (Medical Network EMN AG) 6.61 Evena Medical 6.62 EWA Solutions AB 6.63 Extension Healthcare 6.64 Fatigue Science 6.65 Finis 6.66 Fitbit 6.67 Flyfit 6.68 Freescale Semiconductor 6.69 FRUCT MD 6.70 Garmin 6.71 Gemalto 6.72 GE Healthcare 6.73 Ginger.io 6.74 Google 6.75 GOQii 6.76 GSK (GlaxoSmithKline) 6.77 HealBe 6.78 HealthTechHatch 6.79 Honeywell Life Care Solutions 6.80 Hovding 6.81 HP 6.82 Huawei 6.83 i4C Innovations 6.84 IBM 6.85 ICEdot 6.86 Ideal Life 6.87 iHealth Lab 6.88 Imec 6.89 Imprivata 6.90 Integron Corporation 6.91 Intel Corporation 6.92 InteraXon 6.93 Intermountain Healthcare 6.94 InTouch Health 6.95 Instabeat 6.96 InvenSense 6.97 IQMax 6.98 iRhythm 6.99 Jawbone 6.100 Jaybird 6.101 Johnson & Johnson 6.102 KDDI Corporation 6.103 Ki Performance Lifestyle 6.104 KORE Telematics 6.105 Kreyos 6.106 Lark Technologies 6.107 Lechal 6.108 LG Electronics 6.109 Lumo BodyTech 6.110 Magellan (MiTAC Digital Corporation) 6.111 Medecin Direct 6.112 MedSignals 6.113 Medtronic 6.114 MedWeb 6.115 Melon 6.116 mHealthAlert 6.117 McKinsey & Company 6.118 Microsoft 6.119 Mio Global 6.120 Misfit Wearables 6.121 Moov 6.122 Moticon 6.123 Motion Computing 6.124 Motion Fitness 6.125 Motorola Mobility / Lenovo 6.126 Myontec 6.127 mQure 6.128 NeuroPro 6.129 Nike 6.130 Nonin Medical 6.131 Notch Interfaces 6.132 Novartis 6.133 NTT DoCoMo 6.134 Nuubo 6.135 NZN Labs 6.136 OnLine Tech 6.137 Omron Corporation 6.138 OMsignal 6.139 Optalert 6.140 Orange 6.141 Orpyx Medical Technologies 6.142 O=96Synce 6.143 Owlet Baby Care 6.144 Panasonic Corporation 6.145 Pharmica Consulting 6.146 Philips 6.147 Phyode 6.148 Polar Electro 6.149 Pragmasystems 6.150 Preventice 6.151 Proteus Digital Health 6.152 PUSH Design Solutions 6.153 Qardio 6.154 Qualcomm Life 6.155 Rest Devices 6.156 Roche Holding (F. Hoffmann-La Roche) 6.157 RSLSteeper 6.158 S3 Group 6.159 Samsung 6.160 Sanofi 6.161 Santech 6.162 SAP 6.163 SCOTTY Group 6.164 SenseCore 6.165 Sensible Baby 6.166 Senso Solutions 6.167 Sentimoto 6.168 Seraphim Sense 6.169 Siemens Healthcare 6.170 SK Telecom 6.171 Snaptracs 6.172 SoftBank Corporation 6.173 SoftServe 6.174 Somaxis 6.175 Sonitus Medical 6.176 Sony Corporation 6.177 Sotera Wireless 6.178 STMicroelectronics 6.179 Swissmed Mobile 6.180 Tactio Health Group 6.181 TCS (TeleCommunication Systems) 6.182 Telcare 6.183 Tele2 6.184 Telecom Italia 6.185 Telenor 6.186 TI (Texas Instruments) 6.187 Toshiba Corporation 6.188 Tunstall Healthcare 6.189 U-blox 6.190 Validic (Motivation Science) 6.191 Vancive Medical Technologies 6.192 Vodafone Group 6.193 Verizon 6.194 Vitaphone 6.195 Voxiva 6.196 Wearable Intelligence 6.197 Wellograph 6.198 WellDoc 6.199 Withings 6.200 Xiaomi 6.201 Zephyr Technology Corporation 6.202 Zinc Software 6.203 Zoll Medical Corporation 6.204 Others =20 Chapter 7: Standardization, Regulation & Development Initiatives 7.1 mHealth Alliance 7.2 GSMA=92s mHealth Program 7.3 Global mHealth Initiative 7.4 MRC (mHealth Regulatory Coalition) 7.5 WLSA (Wireless=96Life Services Alliance) 7.6 EuMHA (European mHealth Alliance) 7.7 mHealth Working Group 7.8 mHIMSS 7.9 Others 7.10 HIPAA and its Implications on mHealth =20 Chapter 8: Market Analysis & Forecasts 8.1 Global Outlook of mHealth Revenue: 2015 =96 2030 8.2 Submarket Segmentation 8.3 Pharmaceutical Applications Submarket Revenue: 2015 =96 2030 8.3.1 Safety Data Collection Use Case 8.3.2 Consumer Education Use Case 8.3.3 Medical Education Use Case 8.3.4 Post=96Market Monitoring Use Case 8.3.5 Drug Authentication Use Case 8.3.6 Social Media Use Case 8.3.7 Patient Compliance & Retention (Clinical Trials) Use Case 8.4 Medical Information & Healthcare Management Submarket Revenue: 2015 =96= 2030 8.4.1 Electronic Health/Medical Records & Tracking Tools Use Case 8.4.2 Diagnostic Tools & Medical Reference Use Case 8.4.3 Continuing Medical Education Use Case 8.4.4 Awareness through Alerts Use Case 8.4.5 Logistical & Payment Support Use Case 8.5 Healthcare & Fitness Submarket Revenue: 2015 =96 2030 8.5.1 Medical Compliance Use Case 8.5.2 Fitness & Nutrition Apps Use Case 8.5.3 Clinical Decision Support Systems Use Case 8.5.4 Prescribable Mobile Apps Use Case 8.6 Remote Consultation/Diagnostic Services Submarket Revenue: 2015 =96 2030 8.6.1 Mobile Video Consultations, Collaboration & Surgery Use Case 8.6.2 Non=96Video Consultations & Collaboration Use Case 8.6.3 Remote Collaboration in Emergency Situations Use Case 8.7 M2M, Wearable Technology, Sensor & Monitoring Applications Submarket Re= venue: 2015 =96 2030 8.7.1 Health and Wellness Monitoring Use Case 8.7.2 Disease Surveillance/Remote Monitoring Use Case 8.7.3 Diagnostic Tools Use Case 8.7.4 Technical Logistics Use Case 8.8 Segmentation by Ecosystem Player 8.8.1 Mobile Network Operators/Connectivity Providers 8.8.2 Mobile & mHealth Device OEMs 8.8.3 Content & Application Providers 8.8.4 Healthcare Service Providers 8.8.5 Pharmaceutical Industry 8.9 Regional Outlook 8.10 Asia Pacific mHealth Revenue: 2015 =96 2030 8.10.1 Country Level Segmentation 8.10.2 Australia 8.10.3 China 8.10.4 India 8.10.5 Japan 8.10.6 South Korea 8.10.7 Pakistan 8.10.8 Thailand 8.10.9 Indonesia 8.10.10 Malaysia 8.10.11 Taiwan 8.10.12 Philippines 8.10.13 Singapore 8.10.14 Rest of Asia Pacific 8.11 Eastern Europe mHealth Revenue: 2015 =96 2030 8.11.1 Country Level Segmentation 8.11.2 Czech Republic 8.11.3 Poland 8.11.4 Russia 8.11.5 Rest of Eastern Europe 8.12 Latin & Central America mHealth Revenue: 2015 =96 2030 8.12.1 Country Level Segmentation 8.12.2 Argentina 8.12.3 Brazil 8.12.4 Mexico 8.12.5 Rest of Latin & Central America 8.13 Middle East & Africa mHealth Revenue: 2015 =96 2030 8.13.1 Country Level Segmentation 8.13.2 Israel 8.13.3 Qatar 8.13.4 Saudi Arabia 8.13.5 South Africa 8.13.6 UAE 8.13.7 Rest of the Middle East & Africa 8.14 North America mHealth Revenue: 2015 =96 2030 8.14.1 Country Level Segmentation 8.14.2 USA 8.14.3 Canada 8.15 Western Europe mHealth Revenue: 2015 =96 2030 8.15.1 Country Level Segmentation 8.15.2 Denmark 8.15.3 Finland 8.15.4 France 8.15.5 Germany 8.15.6 Italy 8.15.7 Spain 8.15.8 Sweden 8.15.9 Norway 8.15.10 UK 8.15.11 Rest of Western Europe =20 Chapter 9: Conclusion & Strategic Recommendations 9.1 Are Prescribable Mobile Apps a Threat to the Pharmaceutical Industry=3F 9.2 Will mHealth Requirements Drive HD Mobile Video Deployments=3F 9.3 Is mHealth Security an All=96or=96nothing Decision=3F 9.4 Healthcare Industry Approval & Accreditation: Key to Success 9.5 Maintenance of Low Costs 9.6 Increase of Operational Efficiency 9.7 Collaborations Help in Promoting mHealth 9.8 The Importance of End User Belief 9.9 Wearable Technology: Prospects in the mHealth Ecosystem 9.10 Are Mobile Network Operators Simply Connectivity Providers for mHealth=3F 9.11 Driving Investments in Big Data & Analytics 9.12 Implementing Successful mHealth Strategies in Hospitals 9.13 Strategic Recommendations 9.13.1 Recommendations for Mobile Network Operators 9.13.2 Recommendations for Wireless Infrastructure & Device OEMs 9.13.3 Recommendations for Application Developers 9.13.4 Recommendations for Healthcare Professionals and Providers 9.13.5 Recommendations for the Pharmaceutical Industry =20 List of Figures Figure 1: Global Connected Consumer Mobile Device vs. PC Shipments: 2015 = =96 2030 (Millions of Units) Figure 2: Mobile Network Subscriptions by Region: 2015 =96 2030 (Millions) Figure 3: Annual Global Throughput of Mobile Network Data Traffic by Region= : 2015 =96 2030 (Exabytes) Figure 4: Cost Saving Potential of mHealth by Region: 2015 =96 2030 ($ Mill= ion) Figure 5: M2M Architecture Figure 6: Global Wireless M2M Connections for mHealth Applications: 2015 = =96 2030 (Millions) Figure 7: Global Mobile Video Calling Users: 2015 =96 2030 (Millions) Figure 8: mHealth Use Case Categories Figure 9: The mHealth Value Chain Figure 10: mHealth Industry Roadmap: 2015 =96 2030 Figure 11: Global mHealth Revenue: 2015 =96 2030 ($ Million) Figure 12: Global mHealth Revenue by Submarket: 2015 =96 2030 ($ Million) Figure 13: Global Pharmaceutical Applications Submarket Revenue: 2015 =96 2= 030 ($ Million) Figure 14: Global Pharmaceutical Applications Submarket Revenue by Use Case= Category: 2015 =96 2030 ($ Million) Figure 15: Global Safety Data Collection Use Case Revenue: 2015 =96 2030 ($= Million) Figure 16: Global Consumer Education Use Case Revenue: 2015 =96 2030 ($ Mil= lion) Figure 17: Global Medical Education Use Case Revenue: 2015 =96 2030 ($ Mill= ion) Figure 18: Global Post=96Market Monitoring Use Case Revenue: 2015 =96 2030 = ($ Million) Figure 19: Global Drug Authentication Use Case Revenue: 2015 =96 2030 ($ Mi= llion) Figure 20: Global Social Media Use Case Revenue: 2015 =96 2030 ($ Million) Figure 21: Global Patient Compliance & Retention (Clinical Trials) Use Case= Revenue: 2015 =96 2030 ($ Million) Figure 22: Global Medical Information & Healthcare Management Submarket Rev= enue: 2015 =96 2030 ($ Million) Figure 23: Global Medical Information & Healthcare Management Submarket Rev= enue by Use Case Category: 2015 =96 2030 ($ Million) Figure 24: Global Electronic Health/Medical Records & Tracking Tools Use Ca= se Revenue: 2015 =96 2030 ($ Million) Figure 25: Global Diagnostic Tools & Medical Reference Use Case Revenue: 20= 15 =96 2030 ($ Million) Figure 26: Global Continuing Medical Education Use Case Revenue: 2015 =96 2= 030 ($ Million) Figure 27: Global Awareness through Alerts Use Case Revenue: 2015 =96 2030 = ($ Million) Figure 28: Global Logistical & Payment Support Use Case Revenue: 2015 =96 2= 030 ($ Million) Figure 29: Global Healthcare & Fitness Submarket Revenue: 2015 =96 2030 ($ = Million) Figure 30: Global Healthcare & Fitness Submarket Revenue by Use Case Catego= ry: 2015 =96 2030 ($ Million) Figure 31: Global Medical Compliance Use Case Revenue: 2015 =96 2030 ($ Mil= lion) Figure 32: Global Fitness & Nutrition Apps Use Case Revenue: 2015 =96 2030 = ($ Million) Figure 33: Global Clinical Decision Support Systems Use Case Revenue: 2015 = =96 2030 ($ Million) Figure 34: Global Prescribable Mobile Apps Use Case Revenue: 2015 =96 2030 = ($ Million) Figure 35: Global Remote Consultation/Diagnostic Services Submarket Revenue= : 2015 =96 2030 ($ Million) Figure 36: Global Remote Consultation/Diagnostic Services Submarket Revenue= by Use Case Category: 2015 =96 2030 ($ Million) Figure 37: Global Mobile Video Consultations, Collaboration & Surgery Use C= ase Revenue: 2015 =96 2030 ($ Million) Figure 38: Global Non=96Video Consultations & Collaboration Use Case Revenu= e: 2015 =96 2030 ($ Million) Figure 39: Global Remote Collaboration in Emergency Situations Use Case Rev= enue: 2015 =96 2030 ($ Million) Figure 40: Global M2M, Wearable Technology, Sensor & Monitoring Application= s Submarket Revenue: 2015 =96 2030 ($ Million) Figure 41: Global M2M, Wearable Technology, Sensor & Monitoring Application= s Submarket Revenue by Use Case Category: 2015 =96 2030 ($ Million) Figure 42: Global Health and Wellness Monitoring Use Case Revenue: 2015 =96= 2030 ($ Million) Figure 43: Global Disease Surveillance/Remote Monitoring Use Case Revenue: = 2015 =96 2030 ($ Million) Figure 44: Global Diagnostic Tools Use Case Revenue: 2015 =96 2030 ($ Milli= on) Figure 45: Global Technical Logistics Use Case Revenue: 2015 =96 2030 ($ Mi= llion) Figure 46: Global mHealth Revenue by Ecosystem Player: 2015 =96 2030 ($ Mil= lion) Figure 47: Global Mobile Network Operators/Connectivity Providers mHealth R= evenue: 2015 =96 2030 ($ Million) Figure 48: Global Mobile & mHealth Device OEMs Revenue: 2015 =96 2030 ($ Mi= llion) Figure 49: Global mHealth Content & Application Providers Revenue: 2015 =96= 2030 ($ Million) Figure 50: Global Healthcare Service Providers mHealth Revenue: 2015 =96 20= 30 ($ Million) Figure 51: Global Pharmaceutical Industry mHealth Revenue: 2015 =96 2030 ($= Million) Figure 52: mHealth Revenue by Region: 2015 =96 2030 ($ Million) Figure 53: Asia Pacific mHealth Revenue: 2015 =96 2030 ($ Million) Figure 54: Asia Pacific mHealth Revenue by Country: 2015 =96 2030 ($ Millio= n) Figure 55: Australia mHealth Revenue: 2015 =96 2030 ($ Million) Figure 56: China mHealth Revenue: 2015 =96 2030 ($ Million) Figure 57: India mHealth Revenue: 2015 =96 2030 ($ Million) Figure 58: Japan mHealth Revenue: 2015 =96 2030 ($ Million) Figure 59: South Korea mHealth Revenue: 2015 =96 2030 ($ Million) Figure 60: Pakistan mHealth Revenue: 2015 =96 2030 ($ Million) Figure 61: Thailand mHealth Revenue: 2015 =96 2030 ($ Million) Figure 62: Indonesia mHealth Revenue: 2015 =96 2030 ($ Million) Figure 63: Malaysia mHealth Revenue: 2015 =96 2030 ($ Million) Figure 64: Taiwan mHealth Revenue: 2015 =96 2030 ($ Million) Figure 65: Philippines mHealth Revenue: 2015 =96 2030 ($ Million) Figure 66: Philippines mHealth Revenue: 2015 =96 2030 ($ Million) Figure 67: mHealth Revenue in the Rest of Asia Pacific: 2015 =96 2030 ($ Mi= llion) Figure 68: Eastern Europe mHealth Revenue: 2015 =96 2030 ($ Million) Figure 69: Eastern Europe mHealth Revenue by Country: 2015 =96 2030 ($ Mill= ion) Figure 70: Czech Republic mHealth Revenue: 2015 =96 2030 ($ Million) Figure 71: Poland mHealth Revenue: 2015 =96 2030 ($ Million) Figure 72: Russia mHealth Revenue: 2015 =96 2030 ($ Million) Figure 73: mHealth Revenue in the Rest of Eastern Europe: 2015 =96 2030 ($ = Million) Figure 74: Latin & Central America mHealth Revenue: 2015 =96 2030 ($ Millio= n) Figure 75: Latin & Central America mHealth Revenue by Country: 2015 =96 203= 0 ($ Million) Figure 76: Argentina mHealth Revenue: 2015 =96 2030 ($ Million) Figure 77: Brazil mHealth Revenue: 2015 =96 2030 ($ Million) Figure 78: Mexico mHealth Revenue: 2015 =96 2030 ($ Million) Figure 79: mHealth Revenue in the Rest of Latin & Central America: 2015 =96= 2030 ($ Million) Figure 80: Middle East & Africa mHealth Revenue: 2015 =96 2030 ($ Million) Figure 81: Middle East & Africa mHealth Revenue by Country: 2015 =96 2030 (= $ Million) Figure 82: Israel mHealth Revenue: 2015 =96 2030 ($ Million) Figure 83: Qatar mHealth Revenue: 2015 =96 2030 ($ Million) Figure 84: Saudi Arabia mHealth Revenue: 2015 =96 2030 ($ Million) Figure 85: South Africa mHealth Revenue: 2015 =96 2030 ($ Million) Figure 86: UAE mHealth Revenue: 2015 =96 2030 ($ Million) Figure 87: mHealth Revenue in the Rest of the Middle East & Africa: 2015 = =96 2030 ($ Million) Figure 88: North America mHealth Revenue: 2015 =96 2030 ($ Million) Figure 89: North America mHealth Revenue by Country: 2015 =96 2030 ($ Milli= on) Figure 90: USA mHealth Revenue: 2015 =96 2030 ($ Million) Figure 91: Canada mHealth Revenue: 2015 =96 2030 ($ Million) Figure 92: Western Europe mHealth Revenue: 2015 =96 2030 ($ Million) Figure 93: Western Europe mHealth Revenue by Country: 2015 =96 2030 ($ Mill= ion) Figure 94: Denmark mHealth Revenue: 2015 =96 2030 ($ Million) Figure 95: Finland mHealth Revenue: 2015 =96 2030 ($ Million) Figure 96: France mHealth Revenue: 2015 =96 2030 ($ Million) Figure 97: Germany mHealth Revenue: 2015 =96 2030 ($ Million) Figure 98: Italy mHealth Revenue: 2015 =96 2030 ($ Million) Figure 99: Spain mHealth Revenue: 2015 =96 2030 ($ Million) Figure 100: Sweden mHealth Revenue: 2015 =96 2030 ($ Million) Figure 101: Norway mHealth Revenue: 2015 =96 2030 ($ Million) Figure 102: UK mHealth Revenue: 2015 =96 2030 ($ Million) Figure 103: mHealth Revenue in the Rest of Western Europe: 2015 =96 2030 ($= Million) Figure 104: Global mHealth Centric Wearable Device Shipments: 2015 - 2030 (= Millions of Units) Figure 105: Global Big Data & Analytics Technology Investments in the Healt= hcare Sector: 2015 - 2030 ($ Billion) =20 =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snscommunication.com Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com From owner-freebsd-ppc@freebsd.org Thu Dec 24 06:07:22 2015 Return-Path: Delivered-To: freebsd-ppc@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 7EF70A4F7F4 for ; Thu, 24 Dec 2015 06:07:22 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from vms173017pub.verizon.net (vms173017pub.verizon.net [206.46.173.17]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 684A112C8 for ; Thu, 24 Dec 2015 06:07:21 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from lenoil1 ([96.255.168.17]) by vms173017.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NZU000XPJJ82C21@vms173017.mailsrvcs.net> for freebsd-ppc@freebsd.org; Wed, 23 Dec 2015 23:06:45 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=btqxfxui c=1 sm=1 tr=0 a=TXQDfM1T7tsaHFmtCUVSow==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=kj9zAlcOel0A:10 a=wUQvQvOEmiQA:10 a=F7XOurNBbong1w4PQMAA:9 a=CjuIK1q_8ugA:10 From: "Curtis Hamilton" To: Subject: Nouveau Port Date: Thu, 24 Dec 2015 00:06:21 -0500 Message-id: <000a01d13e08$d4ff0bc0$7efd2340$@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-index: AdE+CLSCIs1hVyZrRkKqYN3pktnQgA== Content-language: en-us X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2015 06:07:22 -0000 Does anyone have any information concerning the status of the Nouveau port?