From: Thomas Lange <thomas@corelatus•com>
To: Steven Scholz <steven.scholz@imc-berlin•de>
Cc: LinuxPPC <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: MPC8xx IDMA and console garbage
Date: Tue, 23 Apr 2002 13:51:32 +0200 [thread overview]
Message-ID: <3CC54AC4.49A243C9@corelatus.com> (raw)
In-Reply-To: 3CC5477E.4955821A@imc-berlin.de
I also played around with IDMA and noticed the
same thing.
Serial works ok if you put idma priority below
SMC priority. Never investigated further...
/Thomas
Steven Scholz wrote:
>
> Hi there,
>
> I am trying to get DMA support for MPC8xx IDE. For now I use the IDMA
> channel.
> It is kind of working although it's not much more than a framework yet.
>
> BUT:
>
> My problem right now is this:
>
> After activating the DMA (e.g. using hdparm -d1 /dev/hda) the output of
> my serial console (connected to SMC1) gets garbaged when there is HDD
> activity.
>
> If I telnet into my machine and do e.g. a "fdisk -l /dev/hda" the output
> of the serial console looks something like this
>
> ^PttyS: 80 input overrun(s)
> ^P^P^P^P^P^P^P^P^P^ ^PP ^ ^PP ^ ^PP ^P ^P^P^P^P^P^P ^P
> ^P^P^P^P^P^P^P^P^P^P^P^P^PttyS: 80 input overrun(s)
>
> If I redirect console input into a file it contains 0x10 and 0x20 bytes.
>
> So someone is flooding the serial port (SMC) with the two byte 0x10 and
> 0x20 !
> (I might have seen 0x10 and 0xA0 as well.)
>
> Any ideas?
>
> Could there be a problem in using the internal ram area. Maybe my IDMA
> is conflicting with anyother existing driver (SMC???) ?
>
> Thanks,
>
> Steven
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-23 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 11:37 MPC8xx IDMA and console garbage Steven Scholz
2002-04-23 11:51 ` Thomas Lange [this message]
2002-04-23 12:17 ` Steven Scholz
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=3CC54AC4.49A243C9@corelatus.com \
--to=thomas@corelatus$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=steven.scholz@imc-berlin$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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