On Fri, Jan 02, 2009 at 10:41:06AM +0100, Jean-Philippe François wrote: > > Just straight forward: > > if you're using a seperate directory for your platform, i.e.: > > phyCORE-i.MX27-trunk, put the kernel patches for linux-2.6.27 into this > > directory: > > configs/phyCORE-i.MX27-trunk/patches/linux-2.6.27/generic/ > > This should be part of my project directory ?
yes > Currently it looks like this : > selected_platformconfig > selected_ptxconfig > platform-AT91SAM9260/ (ptxdist generated) > rules/ > > I guess I don't understand the "if you're using a separate directory for > your platform" part We do it a little bit different here usually, by putting the platformconfig into a separate sub dir (configs/<platformname>), but this makes only sense for multi-platform projects. So in your case there should be no difference between patches/* and the variant Marc described above, because ptxdist first looks in the directory where the platformconfig file is and checks if there is a patches/ directory which is being used and falls back to the workspace if not. In your case both should be identical. <sound of rsc testing/> What you also need in addition to the above is a kernelconfig file; for optical purpuses, you can call it "selected_kernelconfig" and reference it in the selected_platformconfig file: PTXCONF_KERNEL_CONFIG="selected_kernelconfig" I've attached a minimal project to this mail; note that it is for trunk, not for 1.99.10. 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-5555 |
OSELAS.BSP-Pengutronix-Standalone-trunk.tar.bz2
Description: Binary data
-- ptxdist mailing list [email protected]
