[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]

    Search the Q&A Archives

...test device drivers,kernels,embedded applications and...

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

Question by pinky
Submitted on 4/1/2004
Related FAQ: comp.software.testing Frequently Asked Questions (FAQ)
Rating: Rate this question: Vote
How to test device drivers,kernels,embedded applications and mobile services ? What are the  requistes for it?


Answer by SENTHIL
Submitted on 6/1/2004
Rating:  Rate this answer: Vote
Give me the detailed

 

Answer by venkatr
Submitted on 11/24/2004
Rating: Not yet rated Rate this answer: Vote
How to test device drivers,kernels,embedded applications and mobile services ? What are the  requistes for it?

 

Answer by Pinak
Submitted on 8/22/2005
Rating: Not yet rated Rate this answer: Vote
Testing a new device driver can cause irreparable harm to the kernel. The following tips can help avoid major problems:

1.Use a serial connection to control your test machine from a separate host system.

2.Use an alternate kernel.

3.Booting from a copy of the kernel and the associated binaries rather than from the default kernel avoids inadvertently rendering the system inoperable.

5.Use an additional kernel module to experiment with different kernel variable settings.

This approach isolates experiments with the kernel variable settings. Make contingency plans for potential data loss on a test system.

If your test system is set up as a client of a server, then you can boot from the network if problems occur. You could also create a special partition to hold a copy of a bootable root file system.
Capture system crash dumps if your test system panics.

Use fsck(1M) to repair the damaged root file system temporarily if your system crashes during the attach(9E) process so that any crash dumps can be salvaged.

Install drivers in the /tmp directory until you are finished modifying and testing the _info(), _init(), and attach() routines.

Keep a driver in the /tmp directory until the driver has been well tested. If a panic occurs, the driver will be removed from /tmp directory and the system will reboot successfully.

 

Your answer will be published for anyone to see and rate.  Your answer will not be displayed immediately.  If you'd like to get expert points and benefit from positive ratings, please create a new account or login into an existing account below.


Your name or nickname:
If you'd like to create a new account or access your existing account, put in your password here:
Your answer:

FAQS.ORG reserves the right to edit your answer as to improve its clarity.  By submitting your answer you authorize FAQS.ORG to publish your answer on the WWW without any restrictions. You agree to hold harmless and indemnify FAQS.ORG against any claims, costs, or damages resulting from publishing your answer.

 

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

 

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]
© 2008 FAQS.ORG. All rights reserved.