ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Petr Vorel <pvorel@suse.cz>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Christophe Lyon <christophe.lyon@linaro.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	buildroot@buildroot.org, Greg Ungerer <gerg@linux-m68k.org>,
	ltp@lists.linux.it, automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] Call for nommu LTP maintainer [was: Re: [PATCH 00/36] Remove UCLINUX from LTP]
Date: Fri, 5 Jan 2024 21:58:30 -0600	[thread overview]
Message-ID: <90c1ddc1-c608-30fc-d5aa-fdf63c90d055@landley.net> (raw)
In-Reply-To: <20240105131135.GA1484621@pevik>

On 1/5/24 07:11, Petr Vorel wrote:
>> Nobody is maintaining "uclinux" because that was a distro, but you can build
>> nommu support in buildroot and such, and people do.
> 
> Right, there are nommu users. Will anybody join LTP development to maintain
> nommu support in LTP? The needed work is to add this support to LTP new C API
> [1] and use it in the relevant test. There is some implementation in the old
> API, I have no idea how well it worked.
> 
> If nobody stands for maintaing nommu, we will have to delete it. There is nobody
> from the current maintainers who is using LTP on nommu HW (that is the reason why
> nommu support have not been implemented in the new API).

I'm interested, but overwhelmed. Not sure I've got the spoons to come up to
speed on a new project and give it regular attention just now.

I see you cc'd buildroot (although the message might not go through if you
aren't subscribed, dunno how clogged their moderation queue is these days, and
the cc: list is long enough it might twig anyway). They had a nommu fix go in
earlier this week (commit 98684ba7885b).

That said, qemu supports several nommu platforms and buildroot has defconfigs to
build systems for them:

$ git clone git://buildroot.org/buildroot
$ make help
$ make list-defconfigs | grep qemu
$ make qemu_ppc_bamboo_defconfig
$ make
  (time passes...)
>>> host-gettext-tiny 0.3.2 Extracting
gzip -d -c
/home/landley/buildroot/buildroot/dl/gettext-tiny/gettext-tiny-0.3.2.tar.gz |
tar --strip-components=1 -C
/home/landley/buildroot/buildroot/output/build/host-gettext-tiny-0.3.2   -xf -
mkdir -p
/home/landley/buildroot/buildroot/output/build/host-gettext-tiny-0.3.2/gettext-gnu
xzcat /home/landley/buildroot/buildroot/dl/gettext-tiny/gettext-0.22.4.tar.xz |
tar --strip-components=1 -C
/home/landley/buildroot/buildroot/output/build/host-gettext-tiny-0.3.2/gettext-gnu
 -xf -
xzcat: /home/landley/buildroot/buildroot/dl/gettext-tiny/gettext-0.22.4.tar.xz:
No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
make: *** [package/pkg-generic.mk:209:
/home/landley/buildroot/buildroot/output/build/host-gettext-tiny-0.3.2/.stamp_extracted]
Error 2


Sigh, never build git pull du jour of anything, buildroot's having glitch du
jour. But the point is:

$ grep -rl bamboo board/
board/qemu/ppc-bamboo/readme.txt
$ cat board/qemu/ppc-bamboo/readme.txt
Run the emulation with:

qemu-system-ppc -nographic -M bamboo -kernel output/images/vmlinux -net
nic,model=virtio-net-pci -net user # qemu_ppc_bamboo_defconfig

The login prompt will appear in the terminal that started Qemu
-------------------

In THEORY, once it builds an image (presumably using a tagged release version
rather than expecting "continuous integration" to ever mean anything) you should
be able to launch it with qemu. Assuming the instructions aren't also
bit-rotted. (Or using one of the other nommu boards, I haven't gone through the
whole list to see what they've got. I used to use a nommu arm board, but the
linux kernel broke it when converting everything to device tree and not
regression testing it.)

Buildroot also apparently has an LTP package selectable in menuconfig:

https://github.com/buildroot/buildroot/tree/master/package/ltp-testsuite

But I haven't tried it...

Rob

P.S. I automate qemu testing all the time over in toybox, see testroot.sh under
https://github.com/landley/toybox/tree/master/mkroot for an example.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-01-08  9:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  1:52 [LTP] [PATCH 00/36] Remove UCLINUX from LTP Petr Vorel
2024-01-03  7:58 ` Cyril Hrubis
2024-01-03  8:04   ` Cyril Hrubis
2024-01-03  8:39     ` Petr Vorel
2024-01-03  9:46 ` Geert Uytterhoeven
2024-01-03 11:49   ` Petr Vorel
2024-01-03 11:54     ` Geert Uytterhoeven
2024-01-03 12:09       ` Cyril Hrubis
2024-01-03 12:40         ` Petr Vorel
2024-01-05  3:52         ` Rob Landley
2024-01-05 13:11           ` [LTP] Call for nommu LTP maintainer [was: Re: [PATCH 00/36] Remove UCLINUX from LTP] Petr Vorel
2024-01-06  3:58             ` Rob Landley [this message]
2024-01-08  9:03               ` Petr Vorel
2024-01-08 10:07                 ` Cyril Hrubis
2024-01-09 22:37                   ` [LTP] [Automated-testing] " Bird, Tim
2024-01-10  5:01                     ` Rob Landley
2024-01-10 14:14                     ` Petr Vorel
2024-01-10 19:23                       ` Rob Landley
2024-01-10 21:17                         ` Niklas Cassel via ltp
2024-01-11  0:00                           ` Greg Ungerer
2024-01-11  9:21                             ` Niklas Cassel via ltp
2024-01-12 20:18                               ` Rob Landley
2024-01-11  2:25                         ` Greg Ungerer
2024-01-12 20:16                           ` Rob Landley
2024-01-14 13:01                             ` Greg Ungerer
2024-01-15 13:41                             ` [LTP] [Buildroot] " Waldemar Brodkorb
2024-01-15 14:22                               ` Cyril Hrubis
2024-01-11 13:11                         ` [LTP] " Geert Uytterhoeven
2024-01-11 13:19                           ` Greg Ungerer
2024-01-09 20:24                 ` [LTP] " Rob Landley
2024-01-09 23:17                   ` Greg Ungerer
2024-01-10  5:47                     ` Rob Landley
2024-01-10 14:46                       ` Greg Ungerer
2024-01-10 13:33                   ` Petr Vorel
2024-01-10 18:23                     ` Rob Landley
2024-01-10 22:33                       ` Petr Vorel
2024-01-08  8:33           ` [LTP] [PATCH 00/36] Remove UCLINUX from LTP Andrea Cervesato via ltp
2024-01-08  8:34           ` Andrea Cervesato via ltp
2024-01-05  3:50   ` Rob Landley
2024-01-31  0:05 [LTP] Call for nommu LTP maintainer [was: Re: [PATCH 00/36] Remove UCLINUX from LTP] Giovanni Lostumbo

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=90c1ddc1-c608-30fc-d5aa-fdf63c90d055@landley.net \
    --to=rob@landley.net \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=buildroot@buildroot.org \
    --cc=christophe.lyon@linaro.org \
    --cc=corbet@lwn.net \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=rdunlap@infradead.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).