+=========================
+
+For Mac OS X there are a few dependencies which must be installed. The wget
+and libftdi packages are required and gmp, mpfr, mpc and libiconv are needed
+by GCC-4.5.1. These can be installed using MacPorts, DarwinPorts or fink.
+
+ $ port install gmp mpfr libmpc wget libftdi
+
+For XML support in gdb you may want to install expat too. And add the
+--with-expat parameter to the GDB target.
+
+Notes for Linux users:
+======================
+You need to install several packages. On Debian just run:
+
+ $ apt-get install flex bison libgmp3-dev libmpfr-dev libncurses5-dev \
+ libmpc-dev autoconf texinfo build-essential libftdi-dev
+
+You may want to try running the following command instead too:
+
+ $ apt-get build-dep gcc-4.5
+
+For XML support in gdb you may want to install libexpat1 and libexpat1-dev too.
+
+Usage notes:
+============
+
+We support multilib now in SAT thanks to Eric Parsonage's and Bernard
+Davison's amazing work. You want to use the following GCC flag combinations to
+generate full fledged floating point supporting code for some selected
+architectures.
+
+* stm32 (probably cortex-m3 in general): -mthumb -march=armv7 -mfix-cortex-m3-ldrd -msoft-float
+* lpc21 (thumb instruction set): -mthumb -msoft-float
+* lpc21 (arm instruction set): -mthumb -march=armv4t -msoft-float
+
+If you need support for some other ARM MCU and know the parameters for it,
+just drop us a line and we will add that combination to the multilibs.
+
+You can list available combinations by running:
+
+ $ arm-none-eabi-gcc -print-multi-lib
+
+How to submit improvements and patches
+======================================
+
+As more and more people start to submit patches and improvements to
+Summon-Arm-Toolchain (SAR) this section seems to become necessary.
+
+First of all any way of submission is appreciated, if you just want to dump
+your version of the script to us feel free to do so. Still if you want your
+improvements and fixes to go upstream quicker there is a good way to do that.
+
+1) Create an account on GitHub (or some other git hosting service, if you
+ really have to).
+2) Fork the main SAR repository.
+3) Clone the forked repository to your disk.
+4) Change the script, try to make small changes adding one feature or bugfix at
+ a time (that makes review much easier for us).
+5) Push your changes to GitHub, or the other service you chose.
+6) Test your changes, by compiling the toolchain (you probably want to do that
+ with different options).
+7) Make sure that everything still works.
+8) Test a little bit more.
+9) Click on "pull request" on GitHub or drop us a line so that we can pull your
+ changes.
+
+I know that sounds like a lot of work, but if you don't we have to do it and
+that means that your awesome improvement or bugfix will take longer to be
+integrated into the official script. And as you, we want everyone to profit
+from such changes sooner then later. :)
+