It would be of great help if you could give me some suggestions. I also need some info on how I can test stuff like flowcontrol, baudrate etc. after setting them in the kernel i.e., I need to verify if the actual flowcontrol is taking place between the computer and the serial port device.Please help.
Now, some of the test cases that I have thought about are :
|
1. |
Open serial port |
|
|
2. |
Write Data to the serial port |
|
|
3. |
Read Data from the serial port |
|
|
4. |
Close serial port |
|
|
Configuration settings |
||
|
5. |
baud rates |
|
|
6. |
close_delay |
|
|
7. |
(Setserial)- closing_wait delay |
|
|
8. |
(Setserial) - autoconfig |
|
|
9. |
(stty)Data character size |
|
|
10. |
(stty)Size of stop bits |
|
|
11. |
(stty)Enable parity bits |
|
|
12. |
Enable odd parity |
|
|
13. |
Enable hangup signals when last tty closed |
|
|
14. |
Diable modem control signals |
|
|
Software/Hardware Flow control |
||
|
15. |
(stty) Enable Hardware Flow control(most be set both in serial port driver and the device using the serial port) |
|
|
16. |
(stty) Disable Hardware Flow control |
|
|
17. |
Set/Unset iXon |
|
|
18. |
Set /Unset iXoff |
|
|
19. |
Set / Unset iXany |
|
|
Input Settings |
||
|
20. |
Enable /disable canonical input |
|
|
21. |
Enable /disable Raw input |
|
|
22. |
Enable / disable Input Parity check |
|
|
23. |
Enable / disable ignore parity check |
|
|
24. |
Set Parity error marking ('0' if ignore parity) |
|
|
25. |
Strip 8th bit of input characters |
|
On 2/6/06, Srinivas G. <srinivasg@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Dear Arun Srinivas,
>
> >Can someone please guide me how do I test device drivers in linux? If
> you can please send me useful links/ materials >on it it wud be very
> helpful.
>
> It is totally depends on what type of device do you want test on Linux
> box? We developed and tested the char and block device drivers
> thoroughly on Fedora Core, Red hat and SuSE Linux boxes.
>
> Suppose, if it is block device driver, test cases includes like,
> 1) copy to and from the device for different sizes of files
> 2) mount and un mount the device
> 3) format the device
> 4) create the partitions and try to mount and format the partitions
> individually
> etc.
>
> In all these cases, try to print the debug messages in the driver and
> see any ERROR messages you come across while testing the driver.
>
> If you are really interested I will send you the more test cases.
>
> Regards,
> Srinivas G
>
--
"There are 10 people in the world - those who understand binary and those who dont !"
