From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Sun, 3 Jan 2016 01:35:26 -0800 From: Bryan Hundven Message-ID: <20160103093526.GB25330@hp2000d> References: <20151231204831.GA28276@hp2000d> <20160102214949.GA1146@localhost.localdomain> <20160103020237.GA23575@hp2000d> <20160103092726.GW30206@pengutronix.de> MIME-Version: 1.0 In-Reply-To: <20160103092726.GW30206@pengutronix.de> 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="===============1653195897==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: Robert Schwebel Cc: ptxdist@pengutronix.de --===============1653195897== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IrhDeMKUP4DT/M7F" Content-Disposition: inline --IrhDeMKUP4DT/M7F Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Robert, On Sun, Jan 03, 2016 at 10:27:26AM +0100, Robert Schwebel wrote: > 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 relativ= ely > > > 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. >=20 > 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. Specifically, I still mess around with the EFM32 port, which is why this was an interest. Although I realize it is not a focus of pengutronix. But being able to turn on and off parts of uClibc/uClibc-ng also helps to shrink the user-space footprint on other systems as well. > 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). >=20 > So uClibc stays relevant and will continue to be in OSELAS.Toolchain. Indeed. -Bryan --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWiOteAAoJEMrXyPw1uHHR8CYIAMzVZ6B8Eou/2jmtVhoVVi02 3dBc/5MVmkO+nRpNzoG6LrF2glpfaua0bOeLd1YmgpyQEDqS5SxrfraVO0OeoWpo AaMmrzkLs2i4BEX36S1uZ0JlvFhxsSB2mXlWx/Lfocg72BW4dyU1xeAoBB4RctNO bOc2+JTTVFw0SY13Vi9/BzaLD1L7rdRCYqUrNjldBmbtOq/socf3i/jiHIDUe7Lb dc8zOXQLBLnvwx68fNeF9SWSEqcWGzr3xe9YTXVtmEdlrBnlTdXCI8J5KbUxg8Nk BjPbIKePookoIO/i9dlYwlFldVE03cgnIpVqK+sNhJvyfOCiVwT3udBysdzN+Vw= =GZ2s -----END PGP SIGNATURE----- --IrhDeMKUP4DT/M7F-- --===============1653195897== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============1653195897==--