mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Koch, Alexander" <akoch@init-ka.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Generic BSP for x86
Date: Wed, 12 Oct 2016 13:31:57 +0200	[thread overview]
Message-ID: <2d419d2c-a908-de90-d78e-7f09b72f4263@init-ka.de> (raw)
In-Reply-To: <114e8b80-9f79-b2f7-2bdc-0443e6d22b43@pengutronix.de>

Hi Alex,

>> Is there anything newer to act as a starting point for creating x86
>> images with recent PTXdist versions?
>>
> The DistroKit [0].

Thanks for the hint. I had had a quick look at this before, but found
only the platform definitions for arm7a and rpi, and therefore dropped it.

>
>> 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).

I know 32bit x86 embedded is dull, but I really need to work that Atom
Z510 which does not support x86_64. The box does not have a NIC (yet),
so NFS is currently not an option for me.

So your advice would be to take the DistroKit BSP and create a new
platform for my x86 target?


Regards,

Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-10-12 11:32 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
2016-10-12 11:31   ` Koch, Alexander [this message]
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=2d419d2c-a908-de90-d78e-7f09b72f4263@init-ka.de \
    --to=akoch@init-ka.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