Here are some details on the project 3 testing method. 1. Initialize the frame buffer. As you know, we should pass a valid frame buffer pointer to fbInit() function. You can prepare some memory space for framebuffer in initialize.c or some other source files executed during the booting process. Or simply you can do that right before the fbInit() function call. Take your pick. 2. Display Use 40 for width and 60 for height of the frame buffer. That means the size of frame buffer is 40*60. Main functionalities are line change and scroll when you meet the end of a line or the end of the frame buffer but you still have some more characters to write. Display(dump) the frame buffer line by line. For examples we can write 5 characters(including white space) in a line and we can write only 5 lines to the frame buffer. For example, the string is "This is the project 3 testing function" and the result would be This. is.th e.pro ject. 3.tes ting. funct ion.. '.' means background(white space). You are supposed to display like This. ..... ..... ..... ..... // after one line writing. This. is.th ..... ..... ..... This. is.th e.pro ..... ..... This. is.th e.pro ject. ..... This. is.th e.pro ject. 3.tes is.th e.pro ject. 3.tes ting. // from here one line scrolled up. e.pro ject. 3.tes ting. funct ject. 3.tes ting. funct ion.. As you can see from the sample, only 5 lines can be written and one line should be scrolled up from the sixth line printing. All characters should be displayed. Dump the frame buffer whenever you fill up a line. I believe that sample explains well enough what you should do for the testing. The test string should be passed through input parameter(one of args) of your test command and you should print out that string to the buffer. I'll input the string in grading time. Your testing command should be something like this fb_test This is testing method for project 3 All characters after the command should be printed out and displayed like the way I showed above.