changes required in u-boot for lz4 compression? [closed] - u-boot

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am using 3.12 Kernel and u-boot. I have selected lz4 compression in "make menuconfig" for kernel.
any changes required in u-bbot side to support lz4 compression?

I have done following steps.
1. Built u-boot image.
2. built device tree.
3. Selected lz4 compression in "make menuconfig" for kernel and built uImage.
4. Flashed u-boot image , device tree binary and uImage. after power up board is booting fine.
I have checked the kernel build logs, I could see "piggy.lz4.o" was created.
LZ4 arch/arm/boot/compressed/piggy.lz4
AS arch/arm/boot/compressed/piggy.lz4.o
my doubht here is whether lz4 compression is used while creating uImage and lz4 un-compression is used during uncompressing the kernel.

Related

Kali Linux Filesystem Hierarchy Standard [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
As per the Filesystem Hierarchy Standard for Linux , there exits a Requirement i.e
There must be no subdirectories in /bin
But in my Kali Linux [Linux kali 5.10.0-kali7-amd64] there exist a sub-directory in /bin folder i.e X11
So should we conclude that Kali Linux Doesn't follow FHS ?
Reference - https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf [Page 5]
This isn't a folder, this is a link. A link is a file linking to another file. Here is a link to a webpage explaining what are links in more detail.

Configuration Linux Kernel [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I need to compile kernel linux 3.4.4. I use "make menuconfig" to have a user-friendly interface to choose configuration.
I haven't understood an aspect of the kernel configuration: what is the difference between i choose to include an option during the configuration and i choose to include, as a module, an option during the configuration?
Thanks
When compiled as a module, the code of that feature/component is built as a separate file, as know as kernel module, separating from the kernel's main image. To use the feature, you have to load it into the kernel with commands like modprobe or insmod. Of course you can later unload this module, to remove the feature/component. The kernel modules are normally placed at /lib/modules/{uname -r} on your system.
While compiled as 'y' means the code will be compiled into the main kernel image, which will be always available when the kernel is loaded and running.

How does the kernel know which drivers belong to which peripherals? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
When the Kernel needs to send output to a certain peripheral, how does it know which driver to use?
The usual way is for each driver when first loaded, typically at boot time, to poll the buses it supports and look for matches between what it is designed to support and the returned signatures (vendor and device IDs), and their classes.
This is at least the way it works for the so-called plug and play peripherals.

AT91SAM7X-EK Evaluation Board [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I just recentely started working with a new board: a AT91SAM7X-EK. I would like to get more information about the board's processor (AT91SAM7X256) and the board's flash. So I looked at a pretty detailed data sheet and a summary of the data sheet, but have been unsucessfull (so far) of finding the information I want. I would appreciate if anyone could help me on the following aspects of the board:
How do I connect to the board? Is it through ssh? If so, how is it possible to recuperate the board's IP address. I have an ethernet cable for the connection.
How do I load an application onto the board's flash? For example, I would like to cross compile (using a toolchain I've already installed - arm-none-eabi) a simple hello world program in C to load onto my board. How would I go about doing so?
I would appreciate any help on this issue.
The board is supplied "bare-metal" - no code, no OS. You will not be able to run Linux on an AT91SAM7X-EK - it has insufficient memory resources and rins at 30MHz tops (and has no MMU).
You need a hardware JTAG or DBGU interface device and a tool-chain that will work with it.
You should probably also be looking at the datasheet for the board itself. From the Getting Started section of that:
The AT91SAM7X-EK evaluation board is delivered with a DVD-ROM containing all necessary
information and step-by-step procedures for working with the most common
development tool chains. Please refer to this DVD-ROM, or to the AT91 web site,
http://www.atmel.com/products/AT91/, for the most up-to-date information on getting
started with the evaluation kit.
So start there.

Trimming down freebsd [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I am trying to trim down FreeBSD to understand/learn how things work. I have a few questions if someone can help me with that:
1) when we say kernel, can I separate code wise from the rest of the FreeBSD code? What I mean is, I want to know what all files/dirs come under kernel.
2) I know a book called Linux from scratch. Is there any related book for FreeBSD?
Any pointers are most welcome.
Thank you.
FreeBSD is one cohesive system. Whereas Linux is a kernel plus a bunch of packages, all of FreeBSD core is built together (everything but the ports tree). The FreeBSD Handbook is the best resource to start from for learning FreeBSD. There is also a Developer's handbook that can be found on the FreeBSD website. As for what the kernel is in terms of source files, anything under /usr/src/sys is kernel source code. If you want to know about the workings of the kernel, the book "The Design and Implementation of the FreeBSD Operating System" is the definitive guide to the details of the kernel.

Resources