sync old files with reality

git-svn-id: https://svn.pengutronix.de/svn/ptxdist/trunks/ptxdist-trunk@8548 33e552b5-05e3-0310-8538-816dae2090ed

3 files changed, 20 insertions, 75 deletions

diff --git a/Documentation/MIGRATION b/Documentation/MIGRATION
deleted file mode 100644
index 137a5d9fd..000000000
--- a/Documentation/MIGRATION
+++ /dev/null
@@ -1,30 +0,0 @@
-This information should help to easily migrate projects from
-any older ptxdist revisions to the current release.
-
-Migrate a configuration from any other revision
- - open the ptxconfig file with your favorite editor and navigate to the
-   variable definition PTXCONF_CONFIGFILE_VERSION
- - replace the revision definition by the current ptxdist revision you like to work
-   with. You will get the current ptxdist revision be entering:
-     $ ptxdist --version
-
-Migrate a configuration from prior 0.10.1:
- To reuse a 0.10.0 configuration file two things have to change
- in this configuration file:
-  - change/add the variable PTXCONF_CONFIGFILE_VERSION to this
-    configuration file like described in migrate from any other
-    revision.
-  - replace any $(VARIABLE) (=parentheses) occurence by ${VARIABLE} (=curly brackets)
-
-Migrate a configuration from prior 0.10.5:
- Kernel configuration variables names are changed. So every 0.10.4 project
- needs to be reconfigured, if user specific values are in use:
- - kernel version
- - kernel patch control file name
- - kernel configuration file name
- - kernel image type to build
- If the defaults are in use, no modification is required. A "ptxdist oldconfig" does
- the job.
-
-You should examine carefully the resulting configuration. Due to variable name changes
-or packet version updates the old configuration may fail or misses something.
diff --git a/Documentation/README b/Documentation/README
index 8f8ea03de..8804913d4 100644
--- a/Documentation/README
+++ b/Documentation/README
@@ -1,32 +1,4 @@
-PTXdist Documentation Fragments
--------------------------------
+For documentation please refer:
 
-This file is meant as an intermediate place where we can collect
-documentation sniplets; later this will be combined into a "real"
-manual. 
+http://www.pengutronix.de/software/ptxdist/documentation_en.html
 
-Configuring the Kernel
-----------------------
-
-It is currently not possible to configure a 2.4 kernel with the config
-system, because 2.4 is still based on the old CML language, not on
-KConfig like 2.6 and PTXdist. There is a workaround: First you have to
-set a path to a kernel configuration file (in: Kernel->Name of config in
-$(PTXDIST)/config/kernel) to be used) to a config file; the kernel
-config file doesn't need to exist. Choose the desired kernelversion,
-then exit the menuconfig with save and 'make kernel_menuconfig' then the
-kernel is downloaded, extracted patched and the normal menuconfig from
-the kernel is started. PTXdist takes care of changes in the kernels
-.config files, it is copied from and to the specified config file.
-
-
-Developement - new Packets
---------------------------
-
-When adding a new packet to ptxdist which requires a patch, you'd like
-to use $(call get_patches) and $(call patchin), but you can't, because
-the patch isn't in the public repository yet.
-
-So, here's a patch against 'ptxdist-testing-20031001-1.tar.bz2' that
-adds a local repository called patches-local; patches in there are
-applied after those from the public repository.
diff --git a/README b/README
index ce42c6c8e..78ed86201 100644
--- a/README
+++ b/README
@@ -79,9 +79,9 @@ kinds of Linux systems. It was written with embedded systems in mind,
 but there is no reason why you can't use it to configure your firewall,
 router or whatever dedicated "device" comes to your mind.
 
-The job works like this: you run 'ptxdist menuconfig', configure what
-you need and get a 'ptxconfig' file. Run 'ptxdist go' and you'll find a
-root tree in root/. Voila.
+The job works like this: you run 'ptxdist menuconfig' and
+"ptxdist platformconfig", configure what you need. Run 'ptxdist go'
+and you'll find a root tree in <you-platform>/root/. Voila.
 
 All magic necessary to do these things in a cross enviroment are written
 into "recipies", living in rules/*.make, and config menues in
@@ -94,8 +94,7 @@ Directory Layout
 These files and directories are supposed to be in an empty project
 directory:
 
-kernelconfig.native	kernel .config file for the native kernel
-kernelconfig.target	kernel .config file for the target kernel
+configs/		project specific configurations (optional)
 patches/		project specific patches, overwrites the generic
 			ones from PTXdist
 projectroot/		put files here which are to be copied over to
@@ -105,6 +104,8 @@ projectroot/		put files here which are to be copied over to
 			specific rule file.
 ptxconfig		.config file to configure the userland for
 			your project.
+platformconfig		.config file to configure the platform specific
+			part of your project.
 rules/			contains project specific rules
 src -> ...		link to point to your directory containing
 			tarball files for the packets.
@@ -112,25 +113,27 @@ src -> ...		link to point to your directory containing
 Additionally some other directories are being built when you run
 "ptxdist go" or other start other build targets.
 
-build-host/		build directory for host tools
-build-cross/		build directory for cross tools
-build-target/		build directory for target tools
-images/			'ptxdist images' creates tarballs and
+<platform>/build-host/	build directory for host tools
+<platform>/build-cross/	build directory for cross tools
+<platform>/build-target/ build directory for target tools
+<platform>/images/	'ptxdist images' creates tarballs and
 			filesystem images in this directory.
-local/			tools which are installed locally go to this dir
-root/			root filesystem for the target
-state/			state files (show in which state packages
+<platform>/sysroot-target/ target related libs and headerfiles are going to
+			this dir
+<platform>/sysroot-cross/ target related tools, but must run on host are
+			going to this dir
+<platform>/sysroot-host/ host related tools are going to this dir
+
+<platform>/root/	root filesystem for the target
+<platform>/state/	state files (show in which state packages
 			currently are during the compilation)
 
 For more details look at the output of 'ptxdist --help' or see the
 PTXdist manual.
 
-
 Bugs
 ----
 
 - search for FIXMEs
 - see TODO, which is out of date :-)
 
-Robert Schwebel <r.schwebel@pengutronix.de>, 2006-02-19
-