From: Alexander Aring <aar@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Generic BSP for x86
Date: Wed, 12 Oct 2016 12:26:08 +0200 [thread overview]
Message-ID: <114e8b80-9f79-b2f7-2bdc-0443e6d22b43@pengutronix.de> (raw)
In-Reply-To: <26b447ea-c4c5-d25b-ff17-bd7001b8ebba@init-ka.de>
Hi,
On 10/12/2016 08:38 AM, Koch, Alexander wrote:
> Hi all,
>
> I'd like to build an image for an x86 box (Intel Atom Z510). Coming from
> the official documentation quickstart I found the OSELAS Generic BSP
> [1], which seems to be based on ptxdist-2014.07.0.
>
> I tried migrating it to ptxdist-2016.04.0 but multiple components (e.g.
> klibc) fail to build.
>
> Is there anything newer to act as a starting point for creating x86
> images with recent PTXdist versions?
>
The DistroKit [0].
> Any advice on how to get to an x86 image without creating a new BSP from
> scratch is appreciated. I'm not new to PTXdist but have only done ARM
> images so far.
>
I currently have some i586 plattform here (because doing some
experiments with a project which has 32 bit support only and I don't
fight currently for x86_64 multilib support.) Nevertheless, it's not
mainline and x86 32 bit system is somewhat deprecated (in my opinion).
It's really simple to create a new plattform, if you are interest in
using the BSP in QEMU, then you can also use v7a plattform and the
run-nfs script will use a nfs userspace server, started by ptxdist
nfsroot.
Also the created image can be put into beaglebone (white/black) or RPi2.
- Alex
[0] https://git.pengutronix.de/cgit/DistroKit
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-12 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 6:38 Koch, Alexander
2016-10-12 10:26 ` Alexander Aring [this message]
2016-10-12 11:31 ` Koch, Alexander
2016-10-12 11:42 ` Alexander Aring
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=114e8b80-9f79-b2f7-2bdc-0443e6d22b43@pengutronix.de \
--to=aar@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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