From: Pintu Kumar <pintu.ping@gmail.com> To: linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org Subject: Re: How to verify linux-next Date: Fri, 29 Sep 2017 16:08:07 +0530 [thread overview] Message-ID: <CAOuPNLgFUgo0Cbbfu_96R3FHUL5VRnZq+-FMYJQ8XB8NLS_Djg@mail.gmail.com> (raw) In-Reply-To: <CAOuPNLgtf6cbU7JHn5-w00EyEz9k6cS5d+n7FfP1fVTYRKpQmw@mail.gmail.com> Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot with linux-next kernel. So I am trying to find alternative ways, like using the virtual box or qemu-arm. 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next kernel is not booting. 2) For qemu-arm (versatilepb), I am able to build the kernel, but I could not figure out which rootfs to use with it. I tried creating minimal rootfs using busybox, but it does not contain enough interface. I am not able to open multiple terminal and also could not setup ssh to access it using PUTTY. So, if you know of any better rootfs to use with qemu-arm please let me know. Or, if you know of any better option to use linux-next please tell me. It will be really helpful. Thank You! Regards, Pintu
WARNING: multiple messages have this Message-ID (diff)
From: pintu.ping@gmail.com (Pintu Kumar) To: kernelnewbies@lists.kernelnewbies.org Subject: How to verify linux-next Date: Fri, 29 Sep 2017 16:08:07 +0530 [thread overview] Message-ID: <CAOuPNLgFUgo0Cbbfu_96R3FHUL5VRnZq+-FMYJQ8XB8NLS_Djg@mail.gmail.com> (raw) In-Reply-To: <CAOuPNLgtf6cbU7JHn5-w00EyEz9k6cS5d+n7FfP1fVTYRKpQmw@mail.gmail.com> Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot with linux-next kernel. So I am trying to find alternative ways, like using the virtual box or qemu-arm. 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next kernel is not booting. 2) For qemu-arm (versatilepb), I am able to build the kernel, but I could not figure out which rootfs to use with it. I tried creating minimal rootfs using busybox, but it does not contain enough interface. I am not able to open multiple terminal and also could not setup ssh to access it using PUTTY. So, if you know of any better rootfs to use with qemu-arm please let me know. Or, if you know of any better option to use linux-next please tell me. It will be really helpful. Thank You! Regards, Pintu
next prev parent reply other threads:[~2017-09-29 10:38 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-29 9:42 How to verify linux-next Pintu Kumar 2017-09-29 9:46 ` Pintu Kumar 2017-09-29 9:46 ` Pintu Kumar 2017-09-29 10:38 ` Pintu Kumar [this message] 2017-09-29 10:38 ` Pintu Kumar 2017-09-29 12:41 ` valdis.kletnieks 2017-09-29 12:41 ` valdis.kletnieks at vt.edu 2017-09-29 13:05 ` Damian Tometzki 2017-09-29 13:05 ` Damian Tometzki 2017-09-29 13:14 ` Damian Tometzki 2017-09-29 13:14 ` Damian Tometzki 2017-09-29 14:26 ` Pintu Kumar 2017-09-29 14:26 ` Pintu Kumar 2017-09-29 15:45 ` valdis.kletnieks 2017-09-29 15:45 ` valdis.kletnieks at vt.edu 2017-10-02 8:11 ` Kamil Konieczny 2017-10-02 8:11 ` Kamil Konieczny 2017-10-02 11:04 ` valdis.kletnieks 2017-10-02 11:04 ` valdis.kletnieks at vt.edu 2017-09-29 17:53 ` Pintu Kumar 2017-09-29 17:53 ` Pintu Kumar 2017-09-29 21:50 ` Theodore Ts'o 2017-09-29 21:50 ` Theodore Ts'o 2017-09-30 3:58 ` Pintu Kumar 2017-09-30 3:58 ` Pintu Kumar 2017-09-30 5:25 ` Theodore Ts'o 2017-09-30 5:25 ` Theodore Ts'o 2017-10-01 16:28 ` Pintu Kumar 2017-10-01 16:28 ` Pintu Kumar 2017-10-01 16:44 ` Damian Tometzki 2017-10-01 16:44 ` Damian Tometzki 2017-10-01 16:48 ` Randy Dunlap 2017-10-01 16:48 ` Randy Dunlap 2017-10-01 17:03 ` Mike Galbraith 2017-10-01 17:03 ` Mike Galbraith 2017-10-01 18:47 ` Pintu Kumar 2017-10-01 18:47 ` Pintu Kumar 2017-10-01 16:47 ` Theodore Ts'o 2017-10-01 16:47 ` Theodore Ts'o
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAOuPNLgFUgo0Cbbfu_96R3FHUL5VRnZq+-FMYJQ8XB8NLS_Djg@mail.gmail.com \ --to=pintu.ping@gmail.com \ --cc=kernelnewbies@kernelnewbies.org \ --cc=linux-kernel@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.