From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Sun, 3 Jan 2016 10:27:26 +0100 From: Robert Schwebel Message-ID: <20160103092726.GW30206@pengutronix.de> References: <20151231204831.GA28276@hp2000d> <20160102214949.GA1146@localhost.localdomain> <20160103020237.GA23575@hp2000d> MIME-Version: 1.0 In-Reply-To: <20160103020237.GA23575@hp2000d> Subject: Re: [ptxdist] Future plans for uClibc-ng? List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============0259058310==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de --===============0259058310== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="niUlcCfh/sMBwTxc" Content-Disposition: inline --niUlcCfh/sMBwTxc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 02, 2016 at 06:02:37PM -0800, Bryan Hundven wrote: > > > I'm curious to know if ptxdist/OSELAS.Toolchain plans to support > > > uClibc-ng in the future? > > >=20 > > > http://www.uclibc-ng.org/ > >=20 > > with half a year without commit to uClib git I'm considering it a dead > > project (I failed to verify mailing list activity as neither Firefox > > nor IE (!) allowed me to enter archives). uClibc-ng should be relatively > > easy to support as config system remained the same... Just tried and > > succeded. But are there any active uClibc users? >=20 > Well, I use it for a few platforms. And I get a lot of requests for it's > support on crosstool-ng. We also use uclibc, especially for uCLinux systems. A few years ago, we mainlined Cortex-M3 support. It never gained business traction so far, because the BoM for a system is more expensive and less powerful than the cheaper systems with mmu (like Atmel 9x25, TI AM335, FSL MX23 etc). We still maintain EFM32 in the kernel. However, these days we are seeing more and more Cortex-A cpus emerging with Cortex-M coprocessors. With these devices, running Linux on both cores is a real option (as far as I know, this is already implemented for Vybrid). So uClibc stays relevant and will continue to be in OSELAS.Toolchain. rsc --=20 Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | --niUlcCfh/sMBwTxc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iD8DBQFWiOl++8z+IKgDhyARAkLgAJoCk3lj+uxjEebwcO6b2GHlajlfZwCeKiQk YwjucTdu1RGqodxWqd4TIxc= =6Yq9 -----END PGP SIGNATURE----- --niUlcCfh/sMBwTxc-- --===============0259058310== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0259058310==--