* [PATCH 1/2] Documentation/filesystems: add barebox prompt to the shell commands
@ 2016-02-29 14:39 yegorslists
2016-02-29 14:39 ` [PATCH 2/2] Documentation/filesystems: pstore: fix formatting yegorslists
0 siblings, 1 reply; 3+ messages in thread
From: yegorslists @ 2016-02-29 14:39 UTC (permalink / raw)
To: barebox
From: Yegor Yefremov <yegorslists@googlemail.com>
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
Documentation/filesystems/fat.rst | 9 ++++-----
Documentation/filesystems/nfs.rst | 4 ++--
Documentation/filesystems/ramfs.rst | 2 +-
Documentation/filesystems/smhfs.rst | 2 +-
Documentation/filesystems/tftp.rst | 2 +-
5 files changed, 9 insertions(+), 10 deletions(-)
diff --git a/Documentation/filesystems/fat.rst b/Documentation/filesystems/fat.rst
index 2138328..e39e34a 100644
--- a/Documentation/filesystems/fat.rst
+++ b/Documentation/filesystems/fat.rst
@@ -7,9 +7,8 @@ barebox supports FAT filesystems in both read and write modes with optional
support for long filenames. A FAT filesystem can be mounted using the
:ref:`command_mount` command::
- mkdir /mnt
- mount /dev/disk0.0 fat /mnt
- ls /mnt
+ barebox:/ mkdir /mnt
+ barebox:/ mount /dev/disk0.0 fat /mnt
+ barebox:/ ls /mnt
zImage barebox.bin
- umount /mnt
-
+ barebox:/ umount /mnt
diff --git a/Documentation/filesystems/nfs.rst b/Documentation/filesystems/nfs.rst
index 4469ac1..ab51241 100644
--- a/Documentation/filesystems/nfs.rst
+++ b/Documentation/filesystems/nfs.rst
@@ -9,7 +9,7 @@ barebox has readonly support for NFSv3 in UDP mode.
Example::
- mount -t nfs 192.168.23.4:/home/user/nfsroot /mnt/nfs
+ barebox:/ mount -t nfs 192.168.23.4:/home/user/nfsroot /mnt/nfs
The barebox NFS driver adds a ``linux.bootargs`` device parameter to the NFS device.
This parameter holds a Linux kernel commandline snippet containing a suitable root=
@@ -17,7 +17,7 @@ option for booting from exactly that NFS share.
Example::
- devinfo nfs0
+ barebox:/ devinfo nfs0
...
linux.bootargs: root=/dev/nfs nfsroot=192.168.23.4:/home/sha/nfsroot/generic-v7,v3,tcp
diff --git a/Documentation/filesystems/ramfs.rst b/Documentation/filesystems/ramfs.rst
index b7ece1a..d27f885 100644
--- a/Documentation/filesystems/ramfs.rst
+++ b/Documentation/filesystems/ramfs.rst
@@ -9,4 +9,4 @@ is ``ramfs``.
Example::
- mount none ramfs /somedir
+ barebox:/ mount none ramfs /somedir
diff --git a/Documentation/filesystems/smhfs.rst b/Documentation/filesystems/smhfs.rst
index 28de146..9e9993c 100644
--- a/Documentation/filesystems/smhfs.rst
+++ b/Documentation/filesystems/smhfs.rst
@@ -20,7 +20,7 @@ directory. Nevertheless, the files are there.
Example::
- mount -t smhfs /dev/null /mnt/smhfs
+ barebox:/ mount -t smhfs /dev/null /mnt/smhfs
Host Side Setup
diff --git a/Documentation/filesystems/tftp.rst b/Documentation/filesystems/tftp.rst
index b5bb1b3..eeb3fcb 100644
--- a/Documentation/filesystems/tftp.rst
+++ b/Documentation/filesystems/tftp.rst
@@ -14,7 +14,7 @@ show an empty directory. Nevertheless, the files are there.
Example::
- mount -t tftp 192.168.23.4 /mnt/tftp
+ barebox:/ mount -t tftp 192.168.23.4 /mnt/tftp
In addition to the TFTP filesystem implementation, barebox does also have a
:ref:`tftp command <command_tftp>`.
--
2.1.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH 2/2] Documentation/filesystems: pstore: fix formatting
2016-02-29 14:39 [PATCH 1/2] Documentation/filesystems: add barebox prompt to the shell commands yegorslists
@ 2016-02-29 14:39 ` yegorslists
2016-03-01 8:46 ` Sascha Hauer
0 siblings, 1 reply; 3+ messages in thread
From: yegorslists @ 2016-02-29 14:39 UTC (permalink / raw)
To: barebox
From: Yegor Yefremov <yegorslists@googlemail.com>
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
Documentation/filesystems/pstore.rst | 51 ++++++++++++++++++------------------
1 file changed, 26 insertions(+), 25 deletions(-)
diff --git a/Documentation/filesystems/pstore.rst b/Documentation/filesystems/pstore.rst
index 74acd87..a8079c2 100644
--- a/Documentation/filesystems/pstore.rst
+++ b/Documentation/filesystems/pstore.rst
@@ -12,6 +12,7 @@ messages are stored by the kernel in a specified RAM area which is never
overwritten by any user. This data can be accessed after a reboot through
/pstore in Barebox or the kernel. The pstore filesystem is automatically mounted
at boot::
+
none on / type ramfs
none on /dev type devfs
none on /pstore type pstore
@@ -40,35 +41,35 @@ and RAM backend support. The kernel receives the parameters describing the
layout over the kernel command line. These parameters are automatically
generated by Barebox. You can change these parameters in Barebox menuconfig. The
RAMOOPS parameters for the Kernel are stored in the variable
-global.linux.bootargs.ramoops::
+global.linux.bootargs.ramoops.
To see where the RAMOOPS area is located, you can execute iomem in Barebox. The
RAMOOPS area is listed as 'persistent ram'::
- 0x10000000 - 0x1fffffff (size 0x10000000) ram0
- 0x17e7c0c0 - 0x1fcf817f (size 0x07e7c0c0) malloc space
- 0x1fcf8180 - 0x1fcfffff (size 0x00007e80) board data
- 0x1fd00000 - 0x1fd6eeff (size 0x0006ef00) barebox
- 0x1fd6ef00 - 0x1fd88dff (size 0x00019f00) barebox data
- 0x1fd88e00 - 0x1fd8c3db (size 0x000035dc) bss
- 0x1fdf4000 - 0x1fe13fff (size 0x00020000) persistent ram
- 0x1fe14000 - 0x1fe33fff (size 0x00020000) persistent ram
- 0x1fe34000 - 0x1fe53fff (size 0x00020000) persistent ram
- 0x1fe54000 - 0x1fe73fff (size 0x00020000) persistent ram
- 0x1fe74000 - 0x1fe93fff (size 0x00020000) persistent ram
- 0x1fe94000 - 0x1feb3fff (size 0x00020000) persistent ram
- 0x1feb4000 - 0x1fed3fff (size 0x00020000) persistent ram
- 0x1fed4000 - 0x1fef3fff (size 0x00020000) persistent ram
- 0x1fef4000 - 0x1ff13fff (size 0x00020000) persistent ram
- 0x1ff14000 - 0x1ff33fff (size 0x00020000) persistent ram
- 0x1ff34000 - 0x1ff53fff (size 0x00020000) persistent ram
- 0x1ff54000 - 0x1ff73fff (size 0x00020000) persistent ram
- 0x1ff74000 - 0x1ff93fff (size 0x00020000) persistent ram
- 0x1ff94000 - 0x1ffb3fff (size 0x00020000) persistent ram
- 0x1ffb4000 - 0x1ffd3fff (size 0x00020000) persistent ram
- 0x1ffd4000 - 0x1fff3fff (size 0x00020000) persistent ram
- 0x1fff4000 - 0x1fff7fff (size 0x00004000) ttb
- 0x1fff8000 - 0x1fffffff (size 0x00008000) stack
+ 0x10000000 - 0x1fffffff (size 0x10000000) ram0
+ 0x17e7c0c0 - 0x1fcf817f (size 0x07e7c0c0) malloc space
+ 0x1fcf8180 - 0x1fcfffff (size 0x00007e80) board data
+ 0x1fd00000 - 0x1fd6eeff (size 0x0006ef00) barebox
+ 0x1fd6ef00 - 0x1fd88dff (size 0x00019f00) barebox data
+ 0x1fd88e00 - 0x1fd8c3db (size 0x000035dc) bss
+ 0x1fdf4000 - 0x1fe13fff (size 0x00020000) persistent ram
+ 0x1fe14000 - 0x1fe33fff (size 0x00020000) persistent ram
+ 0x1fe34000 - 0x1fe53fff (size 0x00020000) persistent ram
+ 0x1fe54000 - 0x1fe73fff (size 0x00020000) persistent ram
+ 0x1fe74000 - 0x1fe93fff (size 0x00020000) persistent ram
+ 0x1fe94000 - 0x1feb3fff (size 0x00020000) persistent ram
+ 0x1feb4000 - 0x1fed3fff (size 0x00020000) persistent ram
+ 0x1fed4000 - 0x1fef3fff (size 0x00020000) persistent ram
+ 0x1fef4000 - 0x1ff13fff (size 0x00020000) persistent ram
+ 0x1ff14000 - 0x1ff33fff (size 0x00020000) persistent ram
+ 0x1ff34000 - 0x1ff53fff (size 0x00020000) persistent ram
+ 0x1ff54000 - 0x1ff73fff (size 0x00020000) persistent ram
+ 0x1ff74000 - 0x1ff93fff (size 0x00020000) persistent ram
+ 0x1ff94000 - 0x1ffb3fff (size 0x00020000) persistent ram
+ 0x1ffb4000 - 0x1ffd3fff (size 0x00020000) persistent ram
+ 0x1ffd4000 - 0x1fff3fff (size 0x00020000) persistent ram
+ 0x1fff4000 - 0x1fff7fff (size 0x00004000) ttb
+ 0x1fff8000 - 0x1fffffff (size 0x00008000) stack
All pstore files that could be found are added to the /pstore directory. This is
a read-only filesystem. If you disable the Kconfig option FS_PSTORE_RAMOOPS_RO,
--
2.1.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 2/2] Documentation/filesystems: pstore: fix formatting
2016-02-29 14:39 ` [PATCH 2/2] Documentation/filesystems: pstore: fix formatting yegorslists
@ 2016-03-01 8:46 ` Sascha Hauer
0 siblings, 0 replies; 3+ messages in thread
From: Sascha Hauer @ 2016-03-01 8:46 UTC (permalink / raw)
To: yegorslists; +Cc: barebox
On Mon, Feb 29, 2016 at 03:39:52PM +0100, yegorslists@googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> Documentation/filesystems/pstore.rst | 51 ++++++++++++++++++------------------
> 1 file changed, 26 insertions(+), 25 deletions(-)
>
> diff --git a/Documentation/filesystems/pstore.rst b/Documentation/filesystems/pstore.rst
> index 74acd87..a8079c2 100644
> --- a/Documentation/filesystems/pstore.rst
> +++ b/Documentation/filesystems/pstore.rst
> @@ -12,6 +12,7 @@ messages are stored by the kernel in a specified RAM area which is never
> overwritten by any user. This data can be accessed after a reboot through
> /pstore in Barebox or the kernel. The pstore filesystem is automatically mounted
> at boot::
> +
> none on / type ramfs
> none on /dev type devfs
> none on /pstore type pstore
> @@ -40,35 +41,35 @@ and RAM backend support. The kernel receives the parameters describing the
> layout over the kernel command line. These parameters are automatically
> generated by Barebox. You can change these parameters in Barebox menuconfig. The
> RAMOOPS parameters for the Kernel are stored in the variable
> -global.linux.bootargs.ramoops::
> +global.linux.bootargs.ramoops.
>
> To see where the RAMOOPS area is located, you can execute iomem in Barebox. The
> RAMOOPS area is listed as 'persistent ram'::
>
> - 0x10000000 - 0x1fffffff (size 0x10000000) ram0
> - 0x17e7c0c0 - 0x1fcf817f (size 0x07e7c0c0) malloc space
> - 0x1fcf8180 - 0x1fcfffff (size 0x00007e80) board data
> - 0x1fd00000 - 0x1fd6eeff (size 0x0006ef00) barebox
> - 0x1fd6ef00 - 0x1fd88dff (size 0x00019f00) barebox data
> - 0x1fd88e00 - 0x1fd8c3db (size 0x000035dc) bss
> - 0x1fdf4000 - 0x1fe13fff (size 0x00020000) persistent ram
> - 0x1fe14000 - 0x1fe33fff (size 0x00020000) persistent ram
> - 0x1fe34000 - 0x1fe53fff (size 0x00020000) persistent ram
> - 0x1fe54000 - 0x1fe73fff (size 0x00020000) persistent ram
> - 0x1fe74000 - 0x1fe93fff (size 0x00020000) persistent ram
> - 0x1fe94000 - 0x1feb3fff (size 0x00020000) persistent ram
> - 0x1feb4000 - 0x1fed3fff (size 0x00020000) persistent ram
> - 0x1fed4000 - 0x1fef3fff (size 0x00020000) persistent ram
> - 0x1fef4000 - 0x1ff13fff (size 0x00020000) persistent ram
> - 0x1ff14000 - 0x1ff33fff (size 0x00020000) persistent ram
> - 0x1ff34000 - 0x1ff53fff (size 0x00020000) persistent ram
> - 0x1ff54000 - 0x1ff73fff (size 0x00020000) persistent ram
> - 0x1ff74000 - 0x1ff93fff (size 0x00020000) persistent ram
> - 0x1ff94000 - 0x1ffb3fff (size 0x00020000) persistent ram
> - 0x1ffb4000 - 0x1ffd3fff (size 0x00020000) persistent ram
> - 0x1ffd4000 - 0x1fff3fff (size 0x00020000) persistent ram
> - 0x1fff4000 - 0x1fff7fff (size 0x00004000) ttb
> - 0x1fff8000 - 0x1fffffff (size 0x00008000) stack
> + 0x10000000 - 0x1fffffff (size 0x10000000) ram0
> + 0x17e7c0c0 - 0x1fcf817f (size 0x07e7c0c0) malloc space
It was intentional the the first line has a different indention. It's
from the original 'iomem' output.
Sascha
--
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-03-01 8:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-29 14:39 [PATCH 1/2] Documentation/filesystems: add barebox prompt to the shell commands yegorslists
2016-02-29 14:39 ` [PATCH 2/2] Documentation/filesystems: pstore: fix formatting yegorslists
2016-03-01 8:46 ` Sascha Hauer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox