Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Marc Karasek <marc_karasek@ivivity.com>
To: Linux MIPS <linux-mips@oss.sgi.com>
Subject: Serial Console on Malta broken?
Date: 26 Nov 2001 16:05:43 -0500	[thread overview]
Message-ID: <1006808755.7860.5.camel@localhost.localdomain> (raw)

I just got the latest source from the cvs server (2.4.14).  I am working
on the MALTA eval board from MIPS.  I noticed that the serial console is
very slow once it is initialized,  once it starts to print the "serial
concole detected" it slows down to a crawl.  Prints around 10+ char and
then pauses.  You can do a ls, etc...  but do not expect the output in
your lifetime. 

In debugging I noticed that the mipsIRQ.S file is no longer used for
interrupt handling.  Does anyone know why this was done?  I have
compared it to source from 2.4.3-01.01 (from the MIPS site).  I checked
the mailing list and there was some discussion about a similar bug that
had to do with the serial port and the interrupt not working right. 

Any enlightenment would be greatly appreciated.  We are looking to put a
stake in the ground as far as kernel version to start working with and
we need something that is post 2.4.10.  

-- 
/*************************
Marc Karasek
Sr. Firmware Engineer
iVivity Inc.
marc_karasek@ivivity.com
(770) 986-8925
(770) 986-8926 Fax
*************************/

             reply	other threads:[~2001-11-26 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 21:05 Marc Karasek [this message]
2001-11-27 12:50 ` Serial Console on Malta broken? Carsten Langgaard
     [not found] ` <20011127175420.F29424@dea.linux-mips.net>
     [not found]   ` <1006884537.2037.4.camel@localhost.localdomain>
     [not found]     ` <20011207100937.D1347@dea.linux-mips.net>
     [not found]       ` <1007741762.1387.3.camel@localhost.localdomain>
2001-12-07 16:52         ` Ralf Baechle

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=1006808755.7860.5.camel@localhost.localdomain \
    --to=marc_karasek@ivivity.com \
    --cc=linux-mips@oss.sgi.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