From 17bd98c1fa7948c0b9df0aab555db9a8c1062f45 Mon Sep 17 00:00:00 2001 From: gdisirio Date: Mon, 12 Jul 2010 08:49:55 +0000 Subject: git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@2073 35acf78f-673a-0410-8e92-d51de3d6d3f4 --- docs/src/portguide.dox | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/src/portguide.dox') diff --git a/docs/src/portguide.dox b/docs/src/portguide.dox index 170ca75a3..087724084 100644 --- a/docs/src/portguide.dox +++ b/docs/src/portguide.dox @@ -78,7 +78,7 @@ * core (a common example: ARM7) of a supported microcontroller but has * differences in the internal peripherals.
* If this is your case proceed as follow: - * -# Create a new directory under @p ./os/io/platforms and + * -# Create a new directory under @p ./os/hal/platforms and * name it with the microcontroller name (or family name).
* In case of the ARM-based microcontroller you also need to create a * equally named directory under @@ -87,11 +87,11 @@ * see the existing ports as example. * -# Copy into the newly created directory the most closely related existing * chip port or the naked template files from - * @p ./os/io/templates. + * @p ./os/hal/templates. * -# Work out the differences in the drivers or implement them if you started * from the templates. * -# Edit/create the documentation file @p platform.dox, this - * is required if you want to regenerate this documentation including + * is only required if you want to regenerate this documentation including * your work. * . * Usually this kind of port just requires a serial driver (and those are very -- cgit v1.2.3