similar to: [PATCH 0/1] Porting klibc to AArch64

Displaying 20 results from an estimated 9000 matches similar to: "[PATCH 0/1] Porting klibc to AArch64"

2013 Nov 11
5
[PATCH V2 0/3] Introduce arm64 support
Hello, Here is V2 of the arm64 support for klibc patch set. Notable changes since the original series: * fp regs dropped from setjmp/longjmp * chmod, lstat and stat re-implemented with *at functions. * open64 merged into open. As with the original, this series is to be applied against the latest klibc, just after 25a66fa README.klibc: update build information V2 has been tested on x86_64
2013 Oct 09
1
[PATCH 0/1] Porting klibc to AArch64
On Wed, 9 Oct 2013 15:51:32 +0200 maximilian attems <maks at stro.at> wrote: > On Wed, Oct 09, 2013 at 03:14:44PM +0530, Anil Singhar wrote: > > Hi All: > > > > We have some patches to port klibc to ArmV8. > > > > The first set of patches from Neil Williams fixes the build issues. > > The second set of patches from Anil Singhar fixes functionalities.
2013 Nov 08
9
[PATCH 0/3] Introduce arm64 support
Hello, This series introduces arm64 support to klibc. I've rebased the work from Neil Williams and Anil Singhar into the following three patches. Most of the code changes are due to new syscall implementations being needed for arm64 as a only a minimal set of syscalls are defined in the arm64 kernel. This series is to be applied against the latest klibc, just after 25a66fa README.klibc:
2013 Oct 09
2
[PATCH 0/1] Porting klibc to arm64
On Wed, 9 Oct 2013 10:44:27 +0000 (UTC) Thorsten Glaser <tg at mirbsd.de> wrote: > Anil Singhar dixit: > > >Manual testing as provided within the package has been done with all > >tests passing. This includes the units tests available under > >usr/klibc/tests, usr/utils, usr/dash and usr/gzip. For dash and > >gzip, only sanity testing has been done. > >
2013 Oct 16
3
Unsupported system calls
On 10/16/2013 12:52 AM, Anil Singhar wrote: > Hi HPA, > > Thanks for your reply. One confusion I have is: > > e.g. 'access' is not supported in aarch64, so should the declaration be: > > <!aarch64> int access(const char *, int); <-- This is how it is currently > indicating that only aarch64 doesn't support it. > > OR > > <?> int
2013 Oct 16
2
Unsupported system calls
On 10/16/2013 12:42 AM, Anil Singhar wrote: > Hi HPA, > > Regarding the architecture un-supported system calls, I wrapped them with > #ifndef __NR_<foo> .. #endif /* __NR_<foo> */ switches. I have already done > that. But you also mentioned that in SYSCALLS.def all these calls should be > present and marked with '?'.. Is that right..? Could you please give
2012 Jan 29
5
[PATCH 0/2 v3] mkstemp() and m68k support
Hi, after a year, I decided to hack on klibc again. I?ve reworked both the patch to add mkstemp(), discussing to use AT_RANDOM as cheap entropy source on IRC (if there will ever be another entropy consumer, I can quickly write a minimal arc4random() seeded from it, as it has only 16 octets), capable of making a working mksh (static and shared) on amd64/xen, and the m68k support code, leading to
2013 Nov 12
0
[klibc:master] arm64: remove useless <klibc/asmmacros.h> file
Commit-ID: 45647d9f97cac184d399eae9bcbe24aef2223f70 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=45647d9f97cac184d399eae9bcbe24aef2223f70 Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Mon, 11 Nov 2013 19:33:40 -0800 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:33:40 -0800 [klibc] arm64: remove useless
2006 Jun 28
35
[klibc 00/31] klibc as a historyless patchset (updated and reorganized)
I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at:
2014 Mar 11
4
[PATCH] add mips64 support
From: Dejan Latinovic <Dejan.Latinovic at imgtec.com> --- usr/include/arch/mips64/klibc/archconfig.h | 3 + usr/include/arch/mips64/klibc/archsetjmp.h | 39 ++++++ usr/include/arch/mips64/machine/asm.h | 76 ++++++++++ usr/include/fcntl.h | 2 +- usr/include/sys/md.h | 1 + usr/include/sys/resource.h | 4 +-
2013 Nov 12
0
[klibc:master] arm64: Add arm64 support
Commit-ID: e4a2c914446ba907c5aaccf6ae1d089a09d21df7 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e4a2c914446ba907c5aaccf6ae1d089a09d21df7 Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:12 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:31:31 -0800 [klibc] arm64: Add arm64 support
2013 Oct 09
0
[PATCH 0/1] Porting klibc to AArch64
On Wed, Oct 09, 2013 at 03:14:44PM +0530, Anil Singhar wrote: > Hi All: > > We have some patches to port klibc to ArmV8. > > The first set of patches from Neil Williams fixes the build issues. > The second set of patches from Anil Singhar fixes functionalities. pleasse come up with a single patchset for the architecture as it is not merged, with signed-offs by both of you
2015 Jan 24
1
[PATCH] add mips64 support
On 12/15/2014 05:56 AM, Dejan Latinovic wrote: > > Hello, > > Any updates on mips64 support for klibc? > > Can I do anything to help merging > mips64 changes? > Sorry, my personal life exploded in late August, and I have bee chronically behind ever since. Is this the only patch needed? From: Dejan Latinovic <Dejan.Latinovic at imgtec.com> Subject: [PATCH]
2013 Oct 15
2
Mailing list fixed
It seems the mailing list has been broken for several days. It should now be temporarily fixed, but because the fix is temporary I can't promise it won't happen again until the permanent fix is available. Sorry for that. -hpa
2013 Aug 02
1
Building klibc on 64-bit Ubuntu
Hi, I am trying to build Klibc on a 64-bit Ubuntu on a x86 machine. Here are the steps I followed: 1. Got the source wget https://launchpad.net/ubuntu/+archive/primary/+files/klibc_2.0.1.orig.tar.gz tar xvzf klibc_2.0.1.orig.tar.gz wget https://launchpad.net/ubuntu/+archive/primary/+files/klibc_2.0.1-3.1ubuntu1.debian.tar.gz tar xvzf
2013 Nov 08
0
[PATCH 3/3] arm64: Introduce arm64 support
Based on work by Neil Williams (codehelp at debian.org) and Anil Singhar (anil.singhar at linaro.org), this patch introduces arm64 support. Signed-off-by: Steve Capper <steve.capper at linaro.org> --- Makefile | 3 +- usr/include/arch/arm64/klibc/archconfig.h | 17 ++++++++++ usr/include/arch/arm64/klibc/archsetjmp.h | 20 ++++++++++++
2014 Sep 08
2
[PATCH] add mips64 support
On 09/08/2014 05:57 AM, Dejan Latinovic wrote: >> From: H. Peter Anvin [hpa at zytor.com] >> Sent: Friday, September 05, 2014 7:13 PM >> To: Dejan Latinovic; YunQiang Su; klibc at zytor.com; maximilian attems >> Subject: Re: [klibc] [PATCH] add mips64 support > >> Why copy the files rather than share them? > > Hi Peter, > here is new version of
2013 Oct 09
0
[PATCH 0/1] Porting klibc to arm64
Anil Singhar dixit: >Manual testing as provided within the package has been done with all tests >passing. This includes the units tests available under usr/klibc/tests, >usr/utils, usr/dash and usr/gzip. For dash and gzip, only sanity testing >has been done. It?s *massively* recommended to try to build mksh against klibc then run mksh?s testsuite, since it?s proven, time and time
2013 Oct 16
1
Unsupported system calls
Also there are lines as follows: <ppc64> int stat::stat(const char *, struct stat *); Should they be changed likewise too..? I mean to <?> Thanks, Anil On 16 October 2013 13:40, Anil Singhar <anil.singhar at linaro.org> wrote: > OK, I will change all <!aarch64> to <?> then. How about lines declared > like the following: > >
2012 May 15
5
[PATCH 0/5] resubmitting pending patches
Hi, I?ve gone through the mailing list archives and hereby want to resubmit my pending patches. Most are independent of each other, except the m68k patch which will only be complete if sigsuspend is also fixed. (It can be applied before that, though.) http://www.zytor.com/pipermail/klibc/2012-January/003173.html [PATCH] fix m68k support Resubmitted here as 0005. While there was a question from