getting versions of uboot, kernel, device tree, file system [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Is there some way to get version and checksum of uboot, kernel, device tree, file system.
(I'm familiar with kernel version)
Thank you :)
version checksum
asked Nov 29 at 6:05
user1977050
139315
closed as too broad by Ipor Sircer, Thomas, Archemar, sourcejedi, Stephen Kitt Nov 29 at 15:14
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
Is there some way to get version and checksum of uboot, kernel, device tree, file system.
(I'm familiar with kernel version)
Thank you :)
version checksum
asked Nov 29 at 6:05
user1977050
139315
closed as too broad by Ipor Sircer, Thomas, Archemar, sourcejedi, Stephen Kitt Nov 29 at 15:14
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
What have you try to the moment?
– Romeo Ninov
Nov 29 at 13:36
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Is there some way to get version and checksum of uboot, kernel, device tree, file system.
(I'm familiar with kernel version)
Thank you :)
version checksum
asked Nov 29 at 6:05
user1977050
139315
Is there some way to get version and checksum of uboot, kernel, device tree, file system.
(I'm familiar with kernel version)
Thank you :)
version checksum
version checksum
asked Nov 29 at 6:05
user1977050
139315
asked Nov 29 at 6:05
user1977050
139315
asked Nov 29 at 6:05
user1977050
139315
asked Nov 29 at 6:05
user1977050
139315
asked Nov 29 at 6:05
user1977050
139315
139315
closed as too broad by Ipor Sircer, Thomas, Archemar, sourcejedi, Stephen Kitt Nov 29 at 15:14
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by Ipor Sircer, Thomas, Archemar, sourcejedi, Stephen Kitt Nov 29 at 15:14
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
What have you try to the moment?
– Romeo Ninov
Nov 29 at 13:36
add a comment |
What have you try to the moment?
– Romeo Ninov
Nov 29 at 13:36
What have you try to the moment?
– Romeo Ninov
Nov 29 at 13:36
What have you try to the moment?
– Romeo Ninov
Nov 29 at 13:36
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
There are specific places to find each one of the version items.
kernel:
uname -rv
device tree:
cat /proc/device-tree/compatible
file system:
cat /proc/issue
u-boot is a trickier. In general you should hexdump the /dev/xxx which is the place the u-boot resides (according to target/method you store the uboot) and then convert it to string.
answered Nov 29 at 8:28
Itzik Chaimov
1
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
There are specific places to find each one of the version items.
kernel:
uname -rv
device tree:
cat /proc/device-tree/compatible
file system:
cat /proc/issue
u-boot is a trickier. In general you should hexdump the /dev/xxx which is the place the u-boot resides (according to target/method you store the uboot) and then convert it to string.
answered Nov 29 at 8:28
Itzik Chaimov
1
add a comment |
up vote
0
down vote
There are specific places to find each one of the version items.
kernel:
uname -rv
device tree:
cat /proc/device-tree/compatible
file system:
cat /proc/issue
u-boot is a trickier. In general you should hexdump the /dev/xxx which is the place the u-boot resides (according to target/method you store the uboot) and then convert it to string.
answered Nov 29 at 8:28
Itzik Chaimov
1
add a comment |
up vote
0
down vote
up vote
0
down vote
There are specific places to find each one of the version items.
kernel:
uname -rv
device tree:
cat /proc/device-tree/compatible
file system:
cat /proc/issue
u-boot is a trickier. In general you should hexdump the /dev/xxx which is the place the u-boot resides (according to target/method you store the uboot) and then convert it to string.
answered Nov 29 at 8:28
Itzik Chaimov
1
There are specific places to find each one of the version items.
kernel:
uname -rv
device tree:
cat /proc/device-tree/compatible
file system:
cat /proc/issue
u-boot is a trickier. In general you should hexdump the /dev/xxx which is the place the u-boot resides (according to target/method you store the uboot) and then convert it to string.
answered Nov 29 at 8:28
Itzik Chaimov
1
answered Nov 29 at 8:28
Itzik Chaimov
1
answered Nov 29 at 8:28
Itzik Chaimov
1
answered Nov 29 at 8:28
Itzik Chaimov
1
1
add a comment |
add a comment |
What have you try to the moment?
– Romeo Ninov
Nov 29 at 13:36