
Procedure for Submission of
Final Invention Statement and Certification (For Grant or Award)
Form HHS 568
A Final Invention Statement and Certification (Form HHS 568) shall be executed and submitted within 90 days following the expiration or termination of a grant or award. The Statement shall include all inventions which were conceived or first actually reduced to practice during the course of work under the grant or award, from the original effective date of support through the date of completion or termination. The Statement shall include any inventions reported previously for the grant or award as part of a non-competing application. This reporting requirement is applicable to grants and awards by Department of Health and Human Services in support of research.
The Final Invention Statement and Certification does not in any way relieve the person responsible for the grant or award, or the institution, of the obligation to assure that all inventions are promptly and fully reported directly to the National Institutes of Health, as required by terms of the grant or award. Information regarding the reporting of inventions, including the reporting form to be followed, may be obtained from the Office of Policy for Extramural Research Administration, Division of Extramural Inventions and Technology Resources, 6701 Rockledge Drive MSC 7750, Bethesda, Maryland 20892-7750, Telephone: (301) 435-1986.
The original of the completed Final Invention Statement and Certification is to be returned to the awarding component that funded the grant or award. The entire grant or award number must appear in the designated box on the form. The period covered by the Final Invention Statement is the project period of the grant or award at a particular grantee institution. If no inventions were involved, insert the word "None" in the first block under item Title of Invention. Each Statement requires the signature of an institution official authorized to sign on behalf of the institution.
The PHS estimates that it will take from 5 to 10 minutes to complete this form. This includes time for reviewing the instructions, gathering needed information, and completing and reviewing the form. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. If you have comments regarding this burden estimate or any other aspects of this collection of information, including suggestions for reducing this burden, send comments to: NIH, Project Clearance Office, 6701 Rockledge Drive MSC 7730, Bethesda, MD
2 of 2
outb(PIC1, ICW1);
outb(PIC2, ICW1);
/* send ICW2 */
outb(PIC1 + 1, pic1); /* remap */
outb(PIC2 + 1, pic2); /* pics */
/* send ICW3 */
outb(PIC1 + 1, 4); /* IRQ2 -> connection to slave */
outb(PIC2 + 1, 2);
/* send ICW4 */
outb(PIC1 + 1, ICW4);
outb(PIC2 + 1, ICW4);
/* disable all IRQs */
outb(PIC1 + 1, 0xFF);
}
So, this call will remap the PICs so that IRQ0 starts at 0x20 and IRQ8 starts at 0x28:
init_pics(0x20, 0x28);
Summary
That's it - I hope you understood the basic things, and take a look at the link I just gave you above. You will
need some knowledge of programming the PICs as a OS developer, so do not think it's not important.
best regards,
The PIC is a controller in the PC hardware that handles hardware interrupts (IRQ0, IRQ1, etc.). When there
wasn't a PIC, we would have to poll the hardware devices regularly, this would be time expensive. So instead
of that, when a hardware interrupt occurs, the PIC gets the signal and sends it to the CPU. The CPU stops
execution and processes the interrupt handler. We actually we have two PICs. The first one is for IRQ0-IRQ7,
and the second for IRQ8-IRQ15. We must have a connection between PIC1 and PIC2.
The CPU only knows interrupts - it makes no difference between hardware or software interrupts. So it's the
job of the programmer to map the hardware interrupts into interrupts that the CPU understands. In Real
Mode, the hardware interrupts are mapped to interrupt 8-15 (first PIC) and 70-77 (second PIC). But that's a
problem when we get into Protected Mode because interrupt 8-15 are reserved for exceptions. That would
mean that when we would get an exception, the CPU would call a handler for the keyboard, for example. So
we have to remap the PICs to use other interrupts...