Blame view
Documentation/rtc.txt
15.6 KB
1da177e4c Linux-2.6.12-rc2 |
1 |
|
7531d8faa [PATCH] Documenta... |
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 |
Real Time Clock (RTC) Drivers for Linux ======================================= When Linux developers talk about a "Real Time Clock", they usually mean something that tracks wall clock time and is battery backed so that it works even with system power off. Such clocks will normally not track the local time zone or daylight savings time -- unless they dual boot with MS-Windows -- but will instead be set to Coordinated Universal Time (UTC, formerly "Greenwich Mean Time"). The newest non-PC hardware tends to just count seconds, like the time(2) system call reports, but RTCs also very commonly represent time using the Gregorian calendar and 24 hour time, as reported by gmtime(3). Linux has two largely-compatible userspace RTC API families you may need to know about: * /dev/rtc ... is the RTC provided by PC compatible systems, so it's not very portable to non-x86 systems. * /dev/rtc0, /dev/rtc1 ... are part of a framework that's supported by a wide variety of RTC chips on all systems. Programmers need to understand that the PC/AT functionality is not always available, and some systems can do much more. That is, the RTCs use the same API to make requests in both RTC frameworks (using different filenames of course), but the hardware may not offer the same functionality. For example, not every RTC is hooked up to an IRQ, so they can't all issue alarms; and where standard PC RTCs can only issue an alarm up to 24 hours in the future, other hardware may be able to schedule one any time in the upcoming century. Old PC/AT-Compatible driver: /dev/rtc -------------------------------------- |
1da177e4c Linux-2.6.12-rc2 |
37 38 39 40 41 |
All PCs (even Alpha machines) have a Real Time Clock built into them. Usually they are built into the chipset of the computer, but some may actually have a Motorola MC146818 (or clone) on the board. This is the clock that keeps the date and time while your computer is turned off. |
7531d8faa [PATCH] Documenta... |
42 43 44 |
ACPI has standardized that MC146818 functionality, and extended it in a few ways (enabling longer alarm periods, and wake-from-hibernate). That functionality is NOT exposed in the old driver. |
1da177e4c Linux-2.6.12-rc2 |
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 |
However it can also be used to generate signals from a slow 2Hz to a relatively fast 8192Hz, in increments of powers of two. These signals are reported by interrupt number 8. (Oh! So *that* is what IRQ 8 is for...) It can also function as a 24hr alarm, raising IRQ 8 when the alarm goes off. The alarm can also be programmed to only check any subset of the three programmable values, meaning that it could be set to ring on the 30th second of the 30th minute of every hour, for example. The clock can also be set to generate an interrupt upon every clock update, thus generating a 1Hz signal. The interrupts are reported via /dev/rtc (major 10, minor 135, read only character device) in the form of an unsigned long. The low byte contains the type of interrupt (update-done, alarm-rang, or periodic) that was raised, and the remaining bytes contain the number of interrupts since the last read. Status information is reported through the pseudo-file /proc/driver/rtc if the /proc filesystem was enabled. The driver has built in locking so that only one process is allowed to have the /dev/rtc interface open at a time. A user process can monitor these interrupts by doing a read(2) or a select(2) on /dev/rtc -- either will block/stop the user process until the next interrupt is received. This is useful for things like reasonably high frequency data acquisition where one doesn't want to burn up 100% CPU by polling gettimeofday etc. etc. At high frequencies, or under high loads, the user process should check the number of interrupts received since the last read to determine if there has been any interrupt "pileup" so to speak. Just for reference, a typical 486-33 running a tight read loop on /dev/rtc will start to suffer occasional interrupt pileup (i.e. > 1 IRQ event since last read) for frequencies above 1024Hz. So you really should check the high bytes of the value you read, especially at frequencies above that of the normal timer interrupt, which is 100Hz. Programming and/or enabling interrupt frequencies greater than 64Hz is only allowed by root. This is perhaps a bit conservative, but we don't want an evil user generating lots of IRQs on a slow 386sx-16, where it might have |
9be05b57b [PATCH] rtc: smal... |
82 83 84 85 |
a negative impact on performance. This 64Hz limit can be changed by writing a different value to /proc/sys/dev/rtc/max-user-freq. Note that the interrupt handler is only a few lines of code to minimize any possibility of this effect. |
1da177e4c Linux-2.6.12-rc2 |
86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 |
Also, if the kernel time is synchronized with an external source, the kernel will write the time back to the CMOS clock every 11 minutes. In the process of doing this, the kernel briefly turns off RTC periodic interrupts, so be aware of this if you are doing serious work. If you don't synchronize the kernel time with an external source (via ntp or whatever) then the kernel will keep its hands off the RTC, allowing you exclusive access to the device for your applications. The alarm and/or interrupt frequency are programmed into the RTC via various ioctl(2) calls as listed in ./include/linux/rtc.h Rather than write 50 pages describing the ioctl() and so on, it is perhaps more useful to include a small test program that demonstrates how to use them, and demonstrates the features of the driver. This is probably a lot more useful to people interested in writing applications |
7531d8faa [PATCH] Documenta... |
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 |
that will be using this driver. See the code at the end of this document. (The original /dev/rtc driver was written by Paul Gortmaker.) New portable "RTC Class" drivers: /dev/rtcN -------------------------------------------- Because Linux supports many non-ACPI and non-PC platforms, some of which have more than one RTC style clock, it needed a more portable solution than expecting a single battery-backed MC146818 clone on every system. Accordingly, a new "RTC Class" framework has been defined. It offers three different userspace interfaces: * /dev/rtcN ... much the same as the older /dev/rtc interface * /sys/class/rtc/rtcN ... sysfs attributes support readonly access to some RTC attributes. |
92589c986 rtc-proc: permit ... |
119 120 121 |
* /proc/driver/rtc ... the system clock RTC may expose itself using a procfs interface. If there is no RTC for the system clock, rtc0 is used by default. More information is (currently) shown |
7531d8faa [PATCH] Documenta... |
122 123 124 125 126 127 128 129 130 131 132 133 134 |
here than through sysfs. The RTC Class framework supports a wide variety of RTCs, ranging from those integrated into embeddable system-on-chip (SOC) processors to discrete chips using I2C, SPI, or some other bus to communicate with the host CPU. There's even support for PC-style RTCs ... including the features exposed on newer PCs through ACPI. The new framework also removes the "one RTC per system" restriction. For example, maybe the low-power battery-backed RTC is a discrete I2C chip, but a high functionality RTC is integrated into the SOC. That system might read the system clock from the discrete RTC, but use the integrated one for all other tasks, because of its greater functionality. |
ea3d1606f rtc: document the... |
135 136 137 138 139 140 141 142 |
SYSFS INTERFACE --------------- The sysfs interface under /sys/class/rtc/rtcN provides access to various rtc attributes without requiring the use of ioctls. All dates and times are in the RTC's timezone, rather than in system time. date: RTC-provided date |
d8c1acb16 rtc: add boot_tim... |
143 144 |
hctosys: 1 if the RTC provided the system time at boot via the CONFIG_RTC_HCTOSYS kernel option, 0 otherwise |
ea3d1606f rtc: document the... |
145 146 147 148 149 150 151 |
max_user_freq: The maximum interrupt rate an unprivileged user may request from this RTC. name: The name of the RTC corresponding to this sysfs directory since_epoch: The number of seconds since the epoch according to the RTC time: RTC-provided time wakealarm: The time at which the clock will generate a system wakeup event. This is a one shot wakeup event, so must be reset |
1df0a4711 rtc: add ability ... |
152 153 154 155 |
after wake if a daily wakeup is required. Format is seconds since the epoch by default, or if there's a leading +, seconds in the future, or if there is a leading +=, seconds ahead of the current alarm. |
ea3d1606f rtc: document the... |
156 157 158 |
IOCTL INTERFACE --------------- |
7531d8faa [PATCH] Documenta... |
159 160 161 162 163 164 165 166 167 168 169 170 |
The ioctl() calls supported by /dev/rtc are also supported by the RTC class framework. However, because the chips and systems are not standardized, some PC/AT functionality might not be provided. And in the same way, some newer features -- including those enabled by ACPI -- are exposed by the RTC class framework, but can't be supported by the older driver. * RTC_RD_TIME, RTC_SET_TIME ... every RTC supports at least reading time, returning the result as a Gregorian calendar date and 24 hour wall clock time. To be most useful, this time may also be updated. * RTC_AIE_ON, RTC_AIE_OFF, RTC_ALM_SET, RTC_ALM_READ ... when the RTC is connected to an IRQ line, it can often issue an alarm IRQ up to |
f8245c268 rtc: remove "RTC_... |
171 |
24 hours in the future. (Use RTC_WKALM_* by preference.) |
7531d8faa [PATCH] Documenta... |
172 |
|
2b1cd4c43 [PATCH] some rtc ... |
173 |
* RTC_WKALM_SET, RTC_WKALM_RD ... RTCs that can issue alarms beyond |
7531d8faa [PATCH] Documenta... |
174 175 176 |
the next 24 hours use a slightly more powerful API, which supports setting the longer alarm time and enabling its IRQ using a single request (using the same model as EFI firmware). |
ea04683f5 RTC: Fix up rtc.t... |
177 178 |
* RTC_UIE_ON, RTC_UIE_OFF ... if the RTC offers IRQs, the RTC framework will emulate this mechanism. |
7531d8faa [PATCH] Documenta... |
179 |
|
ea04683f5 RTC: Fix up rtc.t... |
180 181 |
* RTC_PIE_ON, RTC_PIE_OFF, RTC_IRQP_SET, RTC_IRQP_READ ... these icotls are emulated via a kernel hrtimer. |
7531d8faa [PATCH] Documenta... |
182 183 184 185 186 |
In many cases, the RTC alarm can be a system wake event, used to force Linux out of a low power sleep state (or hibernation) back to a fully operational state. For example, a system could enter a deep power saving state until it's time to execute some scheduled tasks. |
1da177e4c Linux-2.6.12-rc2 |
187 |
|
ea04683f5 RTC: Fix up rtc.t... |
188 189 |
Note that many of these ioctls are handled by the common rtc-dev interface. Some common examples: |
2b1cd4c43 [PATCH] some rtc ... |
190 191 192 |
* RTC_RD_TIME, RTC_SET_TIME: the read_time/set_time functions will be called with appropriate values. |
ea04683f5 RTC: Fix up rtc.t... |
193 194 |
* RTC_ALM_SET, RTC_ALM_READ, RTC_WKALM_SET, RTC_WKALM_RD: gets or sets the alarm rtc_timer. May call the set_alarm driver function. |
2b1cd4c43 [PATCH] some rtc ... |
195 |
|
ea04683f5 RTC: Fix up rtc.t... |
196 |
* RTC_IRQP_SET, RTC_IRQP_READ: These are emulated by the generic code. |
2b1cd4c43 [PATCH] some rtc ... |
197 |
|
ea04683f5 RTC: Fix up rtc.t... |
198 |
* RTC_PIE_ON, RTC_PIE_OFF: These are also emulated by the generic code. |
ad91fd854 rtc: update docum... |
199 |
|
2b1cd4c43 [PATCH] some rtc ... |
200 |
If all else fails, check out the rtc-test.c driver! |
1da177e4c Linux-2.6.12-rc2 |
201 202 203 204 |
-------------------- 8< ---------------- 8< ----------------------------- /* |
7531d8faa [PATCH] Documenta... |
205 |
* Real Time Clock Driver Test/Example Program |
1da177e4c Linux-2.6.12-rc2 |
206 |
* |
7531d8faa [PATCH] Documenta... |
207 208 |
* Compile with: * gcc -s -Wall -Wstrict-prototypes rtctest.c -o rtctest |
1da177e4c Linux-2.6.12-rc2 |
209 |
* |
7531d8faa [PATCH] Documenta... |
210 |
* Copyright (C) 1996, Paul Gortmaker. |
1da177e4c Linux-2.6.12-rc2 |
211 |
* |
7531d8faa [PATCH] Documenta... |
212 213 |
* Released under the GNU General Public License, version 2, * included herein by reference. |
1da177e4c Linux-2.6.12-rc2 |
214 215 216 217 218 219 220 221 222 223 |
* */ #include <stdio.h> #include <linux/rtc.h> #include <sys/ioctl.h> #include <sys/time.h> #include <sys/types.h> #include <fcntl.h> #include <unistd.h> |
7531d8faa [PATCH] Documenta... |
224 |
#include <stdlib.h> |
1da177e4c Linux-2.6.12-rc2 |
225 |
#include <errno.h> |
1da177e4c Linux-2.6.12-rc2 |
226 |
|
7531d8faa [PATCH] Documenta... |
227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 |
/* * This expects the new RTC class driver framework, working with * clocks that will often not be clones of what the PC-AT had. * Use the command line to specify another RTC if you need one. */ static const char default_rtc[] = "/dev/rtc0"; int main(int argc, char **argv) { int i, fd, retval, irqcount = 0; unsigned long tmp, data; struct rtc_time rtc_tm; const char *rtc = default_rtc; switch (argc) { case 2: rtc = argv[1]; /* FALLTHROUGH */ case 1: break; default: fprintf(stderr, "usage: rtctest [rtcdev] "); return 1; } |
1da177e4c Linux-2.6.12-rc2 |
253 |
|
7531d8faa [PATCH] Documenta... |
254 |
fd = open(rtc, O_RDONLY); |
1da177e4c Linux-2.6.12-rc2 |
255 |
|
7531d8faa [PATCH] Documenta... |
256 257 258 259 |
if (fd == -1) { perror(rtc); exit(errno); } |
1da177e4c Linux-2.6.12-rc2 |
260 |
|
7531d8faa [PATCH] Documenta... |
261 262 263 264 |
fprintf(stderr, " \t\t\tRTC Driver Test Example. "); |
1da177e4c Linux-2.6.12-rc2 |
265 |
|
7531d8faa [PATCH] Documenta... |
266 267 |
/* Turn on update interrupts (one per second) */ retval = ioctl(fd, RTC_UIE_ON, 0); |
1da177e4c Linux-2.6.12-rc2 |
268 |
if (retval == -1) { |
7531d8faa [PATCH] Documenta... |
269 270 271 272 273 274 275 |
if (errno == ENOTTY) { fprintf(stderr, " ...Update IRQs not supported. "); goto test_READ; } |
2b1cd4c43 [PATCH] some rtc ... |
276 |
perror("RTC_UIE_ON ioctl"); |
1da177e4c Linux-2.6.12-rc2 |
277 278 |
exit(errno); } |
7531d8faa [PATCH] Documenta... |
279 280 281 |
fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading %s:", rtc); |
1da177e4c Linux-2.6.12-rc2 |
282 |
fflush(stderr); |
7531d8faa [PATCH] Documenta... |
283 284 285 286 |
for (i=1; i<6; i++) { /* This read will block */ retval = read(fd, &data, sizeof(unsigned long)); if (retval == -1) { |
8696e7026 rtc: cleanup exam... |
287 288 |
perror("read"); exit(errno); |
7531d8faa [PATCH] Documenta... |
289 290 291 292 293 |
} fprintf(stderr, " %d",i); fflush(stderr); irqcount++; } |
1da177e4c Linux-2.6.12-rc2 |
294 |
|
7531d8faa [PATCH] Documenta... |
295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 |
fprintf(stderr, " Again, from using select(2) on /dev/rtc:"); fflush(stderr); for (i=1; i<6; i++) { struct timeval tv = {5, 0}; /* 5 second timeout on select */ fd_set readfds; FD_ZERO(&readfds); FD_SET(fd, &readfds); /* The select will wait until an RTC interrupt happens. */ retval = select(fd+1, &readfds, NULL, NULL, &tv); if (retval == -1) { perror("select"); exit(errno); } /* This read won't block unlike the select-less case above. */ retval = read(fd, &data, sizeof(unsigned long)); if (retval == -1) { perror("read"); exit(errno); } fprintf(stderr, " %d",i); fflush(stderr); irqcount++; } |
1da177e4c Linux-2.6.12-rc2 |
320 |
|
7531d8faa [PATCH] Documenta... |
321 322 |
/* Turn off update interrupts */ retval = ioctl(fd, RTC_UIE_OFF, 0); |
1da177e4c Linux-2.6.12-rc2 |
323 |
if (retval == -1) { |
2b1cd4c43 [PATCH] some rtc ... |
324 |
perror("RTC_UIE_OFF ioctl"); |
1da177e4c Linux-2.6.12-rc2 |
325 326 |
exit(errno); } |
7531d8faa [PATCH] Documenta... |
327 328 329 330 |
test_READ: /* Read the RTC time/date */ retval = ioctl(fd, RTC_RD_TIME, &rtc_tm); |
1da177e4c Linux-2.6.12-rc2 |
331 |
if (retval == -1) { |
2b1cd4c43 [PATCH] some rtc ... |
332 |
perror("RTC_RD_TIME ioctl"); |
1da177e4c Linux-2.6.12-rc2 |
333 334 |
exit(errno); } |
1da177e4c Linux-2.6.12-rc2 |
335 |
|
7531d8faa [PATCH] Documenta... |
336 337 338 339 340 341 |
fprintf(stderr, " Current RTC date/time is %d-%d-%d, %02d:%02d:%02d. ", rtc_tm.tm_mday, rtc_tm.tm_mon + 1, rtc_tm.tm_year + 1900, rtc_tm.tm_hour, rtc_tm.tm_min, rtc_tm.tm_sec); |
1da177e4c Linux-2.6.12-rc2 |
342 |
|
7531d8faa [PATCH] Documenta... |
343 344 345 346 347 348 |
/* Set the alarm to 5 sec in the future, and check for rollover */ rtc_tm.tm_sec += 5; if (rtc_tm.tm_sec >= 60) { rtc_tm.tm_sec %= 60; rtc_tm.tm_min++; } |
8696e7026 rtc: cleanup exam... |
349 |
if (rtc_tm.tm_min == 60) { |
7531d8faa [PATCH] Documenta... |
350 351 352 |
rtc_tm.tm_min = 0; rtc_tm.tm_hour++; } |
8696e7026 rtc: cleanup exam... |
353 |
if (rtc_tm.tm_hour == 24) |
7531d8faa [PATCH] Documenta... |
354 |
rtc_tm.tm_hour = 0; |
1da177e4c Linux-2.6.12-rc2 |
355 |
|
7531d8faa [PATCH] Documenta... |
356 357 358 359 360 361 362 363 364 |
retval = ioctl(fd, RTC_ALM_SET, &rtc_tm); if (retval == -1) { if (errno == ENOTTY) { fprintf(stderr, " ...Alarm IRQs not supported. "); goto test_PIE; } |
2b1cd4c43 [PATCH] some rtc ... |
365 |
perror("RTC_ALM_SET ioctl"); |
7531d8faa [PATCH] Documenta... |
366 367 |
exit(errno); } |
1da177e4c Linux-2.6.12-rc2 |
368 |
|
7531d8faa [PATCH] Documenta... |
369 370 371 |
/* Read the current alarm settings */ retval = ioctl(fd, RTC_ALM_READ, &rtc_tm); if (retval == -1) { |
2b1cd4c43 [PATCH] some rtc ... |
372 |
perror("RTC_ALM_READ ioctl"); |
7531d8faa [PATCH] Documenta... |
373 374 |
exit(errno); } |
1da177e4c Linux-2.6.12-rc2 |
375 |
|
7531d8faa [PATCH] Documenta... |
376 377 378 |
fprintf(stderr, "Alarm time now set to %02d:%02d:%02d. ", rtc_tm.tm_hour, rtc_tm.tm_min, rtc_tm.tm_sec); |
1da177e4c Linux-2.6.12-rc2 |
379 |
|
7531d8faa [PATCH] Documenta... |
380 381 |
/* Enable alarm interrupts */ retval = ioctl(fd, RTC_AIE_ON, 0); |
1da177e4c Linux-2.6.12-rc2 |
382 |
if (retval == -1) { |
2b1cd4c43 [PATCH] some rtc ... |
383 |
perror("RTC_AIE_ON ioctl"); |
1da177e4c Linux-2.6.12-rc2 |
384 385 |
exit(errno); } |
7531d8faa [PATCH] Documenta... |
386 |
fprintf(stderr, "Waiting 5 seconds for alarm..."); |
1da177e4c Linux-2.6.12-rc2 |
387 |
fflush(stderr); |
7531d8faa [PATCH] Documenta... |
388 389 390 391 392 393 394 395 396 |
/* This blocks until the alarm ring causes an interrupt */ retval = read(fd, &data, sizeof(unsigned long)); if (retval == -1) { perror("read"); exit(errno); } irqcount++; fprintf(stderr, " okay. Alarm rang. "); |
1da177e4c Linux-2.6.12-rc2 |
397 |
|
7531d8faa [PATCH] Documenta... |
398 399 |
/* Disable alarm interrupts */ retval = ioctl(fd, RTC_AIE_OFF, 0); |
1da177e4c Linux-2.6.12-rc2 |
400 |
if (retval == -1) { |
2b1cd4c43 [PATCH] some rtc ... |
401 |
perror("RTC_AIE_OFF ioctl"); |
1da177e4c Linux-2.6.12-rc2 |
402 403 |
exit(errno); } |
7531d8faa [PATCH] Documenta... |
404 405 406 407 408 409 410 411 412 |
test_PIE: /* Read periodic IRQ rate */ retval = ioctl(fd, RTC_IRQP_READ, &tmp); if (retval == -1) { /* not all RTCs support periodic IRQs */ if (errno == ENOTTY) { fprintf(stderr, " No periodic IRQ support "); |
7a39a49c7 rtc: make example... |
413 |
goto done; |
7531d8faa [PATCH] Documenta... |
414 |
} |
2b1cd4c43 [PATCH] some rtc ... |
415 |
perror("RTC_IRQP_READ ioctl"); |
7531d8faa [PATCH] Documenta... |
416 417 418 419 420 421 422 423 424 425 426 427 428 |
exit(errno); } fprintf(stderr, " Periodic IRQ rate is %ldHz. ", tmp); fprintf(stderr, "Counting 20 interrupts at:"); fflush(stderr); /* The frequencies 128Hz, 256Hz, ... 8192Hz are only allowed for root. */ for (tmp=2; tmp<=64; tmp*=2) { retval = ioctl(fd, RTC_IRQP_SET, tmp); |
1da177e4c Linux-2.6.12-rc2 |
429 |
if (retval == -1) { |
7531d8faa [PATCH] Documenta... |
430 431 432 433 434 435 436 437 |
/* not all RTCs can change their periodic IRQ rate */ if (errno == ENOTTY) { fprintf(stderr, " ...Periodic IRQ rate is fixed "); goto done; } |
8696e7026 rtc: cleanup exam... |
438 439 |
perror("RTC_IRQP_SET ioctl"); exit(errno); |
1da177e4c Linux-2.6.12-rc2 |
440 |
} |
7531d8faa [PATCH] Documenta... |
441 442 443 |
fprintf(stderr, " %ldHz:\t", tmp); |
1da177e4c Linux-2.6.12-rc2 |
444 |
fflush(stderr); |
1da177e4c Linux-2.6.12-rc2 |
445 |
|
7531d8faa [PATCH] Documenta... |
446 447 448 |
/* Enable periodic interrupts */ retval = ioctl(fd, RTC_PIE_ON, 0); if (retval == -1) { |
8696e7026 rtc: cleanup exam... |
449 450 |
perror("RTC_PIE_ON ioctl"); exit(errno); |
7531d8faa [PATCH] Documenta... |
451 452 453 |
} for (i=1; i<21; i++) { |
8696e7026 rtc: cleanup exam... |
454 455 456 457 458 459 460 461 462 |
/* This blocks */ retval = read(fd, &data, sizeof(unsigned long)); if (retval == -1) { perror("read"); exit(errno); } fprintf(stderr, " %d",i); fflush(stderr); irqcount++; |
7531d8faa [PATCH] Documenta... |
463 464 465 466 467 |
} /* Disable periodic interrupts */ retval = ioctl(fd, RTC_PIE_OFF, 0); if (retval == -1) { |
8696e7026 rtc: cleanup exam... |
468 469 |
perror("RTC_PIE_OFF ioctl"); exit(errno); |
7531d8faa [PATCH] Documenta... |
470 |
} |
1da177e4c Linux-2.6.12-rc2 |
471 |
} |
1da177e4c Linux-2.6.12-rc2 |
472 |
|
7531d8faa [PATCH] Documenta... |
473 474 475 476 477 |
done: fprintf(stderr, " \t\t\t *** Test complete *** "); |
1da177e4c Linux-2.6.12-rc2 |
478 |
|
7531d8faa [PATCH] Documenta... |
479 |
close(fd); |
1da177e4c Linux-2.6.12-rc2 |
480 |
|
7531d8faa [PATCH] Documenta... |
481 482 |
return 0; } |