<br><font size=2 face="sans-serif">Thanks very much for your reply. It's
seems you have already developed the MCC driver. Are you using channels
32 to 96? Have you made any changes in the dp ram allocation for uart or
ethernet driver?</font>
<br><font size=2 face="sans-serif">Please help me...</font>
<br>
<br><font size=2 face="sans-serif">Thanks and regards,<br>
Souvik Maiti<br>
Tata Consultancy Services Limited<br>
Mailto: s.maiti@tcs.com<br>
Website: http://www.tcs.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Rune Torgersen"
<runet@innovsys.com></b> </font>
<p><font size=1 face="sans-serif">05/10/2006 08:45 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"Stevan Ignjatovic" <stevan@iritel.com>,
<s.maiti@tcs.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif"><linuxppc-embedded@ozlabs.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: Help Needed: input overrun(s)</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>> -----Original Message-----<br>
> From: Stevan Ignjatovic<br>
> Hello,<br>
> <br>
> > console we are receiving a print "ttyS: 1 input overrun(s)"
<br>
> along with <br>
> > other prints of the driver and resulting in scrambled output.
<br>
> > Can anyone suggest why this is happening? Is the driver <br>
> affecting the uart <br>
> > driver?<br>
> <br>
> As far as UART driver is concerned, it could be affected if <br>
> you did not<br>
> carefully allocate some resources. Are you using MCC1 or MCC2? Channel<br>
> specific parameters of MCC1 (channels 0-127) are at the <br>
> beginning of the<br>
> DPRAM (channel CH_NUM at address 64*CH_NUM). UART driver (as well
as<br>
> ethernet driver) allocates its buffer descriptors with<br>
> m8260_cpm_dpalloc. I think that allocating with this function <br>
> starts at<br>
> the beginning of the DPRAM, so you might have overwritten <br>
> UART's buffer<br>
> descriptors. So, use MCC2 if you can. If you use some BRGs in your
MCC<br>
> driver you should check that as well. <br>
<br>
We have a MCC driver that we see the same happening on. It only occurs<br>
under heavy load (top sows us usig 20-40 % cpu in interrupt).<br>
I am pretty confident that we are not overwriting uart DPRAM. (MCC1 only<br>
uses the middle 64 channels, skipping over the first 32 where the<br>
conflict witht he UARTS are)<br>
<br>
I have not seen it corrupt anything, so we have more or less ignored it.<br>
Our theory is that it happens when the CPM gets overloaded.<br>
It would be nice to actually fix it though....<br>
</tt></font>
<br><font size=1 color=white face="sans-serif">ForwardSourceID:NT00006D1A
</font>
<br><pre>=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
</pre>