Minix/minix
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

AT driver is not modified (debugging only);

Browse Source 
TTY: select and revive with new notify and FS call back;
kernel: removed old notify code; removed ugly prepare_shutdown timer
kputc: don't send to FS if PRINTF_PROC fails
This commit is contained in:
Jorrit Herder
2005-07-27 14:32:16 +00:00
parent 28958cca35
commit fe0dcb5c00
23 changed files with 172 additions and 267 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
lib/sysutil/kputc.c
View File

@@ -1,8 +1,6 @@
/* A server must occasionally print some message. It uses a simple version of
* printf() found in the system lib that calls kputc() to output characters.
* Printing is done with a call to the kernel, and not by going through FS.
* This way system messages end up in the kernel messages buffer and can be
* reviewed at a later time.
*
* This routine can only be used by servers and device drivers. The kernel
* must define its own kputc(). Note that the log driver also defines its own
@@ -24,21 +22,23 @@ int c;
message m;
if ((c == 0 && buf_count > 0) || buf_count == sizeof(print_buf)) {
/* Send the buffer to the system task, or, if this process is not a
* server yet, to standard error.
*/
/* Send the buffer to the PRINTF_PROC driver. */
m.DIAG_BUF_COUNT = buf_count;
m.DIAG_PRINT_BUF = print_buf;
m.DIAG_PROC_NR = SELF;
m.m_type = DIAGNOSTICS;
if (_sendrec(PRINTF_PROC, &m) != 0) {
m.m1_i1 = 2;
m.m1_i2 = buf_count;
m.m1_p1 = print_buf;
m.m_type = WRITE;
(void) _sendrec(FS, &m);
}
(void) _sendrec(PRINTF_PROC, &m);
buf_count = 0;
/* If the output fails, e.g., due to an ELOCKED, do not retry output
* at the FS as if this were a normal user-land printf(). This may
* result in even worse problems.
*/
}
if (c != 0) {
/* Append a single character to the output buffer. */
print_buf[buf_count++] = c;
}
if (c != 0) print_buf[buf_count++] = c;
}