>> > The problem we see is that the system call numbers in qemus
>> > unicore32/syscall_nr.h dont match what is linux mainline kernel. From
>> the
>> > toolchain linked, you seem to have kernel headers and syscall numbers
>> > based on a custom 2.6.32 fork. If one builds unicore32 binaries based
>>
> > The problem we see is that the system call numbers in qemus
> > unicore32/syscall_nr.h dont match what is linux mainline kernel. From the
> > toolchain linked, you seem to have kernel headers and syscall numbers
> > based on a custom 2.6.32 fork. If one builds unicore32 binaries based on
> > Li
> On Thu, Sep 22, 2016 at 11:09:55PM +0800, MPRC wrote:
>> Hi, I'm fixing the syscall problem for linux-user/unicore32 in qemu.
>>
>> I write a "hello world" program to test linux-user/unicore32 in qemu 2.7
>> with toolchain of uc4-1.0.5(you can download it through
>> http://mprc.pku.edu.cn/~guanxu
On Thu, Sep 22, 2016 at 11:09:55PM +0800, MPRC wrote:
> Hi, I'm fixing the syscall problem for linux-user/unicore32 in qemu.
>
> I write a "hello world" program to test linux-user/unicore32 in qemu 2.7 with
> toolchain of uc4-1.0.5(you can download it through
> http://mprc.pku.edu.cn/~guanxuetao
Hi, I'm fixing the syscall problem for linux-user/unicore32 in qemu.
I write a "hello world" program to test linux-user/unicore32 in qemu 2.7 with
toolchain of uc4-1.0.5(you can download it through
http://mprc.pku.edu.cn/~guanxuetao/linux/uc4-1.0.5-hard.tgz). And it's just OK.
It goes well in th
> On 14 June 2016 at 14:43, Xuetao Guan wrote:
>>> On 20 May 2016 at 13:48, Riku Voipio wrote:
On torstaina 12. toukokuuta 2016 17.34.42 EEST, Peter Maydell wrote:
> We should either fix our unicore32 support to use the real
> syscall numbers, or just drop it; since nobody has touche
On 14 June 2016 at 14:43, Xuetao Guan wrote:
>> On 20 May 2016 at 13:48, Riku Voipio wrote:
>>> On torstaina 12. toukokuuta 2016 17.34.42 EEST, Peter Maydell wrote:
We should either fix our unicore32 support to use the real
syscall numbers, or just drop it; since nobody has touched
> On 20 May 2016 at 13:48, Riku Voipio wrote:
>> On torstaina 12. toukokuuta 2016 17.34.42 EEST, Peter Maydell wrote:
>>> We should either fix our unicore32 support to use the real
>>> syscall numbers, or just drop it; since nobody has touched
>>> linux-user/unicore32 since 2012, and there have be
On 20 May 2016 at 13:48, Riku Voipio wrote:
> On torstaina 12. toukokuuta 2016 17.34.42 EEST, Peter Maydell wrote:
>> We should either fix our unicore32 support to use the real
>> syscall numbers, or just drop it; since nobody has touched
>> linux-user/unicore32 since 2012, and there have been no
On torstaina 12. toukokuuta 2016 17.34.42 EEST, Peter Maydell wrote:
QEMU has something that claims to be linux-user support for
the unicore32 guest CPU. However the syscall numbers in
linux-user/unicore32 are nothing like those actually implemented
in the upstream kernel (which uses asm-generic
On 05/12/2016 04:34 AM, Peter Maydell wrote:
QEMU has something that claims to be linux-user support for
the unicore32 guest CPU. However the syscall numbers in
linux-user/unicore32 are nothing like those actually implemented
in the upstream kernel (which uses asm-generic syscall numbers).
We sh
11 matches
Mail list logo
