Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jeroen Vreeken <pe1rxq@amsat.org>
To: "Tom Vrána" <tom@voda.cz>, linux-mips@linux-mips.org
Subject: Re: ADM5120: time.c issues ?
Date: Tue, 08 Feb 2005 18:13:43 +0100	[thread overview]
Message-ID: <4208F347.4050304@amsat.org> (raw)
In-Reply-To: <4207C71F.7050204@voda.cz>

Tom Vrána wrote:

> Using jeroens time.c the system boots painfully slow, sort of loops 
> int the beginning and the finally freezes on the FPU emulator... any 
> suggestions ?
>
The 2.6.10 kernels I compiled don't seem slow to me.. So there is some 
difference between those two... (Is there a reason you need a 2.4 kernel 
instead of 2.6?)

>
> ttyS28 at 0x03f8 (irq = 4) is a 16450
> ttyS29 at 0x02f8 (irq = 3) is a 16450
> ttyS30 at 0x03e8 (irq = 4) is a 16450

This might have something to do with it... I don't think this serial 
driver should be used. There might be more unneeded stuff in your kernel 
that might do funny things.

Jeroen

      parent reply	other threads:[~2005-02-08 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 19:53 ADM5120: time.c issues ? Tom Vrána
2005-02-07 20:48 ` Florian Lohoff
2005-02-08 17:13 ` Jeroen Vreeken [this message]

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=4208F347.4050304@amsat.org \
    --to=pe1rxq@amsat.org \
    --cc=linux-mips@linux-mips.org \
    --cc=tom@voda.cz \
    /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