On 04/09/2018 11:01 PM, Kito Cheng wrote:
> Hi Jeff:
>
> You can use -r option (e.g. ./qemu-riscv64 -r 4.15) or set QEMU_UNAME
> environment variable to change the uname for qemu.
That did the trick. Exactly what I needed.
Thanks!
jeff
On 04/10/2018 12:27 AM, Richard W.M. Jones wrote:
> On Mon, Apr 09, 2018 at 04:37:30PM -0600, Jeff Law wrote:
>> Are you guys using qemu user mode emulation for testing purposes? When
>> I've set up a suitable riscv64 rootfs and try to do anything nontrivial
>> in it with qemu user mode emulation
On 04/10/2018 01:55 AM, Andreas Schwab wrote:
> On Apr 10 2018, Kito Cheng wrote:
>
>> You can use -r option (e.g. ./qemu-riscv64 -r 4.15) or set QEMU_UNAME
>> environment variable to change the uname for qemu.
>
> But be aware that the emulated environment still assumes that all system
> calls
>> You can use -r option (e.g. ./qemu-riscv64 -r 4.15) or set QEMU_UNAME
>> environment variable to change the uname for qemu.
>
> But be aware that the emulated environment still assumes that all system
> calls implemented by 4.15 are available, and qemu linux-user generally
> just passes them thr
On Apr 10 2018, Kito Cheng wrote:
> You can use -r option (e.g. ./qemu-riscv64 -r 4.15) or set QEMU_UNAME
> environment variable to change the uname for qemu.
But be aware that the emulated environment still assumes that all system
calls implemented by 4.15 are available, and qemu linux-user gen
On Mon, Apr 09, 2018 at 04:37:30PM -0600, Jeff Law wrote:
> Are you guys using qemu user mode emulation for testing purposes? When
> I've set up a suitable riscv64 rootfs and try to do anything nontrivial
> in it with qemu user mode emulation it immediately complains that my
> kernel is too old --
Hi Jeff:
You can use -r option (e.g. ./qemu-riscv64 -r 4.15) or set QEMU_UNAME
environment variable to change the uname for qemu.
On Tue, Apr 10, 2018 at 6:50 AM, Jeff Law wrote:
> On 04/09/2018 04:47 PM, Stef O'Rear wrote:
>> On Mon, Apr 9, 2018 at 6:37 PM, Jeff Law wrote:
>>> On 04/09/2018 12
On 04/09/2018 04:47 PM, Stef O'Rear wrote:
> On Mon, Apr 9, 2018 at 6:37 PM, Jeff Law wrote:
>> On 04/09/2018 12:04 PM, Jim Wilson wrote:
>>> On 04/08/2018 08:22 AM, Jeff Law wrote:
On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
> I'd like to talk about what changes we (may) need to GC
On Mon, Apr 9, 2018 at 6:37 PM, Jeff Law wrote:
> On 04/09/2018 12:04 PM, Jim Wilson wrote:
>> On 04/08/2018 08:22 AM, Jeff Law wrote:
>>> On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
I'd like to talk about what changes we (may) need to GCC in
Fedora to get it working on 64-bit RISC
On 04/09/2018 12:04 PM, Jim Wilson wrote:
> On 04/08/2018 08:22 AM, Jeff Law wrote:
>> On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
>>> I'd like to talk about what changes we (may) need to GCC in
>>> Fedora to get it working on 64-bit RISC-V, and also (more
>>> importantly) to ask your advice
On 04/08/2018 08:22 AM, Jeff Law wrote:
On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
I'd like to talk about what changes we (may) need to GCC in
Fedora to get it working on 64-bit RISC-V, and also (more
importantly) to ask your advice on things we don't fully
understand yet. However, I don
On Sun, Apr 08, 2018 at 09:22:07AM -0600, Jeff Law wrote:
> On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
> > Hi GCC maintainers!
> >
> > I'd like to talk about what changes we (may) need to GCC in
> > Fedora to get it working on 64-bit RISC-V, and also (more
> > importantly) to ask your advic
On 03/31/2018 12:27 PM, Richard W.M. Jones wrote:
> Hi GCC maintainers!
>
> I'd like to talk about what changes we (may) need to GCC in
> Fedora to get it working on 64-bit RISC-V, and also (more
> importantly) to ask your advice on things we don't fully
> understand yet. However, I don't know ev
13 matches
Mail list logo
