From owner-freebsd-ppc@freebsd.org Mon Jan 8 18:18:00 2018 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 CDF06E7C930 for ; Mon, 8 Jan 2018 18:18:00 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E6386B1E4 for ; Mon, 8 Jan 2018 18:18:00 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id d19so4785716lfj.5 for ; Mon, 08 Jan 2018 10:18:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=GtyC9nVkKfcZ5wpe5vm+jyPuMYPdLiK88rZHenMY6wQ=; b=OPi8phL9X6DrYk49hw30wcE202SYAYbgIo9MBVJqVMgpvNypTKQOJdecGm3Q/yXvx9 8ImmVn96Eazf9cC32xQTjUbqQt5efKdlMSNU6sq7XcYY8q/XOmifTFAo6iYWscK174FQ BBwz0rQFdrhed44jJLBqGZpyxgzZJTsusvs1toYplKZ4mkfEDeQWeHdx3a0Olv8hwZQZ h7lWGcrn90rmxaKCK6Tcf5h79tTaJdAkj8g8KXXTbBuqq2hfKa7gZNvH0s3UlviYSARf 8zqQR2HLWmXk0GF9pmsrPaWVVpVlf3Ej+Pa+4BoixlUe117FW9pnId1IK07CEdL6BDEk P89w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :mime-version:content-disposition:user-agent; bh=GtyC9nVkKfcZ5wpe5vm+jyPuMYPdLiK88rZHenMY6wQ=; b=uQgYuK+AMH8lVvsf6ArCt05Vpmc2jOYJ7btMJlWY70sINoW7CWfHX8CIRGibZPgPy1 cW5xaX+SKKQrRC5j6xiA7nGhrxVyGh58LEx6vf+1eebqVnH95B7IItTC/XlOBQXJ6Xq9 TqcPG/YEhLFwDSp4K9VUJkb+PR7gCO/R1C9kzc9PBNzhlMg0yP4j1H1YM3DUeqLG72JJ 57drfk16QAjhjvrK8ioyF5axXIJqd5vIhc/nKUgiIuW/S1IbLEFx4UTfGeTk8p0rirX/ 5aZl+uL02pg7vQAnTKYGvbfrAAkWZW8/fWLcIJ+GRQ3TkvGXWDAzC5Uw05i4YCxkl0Ji 9IMA== X-Gm-Message-State: AKGB3mJCMiydmyEZo5rRuI8OwXs+T7wVHCts9t4Xt/UmGapUhr2Xa+ky qLj7U9YqvQqwJ39KPsuujlQ/4w== X-Google-Smtp-Source: ACJfBouFjTbtDaOjgOgqHUVtUf/qX/bMiz2n1jwLYxgtZiNgcid5Is6PIXgzjAToXAJp3g2Bh3a+rA== X-Received: by 10.46.71.68 with SMTP id u65mr7203583lja.141.1515435478023; Mon, 08 Jan 2018 10:17:58 -0800 (PST) Received: from kloomba ([213.147.204.3]) by smtp.gmail.com with ESMTPSA id z10sm2493639ljb.75.2018.01.08.10.17.56 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jan 2018 10:17:57 -0800 (PST) Sender: Roman Bogorodskiy Date: Mon, 8 Jan 2018 22:17:51 +0400 From: Roman Bogorodskiy To: freebsd-ppc@freebsd.org Subject: Booting an alternate kernel Message-ID: <20180108181749.GA3689@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 18:18:00 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Recently I upgraded FreeBSD -CURRENT as of mid-2016 to a fresh one (Jan 6-7 -CURRENT). Of course I didn't read UPDATING and missed 20171125 entry so it failed to find root. However, when I manually set root to 'ufs:/dev/ada0s3', it failed to boot because init segfaulted (I did installkernel but not installworld). I decided to boot kernel.old. There's a note here: https://www.freebsd.org/platforms/ppc.html#issues that tells how to boot a custom kernel, e.g. doing 0 > boot hd:loader hd:0 It doesn't work for me. I figured out that I can proceed to normal boot from the OpenFirmware shell using 0 > boot hd:\ppc\boot1.elf But I don't quite understand how to specify invalid partition? I tried things like "boot hd:\ppc\boot1.elf hd:4" but it appears to treat "hd:4" as a loader. As far as I understand, boot1.elf source code is: https://github.com/freebsd/freebsd/blob/master/stand/powerpc/boot1.chrp/boo= t1.c =46rom what I can see: https://github.com/freebsd/freebsd/blob/master/stand/powerpc/boot1.chrp/boo= t1.c#L414 it only allows to define 'path' which is PATH_LOADER "/boot/loader" by default; and bootpath is set from /chosen bootpath property. Would appreciate if somebody could help with the follow: * How do I force invalid 'bootpath' so it drops into loader without loading kernel (or other ways to load kernel.old)? * Hints how to debug init segfault issue Thanks, Roman Bogorodskiy --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJaU7XNAAoJEMltX/4IwiJqDscH/A3HYtTm0vZWdBqpBqaIGNz5 153XbSVRk8tAMXYeWcSzeKEagjjnyEHH89UuYKsII4jovVv9WyOP+Hvsmo2hw2fg J0n+eVw53lqp7XEufEYPYLBEHKLkWbojohjRErsamXMQw129zLqNxFpNNEO91BTM olf9yWr50HOK3YnU9XsNZ7MvGnuFMm2Wa7aoJwaLp89bhYHtw2XVUpwcmbN5vQdM 03sGUkxpyDPRaOrIdMLFcofG3eipw/o6biHyLm62ZSYxm7s1WVXCya+ErMYwM55C BXxzvJ9Fwr6dxMnruH3LcyOD9uAt5ai1jEw3PszAxnb8QQnQIZ7th5hoyEh8nJk= =RiJB -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-ppc@freebsd.org Mon Jan 8 19:21:31 2018 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 26D6AE5B00E for ; Mon, 8 Jan 2018 19:21:31 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E383E6F005; Mon, 8 Jan 2018 19:21:30 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-io0-x230.google.com with SMTP id e20so15781251iof.12; Mon, 08 Jan 2018 11:21:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KlNhEyETT/m0M60Hatxaxb4exjwCsox1xFu6Kq30Iyw=; b=kVkK/96IwgL1TPYbCFUAsVRzz3BlKM3yH7FBOuSm5QuDLZRE9sYFWZE2TPVZmbd3lY tR0ce4u38m3BqgLpdrzwhOn22EsVTQq2C3UXMGiJQ3xAsoCtEW7WcY7+arv45gASwcUD GQSnabBLuypHHWZgnJHbYaWiufCxd6M3inr8DfvU/v9IDBvjZnPGnHlwLA5bo8x0stag DvPlVR6mrsKOynicyXy+76E9dG2Qvqyrf/AwK60O8ONWU2wu3TQudqmhP6AqDsjZo3T+ L/wkYQSf6ZOBRpwZpe3N+DUseRnzXCWJvcrUmB+ipRyDaQAPSFDW5lrNQ9vof8VnrRUP 5Fsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=KlNhEyETT/m0M60Hatxaxb4exjwCsox1xFu6Kq30Iyw=; b=HE+bOyP0JrzH2eZQNjW6W0I1i5aWBvuF6hugGKCgYNIkTD12ODpzqUNnAXOb3qMYRv Yn2ekGs6hErIsF0Vk0R4FgcSdXw+UpHVS/lBUZRZUwxysXcF/2qB0jvGG2KyOgUo9nhy U9fUeHzdXTQKla7VGFv79yX77nEtn/qw4V2Cz+3Sol8gTCyjfCtDLtChElFQoipWCPIB +d76N4M/RlZnTXcbQBlWptkgYAkBpuw7/Vvo4dvDoLo3+OylRvMgDUlLeLwfziW4xDUl ORyg46/vMXyc5o0gBocw55tbK8y/Yn9jvwTLi80Kvn3LHAYfb8xlqMUeqPXaEuj9XY48 /FIA== X-Gm-Message-State: AKwxytcrFojVUhf7XSxalUhb7Qzlt+mBAaohrAud+KYZgcfnogdPZG5U F5NtXPA/UStPsO9ZPI6787DNNc06XDd6vO70+xA= X-Google-Smtp-Source: ACJfBouonxL9OjgfjTH6cnmmGlNDtWfz+4z6g6UACMqqaV9UkUu8RA39EwnA3TrbdUh5nYhXDlUuapoOQIHETWCXtR0= X-Received: by 10.107.10.20 with SMTP id u20mr12927102ioi.232.1515439289895; Mon, 08 Jan 2018 11:21:29 -0800 (PST) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.79.149.82 with HTTP; Mon, 8 Jan 2018 11:21:29 -0800 (PST) In-Reply-To: <20180108181749.GA3689@kloomba> References: <20180108181749.GA3689@kloomba> From: Justin Hibbits Date: Mon, 8 Jan 2018 13:21:29 -0600 X-Google-Sender-Auth: or2FcYcVN5nW1p6jKxAvY41lXDA Message-ID: Subject: Re: Booting an alternate kernel To: Roman Bogorodskiy Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 19:21:31 -0000 Hi Roman, Not a direct answer to your question, but more addressing what your real problem might be. Are you booting powerpc or powerpc64? Powerpc (32-bit) got updated to 64-bit time_t, which requires everything new. Easiest way to update that is a fresh install (See UPDATING note 20170625). - Justin On Mon, Jan 8, 2018 at 12:17 PM, Roman Bogorodskiy wrote: > Hi, > > Recently I upgraded FreeBSD -CURRENT as of mid-2016 to a fresh one (Jan > 6-7 -CURRENT). Of course I didn't read UPDATING and missed 20171125 > entry so it failed to find root. However, when I manually set root to > 'ufs:/dev/ada0s3', it failed to boot because init segfaulted (I did > installkernel but not installworld). > > I decided to boot kernel.old. There's a note here: > > https://www.freebsd.org/platforms/ppc.html#issues > > that tells how to boot a custom kernel, e.g. doing > > 0 > boot hd:loader hd:0 > > It doesn't work for me. > > I figured out that I can proceed to normal boot from the OpenFirmware > shell using > > 0 > boot hd:\ppc\boot1.elf > > But I don't quite understand how to specify invalid partition? > > I tried things like "boot hd:\ppc\boot1.elf hd:4" but it appears to > treat "hd:4" as a loader. > > As far as I understand, boot1.elf source code is: > > https://github.com/freebsd/freebsd/blob/master/stand/powerpc/boot1.chrp/boot1.c > > From what I can see: > > https://github.com/freebsd/freebsd/blob/master/stand/powerpc/boot1.chrp/boot1.c#L414 > > it only allows to define 'path' which is PATH_LOADER "/boot/loader" by > default; and bootpath is set from /chosen bootpath property. > > Would appreciate if somebody could help with the follow: > > * How do I force invalid 'bootpath' so it drops into loader without > loading kernel (or other ways to load kernel.old)? > * Hints how to debug init segfault issue > > Thanks, > > Roman Bogorodskiy From owner-freebsd-ppc@freebsd.org Tue Jan 9 08:45:40 2018 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 AA32DE6E84C for ; Tue, 9 Jan 2018 08:45:40 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 2ACE37163B for ; Tue, 9 Jan 2018 08:45:40 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id e27so15012194lfb.9 for ; Tue, 09 Jan 2018 00:45:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=+nxFp/h35F3za9Hj1MUoYTO7JG0m+CRUVoMiS1y8MIA=; b=VpeX1lLvep4m0/v6oFlnz1al6I/qnjXO4aQbwAdcVRzIDaOKP7C2a+g7St9wI0Prc7 PX5iszyOg6QKCNxlOtL0IaZqQYhLCgm7QWk9qR6jRgXfx1VvuyqSsy4mAakHA3miDlDf 5deCIpoNeOIq7/gkcKIkX0uoAZI4EBEf6nyYyzdJMR0MStKZ+wFR3SRJCppT0VraKo68 0nnzN3B1Y0HPsdawvScpKHvy3h5sAuu52K4H1NRyt2Gd1a6egoR7ukzc3IwkDrWBXiKE b+OM7DgMMX2BjV0TLdfrzQ37PZPeLP2Zc5bp2maa8oqLmTFUfENjHXzKJeaXaf3eJUwX 8i+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=+nxFp/h35F3za9Hj1MUoYTO7JG0m+CRUVoMiS1y8MIA=; b=VCWWb1HoQmO+P2PHSDjlxpe+AVKrA+HsvC7wNyrI4guZpiv+sA1u4fGTzioZQBSrM7 qW8AMLCDgX6vTrWfVQZLMpbTfYbSDixZw+i1plRi7zO7s0/ju6Pv35u9S2YErYuH/zIG jwyvmJIf+xxdnDp146pMAzmhkQXhqriGBsT2fEE+7B0FYW/PGnxI6qR5PTD/eYGXZTqk ssn5Pam5yZ4xxkLPvE8O7FnTiGJGq48Gj4GbAMzV06G9dRpk3dquJ7bG5IF/KNHtamSu +QeyBIhIjbMHqrkC0Jt1sk7PbrDxV6Lc1znsBNuwul+QkzR5tNsfkBh2CeJsra433GJM FDjA== X-Gm-Message-State: AKwxytcYTaI056mLTLTSyZlNAkuHq1YwTiUZPGO7A62rFFZBN4S37Buf FS93Gh4MMNrYcN8MxmvyaqdHvg== X-Google-Smtp-Source: ACJfBotFhcXNHsA5NIEEJuPGnxzeENw11t5RRQmZLs6ZK2uz92iN9bTSHGG/f30trOxWXxTMR4EZLQ== X-Received: by 10.25.121.6 with SMTP id u6mr6788150lfc.34.1515487536846; Tue, 09 Jan 2018 00:45:36 -0800 (PST) Received: from kloomba ([213.147.204.3]) by smtp.gmail.com with ESMTPSA id p62sm2747931lje.67.2018.01.09.00.45.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jan 2018 00:45:36 -0800 (PST) Sender: Roman Bogorodskiy Date: Tue, 9 Jan 2018 12:45:27 +0400 From: Roman Bogorodskiy To: Justin Hibbits Cc: FreeBSD PowerPC ML Subject: Re: Booting an alternate kernel Message-ID: <20180109084525.GA1818@kloomba> References: <20180108181749.GA3689@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 08:45:40 -0000 --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Justin Hibbits wrote: > Hi Roman, >=20 > Not a direct answer to your question, but more addressing what your > real problem might be. > Are you booting powerpc or powerpc64? Powerpc (32-bit) got updated to > 64-bit time_t, which requires everything new. Easiest way to update > that is a fresh install (See UPDATING note 20170625). >=20 > - Justin Thanks for the pointer, I'm booting powerpc indeed. > On Mon, Jan 8, 2018 at 12:17 PM, Roman Bogorodskiy wr= ote: > > Hi, > > > > Recently I upgraded FreeBSD -CURRENT as of mid-2016 to a fresh one (Jan > > 6-7 -CURRENT). Of course I didn't read UPDATING and missed 20171125 > > entry so it failed to find root. However, when I manually set root to > > 'ufs:/dev/ada0s3', it failed to boot because init segfaulted (I did > > installkernel but not installworld). > > > > I decided to boot kernel.old. There's a note here: > > > > https://www.freebsd.org/platforms/ppc.html#issues > > > > that tells how to boot a custom kernel, e.g. doing > > > > 0 > boot hd:loader hd:0 > > > > It doesn't work for me. > > > > I figured out that I can proceed to normal boot from the OpenFirmware > > shell using > > > > 0 > boot hd:\ppc\boot1.elf > > > > But I don't quite understand how to specify invalid partition? > > > > I tried things like "boot hd:\ppc\boot1.elf hd:4" but it appears to > > treat "hd:4" as a loader. > > > > As far as I understand, boot1.elf source code is: > > > > https://github.com/freebsd/freebsd/blob/master/stand/powerpc/boot1.chrp= /boot1.c > > > > From what I can see: > > > > https://github.com/freebsd/freebsd/blob/master/stand/powerpc/boot1.chrp= /boot1.c#L414 > > > > it only allows to define 'path' which is PATH_LOADER "/boot/loader" by > > default; and bootpath is set from /chosen bootpath property. > > > > Would appreciate if somebody could help with the follow: > > > > * How do I force invalid 'bootpath' so it drops into loader without > > loading kernel (or other ways to load kernel.old)? > > * Hints how to debug init segfault issue > > > > Thanks, > > > > Roman Bogorodskiy Roman Bogorodskiy --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJaVIElAAoJEMltX/4IwiJqUHUH/j/vLPE9oMxMVr39sc6KddIv RUoGEM5at9U+eJP4ix5dV1g0ILLL9Pibk1s1XfF0h6ScTOdzx7x8F5y8bmPMHSgi 2GDf5wNFizPfuAl5uoHbKX293s3KaCREQqQUSaeeqX86cVSaebhoBEFg5cy45n2k JUMFoyAay53Up3sFJ8fXE8E13ekxR1Gy4wvl0OASijlG6uSBTDp2FL4783OO4AXF 6+9gVx0hgueQZ9yIUye1EPyfIhRfGovKEtsYOh6Z72th7TTqcKKGO5b8tQ/W5Dqt zGYmujihibV9nfKc33H3JVRHZ2E5gt8ASLlEGHWTVgKgvvh24LM4owe7hJmoIAc= =NsRZ -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- From owner-freebsd-ppc@freebsd.org Tue Jan 9 19:41:55 2018 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 BAC2EE6D7AA for ; Tue, 9 Jan 2018 19:41:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 833A76D002 for ; Tue, 9 Jan 2018 19:41:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id CAA96155A8; Tue, 9 Jan 2018 19:41:54 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id B53EC155A7 for ; Tue, 9 Jan 2018 19:41:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E29D06CFF9 for ; Tue, 9 Jan 2018 19:41:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D7AE21238E for ; Tue, 9 Jan 2018 19:41:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w09JfrJF094977 for ; Tue, 9 Jan 2018 19:41:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w09Jfr9n094976 for freebsd-powerpc@FreeBSD.org; Tue, 9 Jan 2018 19:41:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-powerpc@FreeBSD.org Subject: [Bug 224940] [patch] PPC64: No input on VNC console due to xhci driver not present as built-in module Date: Tue, 09 Jan 2018 19:41:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-powerpc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 19:41:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224940 --- Comment #2 from commit-hook@freebsd.org --- A commit references this bug: Author: nwhitehorn Date: Tue Jan 9 19:41:10 UTC 2018 New revision: 327736 URL: https://svnweb.freebsd.org/changeset/base/327736 Log: Add XHCI support to powerpc64 GENERIC. This is useful to get input devices supported on newer POWER hardware and in graphical VMs run on the same, which are typically XHCI-only. The 32-bit GENERIC kernel, which does not run on hardware made in the last decade and is unlikely to encounter XHCI devices, is left unchanged. PR: kern/224940 Submitted by: Gustavo Romero MFC after: 1 week Changes: head/sys/powerpc/conf/GENERIC64 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Wed Jan 10 18:09:57 2018 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 042E4E6C0F8 for ; Wed, 10 Jan 2018 18:09:57 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.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 814FC82957 for ; Wed, 10 Jan 2018 18:09:56 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.com) X-MSFBL: NDnSq16CJkfdJ9nSdpP2YH9V8KpgRw7qaJ2alQdc2Lc=|eyJyIjoiZnJlZWJzZC1 wcGNAZnJlZWJzZC5vcmciLCJiIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbF8 3NF85MV84NV8yMzgiLCJnIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbCJ9 Received: from [10.137.129.34] ([10.137.129.34:50490] helo=mtl-mtsp-c02-2.int.smtp) by mtl-mtsp-mta05-out1.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id DA/68-30628-B32565A5; Wed, 10 Jan 2018 17:49:47 +0000 Received: from 10.137.11.85 by Caffeine (mtl-mtsp-c02-2) with SMTP id 6027134a-02f0-46bd-9ac7-71899df19666 for freebsd-ppc@freebsd.org; Wed, 10 Jan 2018 17:49:44 +0000 (UTC) Received: from [65.49.242.4] ([65.49.242.4:25134] helo=gull-dhcp-65-49-242-4.bloombb.net) by mtl-mtsp-mta03-in1 (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id F2/52-22882-732565A5; Wed, 10 Jan 2018 17:49:44 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsresearchreports.com To: freebsd-ppc@freebsd.org Subject: The SDN, NFV & Network Virtualization Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Wed, 10 Jan 2018 12:49:41 -0500 Message-ID: <95964428775123191426297@Ankur> X-SMTPCOM-Tracking-Number: 6027134a-02f0-46bd-9ac7-71899df19666 X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=snsresearchreports.com; i=@snsresearchreports.com; q=dns/txt; s=snskey; t=1515606585; h=MIME-Version : From : Reply-To : To : Subject : Content-Type : Date : Message-ID : From : Subject : Date; bh=vsrCXNB4VR7M5vhqyS0KegBDXn8Os8NddPKGzkTNfYA=; b=kCF3Vfl/acDn/7fWRTDI7HsUESX5RDlxDRhmuxhCxMnI6n/FvCuiJYI0Se0bq6grt5QPs9 oB9ZjFVv/bMdjPLxIgT+AUO2E1SzD5tCR8vMMEBThII8ql/qLyIYjuNCxrHGSEW4sEqUho0s t1UfTfaHJ5SIVQKizf2b9FBPUhXrM71xyI5/+I096edTOWy2nGvGbetrs6Rnoug9S5Zx5maB 9uBn8Prgbhva18/LePmroXvBqF3ucMeRj32CT5vK5AzH3m3BILpSSKMxfp1oviLuDbg45OVh S3wa9jZH5UeoxZYCP32Xj2vtN27Th8anrt796naXJ4sjKKf0dLHMXX6g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smtpserver.email; i=@smtpserver.email; q=dns/txt; s=smtpcustomer; t=1515606585; h=MIME-Version : From : Reply-To : To : Subject : Content-Type : Date : Message-ID : From : Subject : Date; bh=vsrCXNB4VR7M5vhqyS0KegBDXn8Os8NddPKGzkTNfYA=; b=ilrymXRrg6zsvTeuGynj8vwfYMnzzh4oRLVJ084oNHvCIgSTui5Ny0+uSdMVJ+WGUFEaiL m5+HwJTMmZRTCjjwDYV9W/ZzGvJk4y/krEaOhY05+HSKuBpOjlwC5lPY/fZwlLYHauDi8jyD IgxKyj7ChCtV/GOHjwfYNp9IEd6XyN/NgknCqVsmqff8iLHnz4xYyt+VrP/UVZ/Mn8G4U32z xuE6zg2uGKZNrMzlBFh+mZZOMOxPgCwVYVOdW0nCK38jum4H70ucdrXIiH+tcxxxS7MHF/4S aRLrwQoBlV9bfbZoD1xNA1MRLtxY9Pl3Xi4kdWS1YzO3efCmUeZA6nGA== X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation. Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 18:09:57 -0000 The SDN, NFV & Network Virtualization Ecosystem: 2017 =96 2030 =96 Opportun= ities, Challenges, Strategies & Forecasts Hello =20 Happy New Year =20 Let me offer you the latest SNS Research report to you and your team, "The = SDN, NFV & Network Virtualization Ecosystem: 2016 =96 2030 =96 Opportunitie= s, Challenges, Strategies & Forecasts." Below is the report highlight and i= f you like I can send you sample pages for your details inside. =20 While the advantages of SDN (Software Defined Networking) and network virtu= alization are well known in the enterprise IT and data center world, both t= echnologies also bring a host of benefits to the telecommunications service= provider community. Service providers =96 both mobile and fixed-line =96 h= ave already begun making significant investments in SDN and NFV across a nu= mber of use cases including but not limited to uCPE/vCPE, SD-WAN, vEPC, vIM= S, Cloud RAN and vCDN. SNS Research estimates that service provider SDN and= NFV investments will grow at a CAGR of approximately 45% between 2017 and = 2020, eventually accounting for nearly $22 Billion in revenue by the end of= 2020. =20 Our reports are compiled with primary and secondary informations to produce= an overall industry outlook. =20 Report Information: Release Date: Jan 2018 Number of Pages: 586 Number of Tables and Figures: 109 Key Questions Answered: =20 The report provides answers to the following key questions: How big is the SDN, NFV and network virtualization opportunity=3F What trends, challenges and barriers are influencing its growth=3F How is the ecosystem evolving by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F Which regions, submarkets and countries will see the highest percentage of = growth=3F What is the status of SDN and NFV deployments across service provider, data= center and enterprise networks=3F How big is the opportunity for service provider and cloud managed SD-WAN se= rvices=3F How are service provider-led initiatives driving SDN and NFV investments=3F How does regulation impact the adoption of software-centric networks=3F What level of CapEx savings can SDN and NFV facilitate for service provider= s=3F Do SDN and NFV pose a threat to traditional network infrastructure vendors=3F Who are the key market players and what are their strategies=3F What strategies should enabling technology providers, network infrastructur= e vendors, SDN/NFV specialists, service providers and other ecosystem play= ers adopt to remain competitive=3F Key Findings: =20 The report has the following key findings: SNS Research estimates that service provider SDN and NFV investments will g= row at a CAGR of approximately 45% between 2017 and 2020, eventually accoun= ting for nearly $22 Billion in revenue by the end of 2020. Spearheaded by internet giants, data center operators and large enterprises= , the adoption of software-centric networking is also continuing to grow in= the enterprise and data center segment. SNS Research estimates that SDN an= d network virtualization investments in this segment accounted for $12 Bill= ion in 2017 alone. New market players are beginning to emerge as service providers accelerate = their transition to software-centric networks. For example, with their earl= y wins in NFV-compliant mobile core and IMS platforms, companies such as Ma= venir Systems and Affirmed Networks have emerged as direct competitors to e= stablished wireless network infrastructure giants. With the emergence of initiatives such as the Linux Foundation's ONAP (Open= Network Automation Platform), ETSI's OSM (Open-Source MANO) and SK Telecom= 's T-MANO, solutions are beginning to be commercialized that can perform in= tegrated management and orchestration of VNFs from multiple vendors. Topics Covered: =20 The report covers the following topics: SDN, NFV and network virtualization ecosystem Market drivers and barriers Enabling technologies, protocols, architecture and key trends SDN and NFV use cases across service provider, data center and enterprise n= etworks Commercial SDN and NFV deployments =96 including 10 comprehensive case stud= ies Review of key functional areas including uCPE/vCPE, SD-WAN, data center SDN= , vEPC, vIMS, Cloud RAN and vCDN Assessment of CapEx savings potential of service provider SDN and NFV inves= tments Management and orchestration platforms for software-centric networks Standardization, regulatory and collaborative initiatives Industry roadmap and value chain Profiles and strategies of over 270 ecosystem players including SDN/NFV spe= cialists Strategic recommendations for enabling technology providers, network infras= tructure vendors, IT giants, pure-play SDN/NFV specialists, enterprises, da= ta center operators and service providers Market analysis and forecasts from 2017 till 2030 Report Pricing: Single User License: USD 2,500 Company Wide License: USD 3,500 =20 Ordering Process: =20 Email 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 - =20 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. =20 I look forward to hearing from you. =20 Kind Regards Andy Silva Marketing Executive Signals and Systems Telecom ___________________________________________________________________________= __________________________________________________________________________ =20 Table of Content 1 Chapter 1: Introduction 1.1 Executive Summary 1.2 Topics Covered 1.3 Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 2 Chapter 2: An Overview of SDN, NFV & Network Virtualization 2.1 What is Network Virtualization=3F 2.2 What is SDN (Software Defined Networking)=3F 2.3 SDN Protocols 2.3.1 OpenFlow 2.3.2 BGP-TE (Border Gateway Protocol =96 Traffic Engineering) 2.3.3 PCEP (Path Computation Element Protocol) 2.3.4 I2RS (Interface to the Routing System) 2.3.5 VxLAN (Virtual Extensible LAN) 2.3.6 ALTO (Application Layer Traffic Optimization) 2.3.7 IETF Software Driven Networks 2.4 SDN Implementation Approaches 2.4.1 Network Virtualization Approach 2.4.2 Evolutionary Approach 2.4.3 The =93Central Control=94 Approach 2.5 What is NFV (Network Functions Virtualization)=3F 2.6 NFV Enabling Technologies 2.6.1 Cloud Computing and Network Virtualization 2.6.2 Open Management and Control Protocols 2.6.3 Industry Standard High-Volume Servers 2.7 NFV Implementation Architecture 2.7.1 NFVI (NFV Infrastructure) 2.7.1.1 Hardware Resources 2.7.1.2 Virtualized Resources 2.7.2 VNFs (Virtualized Network Functions) 2.7.3 NFV-MANO (NFV-Management and Orchestration) 2.7.3.1 VIM (Virtualized Infrastructure Manager) 2.7.3.2 NFVO (NFV Orchestrator) 2.7.3.3 VNF Manager 2.8 How SDN and NFV Differ from Each Other=3F 2.8.1 Similarities and Differences 2.8.2 Can Both Technologies Complement Each Other=3F 2.8.3 How Are Vendors Positioning their Solutions=3F 2.9 Market Drivers 2.9.1 Leveraging Generic Low-Cost Hardware 2.9.2 Multi-Tenancy on Same Hardware 2.9.3 Reduced Power Consumption 2.9.4 Faster TTM (Time-to-Market) 2.9.5 Improved Operational Efficiency & Performance 2.9.6 Centralized Provisioning and Network Control 2.9.7 Ability to Launch New Services & Virtual Networks Quickly 2.9.8 Dynamic Scaling of Services 2.9.9 Opening the Door to Multi-vendor Interoperability 2.9.10 CapEx and OpEx Reduction 2.9.11 Fast Troubleshooting and Improved Diagnostics 2.9.12 Vendor Support 2.10 Market Barriers 2.10.1 Lack of Standardization & Technology Maturity 2.10.2 Uncertain Cost-Benefits Tradeoffs 2.10.3 NFV May Slow/Delay Traffic 2.10.4 Will Multi-vendor Interoperability Really Work=3F 2.10.5 Co-Existence with Legacy Networks: Integration Challenges =20 3 Chapter 3: SDN & NFV Use Case Scenarios 3.1 Enterprise, Data Center & Generic Use Cases 3.1.1 Network Virtualization 3.1.2 Data Center Optimization 3.1.3 SD-WAN (Software Defined WAN) 3.1.4 Tap Aggregation 3.1.5 Dynamic WAN Re-Routing 3.1.6 Network Exchange: Interconnecting Physical Networks 3.1.7 Improved Traffic Engineering 3.1.8 Converged Storage 3.2 Service Provider Centric Use Cases 3.2.1 vRAN (Virtualized RAN) & Cloud RAN 3.2.2 Wireline Fixed Access Network Virtualization 3.2.3 vCPE/uCPE (Virtualized & Universal Customer Premises Equipment) 3.2.4 Mobile Backhaul Virtualization 3.2.5 Mobile Core & Gi-LAN Virtualization 3.2.6 IMS & VoLTE Virtualization 3.2.7 DPI Virtualization 3.2.8 Policy Control Virtualization 3.2.9 OSS/BSS Virtualization 3.2.10 Virtual Routers 3.2.11 Virtualization & Control of Security Functions 3.2.12 Virtualization of CDNs (Content Delivery Networks) 3.2.13 MEC (Multi-Access Edge Computing) 3.2.14 Network Slicing 3.2.15 Service Chaining 3.2.16 Bandwidth-on-Demand 3.2.17 Packet-Optical Integration 3.2.18 SDN/NFV Iaas (Infrastructure-as-a-Service) 3.2.19 VNFaas (VNF-as-a-Service) 3.2.20 VNPaaS (Virtual Network-Platform-as-a-Service) =20 4 Chapter 4: SDN & NFV Deployment Case Studies & Commitments 4.1 Case Studies 4.1.1 AT&T 4.1.1.1 Overview 4.1.1.2 Key Vendors 4.1.1.3 SDN/NFV Deployment Review 4.1.2 Baidu 4.1.2.1 Overview 4.1.2.2 Key Vendors 4.1.2.3 SDN/NFV Deployment Review 4.1.3 CenturyLink 4.1.3.1 Overview 4.1.3.2 Key Vendors 4.1.3.3 SDN/NFV Deployment Review 4.1.4 Equinix 4.1.4.1 Overview 4.1.4.2 Key Vendors 4.1.4.3 SDN/NFV Deployment Review 4.1.5 Google 4.1.5.1 Overview 4.1.5.2 Key Vendors 4.1.5.3 SDN/NFV Deployment Review 4.1.6 NTT Group 4.1.6.1 Overview 4.1.6.2 Key Vendors 4.1.6.3 SDN/NFV Deployment Review 4.1.7 SK Telecom 4.1.7.1 Overview 4.1.7.2 Key Vendors 4.1.7.3 SDN/NFV Deployment Review 4.1.8 Telef=F3nica Group 4.1.8.1 Overview 4.1.8.2 Key Vendors 4.1.8.3 SDN/NFV Deployment Review 4.1.9 Verizon Communications 4.1.9.1 Overview 4.1.9.2 Key Vendors 4.1.9.3 SDN/NFV Deployment Review 4.1.10 Vodafone Group 4.1.10.1 Overview 4.1.10.2 Key Vendors 4.1.10.3 SDN/NFV Deployment Review 4.2 Review of Other SDN & NFV Commitments 4.2.1 Service Providers 4.2.1.1 A1 Telekom Austria Group 4.2.1.2 Altice Group 4.2.1.3 ASPIDER-NGI 4.2.1.4 Axiata Group 4.2.1.5 BCE (Bell Canada) 4.2.1.6 BT Group 4.2.1.7 China Mobile 4.2.1.8 China Telecom 4.2.1.9 China Unicom 4.2.1.10 Colt Technology Services Group 4.2.1.11 Comcast 4.2.1.12 Digicel 4.2.1.13 DT (Deutsche Telekom) 4.2.1.14 Etisalat 4.2.1.15 IIJ (Internet Initiative Japan) 4.2.1.16 KDDI Corporation 4.2.1.17 KPN 4.2.1.18 KT Corporation 4.2.1.19 LG Uplus 4.2.1.20 NAKA Mobile 4.2.1.21 Ngena 4.2.1.22 Ooredoo 4.2.1.23 Orange 4.2.1.24 PCCW Global 4.2.1.25 Singtel 4.2.1.26 SoftBank Group 4.2.1.27 Sprint Corporation 4.2.1.28 STC (Saudi Telecom Company) 4.2.1.29 Swisscom 4.2.1.30 Telecom Italia 4.2.1.31 Telenor Group 4.2.1.32 Telstra 4.2.1.33 Turk Telekom 4.2.1.34 Windstream Communications 4.2.2 Enterprises & Data Centers 4.2.2.1 Internet Giants 4.2.2.2 Data Center Operators 4.2.2.3 Large Enterprises 4.2.2.4 SMEs (Small and Medium-Sized Enterprises) =20 5 Chapter 5: Industry Roadmap and Value Chain 5.1 Industry Roadmap 5.1.1 Pre-2020: Moving Towards Network-Wide Orchestration 5.1.2 2020 =96 2025: Large-Scale Service Provider Rollouts 5.1.3 2025 =96 2030: Continued Investments with 5G & Next Generation Networ= k Rollouts 5.2 Value Chain 5.2.1 Enabling Technology Providers 5.2.2 Pure-Play SDN & NFV Specialists 5.2.3 Network Infrastructure Vendors 5.2.4 IT Industry Giants 5.2.5 Mobile Infrastructure Vendors 5.2.6 Policy, OSS, BSS & Other Software Vendors 5.2.7 Enterprises 5.2.8 Service Providers 5.2.9 Data Center Operators =20 6 Chapter 6: Standardization, Regulatory & Collaborative Initiatives 6.1 3GPP (3rd Generation Partnership Project) 6.1.1 End-to-End Management for Virtualized 3GPP Networks 6.2 5G PPP (5G Infrastructure Public Private Partnership) 6.2.1 SDN / NFV WG (Working Group) 6.2.2 Key Projects Focusing on the Use of SDN & NFV 6.3 ASF (Apache Software Foundation) 6.3.1 Mesos 6.3.2 ARIA TOSCA 6.3.3 CloudStack 6.4 ATIS (Alliance for Telecommunications Industry Solutions) 6.4.1 NFV-F (NFV Forum) 6.5 Broadband Forum 6.5.1 TR-317 & TR-328: vCPE Implementation 6.5.2 SDN and NFV Work Area 6.5.2.1 CloudCO (Cloud Central Office) 6.5.2.2 Migration to SDN-Enabled Management and Control 6.5.2.3 FANS (Fixed Access Network Sharing) 6.5.2.4 Support for SDN in Access Network Nodes 6.5.2.5 YANG Models for SDN in Access Nodes 6.5.3 Other Work 6.6 CableLabs 6.6.1 SNAPS (SDN/NFV Application development Platform and Stack) 6.7 CAICT (China Academy of Information and Communications Technology) 6.7.1 SDNFVIA (SDN/NFV Industry Alliance) 6.8 CloudNFV & ExperiaSphere 6.8.1 Open Platform for NFV 6.8.2 Service-Layer Based MANO 6.9 Django Software Foundation 6.9.1 Django Web Framework 6.10 ETSI (European Telecommunications Standards Institute) 6.10.1 NFV ISG (Industry Specification Group) 6.10.1.1 Release 1 6.10.1.2 Release 2 6.10.1.3 Release 3 6.10.2 OSM (Open Source MANO) Group 6.10.3 ZSM (Zero touch network and Service Management) ISG 6.11 FreeBSD Foundation 6.11.1 FreeBSD Operating System 6.12 IEEE (Institute of Electrical and Electronics Engineers) 6.12.1 IEEE SDN Initiative 6.12.2 IEEE 1903: NGSON (Next Generation Service Overlay Networks) 6.12.3 IEEE 1913: SDQC (Software-Defined Quantum Communication) 6.12.4 IEEE 1915.1, 1916.1 & 1917.1: Standards for SDN/NFV Security, Perfor= mance & Reliability 6.12.5 IEEE 1921.1: SDN Bootstrapping Procedures 6.12.6 IEEE 1930.1: SDN based Middleware for Control and Management 6.12.7 Other Standards & Recommended Practices 6.13 IETF (Internet Engineering Task Force) & IRTF (Internet Research Task = Force) 6.13.1 SDN Protocols, Working Groups, & Research Programs 6.13.2 NFV Working Groups & Research Programs 6.14 ITU (International Telecommunications Union) 6.14.1 Standardization Activities for SDN & Network Virtualization 6.14.1.1 JCA-SDN (Joint Coordination Activity on Software-Defined Networkin= g) 6.14.1.2 SG (Study Group) 13 on Future Networks 6.14.1.3 SG (Study Group) 11: Signaling Requirements, Protocols & Test Spec= ifications 6.14.1.4 Other Study Groups: Transport, Multimedia & Security 6.15 Linux Foundation 6.15.1 ODL (OpenDayLight) 6.15.2 OpenContrail 6.15.3 OPNFV (Open Platform for NFV) 6.15.4 ONAP (Open Network Automation Platform) 6.15.5 CNCF (Cloud Native Computing Foundation) 6.15.5.1 Kubernetes 6.15.6 Cloud Foundry Foundation 6.15.6.1 CF (Cloud Foundry) Application Runtime 6.15.6.2 CF Container Runtime 6.15.6.3 CF BOSH & Other Projects 6.15.7 ONOS (Open Network Operating System) 6.15.8 OCI (Open Container Initiative) 6.15.9 CORD (Central Office Re-architected as a Datacenter) 6.15.10 Open Switch 6.15.11 Open vSwitch 6.15.12 DPDK (Data Plane Development Kit) 6.15.13 FD.io (Fast Data Project) 6.15.14 Xen Project 6.15.14.1 Xen Hypervisor 6.15.14.2 Xen Cloud Platform 6.15.14.3 XAPI 6.15.14.4 Mirage OS 6.15.14.5 Unikraft 6.15.14.6 Xen ARM 6.15.15 Node.js 6.15.16 Other Relevant Projects & Specifications 6.16 MEF (Metro Ethernet Forum) 6.16.1 Third Network Vision 6.16.1.1 Third Network Orchestration Services 6.16.1.2 LSO (Lifecycle Services Orchestration) Framework, APIs & SDKs 6.16.1.3 Inter-Provider LSO Sonata APIs & SDK 6.16.1.4 Intra-Provider LSO Presto APIs & SDK 6.16.1.5 Software-Driven Reference Implementations and MEFnet 6.17 NetBSD Foundation 6.17.1 NetBSD Operating System 6.18 OASIS (Organization for the Advancement of Structured Information Stan= dards) 6.18.1 TOSCA (Topology and Orchestration Specification for Cloud Applicatio= ns) 6.19 OCP (Open Compute Project) Foundation 6.19.1 Telco Project 6.19.2 Networking Project 6.20 OMG (Object Management Group) 6.20.1 SDN Working Group 6.21 ONF (Open Networking Foundation) 6.21.1 Software Defined Standards 6.21.1.1 OpenFlow 6.21.1.2 Other Recommendations & Publications 6.21.2 Platforms 6.21.2.1 CORD (Central Office Re-Architected as a Datacenter) 6.21.2.2 CORD-XOS 6.21.2.3 CORD-Trellis 6.21.2.4 ONOS (Open Network Operating System) 6.21.2.5 MININET 6.21.3 Solutions 6.21.3.1 R-CORD, M-CORD & E-CORD 6.21.3.2 ODTN (Open Disaggregated Transport Network) 6.21.4 Incubator Projects 6.21.4.1 Delta 6.21.4.2 Information Modeling 6.21.4.3 iSDX 6.21.4.4 Open Datapath 6.21.4.5 Open Transport Configuration & Control 6.22 ONUG (Open Networking User Group) 6.22.1 ONUG Working Groups 6.22.1.1 OSE (Open SD-WAN Exchange) 6.22.1.2 M&A (Monitoring & Analytics) 6.22.1.3 S-DSS (Software-Defined Security Services) 6.22.1.4 HMC (Hybrid Multi-Cloud) 6.22.1.5 Container 6.23 OpenStack Foundation 6.23.1 OpenStack Operating System 6.23.1.1 Compute 6.23.1.2 Storage, Backup & Recovery 6.23.1.3 Networking & Content Delivery 6.23.1.4 Data & Analytics 6.23.1.5 Security, Identity & Compliance 6.23.1.6 Management Tools 6.23.1.7 Deployment Tools 6.23.1.8 Application Services 6.23.1.9 Monitoring & Metering 6.24 P4 Language Consortium 6.24.1 P4 Programming Language for Network Switches 6.25 SDN/NFV Forum, South Korea 6.25.1 Committees & Working Groups 6.26 TIP (Telecom Infra Project) 6.26.1 Use of SDN & NFV in Access, Transport & Core Networks 6.27 TM Forum 6.27.1 ZOOM (Zero-touch Orchestration, Operations and Management) Project 6.27.2 Core Frameworx 6.27.3 Virtualization Proof-of-Concept Catalysts 6.28 TTA (Telecommunications Technology Association of Korea) 6.28.1 PG220 (Future Internet Project Group) 6.29 Vendor Led Initiatives & Ecosystem Programs 6.29.1 ADTRAN's Mosaic Open Network Alliance 6.29.2 ADVA's Ensemble Harmony Ecosystem 6.29.3 Amdocs' NFV Partner Program 6.29.4 Big Switch Networks' Open Source Projects 6.29.4.1 ONL (Open Network Linux) 6.29.4.2 Project Floodlight & Others 6.29.5 Canonical's Open Source Projects 6.29.5.1 Ubuntu 6.29.5.2 Juju 6.29.5.3 Linux Containers 6.29.6 Ciena Blue Orbit Ecosystem 6.29.7 Cloudify's Open-Source NFV Orchestration Platform 6.29.8 Docker's Partner Program & Moby Project 6.29.9 HPE's OpenNFV Partner Program & SDN Ecosystem Alliance 6.29.9.1 OpenNFV Partner Program 6.29.9.2 SDN Ecosystem Alliance 6.29.10 Intel's Network, Cloud, Fabric & Storage Builders Programs 6.29.11 Juniper's Data Center, Cloud, and NFV Partner Program 6.29.12 Midokura's MidoNet 6.29.13 NEC/NetCracker's Ecosystem 2.0 & SDN Partner Space 6.29.13.1 Ecosystem 2.0 6.29.13.2 SDN Partner Space 6.29.14 Nokia's CloudBand Ecosystem & VSP Integration Partner Program 6.29.14.1 CloudBand Ecosystem 6.29.14.2 VSP Integration Partner Program 6.29.15 Red Hat's NFV Ecosystem & Open-Source Projects 6.29.15.1 NFV Ecosystem 6.29.15.2 OpenShift 6.29.15.3 Fedora 6.29.16 Wind River's Titanium Cloud Ecosystem =20 7 Chapter 7: Company Profiles 7.1 6WIND 7.2 A10 Networks 7.3 Accedian Networks 7.4 Accelleran 7.5 Accton Technology Corporation/Edgecore Networks 7.6 Actus Networks 7.7 ADARA Networks 7.8 Adax 7.9 ADLINK Technology 7.1 ADTRAN 7.11 ADVA Optical Networking 7.12 Advantech 7.13 Affirmed Networks 7.14 Airspan Networks 7.15 Akamai Technologies 7.16 ALAXALA Networks Corporation 7.17 Albis Technologies 7.18 Alepo 7.19 Alianza 7.2 Allied Telesis 7.21 Allot Communications 7.22 Alpha Networks 7.23 ALTEN Calsoft Labs 7.24 Altiostar Networks 7.25 Alvarion Technologies 7.26 AMD (Advanced Micro Devices) 7.27 Amdocs 7.28 ANEVIA 7.29 Argela 7.3 Aricent 7.31 Arista Networks 7.32 ARM Holdings 7.33 ARRIS International 7.34 Artesyn Embedded Technologies 7.35 ASOCS 7.36 Astellia 7.37 Athonet 7.38 AttoCore 7.39 AudioCodes 7.4 Avaya 7.41 Avi Networks 7.42 AWS (Amazon Web Services) 7.43 Baicells Technologies 7.44 Barefoot Networks 7.45 Barracuda Networks 7.46 Benu Networks 7.47 Big Switch Networks 7.48 Brain4Net 7.49 Broadcom 7.5 Broadpeak 7.51 CA Technologies 7.52 Canoga Perkins Corporation 7.53 Canonical 7.54 Casa Systems 7.55 CCN (Cirrus Core Networks) 7.56 Cedexis 7.57 Centec Networks 7.58 CENX 7.59 Ceragon Networks 7.6 Certes Networks 7.61 CertusNet 7.62 Check Point Software Technologies 7.63 Ciena Corporation 7.64 Cisco Systems 7.65 Citrix Systems 7.66 Clavister 7.67 ClearPath Networks 7.68 CloudGenix 7.69 Cloudify 7.7 CND (Core Network Dynamics) 7.71 Cobham Group 7.72 Cohesive Networks 7.73 Colt Technology Services Group 7.74 Comodo 7.75 Concurrent 7.76 Contela 7.77 Coriant 7.78 Corsa Technology 7.79 Cradlepoint 7.8 Creanord 7.81 Cumulus Networks 7.82 Cyxtera Technologies 7.83 DASAN Zhone Solutions 7.84 Datavision 7.85 Dell Technologies 7.86 Delta 7.87 Dialogic 7.88 Dimetis 7.89 Docker 7.9 Dorado Software 7.91 Druid Software 7.92 DXC Technology 7.93 ECI Telecom 7.94 Edgeware 7.95 Ekinops 7.96 ELUON Corporation 7.97 Enea 7.98 ENENSYS Technologies 7.99 EnterpriseWeb 7.1 Ericsson 7.101 Ethernity Networks 7.102 Exaware 7.103 EXFO 7.104 Expeto Wireless 7.105 Expway 7.106 Extreme Networks 7.107 F5 Networks 7.108 FibroLAN 7.109 Flash Networks 7.11 Flex 7.111 Fortinet 7.112 FRAFOS 7.113 Fraunhofer FOKUS 7.114 Fujitsu 7.115 Gigamon 7.116 Global Wavenet 7.117 Guangzhou Iplook Technologies 7.118 Harmonic 7.119 Hitachi 7.12 HPE (Hewlett Packard Enterprise) 7.121 Huawei 7.122 HUBER+SUHNER 7.123 HyTrust 7.124 IBM Corporation 7.125 Illumio 7.126 Imagine Communications Corporation 7.127 Infinera 7.128 Infoblox 7.129 Inocybe Technologies 7.13 Intel Corporation 7.131 Interface Masters Technologies 7.132 Intracom Telecom 7.133 IP Infusion 7.134 ip.access 7.135 IPgallery 7.136 iPhotonix 7.137 IPITEK 7.138 Italtel 7.139 iwNetworks 7.14 Juniper Networks 7.141 KEMP Technologies 7.142 Keysight Technologies 7.143 Kleos 7.144 Lanner Electronics 7.145 Lemko Corporation 7.146 Lenovo 7.147 Linker Networks 7.148 Lumeta Corporation 7.149 Lumina Networks 7.15 Luminate Wireless 7.151 Luxoft Holding 7.152 Maipu Communication Technology 7.153 Marvell Technology Group 7.154 MatrixStream Technologies 7.155 Mavenir Systems 7.156 MediaTek 7.157 Megaport 7.158 Mellanox Technologies 7.159 Mesosphere 7.16 Metaswitch Networks 7.161 Microsoft Corporation 7.162 Midokura 7.163 Mirantis 7.164 Mojatatu Networks 7.165 MRV Communications 7.166 Mushroom Networks 7.167 Napatech 7.168 NEC Corporation/Netcracker Technology 7.169 NETGEAR 7.17 Netronome 7.171 Netrounds 7.172 NETSCOUT Systems 7.173 Netsil 7.174 NetYCE 7.175 New H3C Group 7.176 NFVWare 7.177 Nokia Networks 7.178 Nominum 7.179 NoviFlow 7.18 NTT Communications 7.181 NXP Semiconductors 7.182 Omnitron Systems 7.183 One2many 7.184 Openet 7.185 Openwave Mobility 7.186 Opera Software 7.187 Optelian 7.188 Oracle Corporation 7.189 Orchestral Networks 7.19 OX (Open-Xchange) 7.191 Ozono Security 7.192 Packet Design 7.193 Packet Ship Technologies 7.194 Padtec 7.195 Palo Alto Networks 7.196 Panda Security 7.197 Pantheon Technologies 7.198 Parallel Wireless 7.199 PeerApp 7.2 Penguin 7.201 Phluido 7.202 Pica8 7.203 PicoCluster 7.204 Pivotal Software 7.205 Plexxi 7.206 Pluribus Networks 7.207 Polaris Networks 7.208 Pulse Secure 7.209 Qualcomm 7.21 Quanta Computer 7.211 Quortus 7.212 Rackspace 7.213 RAD Data Communications 7.214 RADCOM 7.215 Radisys Corporation 7.216 Radware 7.217 Rapid7 7.218 Realtek Semiconductor Corporation 7.219 Red Hat 7.22 Redknee 7.221 Ribbon Communications 7.222 RIFT.io 7.223 RightScale 7.224 Riverbed Technology 7.225 Ruckus Wireless 7.226 Saguna Networks 7.227 Saisei 7.228 Samsung Electronics 7.229 Sandvine 7.23 Sansay 7.231 Sedona Systems 7.232 Sencore 7.233 SevOne 7.234 Silver Peak 7.235 SiRRAN Communications 7.236 Sistelbanda 7.237 SITRONICS 7.238 Sooktha 7.239 Sophos 7.24 SpiderCloud Wireless 7.241 Spirent Communications 7.242 Stormshield 7.243 SunTec 7.244 Supermicro (Super Micro Computer) 7.245 Symantec Corporation 7.246 SysMaster 7.247 Tango Telecom 7.248 Tecore Networks 7.249 Tejas Networks 7.25 Telchemy 7.251 Telco Systems 7.252 Telcoware 7.253 Telrad Networks 7.254 TI (Texas Instruments) 7.255 Tieto Corporation 7.256 TitanHQ 7.257 Trend Micro 7.258 Tr=F3pico 7.259 UBIqube 7.26 Ultra Electronics 7.261 UTStarcom 7.262 vArmour 7.263 Vasona Networks 7.264 Versa Networks 7.265 Veryx Technologies 7.266 Viavi Solutions 7.267 VMware 7.268 VNC (Virtual Network Communications) 7.269 WatchGuard Technologies 7.27 Wedge Networks 7.271 Wipro 7.272 Wowza Media Systems 7.273 Xilinx 7.274 XOR Media 7.275 Xtera Communications 7.276 Zoho Corporation/WebNMS 7.277 ZTE =20 8 Chapter 8: Market Analysis & Forecasts 8.1 Global Outlook for SDN, NFV & Network Virtualization Revenue: 2017 =96 = 2030 8.2 User Base Segmentation 8.2.1 Enterprises & Data Centers 8.2.2 Service Providers 8.3 Submarket Segmentation 8.3.1 SDN/SD-WAN Hardware & Software 8.3.2 NFV Hardware & Software 8.3.3 Other Network Virtualization Software 8.3.4 Service Provider Submarket Segmentation 8.4 SDN & SD-WAN User Base Revenue: 2017 =96 2030 8.4.1 Service Provider SDN/SD-WAN 8.4.2 Enterprise & Data Center SDN/SD-WAN 8.5 SDN & SD-WAN Submarket Revenue: 2017 =96 2030 8.5.1 SDN-Enabled Switches, Routers & Other Appliances 8.5.2 SDN Controller Software 8.5.3 SDN Orchestration Software 8.5.4 SDN Network Applications 8.5.5 SD-WAN Appliances 8.5.6 SD-WAN Control & Overlay Software 8.6 NFV Submarket Revenue: 2017 =96 2030 8.6.1 NFVI (NFV Infrastructure) 8.6.2 NFV MANO (Management & Orchestration) Software 8.6.3 VNF (Virtualized Network Function) Software 8.7 Functional Area Segmentation for Service Provider SDN & NFV Revenue: 20= 17 =96 2030 8.7.1 CDN 8.7.2 CPE 8.7.3 Data Center 8.7.4 Fixed Access Network 8.7.5 IMS & VoLTE 8.7.6 Mobile Core 8.7.7 Policy Control 8.7.8 RAN 8.7.9 Transport Network 8.7.10 Others 8.8 Regional Outlook 8.9 Asia Pacific SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 8.9.1 Australia 8.9.2 China 8.9.3 India 8.9.4 Japan 8.9.5 South Korea 8.9.6 Pakistan 8.9.7 Thailand 8.9.8 Indonesia 8.9.9 Malaysia 8.9.10 Taiwan 8.9.11 Philippines 8.9.12 Singapore 8.9.13 Rest of Asia Pacific 8.10 Eastern Europe SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 8.10.1 Czech Republic 8.10.2 Poland 8.10.3 Russia 8.10.4 Rest of Eastern Europe 8.11 Latin & Central America SDN, NFV & Network Virtualization Revenue: 201= 7 =96 2030 8.11.1 Argentina 8.11.2 Brazil 8.11.3 Mexico 8.11.4 Rest of Latin & Central America 8.12 Middle East & Africa SDN, NFV & Network Virtualization Revenue: 2017 = =96 2030 8.12.1 South Africa 8.12.3 Qatar 8.12.4 Saudi Arabia 8.12.5 Israel 8.12.6 Rest of the Middle East & Africa 8.13 North America SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 8.13.1 USA 8.13.2 Canada 8.14 Western Europe SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 8.14.1 Denmark 8.14.2 Finland 8.14.3 France 8.14.4 Germany 8.14.5 Italy 8.14.6 Spain 8.14.7 Sweden 8.14.8 Norway 8.14.9 UK 8.14.10 Rest of Western Europe =20 9 Chapter 9: Conclusion & Strategic Recommendations 9.1 Why is the Market Poised to Grow=3F 9.2 Will SDN & NFV Disrupt the Network Infrastructure Value Chain=3F 9.3 Is There a Ring Leader in the SDN & NFV Ecosystem=3F 9.4 Facilitating Fixed-Mobile Network Convergence 9.5 Buyers Will Maintain Focus on Business Agility & CapEx Reduction 9.6 Will Proprietary Hardware Platforms Continue to Exist=3F 9.7 Functional Area Adoption Trends 9.7.1 vCPEs & uCPEs 9.7.2 SD-WAN 9.7.3 Data Center SDN 9.7.4 vIMS 9.7.5 vEPC 9.7.6 vCDN 9.7.7 Cloud RAN 9.7.8 Other Use Cases 9.8 How Much CapEx Can Service Providers Save with SDN & NFV Investments=3F 9.9 The Importance of Interoperable MANO Platforms 9.10 Strategic Recommendations 9.10.1 Recommendations for Enabling Technology Providers 9.10.2 Recommendations for Network Infrastructure Vendors & IT Giants 9.10.3 Recommendations for Pure-Play SDN & NFV Specialists 9.10.4 Recommendations for Enterprises & Data Center Operators 9.10.5 Recommendations for Service Providers List of Figures: Figure 1: The NFV Concept Figure 2: A Comparison of SDN and NFV Figure 3: vRAN Architecture Figure 4: Cloud RAN Concept Figure 5: Virtualized and Non-Virtualized Mobile Core Networks Figure 6: Conceptual Architecture for End-to-End Network Slicing in Mobile = Networks Figure 7: Key Functional Elements of AT&T's FlexWare uCPE Figure 8: Baidu's SDN-Capable IDC (Internet Data Center) Transport Network Figure 9: Key Components of CenturyLink's PSB (Programmable Services Backbo= ne) Architecture Figure 10: CenturyLink's SD-WAN Service Figure 11: ECX Fabric (Equinix Cloud Exchange Fabric) Framework Figure 12: Key Pillar's of Google's SDN Strategy Figure 13: Google's Espresso Peering Edge Architecture Figure 14: NTT Communications' Hybrid Cloud Service Figure 15: NTT Communications' SD-Exchange (Software Defined-Exchange) Figure 16: Evolution of SK Telecom's Infrastructure: COSMOS and ATSCALE Figure 17: SK Telecom=92s SDRAN (Software Defined RAN) Architecture Figure 18: Telef=F3nica's UNICA Infrastructure Platform Figure 19: Telef=F3nica's NFV Development Roadmap Figure 20: Verizon's SDN-NFV High Level Architecture Figure 21: Conceptual Layers of Vodafone's SDN & NFV Architecture Figure 22: SDN, NFV & Network Virtualization Industry Roadmap: 2017 =96 2030 Figure 23: SDN, NFV & Network Virtualization Value Chain Figure 24: CloudNFV Architecture Figure 25: ETSI NFV Architecture Figure 26: Global SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 27: Global SDN, NFV & Network Virtualization Revenue by User Base: 2= 017 =96 2030 ($ Million) Figure 28: Global Enterprise & Data Center SDN & Network Virtualization Rev= enue: 2017 =96 2030 ($ Million) Figure 29: Global Service Provider SDN & NFV Revenue: 2017 =96 2030 ($ Mill= ion) Figure 30: Global SDN, NFV & Network Virtualization Revenue by Submarket: 2= 017 =96 2030 ($ Million) Figure 31: Global SDN/SD-WAN Hardware & Software Revenue: 2017 =96 2030 ($ = Million) Figure 32: Global NFV Hardware & Software Revenue: 2017 =96 2030 ($ Million) Figure 33: Global Other Network Virtualization Software Revenue: 2017 =96 2= 030 ($ Million) Figure 34: Global Service Provider SDN & NFV Revenue by Submarket: 2017 =96= 2030 ($ Million) Figure 35: Global SDN & SD-WAN Revenue by User Base: 2017 =96 2030 ($ Milli= on) Figure 36: Global Service Provider SDN/SD-WAN Hardware & Software Revenue: = 2017 =96 2030 ($ Million) Figure 37: Global Enterprise & Data Center SDN/SD-WAN Revenue: 2017 =96 203= 0 ($ Million) Figure 38: Global SDN & SD-WAN Revenue by Submarket: 2017 =96 2030 ($ Milli= on) Figure 39: Global SDN-Enabled Switch, Router & Other Appliance Revenue: 201= 7 =96 2030 ($ Million) Figure 40: Global SDN Controller Software Revenue: 2017 =96 2030 ($ Million) Figure 41: Global SDN Orchestration Software Revenue: 2017 =96 2030 ($ Mill= ion) Figure 42: Global SDN Network Applications Revenue: 2017 =96 2030 ($ Millio= n) Figure 43: Global SD-WAN Appliance Revenue: 2017 =96 2030 ($ Million) Figure 44: Global SD-WAN Control & Overlay Software Revenue: 2017 =96 2030 = ($ Million) Figure 45: Global NFV Revenue by Submarket: 2017 =96 2030 ($ Million) Figure 46: Global NFVI (NFV Infrastructure) Revenue: 2017 =96 2030 ($ Milli= on) Figure 47: Global NFV MANO (Management & Orchestration) Software Revenue: 2= 017 =96 2030 ($ Million) Figure 48: Global VNF (Virtualized Network Function) Software Revenue: 2017= =96 2030 ($ Million) Figure 49: Global Service Provider SDN & NFV Revenue by Functional Area: 20= 17 =96 2030 ($ Million) Figure 50: Global Service Provider SDN & NFV Revenue in the CDN Functional = Area: 2017 =96 2030 ($ Million) Figure 51: Global Service Provider SDN & NFV Revenue in the CPE Functional= Area: 2017 =96 2030 ($ Million) Figure 52: Global Service Provider SDN & NFV Revenue in the Data Center Fun= ctional Area: 2017 =96 2030 ($ Million) Figure 53: Global Service Provider SDN & NFV Revenue in the Fixed Access Ne= twork Functional Area: 2017 =96 2030 ($ Million) Figure 54: Global Service Provider SDN & NFV Revenue in the IMS & VoLTE Fun= ctional Area: 2017 =96 2030 ($ Million) Figure 55: Global Service Provider SDN & NFV Revenue in the Mobile Core Fun= ctional Area: 2017 =96 2030 ($ Million) Figure 56: Global Service Provider SDN & NFV Revenue in the Policy Control = Functional Area: 2017 =96 2030 ($ Million) Figure 57: Global Service Provider SDN & NFV Revenue in the RAN Functional = Area: 2017 =96 2030 ($ Million) Figure 58: Global Service Provider SDN & NFV Revenue in the Transport Netwo= rk Functional Area: 2017 =96 2030 ($ Million) Figure 59: Global Service Provider SDN & NFV Revenue in the Other Areas: 20= 17 =96 2030 ($ Million) Figure 60: SDN, NFV & Network Virtualization Revenue by Region: 2017 =96 20= 30 ($ Million) Figure 61: Asia Pacific SDN, NFV & Network Virtualization Revenue: 2017 =96= 2030 ($ Million) Figure 62: Australia SDN, NFV & Network Virtualization Revenue: 2017 =96 20= 30 ($ Million) Figure 63: China SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 (= $ Million) Figure 64: India SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 (= $ Million) Figure 65: Japan SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 (= $ Million) Figure 66: South Korea SDN, NFV & Network Virtualization Revenue: 2017 =96 = 2030 ($ Million) Figure 67: Pakistan SDN, NFV & Network Virtualization Revenue: 2017 =96 203= 0 ($ Million) Figure 68: Thailand SDN, NFV & Network Virtualization Revenue: 2017 =96 203= 0 ($ Million) Figure 69: Indonesia SDN, NFV & Network Virtualization Revenue: 2017 =96 20= 30 ($ Million) Figure 70: Malaysia SDN, NFV & Network Virtualization Revenue: 2017 =96 203= 0 ($ Million) Figure 71: Taiwan SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 72: Philippines SDN, NFV & Network Virtualization Revenue: 2017 =96 = 2030 ($ Million) Figure 73: Singapore SDN, NFV & Network Virtualization Revenue: 2017 =96 20= 30 ($ Million) Figure 74: SDN, NFV & Network Virtualization Revenue in the Rest of Asia Pa= cific: 2017 =96 2030 ($ Million) Figure 75: Eastern Europe SDN, NFV & Network Virtualization Revenue: 2017 = =96 2030 ($ Million) Figure 76: Czech Republic SDN, NFV & Network Virtualization Revenue: 2017 = =96 2030 ($ Million) Figure 77: Poland SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 78: Russia SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 79: SDN, NFV & Network Virtualization Revenue in the Rest of Eastern= Europe: 2017 =96 2030 ($ Million) Figure 80: Latin & Central America SDN, NFV & Network Virtualization Revenu= e: 2017 =96 2030 ($ Million) Figure 81: Argentina SDN, NFV & Network Virtualization Revenue: 2017 =96 20= 30 ($ Million) Figure 82: Brazil SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 83: Mexico SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 84: SDN, NFV & Network Virtualization Revenue in the Rest of Latin &= Central America: 2017 =96 2030 ($ Million) Figure 85: Middle East & Africa SDN, NFV & Network Virtualization Revenue: = 2017 =96 2030 ($ Million) Figure 86: South Africa SDN, NFV & Network Virtualization Revenue: 2017 =96= 2030 ($ Million) Figure 87: UAE SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 ($ = Million) Figure 88: Qatar SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 (= $ Million) Figure 89: Saudi Arabia SDN, NFV & Network Virtualization Revenue: 2017 =96= 2030 ($ Million) Figure 90: Israel SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 91: SDN, NFV & Network Virtualization Revenue in the Rest of the Mid= dle East & Africa: 2017 =96 2030 ($ Million) Figure 92: North America SDN, NFV & Network Virtualization Revenue: 2017 = =96 2030 ($ Million) Figure 93: USA SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 ($ = Million) Figure 94: Canada SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 95: Western Europe SDN, NFV & Network Virtualization Revenue: 2017 = =96 2030 ($ Million) Figure 96: Denmark SDN, NFV & Network Virtualization Revenue: 2017 =96 2030= ($ Million) Figure 97: Finland SDN, NFV & Network Virtualization Revenue: 2017 =96 2030= ($ Million) Figure 98: France SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 99: Germany SDN, NFV & Network Virtualization Revenue: 2017 =96 2030= ($ Million) Figure 100: Italy SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 101: Spain SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 = ($ Million) Figure 102: Sweden SDN, NFV & Network Virtualization Revenue: 2017 =96 2030= ($ Million) Figure 103: Norway SDN, NFV & Network Virtualization Revenue: 2017 =96 2030= ($ Million) Figure 104: UK SDN, NFV & Network Virtualization Revenue: 2017 =96 2030 ($ = Million) Figure 105: SDN, NFV & Network Virtualization Revenue in the Rest of Wester= n Europe: 2017 =96 2030 ($ Million) Figure 106: Global SD-WAN Service Revenue by Submarket: 2017 =96 2030 ($ Mi= llion) Figure 107: Global Virtualized Mobile Core Investments by Technology: 2017 = =96 2030 ($ Million) Figure 108: Global Cloud RAN Investments by Submarket: 2017 =96 2030 ($ Mil= lion) Figure 109: Global SDN & NFV Induced Service Provider CapEx Savings Potenti= al: 2017 =96 2030 ($ Million) Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com From owner-freebsd-ppc@freebsd.org Fri Jan 12 22:20:59 2018 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 60E58E7FFE8 for ; Fri, 12 Jan 2018 22:20:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 486B983E9F for ; Fri, 12 Jan 2018 22:20:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3D32F19FBD for ; Fri, 12 Jan 2018 22:20:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0CMKxRF025416 for ; Fri, 12 Jan 2018 22:20:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0CMKxqM025415 for freebsd-ppc@FreeBSD.org; Fri, 12 Jan 2018 22:20:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 201623] /usr/ports/graphics/dri fails on powerpc Date: Fri, 12 Jan 2018 22:20:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zeising@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 22:20:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201623 --- Comment #7 from Niclas Zeising --- Hi! This feels like an issue in the FreeBSD toolchain for ppc rather than an is= sue with the port directly? I have no ppc or ppc64 system to test with, so I need help in fixing this. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Jan 13 00:23:42 2018 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 D7CB9E613C7 for ; Sat, 13 Jan 2018 00:23:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BEE0C6800E for ; Sat, 13 Jan 2018 00:23:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B41A01B273 for ; Sat, 13 Jan 2018 00:23:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0D0Ngtb001507 for ; Sat, 13 Jan 2018 00:23:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0D0Ngmv001506 for freebsd-ppc@FreeBSD.org; Sat, 13 Jan 2018 00:23:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 201623] /usr/ports/graphics/dri fails on powerpc Date: Sat, 13 Jan 2018 00:23:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 00:23:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201623 --- Comment #8 from Mark Millard --- (In reply to Niclas Zeising from comment #7) Some ports allow picking compilers/toolchains that are used in building the port. Others only work with a specific family. Yet others with only specific vintages/versions. What are the constraints on the graphics/mesa-dri compiler/toolchain usage? Can something like lang/gcc6 be used by graphics/mesa-dri ? (Might also require devel/binutils instead of the system toolchain.) If yes, then switching the port to use such a lang/gcc* (and devel/binutils ) might avoid any issues with the previously default compiler, whatever it was. (Presumes someone then uses a powerpc host to test the alternate compiler and toolchain.) If no, then can graphics/mesa-dri be modified to allow alternative compilers/toolchains=20 from ports to be tried by those with an appropriate context for targeting powerpc? [My normal powerpc64 and powerpc context is not a great test case because buildworld was using the problematical clang that messes up handling thrown C++ exceptions in the libraries that clang builds. I report problems that I find, which is why I do the experiments.] --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Jan 13 07:56:48 2018 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 C8D5BE7B27A for ; Sat, 13 Jan 2018 07:56:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFD6E790BF for ; Sat, 13 Jan 2018 07:56:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A3C771F346 for ; Sat, 13 Jan 2018 07:56:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0D7umjb061329 for ; Sat, 13 Jan 2018 07:56:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0D7um20061328 for freebsd-ppc@FreeBSD.org; Sat, 13 Jan 2018 07:56:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 201623] /usr/ports/graphics/dri fails on powerpc Date: Sat, 13 Jan 2018 07:56:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zeising@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 07:56:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201623 --- Comment #9 from Niclas Zeising --- (In reply to Mark Millard from comment #8) I'm not sure about the constraints. It is definitely possible to test anot= her toolchain if the llvm one does not work. However, we are very low on manpow= er, so we would need help in maintaining that, and I don't think any of us have= a readily accessible ppc[64] system to test with. I'm also not sure what the interaction with mesa ports will be, since they explicitly use llvm. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Jan 13 13:02:43 2018 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 504B9E63CC5 for ; Sat, 13 Jan 2018 13:02:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 37BF21046 for ; Sat, 13 Jan 2018 13:02:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2CECB21F19 for ; Sat, 13 Jan 2018 13:02:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0DD2hOR043713 for ; Sat, 13 Jan 2018 13:02:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0DD2gN9043712 for freebsd-ppc@FreeBSD.org; Sat, 13 Jan 2018 13:02:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 201623] /usr/ports/graphics/dri fails on powerpc Date: Sat, 13 Jan 2018 13:02:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: danfe@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 13:02:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201623 Alexey Dokuchaev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danfe@FreeBSD.org --- Comment #10 from Alexey Dokuchaev --- I've just tried to build fresh `graphics/mesa-dri` port on Mac mini G4 runn= ing 12.0-CURRENT (albeit pretty old one, around Mid-2016), and it builds and packages fine (it pulls GCC, but since 5.x and 6.x are broken on powerpc, I have GCC_VERSION set to 4.9 for powerpc). No changes were required for the port itself. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Jan 13 21:53:03 2018 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 C17C9EA71AD for ; Sat, 13 Jan 2018 21:53:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A57A679CC1 for ; Sat, 13 Jan 2018 21:53:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 9AA50269F9 for ; Sat, 13 Jan 2018 21:53:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0DLr3vi001762 for ; Sat, 13 Jan 2018 21:53:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0DLr359001760 for freebsd-ppc@FreeBSD.org; Sat, 13 Jan 2018 21:53:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 201623] /usr/ports/graphics/dri fails on powerpc Date: Sat, 13 Jan 2018 21:53:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zeising@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 21:53:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201623 --- Comment #11 from Niclas Zeising --- (In reply to Alexey Dokuchaev from comment #10) This sounds like everything is ok. Do you set the GCC version globally, or does the ports system pick it up automatically? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Jan 13 22:44:28 2018 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 8E08DEB3DF5 for ; Sat, 13 Jan 2018 22:44:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75AEB7BE05 for ; Sat, 13 Jan 2018 22:44:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6B11A27142 for ; Sat, 13 Jan 2018 22:44:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0DMiSmX027089 for ; Sat, 13 Jan 2018 22:44:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0DMiS8l027088 for freebsd-ppc@FreeBSD.org; Sat, 13 Jan 2018 22:44:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 201623] /usr/ports/graphics/dri fails on powerpc Date: Sat, 13 Jan 2018 22:44:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 22:44:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201623 --- Comment #12 from Mark Millard --- (In reply to Alexey Dokuchaev from comment #10) > it pulls GCC, but since 5.x and 6.x are broken on powerpc What is broken for each of them? The Makefiles are not set up to block building these, which suggests that Mark Linimon's builds have been completing in what looks like a successful status. (He marks things as broken for powerpc64 and for powerpc periodically.) Of course it could be that what is built is still broken in some way at run-time. It is true that, for powerpc64, lang/gcc6 will first cause a lang/gcc5 build in order to bootstrap, avoiding gcc 4.2.1 from the system. The Makefile does not set up such for (32-bit) powerpc . (Should it?) [As I use system-clang in order to find and report problems for targeting powerpc64 and powerpc, my normal powerpc and powerpc64 contexts are not appropriate for tests of such for the officially supported context.] --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Jan 13 22:52:32 2018 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 CD36CEB4597 for ; Sat, 13 Jan 2018 22:52:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 975927C579 for ; Sat, 13 Jan 2018 22:52:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id DFC151F329; Sat, 13 Jan 2018 22:52:31 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id C8D7D1F328 for ; Sat, 13 Jan 2018 22:52:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A8347C570 for ; Sat, 13 Jan 2018 22:52: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id F3F6D272B3 for ; Sat, 13 Jan 2018 22:52:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0DMqUiY051176 for ; Sat, 13 Jan 2018 22:52:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0DMqUat051175 for freebsd-powerpc@FreeBSD.org; Sat, 13 Jan 2018 22:52:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-powerpc@FreeBSD.org Subject: [Bug 214405] base/gcc (r424540) for TARGET_ARCH=powerpc64: g++ does not find the standard c++ headers (file placement vs. lookup mismatch) Date: Sat, 13 Jan 2018 22:52:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-powerpc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 22:52:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214405 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 242 | |17 --=20 You are receiving this mail because: You are the assignee for the bug.=