From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-yw0-f44.google.com ([209.85.213.44]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RN874-0006ou-WA for ptxdist@pengutronix.de; Sun, 06 Nov 2011 20:10:59 +0100 Received: by ywt2 with SMTP id 2so5214870ywt.31 for ; Sun, 06 Nov 2011 11:10:32 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20111106144029.GK20768@pengutronix.de> References: <4EB44121.2010107@erwinrol.com> <20111105112309.GH20768@pengutronix.de> <4EB5D6C9.7040605@erwinrol.com> <20111106103301.GJ20768@pengutronix.de> <4EB688C8.1060205@erwinrol.com> <20111106144029.GK20768@pengutronix.de> Date: Sun, 6 Nov 2011 14:10:32 -0500 Message-ID: From: Jon Ringle Subject: Re: [ptxdist] lndir'ing sysroot-target Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0193965058==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de --===============0193965058== Content-Type: multipart/alternative; boundary=14dae9341151377d1504b115b12e --14dae9341151377d1504b115b12e Content-Type: text/plain; charset=ISO-8859-1 On Sun, Nov 6, 2011 at 9:40 AM, Michael Olbrich wrote: > This won't be a short discussion, but a very welcome one. I've talked a lot > about separating the image generation a bit more. But that's not that easy. > In the end running "ptxdist images" to get on final blob must still be > possible. > We're actually working on some separate tool to create the images, that can > be used separately or by ptxdist to create the images. The main problem we > have here is configuration. Defining the images in kconfig is rather > awkward and not really flexible. However, while we think, we now have > something nice to define images, I still need to work out how to integrate > that with ptxdist... > Any comments on what you would like to see there are welcome. > > Something that I'd like to see is a way to have a kernel+initramfs image to be created as a package. As it stands now, I create a kernel platform image and a rootfs platform image, and because the rootfs image contains kernel modules not contained within the initramfs image, I end up having the kernel built twice with two separate kernel source trees that are basically the same. Jon --14dae9341151377d1504b115b12e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sun, Nov 6, 2011 at 9:40 AM, Michael Olbrich = <m.olbrich= @pengutronix.de> wrote:
This won't be a short discussion, but a very welcome = one. I've talked a lot
about separating the image generation a bit more. But that's not that e= asy.
In the end running "ptxdist images" to get on final blob must sti= ll be
possible.
We're actually working on some separate tool to create the images, that= can
be used separately or by ptxdist to create the images. The main problem we<= br> have here is configuration. Defining the images in kconfig is rather
awkward and not really flexible. However, while we think, we now have
something nice to define images, I still need to work out how to integrate<= br> that with ptxdist...
Any comments on what you would like to see there are welcome.

Something that I'd= like to see is a way to have a kernel+initramfs image to be created as a p= ackage. As it stands now, I create a kernel platform image and a rootfs pla= tform image, and because the rootfs image contains kernel modules not conta= ined within the initramfs image, I end up having the kernel built twice wit= h two separate kernel source trees that are basically the same.

Jon

--14dae9341151377d1504b115b12e-- --===============0193965058== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============0193965058==--