aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTanguy Pruvot <tanguy.pruvot@gmail.com>2013-05-04 16:55:58 +0200
committerTanguy Pruvot <tanguy.pruvot@gmail.com>2013-05-04 16:59:58 +0200
commitdb8811f958dee3a9a5287d30aac188dd2ae9e191 (patch)
tree6b678024ebf807fbb8346afd5abe3d01ca2f10e4
parent117b4fa5d9781e7cfd60dd20c5c4ec76d32172a5 (diff)
downloadexternal_heimdall-db8811f958dee3a9a5287d30aac188dd2ae9e191.zip
external_heimdall-db8811f958dee3a9a5287d30aac188dd2ae9e191.tar.gz
external_heimdall-db8811f958dee3a9a5287d30aac188dd2ae9e191.tar.bz2
fix readme mixed dos/unix
Change-Id: Iefcc96166398a9e12f9339fdc707f6d0214cea73
-rw-r--r--Linux/README64
-rw-r--r--OSX/README.txt4
-rw-r--r--heimdall-frontend/doc-pak/README64
-rw-r--r--heimdall/doc-pak/README64
4 files changed, 98 insertions, 98 deletions
diff --git a/Linux/README b/Linux/README
index a181796..a0ca91e 100644
--- a/Linux/README
+++ b/Linux/README
@@ -84,11 +84,11 @@ Performing a Custom Flash with Heimdall Frontend:
This is the advanced means of flashing firmware to your device.
If you're not an advanced user or a developer, in the event that a Heimdall
- Firmware Package doesn't exist for the particular firmware (or files) that
- you wish to flash, then I strongly recommend you get in touch with the
- developer of the firmware (or files) and politely ask them to create a
- Heimdall Firmware Package for you. In doing so, you avoid the risk of
- making mistakes due to inexperience.
+ Firmware Package doesn't exist for the particular firmware (or files) that
+ you wish to flash, then I strongly recommend you get in touch with the
+ developer of the firmware (or files) and politely ask them to create a
+ Heimdall Firmware Package for you. In doing so, you avoid the risk of
+ making mistakes due to inexperience.
If you're looking to customise an existing Heimdall Firmware Package then
@@ -118,14 +118,14 @@ Performing a Custom Flash with Heimdall Frontend:
5. Before you can chose which partitions you want to flash with particular
files you MUST first select a PIT file. To do this click the "Browse"
button in the "PIT" section. This will open a dialogue allowing you to
- navigate to and select a valid PIT (.pit) file.
+ navigate to and select a valid PIT (.pit) file.
- If you do not already have a valid PIT file stored on your computer you
- can download your device's PIT file from the "Utilities" tab.
-
- 6. If a valid PIT file has been selected then the "Add" button below the
- "Partitions (Files)" list-box will be enabled. Press this button to add
- a partition to your flash.
+ If you do not already have a valid PIT file stored on your computer you
+ can download your device's PIT file from the "Utilities" tab.
+
+ 6. If a valid PIT file has been selected then the "Add" button below the
+ "Partitions (Files)" list-box will be enabled. Press this button to add
+ a partition to your flash.
7. When you first add a partition you will see the "Partition Name" and
"Partition ID" be populated with information. Use the "Partition Name"
@@ -255,11 +255,11 @@ How to Create a Heimdall Firmware Package:
Firmware Name - This is the name of your particular firmware. An
example would be "Cyanogenmod".
- Firmware Version - This is the version identifier for your package. Any
- valid string will be accepted, although the inclusion of decimal
- point version number is preferred i.e. "7.1". If it makes sense
- then feel free to append a text string like "RC1" or "Beta 1" to
- the decimal point version.
+ Firmware Version - This is the version identifier for your package. Any
+ valid string will be accepted, although the inclusion of decimal
+ point version number is preferred i.e. "7.1". If it makes sense
+ then feel free to append a text string like "RC1" or "Beta 1" to
+ the decimal point version.
Platform Name - This is the name of platform (or operating system) that
your firmware is based on. In most cases this will simply be
@@ -296,8 +296,8 @@ How to Create a Heimdall Firmware Package:
team name. Click "Add" and the developer will be added to the list
on the right. If you make a mistake you can select a developer from
the list and click "Remove". You can list as many developers as you
- like, however visual constraints of the "Load Package" tab means
- only a few names will be visible. Where possible you may want to
+ like, however visual constraints of the "Load Package" tab means
+ only a few names will be visible. Where possible you may want to
opt for team names over listing individual team members.
@@ -360,8 +360,8 @@ for the format in their own software.
All Heimdall Firmware Packages must contain a file called firmware.xml. This
-file stores flash information and meta-data for the package as well as
-information about other files contained within the package.
+file stores flash information and meta-data for the package as well as
+information about other files contained within the package.
The format is fairly straight-forward so it won't be explained in great detail.
@@ -462,9 +462,9 @@ be included.
Appendix B - Installing Heimdall from Source:
- 1. First make sure you have installed build-tools, pkgconfig, zlib-dev and
- libusb-1.0-dev (v1.0.8 or newer).
-
+ 1. First make sure you have installed build-tools, pkgconfig, zlib-dev and
+ libusb-1.0-dev (v1.0.8 or newer).
+
NOTE: Package names may not be absolutely identical to those above.
2. Open a terminal and navigate to the directory you downloaded,
@@ -473,8 +473,8 @@ Appendix B - Installing Heimdall from Source:
3. Enter the following commands to compile libpit:
cd libpit
- ./configure
- make
+ ./configure
+ make
cd ..
If you have problems please consult http://www.libusb.org/
@@ -496,11 +496,11 @@ Appendix B - Installing Heimdall from Source:
sudo make install
cd ..
- NOTE: As an alternative to "sudo make install" you may chose to generate
- a package by typing the following:
-
- sudo checkinstall --pkgversion <version>
-
+ NOTE: As an alternative to "sudo make install" you may chose to generate
+ a package by typing the following:
+
+ sudo checkinstall --pkgversion <version>
+
Where <version> is the current Heimdall release e.g. 1.3.0
5. Done
@@ -522,7 +522,7 @@ Appendix C - Installing Heimdall Frontend from Source:
cd heimdall-frontend
qmake-qt4 heimdall-frontend.pro
make
- sudo make install
+ sudo make install
NOTE: As an alternative to "sudo make install" you may chose to generate
a package by typing the following:
diff --git a/OSX/README.txt b/OSX/README.txt
index 3f27a04..deec2a5 100644
--- a/OSX/README.txt
+++ b/OSX/README.txt
@@ -477,8 +477,8 @@ Appendix B - Installing Heimdall from Source:
3. Download, compile and install libusb-1.0:
- http://www.libusb.org/
-
+ http://www.libusb.org/
+
NOTE: Alternatively you may install Macport's libusb-devel package.
4. Enter the following commands to compile libpit.
diff --git a/heimdall-frontend/doc-pak/README b/heimdall-frontend/doc-pak/README
index a181796..a0ca91e 100644
--- a/heimdall-frontend/doc-pak/README
+++ b/heimdall-frontend/doc-pak/README
@@ -84,11 +84,11 @@ Performing a Custom Flash with Heimdall Frontend:
This is the advanced means of flashing firmware to your device.
If you're not an advanced user or a developer, in the event that a Heimdall
- Firmware Package doesn't exist for the particular firmware (or files) that
- you wish to flash, then I strongly recommend you get in touch with the
- developer of the firmware (or files) and politely ask them to create a
- Heimdall Firmware Package for you. In doing so, you avoid the risk of
- making mistakes due to inexperience.
+ Firmware Package doesn't exist for the particular firmware (or files) that
+ you wish to flash, then I strongly recommend you get in touch with the
+ developer of the firmware (or files) and politely ask them to create a
+ Heimdall Firmware Package for you. In doing so, you avoid the risk of
+ making mistakes due to inexperience.
If you're looking to customise an existing Heimdall Firmware Package then
@@ -118,14 +118,14 @@ Performing a Custom Flash with Heimdall Frontend:
5. Before you can chose which partitions you want to flash with particular
files you MUST first select a PIT file. To do this click the "Browse"
button in the "PIT" section. This will open a dialogue allowing you to
- navigate to and select a valid PIT (.pit) file.
+ navigate to and select a valid PIT (.pit) file.
- If you do not already have a valid PIT file stored on your computer you
- can download your device's PIT file from the "Utilities" tab.
-
- 6. If a valid PIT file has been selected then the "Add" button below the
- "Partitions (Files)" list-box will be enabled. Press this button to add
- a partition to your flash.
+ If you do not already have a valid PIT file stored on your computer you
+ can download your device's PIT file from the "Utilities" tab.
+
+ 6. If a valid PIT file has been selected then the "Add" button below the
+ "Partitions (Files)" list-box will be enabled. Press this button to add
+ a partition to your flash.
7. When you first add a partition you will see the "Partition Name" and
"Partition ID" be populated with information. Use the "Partition Name"
@@ -255,11 +255,11 @@ How to Create a Heimdall Firmware Package:
Firmware Name - This is the name of your particular firmware. An
example would be "Cyanogenmod".
- Firmware Version - This is the version identifier for your package. Any
- valid string will be accepted, although the inclusion of decimal
- point version number is preferred i.e. "7.1". If it makes sense
- then feel free to append a text string like "RC1" or "Beta 1" to
- the decimal point version.
+ Firmware Version - This is the version identifier for your package. Any
+ valid string will be accepted, although the inclusion of decimal
+ point version number is preferred i.e. "7.1". If it makes sense
+ then feel free to append a text string like "RC1" or "Beta 1" to
+ the decimal point version.
Platform Name - This is the name of platform (or operating system) that
your firmware is based on. In most cases this will simply be
@@ -296,8 +296,8 @@ How to Create a Heimdall Firmware Package:
team name. Click "Add" and the developer will be added to the list
on the right. If you make a mistake you can select a developer from
the list and click "Remove". You can list as many developers as you
- like, however visual constraints of the "Load Package" tab means
- only a few names will be visible. Where possible you may want to
+ like, however visual constraints of the "Load Package" tab means
+ only a few names will be visible. Where possible you may want to
opt for team names over listing individual team members.
@@ -360,8 +360,8 @@ for the format in their own software.
All Heimdall Firmware Packages must contain a file called firmware.xml. This
-file stores flash information and meta-data for the package as well as
-information about other files contained within the package.
+file stores flash information and meta-data for the package as well as
+information about other files contained within the package.
The format is fairly straight-forward so it won't be explained in great detail.
@@ -462,9 +462,9 @@ be included.
Appendix B - Installing Heimdall from Source:
- 1. First make sure you have installed build-tools, pkgconfig, zlib-dev and
- libusb-1.0-dev (v1.0.8 or newer).
-
+ 1. First make sure you have installed build-tools, pkgconfig, zlib-dev and
+ libusb-1.0-dev (v1.0.8 or newer).
+
NOTE: Package names may not be absolutely identical to those above.
2. Open a terminal and navigate to the directory you downloaded,
@@ -473,8 +473,8 @@ Appendix B - Installing Heimdall from Source:
3. Enter the following commands to compile libpit:
cd libpit
- ./configure
- make
+ ./configure
+ make
cd ..
If you have problems please consult http://www.libusb.org/
@@ -496,11 +496,11 @@ Appendix B - Installing Heimdall from Source:
sudo make install
cd ..
- NOTE: As an alternative to "sudo make install" you may chose to generate
- a package by typing the following:
-
- sudo checkinstall --pkgversion <version>
-
+ NOTE: As an alternative to "sudo make install" you may chose to generate
+ a package by typing the following:
+
+ sudo checkinstall --pkgversion <version>
+
Where <version> is the current Heimdall release e.g. 1.3.0
5. Done
@@ -522,7 +522,7 @@ Appendix C - Installing Heimdall Frontend from Source:
cd heimdall-frontend
qmake-qt4 heimdall-frontend.pro
make
- sudo make install
+ sudo make install
NOTE: As an alternative to "sudo make install" you may chose to generate
a package by typing the following:
diff --git a/heimdall/doc-pak/README b/heimdall/doc-pak/README
index a181796..a0ca91e 100644
--- a/heimdall/doc-pak/README
+++ b/heimdall/doc-pak/README
@@ -84,11 +84,11 @@ Performing a Custom Flash with Heimdall Frontend:
This is the advanced means of flashing firmware to your device.
If you're not an advanced user or a developer, in the event that a Heimdall
- Firmware Package doesn't exist for the particular firmware (or files) that
- you wish to flash, then I strongly recommend you get in touch with the
- developer of the firmware (or files) and politely ask them to create a
- Heimdall Firmware Package for you. In doing so, you avoid the risk of
- making mistakes due to inexperience.
+ Firmware Package doesn't exist for the particular firmware (or files) that
+ you wish to flash, then I strongly recommend you get in touch with the
+ developer of the firmware (or files) and politely ask them to create a
+ Heimdall Firmware Package for you. In doing so, you avoid the risk of
+ making mistakes due to inexperience.
If you're looking to customise an existing Heimdall Firmware Package then
@@ -118,14 +118,14 @@ Performing a Custom Flash with Heimdall Frontend:
5. Before you can chose which partitions you want to flash with particular
files you MUST first select a PIT file. To do this click the "Browse"
button in the "PIT" section. This will open a dialogue allowing you to
- navigate to and select a valid PIT (.pit) file.
+ navigate to and select a valid PIT (.pit) file.
- If you do not already have a valid PIT file stored on your computer you
- can download your device's PIT file from the "Utilities" tab.
-
- 6. If a valid PIT file has been selected then the "Add" button below the
- "Partitions (Files)" list-box will be enabled. Press this button to add
- a partition to your flash.
+ If you do not already have a valid PIT file stored on your computer you
+ can download your device's PIT file from the "Utilities" tab.
+
+ 6. If a valid PIT file has been selected then the "Add" button below the
+ "Partitions (Files)" list-box will be enabled. Press this button to add
+ a partition to your flash.
7. When you first add a partition you will see the "Partition Name" and
"Partition ID" be populated with information. Use the "Partition Name"
@@ -255,11 +255,11 @@ How to Create a Heimdall Firmware Package:
Firmware Name - This is the name of your particular firmware. An
example would be "Cyanogenmod".
- Firmware Version - This is the version identifier for your package. Any
- valid string will be accepted, although the inclusion of decimal
- point version number is preferred i.e. "7.1". If it makes sense
- then feel free to append a text string like "RC1" or "Beta 1" to
- the decimal point version.
+ Firmware Version - This is the version identifier for your package. Any
+ valid string will be accepted, although the inclusion of decimal
+ point version number is preferred i.e. "7.1". If it makes sense
+ then feel free to append a text string like "RC1" or "Beta 1" to
+ the decimal point version.
Platform Name - This is the name of platform (or operating system) that
your firmware is based on. In most cases this will simply be
@@ -296,8 +296,8 @@ How to Create a Heimdall Firmware Package:
team name. Click "Add" and the developer will be added to the list
on the right. If you make a mistake you can select a developer from
the list and click "Remove". You can list as many developers as you
- like, however visual constraints of the "Load Package" tab means
- only a few names will be visible. Where possible you may want to
+ like, however visual constraints of the "Load Package" tab means
+ only a few names will be visible. Where possible you may want to
opt for team names over listing individual team members.
@@ -360,8 +360,8 @@ for the format in their own software.
All Heimdall Firmware Packages must contain a file called firmware.xml. This
-file stores flash information and meta-data for the package as well as
-information about other files contained within the package.
+file stores flash information and meta-data for the package as well as
+information about other files contained within the package.
The format is fairly straight-forward so it won't be explained in great detail.
@@ -462,9 +462,9 @@ be included.
Appendix B - Installing Heimdall from Source:
- 1. First make sure you have installed build-tools, pkgconfig, zlib-dev and
- libusb-1.0-dev (v1.0.8 or newer).
-
+ 1. First make sure you have installed build-tools, pkgconfig, zlib-dev and
+ libusb-1.0-dev (v1.0.8 or newer).
+
NOTE: Package names may not be absolutely identical to those above.
2. Open a terminal and navigate to the directory you downloaded,
@@ -473,8 +473,8 @@ Appendix B - Installing Heimdall from Source:
3. Enter the following commands to compile libpit:
cd libpit
- ./configure
- make
+ ./configure
+ make
cd ..
If you have problems please consult http://www.libusb.org/
@@ -496,11 +496,11 @@ Appendix B - Installing Heimdall from Source:
sudo make install
cd ..
- NOTE: As an alternative to "sudo make install" you may chose to generate
- a package by typing the following:
-
- sudo checkinstall --pkgversion <version>
-
+ NOTE: As an alternative to "sudo make install" you may chose to generate
+ a package by typing the following:
+
+ sudo checkinstall --pkgversion <version>
+
Where <version> is the current Heimdall release e.g. 1.3.0
5. Done
@@ -522,7 +522,7 @@ Appendix C - Installing Heimdall Frontend from Source:
cd heimdall-frontend
qmake-qt4 heimdall-frontend.pro
make
- sudo make install
+ sudo make install
NOTE: As an alternative to "sudo make install" you may chose to generate
a package by typing the following: