From: "Ana Guerrero Lopez" <ana.guerrero@collabora.com>
To: kernelci@groups.io
Subject: New images and possible arch rename
Date: Fri, 31 Aug 2018 01:32:12 +0200 [thread overview]
Message-ID: <20180830233212.GA19856@delenn> (raw)
Hi,
After the PR for adding MIPS got accepted, I have built new debian rootfs images in staging.
They are available at http://staging-storage.kernelci.org/images/rootfs/debian/stretch/20180830.2/
and http://staging-storage.kernelci.org/images/rootfs/debian/stretchtests/20180830.1/
The stretchtest images have been built with this patch https://github.com/kernelci/kernelci-build-staging/pull/54
needed to fix the build of IGT GPU tools from git. Merge welcome!
We have now images for 8 architectures:
- armhf, 32 bits ARM v7 with floating point, little endian.
- armel, 32 bits ARM v4t, little endian.
- arm64, 64 bits ARM v8, little endian. Also known as AArch64.
- x86, 32 bits. Also known as i386.
- x86_64, 64 bits x86. Also known as amd64.
- mips, 32 bits, big endian.
- mipsel, 32 bits, little endian.
- mips64el, 64 bits little endian.
Except for x86 and x86_64, we're using the names used in debian for the archs.
Any objection against renaming them in the future as i386 and amd64? Or at the very least to name
x86 as i386? Guillaume has pointed to me that currently in the kernelci x86 means only x86 on 32 bits
and we would need to introduce x86_64 (or amd64). So for avoiding confusion with x86 and x86_64,
the rename would be a good idea.
Cheers,
Ana
next reply other threads:[~2018-08-30 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 23:32 Ana Guerrero Lopez [this message]
2018-09-03 9:56 ` [kernelci] New images and possible arch rename Guillaume Tucker
2018-09-05 21:23 ` Kevin Hilman
2018-09-06 12:49 ` Guillaume Tucker
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=20180830233212.GA19856@delenn \
--to=ana.guerrero@collabora.com \
--cc=kernelci@groups.io \
/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