Re: [ptxdist] [PATCH 1/1] add new packet x-load
Hello, I'm affraid that the file x-load-f243938.tar.bz2 located at the repository is not fine. I was unable to build MLO file with that file. Comparing with the git repository (https://git.gitorious.org/x-load-omap3/mainline.git), I could find the ift target. Best regards, Flavio Flavio de Castro Alves Filho Phi Innovations www.phiinnovations.com Phone: +55 19 3709 1358 Mobile: +55 19 9823 9332 Skype: flavio.de.castro.alves.filho 2010/8/6 Stephan Linz l...@li-pro.net Am Freitag, 6. August 2010, um 09:20:17 schrieb Marc Kleine-Budde: ---snip-- tnx, pushed to master. but, crap, it doesn't work :(...see inline comments: --snip-- +X_LOAD_MAKE_OPT:= CROSS_COMPILE=$(BOOTLOADER_CROSS_COMPILE) HOSTCC=$(HOSTCC) +X_LOAD_MAKE_PAR := NO + +$(STATEDIR)/x-load.prepare: + @$(call targetinfo) + @$(call compile, X_LOAD, $(PTXCONF_X_LOAD_CONFIG)) I think the second parameter overwrites _MAKE_OPT. I'm not sure why it does this, looks like a bug. It should be fixed, but that requires some time and testing... However I can work around this limitation by changing _MAKE_OPT to _MAKE_ENV. This surprises me because it has properly compiled for me I'll push this fix. tnx a lot. I'll try out your fix. Give me a hint (here). -- Viele Grüße, Stephan Linz __ OpenDCC: http://www.li-pro.net/opendcc.phtml PC/M: http://www.li-pro.net/pcm.phtml CDK4AVR: http://cdk4avr.sourceforge.net/ CDK4NIOS: http://cdk4nios.sourceforge.net/ CDK4MSP: http://cdk4msp.sourceforge.net/ CPM4L: http://download.opensuse.org/repositories/home:/rexut:/CPM4L -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Application Development on Ptxdist based OS's
Hello, I would like to share my thoughts about this too. Currently we are using Ptxdist to build embedded Linux distributions for some boards and customized applications. Recently we started to provide training sessions. And our first training is not about how to build new Linux distributions, but how to develop software using embedded Linux. We had this same issue here. Essentialy, an SDK is composed by the toolchain, RFS, kernel source and a board with a previously set embedded Linux distribution. We teach how to use the toolchain and set the communication between the workstation and the board (ssh, nfs, ...). At least here in Brazil, Eclipse IDE is very popular. And, looking at the evolution of the C/C++ customized branch of Eclipse, from the project's website, it is possible to cross-compile applications, load it to the board and launch GDB remote debugging. Everything straight and simple. We adopted this strategy in our training sessions. When we build BSPs, we get the last version of the project, in Eclipse format, and prepare a Ptxdist project as a conventional make project. It works fine. I don't see Ptxdist as a tool for application development. It is a tool to low level system customization. I believe that the challenge here is the easy integration between the Linux distribution and the final application in order to have a final image of the complete software for the embedded system. Best regards, Flavio 2011/11/2 Erwin Rol mailingli...@erwinrol.com: Hey all, a while back I asked if it was possible to split an ptxdist build in two parts, one for the (stable) OS and one for the application. On that question I got some interesting answers that made me wonder; How do others do their application development on ptxdist? From origin Ptxdist is a distribution building tool, so it assumes all applications are finished and combines all parts in a running distribution. And it does a great job, I really can't complain about that. But what if the applications are still in development, they need to be edited, cross-compiled, debugged. And there is where Ptxdist is not so great, at least that's my experience. So how do other people do that ? I read some ppl just don't use Ptxdist at all and just compile their applications in a different way and install them on the finished Ptxdist OS. But that duplicates the whole cross-chain stuff, like compiler, libraries and headers. I have seen other build systems that seem to export some API for use by applications developers. Maybe something like that can be done with Ptxdist too, for example exporting the sysroot-target directory and use that to build applications. Anny other people with wild ideas and nice custom Ptxdist enhancements that they want to share ? - Erwin -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] General Ptxdist usecase question
Hello Erwin, I would encourage you use the pre-built packages approach from Ptxdist, as suggested. The main issue will be managing the packages correctly. For now, I'm not using this approach. But, for bigger systems, it seems to be inevitable. Best regards, Flavio 2011/10/28 Michael Olbrich m.olbr...@pengutronix.de: On Fri, Oct 28, 2011 at 12:05:06PM +0200, Erwin Rol wrote: On 28-10-2011 11:29, Michael Olbrich wrote: On Fri, Oct 28, 2011 at 10:21:22AM +0200, Erwin Rol wrote: The projects I use Ptxdist for have grown in size over the last few years, they now include mono, gtkwebkit, boost, clutter, gtk3 and all the Xorg stuff. That means it now takes more than 2 hours to compile it from scratch. The machine is not the fastest (only 4 core 3GHz) but even if it was twice as fast it would still compile over and hour. So I am looking for a way to prevent a full rebuild on every project release. There seem to be some features in Ptxdist that should allow this, but I could not really figure out how to use them. What I would like to do is this; 1) Build an OS with all the Xorg, mono, gtk, etc. stuff and version that. This is stable, right? Fix PTXdist version, no option changes etc.? Yeah that is the idea. Of course like with any other OS/distribution there will be updates at some point. 2) build my own applications. 3) combine the results from step 1 and 2 into an image for flashing 4) goto 2 Is it possible to do this with Ptxdist and if so, how ? Take a look at the PROJECT_CREATE_DEVPKGS/PROJECT_USE_DEVPKGS options. With PROJECT_CREATE_DEVPKGS you getpkg-version-hash-dev.tar.gz for most packages. This is the content ofPKG_PKGDIR. With PROJECT_USE_DEVPKGS you can specify a folder contain such archives. If a matching archive is found, the stages up to install are skipped and the archive is extracted instead. The hash makes sure the sub-options used to create the archive are the correct ones. Note: You cannot use your own packages dir. That introduces really strange circular dependencies. I looked into that a bit, but my problem are the configuration files. If I understand the idea correct you start with two exactly the same setups (same ptxdistconfig and pladformconfig) and than say the first setup should create packages and the second setup should use packages. Is it possible to somehow reference to the prebuild system and prevent the user from changing the settings that are in common with that prebuild system? No, but if you change an option, then the affected package is built again instead of using the pre-built archive. You won't get a broken system, you'll just rebuild more. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Order of packages to be built
Hello, I did that, and worked. But, I'm curious if ptxdist could generate a priori a list of the order of the packages that will be compiled. It would be a nice tool, specially for debugging purposes. Best regards, Flavio 2011/2/10 Michael Olbrich m.olbr...@pengutronix.de: Hi, On Thu, Feb 10, 2011 at 10:02:07AM -0200, Flavio de Castro Alves Filho wrote: How do I know the order of the packages that will be compiled in ptxdist? I am currently creating the packages for the EFL libraries and I need to build the X11 before starting the build of my packages. have a look at rules/*.in: select PKG_NAME is translated into the correct make dependencies. Note, that the selects must be defined for the primary kconfig option for the package. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Order of packages to be built
Hello, How do I know the order of the packages that will be compiled in ptxdist? I am currently creating the packages for the EFL libraries and I need to build the X11 before starting the build of my packages. Best regards, Flavio -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Toolchain - generating big endian arm cortex a8 toolchain
Hello Marc, I used ptxdist 2010.10 and it worked perfectly. Thank you for your help. Just one final question: how can I validate that a kernel was correctly compiled in big endian? Best regards. Flavio 2010/11/16 Marc Kleine-Budde m...@pengutronix.de: On 11/16/2010 10:22 PM, Flavio de Castro Alves Filho wrote: Hello Marc, I was quite daring ... I tried the default configuration file ptxconfigs/armeb-cortexa8-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig and changed the arm- to armeb-, as you adviced. Unfortunatelly, it doesn't worked. I got the following error message: any idea? I think ptxdist-2010.11.0 has a bug, try 2010.10.0 or http://git.pengutronix.de/?p=ptxdist.git;a=shortlog;h=refs/heads/stable/ptxdist-2010.11.x cheers, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917- | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de | -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Toolchain - generating big endian arm cortex a8 toolchain
Hello Marc, Does it mean that, even if I build a big endian toolchain, my arm-cortex-a8 kernel (in my case, the am3517 from TI) will be built in little endian? How about the applications? I thought that if I build a toolchain with just big endian capabilities, all the generated code would be big endian. Am I correct? Thank you for your help. Best regards, Flavio 2010/11/17 Marc Kleine-Budde m...@pengutronix.de: On 11/17/2010 03:19 PM, Flavio de Castro Alves Filho wrote: Hello Marc, I used ptxdist 2010.10 and it worked perfectly. Thank you for your help. Just one final question: how can I validate that a kernel was correctly compiled in big endian? The kernel build system doesn't care about the defaults of the toolchain. You can use a arm-11 le toolchain to build a arm v5 be kernel and vice versa. The actual endianess is controlled by the kernel build options. For example if I select the ARM system type (IXP4xx-based) the Kconfig system gives me the option Build big-endian kernel. A quick search shows that only the IXPs support BE Kernels: wcgrep ARCH_SUPPORTS_BIG_ENDIAN arch/arm/ arch/arm/mach-ixp4xx/Kconfig:3:config ARCH_SUPPORTS_BIG_ENDIAN arch/arm/mm/Kconfig:633: depends on ARCH_SUPPORTS_BIG_ENDIAN arch/arm/mach-ixp23xx/Kconfig:3:config ARCH_SUPPORTS_BIG_ENDIAN arch/arm/mach-ixp2000/Kconfig:4:config ARCH_SUPPORTS_BIG_ENDIAN cheers, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917- | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de | -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Toolchain - generating big endian arm cortex a8 toolchain
Hello Marc, That's what happened. My ptxdist builds an LE kernel (using a BE toolchain) and does not boot the root filesystem because it is BE. For now, I could now find an option in the kernelconfig in order to allow BE build of the kernel. I am using the Linux provided by Texas Instruments, with the pre-implemented patches. The configuration file is the specific for the AM3517 processor. Thank you for your help. Now I'm searching a way do set the Linux kernel to, at least, accept big endian binaries. Best regards, Flavio 2010/11/17 Marc Kleine-Budde m...@pengutronix.de: On 11/17/2010 05:04 PM, Flavio de Castro Alves Filho wrote: Does it mean that, even if I build a big endian toolchain, my arm-cortex-a8 kernel (in my case, the am3517 from TI) will be built in little endian? That depends on your kernelconfig. I don't know if big endian is supported by the processor in general and the kernel for that processor. How about the applications? They are build as big endian. But they won't run on a LE system :(. I thought that if I build a toolchain with just big endian capabilities, all the generated code would be big endian. Am I correct? All code by default, unless you tell the compiler to do otherwise. And the kernel does so. It will overwrite the default endianess of the toolchain. cheers, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917- | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de | -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Toolchain - generating big endian arm cortex a8 toolchain
Hello, We are currently working on a platform migration from a big endian processor to an ARM Cortex A8 processor. I saw that ARM processors are bi-endian - it supports both little endian and bi endian software. And the compiler must be prepared to generate both little endian and big endian code. Looking at the OSELAS.Toolchain project, I could not see any option regarding the endianess of the generated toolchain. So, I would like to ask if it is possible to have an arm-cortexa8 toolchain that generates big endian code and what should I do to build this toolchain. Thank you and best regards, Flavio -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Backport of udev
Hello, I am currently working on a project that I have to use udev version 140. The reason is that I have to use a kernel version 2.6.23, which does not support signalfd. This features (signalfd) is used by udev in order to create devices configuration. I am using ptxdist 2010.11, which uses a newer version of udev (160 or 162, I believe). So, I would like to ask which is the best approach, considering that we use ptxdist for several projects and the use of this udev is an exceptional case for this project. Best regards, Flavio -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Backport of udev
Hello Juergen, I did that ... before posting this email. It worked fine. But, later on I perfomed a rebuild and saw some errors during the build. Not really error, but some internal environment variables problems, but the build worked fine. For now, the solution was to use ptxdist 2010.01. That's not that bad, considering that's a small system. I will perform again the procedure and send you more details. Thank you and best regards, Flavio 2010/11/7 Juergen Beisert j...@pengutronix.de: Hi Flavia, Flavio de Castro Alves Filho wrote: I am currently working on a project that I have to use udev version 140. The reason is that I have to use a kernel version 2.6.23, which does not support signalfd. This features (signalfd) is used by udev in order to create devices configuration. I am using ptxdist 2010.11, which uses a newer version of udev (160 or 162, I believe). So, I would like to ask which is the best approach, considering that we use ptxdist for several projects and the use of this udev is an exceptional case for this project. You can search in older ptxdist revisions for a matching udev version. Just search for the files rules/udev.make and check the used udev version (the UDEV_VERSION macro). If you found a matching version, copy the files rules/udev.make, rules/udev.in and (maybe) patches/udevversion to your local project directory. ptxdist will prefer these local files from the global files. So, this is a way to use an older revision of a package in a project, even if the used ptxdist comes with a more recent one. jbe -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | Phone: +49-8766-939 228 | Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917- | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ | -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Several partitions in ptxdist images
Hello, I am using ptxdist to build a x86 Linux to be inserted in a compact flash disk. I intend to have two partitions: one with the operating system and another with the application. With ptxdist I could easily create both partitions. Using ptxdist images, the image with both partitions is created but I don't know how to add files to the second partition. I would like to add my application package directly to this second partition. How could I do this using ptxdist? Best regards, Flavio -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Ptxdist for mpc8313 rdb
Hello, I am currently trying to build a ptxdist application for the Freescale PowerPC MPC8313 RDB board. I configured the linux kernel 2.6.34 using the 83xx/mpc8313_rdb_defconfig configuration file and compiled with the gcc 4.3.2 from the OSELAS toolchain project for the powerpc-603e. All the compilation works fine, from both kernel and root filesystem. When I load the kernel to the board, the kernel is correctly load and uncompressed but the boot does not occur. After the uncompression, it hangs. The kernel is loaded in the memory position 0x100 and the bootargs is rw console=ttys0,115200 root=/dev/nfs. Does anybody have any idea about what is causing this problem? Best regards, Flavio -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Ptxdist for mpc8313 rdb
Hello, I changed to ttyS0 but the problem persists. Here it is the output. === CPU: e300c3, MPC8313E, Rev: 21 at 333.333 MHz, CSB: 166 MHz Board: Freescale MPC8313ERDB I2C: ready DRAM: 128 MB FLASH: 8 MB NAND: 32 MiB In:serial Out: serial Err: serial Net: TSEC0, TSEC1 [PRIME] Hit any key to stop autoboot: 0 Speed: 100, full duplex Using TSEC1 device TFTP from server 192.168.0.1; our IP address is 192.168.0.2 Filename 'uImage'. Load address: 0x100 Loading: # # # # # # ### done Bytes transferred = 2010252 (1eac8c hex) ## Booting image at 0100 ... Image Name: Linux-2.6.34 Created: 2010-09-23 15:54:10 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:2010188 Bytes = 1.9 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK === Is there any specific powerpc configuration that might be done? I am using the kernel configuration file from the mainstream. Is it an issue? Best regards, Flavio 2010/9/23 Gary Thomas g...@mlbassoc.com: On 09/23/2010 12:42 PM, Flavio de Castro Alves Filho wrote: Hello, I am currently trying to build a ptxdist application for the Freescale PowerPC MPC8313 RDB board. I configured the linux kernel 2.6.34 using the 83xx/mpc8313_rdb_defconfig configuration file and compiled with the gcc 4.3.2 from the OSELAS toolchain project for the powerpc-603e. All the compilation works fine, from both kernel and root filesystem. When I load the kernel to the board, the kernel is correctly load and uncompressed but the boot does not occur. After the uncompression, it hangs. The kernel is loaded in the memory position 0x100 and the bootargs is rw console=ttys0,115200 root=/dev/nfs. Does anybody have any idea about what is causing this problem? The console device should be ttyS0 (upper case matters) -- Gary Thomas | Consulting for the MLB Associates | Embedded world -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] How to apply a u-boot patch?
It worked. Thank you very much. Flavio 2010/8/23 Robert Schwebel r.schwe...@pengutronix.de: On Mon, Aug 23, 2010 at 04:56:39PM -0300, Flavio de Castro Alves Filho wrote: As previously defined, the patch series file field in ptxdist platformconfig - bootloaders - U-Boot contains the value series. Correct. I created the series file in patches/u-boot directory and stored the patch file in the same directory. It has to be patches/u-boot-version, not just u-boot. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] How to apply a u-boot patch?
Hello, I am trying to build u-boot on ptxdist and I am having problems with the patch file. As previously defined, the patch series file field in ptxdist platformconfig - bootloaders - U-Boot contains the value series. I created the series file in patches/u-boot directory and stored the patch file in the same directory. When I launch the ptxdist, after extracting the file, it doesn't find the patch information. What am I doing wrong? I am using ptxdist version 2010.07.1. Best regards, Flavio -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Ptxdist support for linux 2.4.x
Hello, I would like to know if the latest version of ptxdist (svn) supports building 2.4.x kernels and filesystems. Should I proceed in the same way as 2.6.x kernel versions? Best regards, Flavio Flavio de Castro Alves Filho Phi Innovations - Embedded Software Services www.phiinnovations.com Phone: +55 11 84 94 56 76 Skype: flavio.de.castro.alves.filho -- ptxdist mailing list ptxdist@pengutronix.de
