If you want to use ram disk, compile with the following command: make zImage.initrd otherwise use the following command: make before compiling the 2.4 kernel before using the make dep command to ensure that all dependencies when compiling the kernel, such as header files, exist. However, for 2.6, it is no longer necessary. Just make a make command to make make dep and make zImage. If you have compiled it before and want to recompile it, it is best to use make clean, which removes all object files and some other legacy files. Of course you can also use make mrproper, which is cleaner than make clean, but be careful with your .config file, it will be deleted together, so first back up, or use make clean. Now we are compiling for the first time, so we don't have to think about it. For insurance, we use the second set of instructions to compile. The time is quite long. If all goes well, the compiled kernel will be placed in the arch/ppc/boot/images/ directory, which may be called zImage.elf or zImage.initrd.elf. The current compilation method is compiled with zImage. Elf. In theory, after the completion, you can copy the executable file to the EDK project directory and enter the step of creating an ACE file. However, in the above explanation, we did not use the kernel module, and in further applications, it is likely that some kernel options are compiled in module form. At this time, the next task is to build and install the module. The command makes modulesmake modules_install to compile. After successful, the system will generate a subdirectory named in the /lib/modules directory named after the version number of the compiled kernel, which stores all the loadable modules of the new kernel. In the future, you can use the insmod command to load. The current Linux 2.6x kernel automatically resolves dependencies, so don't worry about depmod for now. CF configuration CF card partition can not be partitioned, but the reason we partition here is to simulate normal Linux to the maximum extent. Think about how the average person installs Linux system when partitioning? /root partition, swap partition and /boot partition. Ok, we are here to give our CF card three zones. For the time being, let me take the example of my 8G CF card here. Insert the CF card into the system and use the command mount | column -t to see what the dev name of the mount directory corresponding to the CF card is. The information on my computer is as shown: Screenshot-coloum@windstorm: ~.png It can be seen that the CF card is /dev/sdc in my place. Then we use fdisk to partition it: fdisk /dev/sdc specific partitioning process I will not talk about, if you feel that you are not used to the fdisk command line operation form, you can also use gparted this graphical partitioning tool, in short, finally divided into The effect is: 1. ParTITIon 1 - Type = FAT16 (6) - Size = 32MB (just need to be able to put your system.ace file) 2. ParTITIon 2 - Type = Linux Swap (82) - Size = 256MB (this actually looks at the situation, regardless of swap) 3. Partition 3 - Type = Linux (83) - Size = ??? (How much is left in CF, used to store the root file system) can be seen The above three areas correspond to the commonly mentioned /boot, /swap and / three partitions. Creating a CF Card File System Xilinx's SystemACE controller is special. It is not a random CF card that can be used. You must create a specific file system for the CF card. The task of mkdosfs is to be able to accomplish this task. Use the following command to operate the CF card: mkdosfs -s 8 -F 16 -R 1 F: The number followed by -s indicates the number of sectors per cluster, which is generally an integer power of 2. The following is the number of sectors per cluster corresponding to the usual capacity of the FAT16 file format. 16–128MB 4128–256MB 8256–512MB 16512–1024MB 321024–2048MB 64 However, I found that the number behind this -s can actually be larger. For example, I use 64, except that when executing the command, a warningWARNING will appear: Not enough clusters for a 16 bit FAT! The filesystem will bemisinterpreted as having a 12 bit FAT without mount option "fat=16". Others have no problem. -F indicates the size of FAT, here is FAT16, the value of -R is not changed here, the number of reserved sectors, old problems, and interested can go online to search. The last F: is the CF card label under Windows, adjust it according to your own system. If it is a Linux environment, replace this volume table with the form /dev/fdx. The specific device name is queried by itself. Download the kernel file OK, here, I assume that you have compiled successfully, and generated the zImage file you need, well, how do you use this file now? There are three ways: 1 Stream the file and hardware bit into an ace file, put it on the flash and load it yourself. 2 Load the elf file on the flash into the internal ram through the bootloader written by yourself. 3 Download the elf file through the xmd dow command. I have not studied the two methods, hehe, so I will not introduce it first. If any friend is familiar with the bootloader, please advise me~~ Well, firstly introduce the ace method used by many people in detail. Create an ACE We can use the XMD tool to create an ACE file. The command is as follows: xmd -tcl genace.tcl -opt genace.optgenace.tcl is in the data/xmd directory under the xps installation directory, and genace.opt needs itself. Created as follows: -jprog-board user-target ppc_hw-hw implementation/download.bit-elf zImage.elf-configdevice devicenr 1 idcode 0×1127e093 irlength 14 partname xc2vp30-debugdevice devicenr 1 cpunr 1-ace system.ace-hw The two lines of -elf need to be modified according to your own situation. The only thing to note is that if your development environment is a Linux system, the -hw implementation/download.bit should be changed to -hw ./implementation/ After download.bit is copied to the CF card in the system.ace file, modify the jumper on the board to make it boot from JTAG, and you can always load the program from the CF card. For non-XUP, the official board, such as the ML-403 development board, the steps are much simpler, genace.opt content is as follows: -jprog-board ml403-hw implementation/download.bit-elf TestApp_memory/executable.elf-ace System.ace You only need to tell the EDK board that it is ml403. Many parameters are not configured by yourself. Which specific development board is directly supported by xmd, you can refer to the genace.tcl file. Some friends will find that following the above steps, the following error message may appear: Error: Executable TestApp_Memory/executable.elf does not contain start address.. I checked some information after encountering this error, and press working harddfen The modification method described in the data has no effect. Finally, the ACE file is successfully generated in the edk environment where the friend installed sp. Therefore, I suspect that it may be a bug in the 9.1 version of edk without sp. If you and I have a headache in the download of sp, still use the environment without sp... Congratulations, or find a way to download sp, or find the machine with sp installed to generate it. In fact, based on windows sp is relatively easy to find, mainly based on Linux sp is too difficult ... silent ing, if any Linuxer knows that there are other ways to correct this error, please let me know, thank you. I am lazy, but also more anxious, do not like to look at the bit + elf such a large file downloaded to the board through the 9600 speed serial port ... so directly use the simplest third method, open xmd, connect ppc hw, dow zImage.elf, con, then it's OK. The information displayed by the terminal is as follows: loaded at: 00400000 0066D19Cboard data at: 0066B120 0066B19Crelocated to: 00404060 004040DCzimage at: 00404ED5 0066A3DDavail ram: 0066E000 08000000Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3 rwUncompressing Linux... done.Now booting the kernel........ (The following information is omitted) This means that the basic kernel is successfully established, we can create the root file system. Oh, I think the hardest step has been done by you, congratulations. If you encounter an error... Many friends will encounter the following error inflate returned FFFFFFFB, error is caused by the size of the uncompressed image. This means that your kernel has been decompressed and the size exceeds your storage space. Usually this happens. Position your storage on bram. How to solve it? Very simple, modify ld, the program is not on the ddr ~ ~ Other friends will encounter the following error: Linux / PPC load: console = ttyS0, 9600Uncompressing Linux...done.Now booting the kernelloaded at: 00400000 005331A0board data at: 40000000 4000007Crelocated to: 00404084 00404100zimage at: 00404EB9 00530A50avail ram: 00534000 00000000Linux/PPC load: console=ttyS0,9600Uncompressing Linux...oops... out of memorypause Check arch/ppc/boot/simple/embed_config.c at this time Whether the vertex support code has been compiled (search ML403) If not configured, the board information will not be built correctly. Reprinted: Baidu space of fcni_cn
Signal
Response time refers to the response speed of the Liquid Crystal Display to the input signal, that is, the response time of the liquid crystal from dark to bright or from bright to dark (the time for the brightness from 10%-->90% or 90%-->10%) , Usually in milliseconds (ms). To make this clear, we have to start with the human eye's perception of dynamic images. There is a phenomenon of "visual residue" in the human eye, and the high-speed motion picture will form a short-term impression in the human brain. Animations, movies, etc. to the latest games have applied the principle of visual residue, allowing a series of gradual images to be displayed in rapid succession in front of people's eyes to form dynamic images. The acceptable display speed of the picture is generally 24 frames per second, which is the origin of the movie playback speed of 24 frames per second. If the display speed is lower than this standard, people will obviously feel the picture pause and discomfort. Calculated according to this index, the display time of each picture needs to be less than 40ms. In this way, for the liquid crystal display, the response time of 40ms becomes a hurdle, and the display above 40ms will have obvious picture flicker, which makes people feel dizzy. If you want the image screen to reach the level of non-flicker, it is best to achieve a speed of 60 frames per second.
I used a very simple formula to calculate the number of frames per second under the corresponding response time as follows:
Response time 30ms=1/0.030=approximately 33 frames per second
Response time 25ms=1/0.025=approximately 40 frames per second
Response time 16ms=1/0.016=approximately 63 frames per second
Response time 12ms=1/0.012=approximately 83 frames of pictures displayed per second
Response time 8ms=1/0.008=approximately 125 frames per second
Response time 4ms=1/0.004=approximately 250 frames per second
Response time 3ms=1/0.003=approximately display 333 frames per second
Response time 2ms=1/0.002=approximately 500 frames per second
Response time 1ms=1/0.001=approximately 1000 frames per second
Tip: Through the above content, we understand the relationship between response time and the number of frames. From this, the response time is as short as possible. At that time, when the LCD market first started, the lowest acceptable range of response time was 35ms, mainly products represented by EIZO. Later, BenQ's FP series came out to 25ms. From 33 to 40 frames, it was basically undetectable, and it was really quality. The change is 16ms, displaying 63 frames per second to meet the requirements of movies and general games, so 16ms is not obsolete. With the improvement of panel technology, BenQ and ViewSonic started a speed battle. ViewSonic started from 8ms to 4ms. Released to 1ms, it can be said that 1ms is the final controversy of LCD speed. For game enthusiasts, 1ms faster means that CS's marksmanship will be more accurate, at least psychologically, such customers should recommend the VX series of monitors. But everyone should pay attention to the grayscale response when selling. The text difference in full-color response may sometimes mean the same thing as gray-scale 8ms and full-color 5ms. It is the same as when we sold CRTs before, we said that the dot pitch is .28, LG just I have to say that he is .21, but the horizontal dot pitch is ignored. In fact, the two are talking about the same thing. LG has come up with a sharpness of 1600:1. This is also a conceptual hype. Everyone uses the basic screen. There are only a few companies on the list, and how can only the LG family achieve 1600:1, and everyone stays at the level of 450:1? When it comes to consumers, the meaning of sharpness and contrast is obvious, just like AMD's PR value, which has no real meaning.
Active Matrix Lcd,Active Matrix Tft Color Lcd,Tft Lcd Color Monitor,Tft Lcd Monitor
ESEN Optoelectronics Technology Co., Ltd, , https://www.esenlcd.com