Hello all,
I'm porting uclinux 2.6.19 on a new architecture (Cortus ASP3) and I have
a problem with the function 'check_tty_count()' (drivers/char/tty_io.c)
On my system, it creates an endless loop in
list_for_each(p, &tty->tty_files) {
count++;
}
I think something in not correclty initialized in my uart driver but I
know what.
However, if I undef CHECK_TTY_COUNT, the kernel reach the point where it
shows the prompt.
(see below).
Have you got an idea how I can fix this problem?
Thanks in advance for your help.
Linux version 2.6.19-uc1 (gcc version 4.1.2 20080812 (Cortus release))
On node 0 totalpages: 1940
DMA zone: 0 pages used for memmap
Normal zone: 15 pages used for memmap
Normal zone: 1925 pages, LIFO batch:0
Built 1 zonelists. Total pages: 1925
Kernel command line:
PID hash table entries: 32 (order: 5, 128 bytes)
Dentry cache hash table entries: 1024 (order: 0, 4096 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mem_init: start=74000, end=794808
Memory available: 1824k/7208k RAM, (619k kernel code, 78k data)
Calibrating delay loop... 0.81 BogoMIPS (lpj=4096)
Mount-cache hash table entries: 512
io scheduler noop registered
io scheduler cfq registered (default)
APS3 Processor Serial Driver v1.0 (c) 2009 Cortus
ttyS0 at MMIO 0x40001000 (irq = 5) is a aps3_uart
uclinux[mtd]: RAM probe address=0x14000 size=0x26000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00026000 : "ROMfs"
uclinux[mtd]: set ROMfs to be root filesystem
VFS: Mounted root (romfs filesystem) readonly.
Freeing unused kernel memory: 2k freed
Shell invoked to run file: /etc/rc
Command: hostname Cortus-aps3
Command: mount -t proc proc /proc
Command: cat /etc/motd
Welcome to
____ _ _
/ __| ||_|
_ _| | | | _ ____ _ _ _ _
| | | | | | || | _ \| | | |\ \/ /
| |_| | |__| || | | | | |_| |/ \
| ___\____|_||_|_| |_|\____|\_/\_/
| |
|_|
For further information check:
http://www.uclinux.org/
Execution Finished, Exiting
Sash command shell (version 1.1.1)
/>
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ