LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stevan Ignjatovic <stevan@iritel.com>
To: s.maiti@tcs.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Help Needed: input overrun(s)
Date: Wed, 10 May 2006 15:32:44 +0200	[thread overview]
Message-ID: <1147267964.25388.41.camel@stevan.iritel.co.yu> (raw)
In-Reply-To: <OF00585CA1.4BAD2F12-ON6525716A.0018127A-6525716A.00191467@tcs.com>

Hello,

On Wed, 2006-05-10 at 06:33, s.maiti@tcs.com wrote:
> Hi all,
> 
> I am currently involve in development of Multi-Channel Controller (MCC) 
> driver for MPC8260 processor. Whenever we are loading the driver, on the 
> console we are receiving a print "ttyS: 1 input overrun(s)" along with 
> other prints of the driver and resulting in scrambled output. 
> Can anyone suggest why this is happening? Is the driver affecting the uart 
> driver?

As far as UART driver is concerned, it could be affected if you did not
carefully allocate some resources. Are you using MCC1 or MCC2? Channel
specific parameters of MCC1 (channels 0-127) are at the beginning of the
DPRAM (channel CH_NUM at address 64*CH_NUM). UART driver (as well as
ethernet driver) allocates its buffer descriptors with
m8260_cpm_dpalloc. I think that allocating with this function starts at
the beginning of the DPRAM, so you might have overwritten UART's buffer
descriptors. So, use MCC2 if you can. If you use some BRGs in your MCC
driver you should check that as well.     

>  We have seen the memory map thoroughly, there is no issue of 
> memory conflict. Any help in this regards, I will be grateful.
> 
> Thnaks and regards,
> Souvik Maiti
> Tata Consultancy Services Limited
> Mailto: s.maiti@tcs.com
> Website: http://www.tcs.com
> =====-----=====-----=====
> 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
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Regards,
Stevan

  reply	other threads:[~2006-05-10 13:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  4:33 Help Needed: input overrun(s) s.maiti
2006-05-10 13:32 ` Stevan Ignjatovic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-10 15:15 Rune Torgersen
2006-05-11 12:56 ` s.maiti
2006-05-11 14:14 Rune Torgersen
2006-05-12  5:07 ` s.maiti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1147267964.25388.41.camel@stevan.iritel.co.yu \
    --to=stevan@iritel.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=s.maiti@tcs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox