[BusyBox] ash : very slow response

[Glenn R.Heard Jr.]

Dinesh,
    Unfortunately, I do not know in the Linux kernel where or how this is done. I am relatively new to the Linux development world. My problem was on an x86 "homegrown" product that I "inherited" when I got this job. The "homegrown" app was on top of DOS where, as you know, the application is responsible for serial drivers.

    Hopefully there is one of these fine Linux gurus reading this thread that can shed some light on the situation.

Good Luck,

Glenn Heard             rayzer at zoominternet.net
Software Engineer       gheard at altronicinc.com
Altronic Inc.           www.altronicinc.com
ICQ: 123194600          www.zoominternet.net/~rayzer
---
File not found. Should I fake it? (Y/N)

>
>Subject: RE: [BusyBox] ash : very slow response
>   From: Dinesh Nagpure <dinesh_nagpure at ivivity.com>
>   Date: Fri, 11 Oct 2002 09:08:36 -0400
>     To: "'rayzer at zoominternet.net'" <rayzer at zoominternet.net>,
>	Dinesh Nagpure <dinesh_nagpure at ivivity.com>, busybox at busybox.net
>
>YES it is infact a 16550A equivalent (ST16C2550 from EXAR) and has 16byte rx
>and 16 byte Tx FIFO. Do you remember how did you fix the problem. I don't
>see where I can set the Tx FIFO threshold, may be I am missing out
>something.
>
>Thanks
>Dinesh
>
>-----Original Message-----
>From: Glenn R. Heard Jr. [mailto:rayzer at zoominternet.net]
>Sent: Friday, October 11, 2002 10:02 AM
>To: dinesh_nagpure at ivivity.com; busybox at busybox.net
>Subject: RE: [BusyBox] ash : very slow response
>
>
>Dinesh,
>    Does the MIPS uart have a tx FIFO? This sounds to me the very same
>problem I had on 16550 UARTS with incorrect FIFO thresholds being set by the
>UART initialization routines.
>
>Glenn Heard             rayzer at zoominternet.net
>Software Engineer       gheard at altronicinc.com
>Altronic Inc.           www.altronicinc.com
>ICQ: 123194600          www.zoominternet.net/~rayzer
>---
>An idea is not responsible for the people who believe in it.
>
>>
>>Subject: RE: [BusyBox] ash : very slow response
>>   From: Dinesh Nagpure <dinesh_nagpure at ivivity.com>
>>   Date: Fri, 11 Oct 2002 08:56:36 -0400
>>     To: busybox at busybox.net
>>
>>Hello again,
>>
>>I am still trying to resolve this problem. This time I am trying with
>>Busybox v0.60.2 and linux kernel 2.4.16. 
>>I did some further debugging, my findings are:
>>For every key pressed I do get a RxData Ready interrupt, my interrupt
>>handler gets called and reads the character properly. The handler then
>>passes the character to the line discipline for processing (This still is a
>>bit of gray area for me).
>>Eventually the rs_write( ) function should get called which then transfers
>>the character to the Tx buffer and enables the Transmit holding register
>>empty interrupt. In my case this rs_write( ) gets called only after the
>>twelth key press and then all the twelve characters are displayed at once.
>>This is very consistent as if there is a threshold or buffer size set
>>somewhere.
>>Does anyone have any clue about what could be happening here? Any
>>help/pointer will be greatly appreciated.
>>
>>Dinesh
>>
>>
>>
>>-----Original Message-----
>>From: Dinesh Nagpure [mailto:dinesh_nagpure at ivivity.com]
>>Sent: Wednesday, October 09, 2002 6:34 PM
>>To: busybox at busybox.net
>>Subject: [BusyBox] ash : very slow response
>>
>>
>>Hello,
>>
>>I am trying to use BusyBox-0.60.4 on our MIPS (little endian) board running
>>Linux kernel version 2.4.16. When init starts,
>>The fist two messages appear quick and proper on the screen as:
>>BusyBox v0.60.4 XXXXXXXXXXXXXXXXXXXXXXXXX Built-in shell (ash)
>>enter 'help' for a list of built in commands
>>
>>But the third line appears mangled. (Which actually should be the string
>>displayed by out2str( ) called from setjobctl( ) in ash.c)
>>
>>Then comes the prompt # .
>>
>>This point onwards the system becomes very slow. Unless I hit return key
>>several times nothing would appear on the screen and then because of all
>>those return keys screen would scroll. 
>>
>>I am using a simple inittab as below:
>>::sysinit:/etc/init.d/rcS
>>::respawn:/bin/sh
>>
>>My rcS does nothing but /bin/mount -a
>>
>>To me this appears to be some TTY setting issue but I am not sure how to go
>>about it. The tty.c_cflag settings in function set_term( ) in file init.c
>>appear reasonable. 
>>
>>Am I missing something here? Has anyone else faced similar problems in the
>>past? any input will be appreciated.
>>
>>Thanks
>>Dinesh
>>iViVITY
>>
>>
>>
>>
>>_______________________________________________
>>busybox mailing list
>>busybox at busybox.net
>>http://busybox.net/mailman/listinfo/busybox
>>_______________________________________________
>>busybox mailing list
>>busybox at busybox.net
>>http://busybox.net/mailman/listinfo/busybox
>_______________________________________________
>busybox mailing list
>busybox at busybox.net
>http://busybox.net/mailman/listinfo/busybox