Well, I'm getting closer. I have been working with my serial port driver for
the LinkUp Systems L7200 chip. I am very confident of the console code and
am properly handling interrupts. After the call for opening '/dev/console'
in 'init/main.c' I decided to make a call to 'write' immediately afterwords
with some test text and that worked just fine by printing the string I gave
it out over my serial console. Next, I verified that after the ramdisk is
mounted it does indeed find the '/sbin/init' file. I created an '/sbin/init'
that looks like this:
#include <stdio.h>
#include <fcntl.h>
int main(void)
{
int i;
i = open("/dev/ttyS1", O_RDWR);
close(i);
while(1);
return 0; /* Should not get here. */
}
I then added a 'printk (KERN_EMERG "Serial port opening\n");' to be the first
line in the 'rs_open' method. I then compiled the above and made it the
'/sbin/init' program and recompiled the kernel. I also made the permissions
666 on '/dev/ttyS1' and made a new ramdisk. So, what I expected to see was a
kernel message on the console after the '/sbin/init' program executed. Well,
after the kernel booted up and gave me the messaged that it did indeed mount
the ramdisk, I did not see the kernel message above. Any thoughts? Also, I
have not yet implemented any of the 'flush' methods and such for the serial
driver. I have the console routines, open and the interrupt handler which
properly receive and transmit characters.
-Steve
--
Steven J. Hill - Embedded SW Engineer
Public Key: 'finger [EMAIL PROTECTED]'
FPR1: E124 6E1C AF8E 7802 A815
FPR2: 7D72 829C 3386 4C4A E17D
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
