public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: Hell.Surfers@cwctv.net
Cc: ahu@ds9a.nl, linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: 2.5.x and 8250 UART problems
Date: Sat, 5 Oct 2002 21:01:46 +0100 (BST)	[thread overview]
Message-ID: <200210052001.g95K1k4t001611@darkstar.example.net> (raw)
In-Reply-To: <01d6006411905a2DTVMAIL4@smtp.cwctv.net> from "Hell.Surfers@cwctv.net" at Oct 05, 2002 08:43:14 PM

> > > > I've noticed that 8250 UART based serial port performance is poorer in
> > > > 2.5.x than 2.4.x and 2.2.x, on a couple of my machines.
> > > > 
> > > > The 486 SX-20 with 4 MB RAM, running 2.2.21 reliably achieves about 650
> > > > BPS download from another machine, with the port runnnig at 9600 bps. 
> > > > With 2.5.40, many characters are lost at 9600, making, e.g. a ZModem
> > > > transfer retry for almost every block.
> > > 
> > > Have you tried 'hdparm -u'?
> > 
> > Hmmm, I can do, but I thought it was a Bad Thing (tm) for ISA based
> > controllers?  I could be wrong...
> 
> Shouldn't it be fixed, it should work normally anyway.

Not sure, without interupt unmasking, I would expect excessive disk activity to potentially cause data loss, but there isn't excessive disk activity going on anyway.

If you look at:

http://www.uwsg.iu.edu/hypermail/linux/kernel/0207.3/0373.html

though, you'll see why I was asking for clarification before trying 'hdparm -u', because the laptop in question has a broken floppy drive, so if I corrupt the root filesystem, I've got to take it apart, and put the hard disk in another machine to re-install.  Not a five minute job, by any means!

John.

  reply	other threads:[~2002-10-05 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 19:43 2.5.x and 8250 UART problems Hell.Surfers
2002-10-05 20:01 ` jbradford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-05 15:06 jbradford
2002-10-05 15:07 ` bert hubert
2002-10-05 15:18   ` jbradford
2002-10-05 19:59 ` Russell King
2002-10-05 21:12   ` jbradford
2002-10-05 15:05 jbradford

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=200210052001.g95K1k4t001611@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=Hell.Surfers@cwctv.net \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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