[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHgaXdL0JY4DQdhAtFcMF245rqHLo+Lvt4apaSROzPGjv7pcMg@mail.gmail.com>
Date: Fri, 26 May 2017 01:38:25 +0530
From: Shubham Bansal <illusionist.neo@...il.com>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Russell King - ARM Linux <linux@...linux.org.uk>
Subject: Re: [PATCH] RFC: arm: eBPF JIT compiler
Hi Florian,
It would be great if you could help me with it.
Currently, what I am doing is.
root@...$ ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make -j4
Then I am using Busybox to build the root filesystem
root@...$ qemu-system-arm -M vexpress-a9 -dtb
./linux/arch/arm/boot/dts/vexpress-v2p-ca9.dtb -kernel
./linux/arch/arm/boot/zImage -append "root=/dev/mmcblk0
console=ttyAMA0" -sd ./a9rootfs.ext3 --nographic
Which machine I should use for ARMv6 in QEMU. Which dtb file I should
use for ? All these questions I have. If anybody knows please let me
know.
Best,
Shubham Bansal
On Fri, May 26, 2017 at 1:14 AM, Florian Fainelli <f.fainelli@...il.com> wrote:
> On 05/25/2017 12:09 PM, Shubham Bansal wrote:
>> Hi Andrew,
>>
>> On Fri, May 26, 2017 at 12:18 AM, Andrew Lunn <andrew@...n.ch> wrote:
>>> On Fri, May 26, 2017 at 12:05:23AM +0530, Shubham Bansal wrote:
>>>> Hi Andrew,
>>>>
>>>> My Apologies.
>>>>
>>>> I will remove the #ifdef CONFIG_CPU_LITTLE_ENDIAN. Do you have the
>>>> ARMv6 machine you can test it on?
>>>
>>> Sorry, i don't have a v6.
>>>
>>> Maybe try kzm with qemu-system-qemu?
>>
>> I am afraid I not so familiar with qemu, otherwise I would have tried
>> to test the code on ARMv5,6,7 myself.
>> If you can help me with that it would be great, Otherwise I think I
>> have to wait for someone to test it for ARMv6. Although, I am pretty
>> sure it would work on that as it worked on ARMv5.
>
> Using QEMU is far less complex than the patch you wrote, the tricky
> point me be to find an ARMv6 root filesystem, unless you build the
> module into the kernel and let it run its tests.
> --
> Florian
Powered by blists - more mailing lists