mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.44 serial driver bug with asus pr-dls m/b
Date: Tue, 12 Nov 2002 14:33:06 +0000	[thread overview]
Message-ID: <20021112143306.A14369@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3DD106FA.5060809@walrond.org>; from andrew@walrond.org on Tue, Nov 12, 2002 at 01:49:46PM +0000

On Tue, Nov 12, 2002 at 01:49:46PM +0000, Andrew Walrond wrote:
> Further to the hanging serial output; disabling DEBUG_AUTOCONF in 8250.c 
> removes this problem.
> 
> So the only remaining problem is when remote console=ENABLED, rather 
> than post only, in the bios. If this is a problem at all ?
> 
> I assume that remote console=enabled redirects the interrupt 0x10 
> “video” requests used to write to the screen and sends the characters to 
> the serial port instead, rather than just the POST messages. Since the 
> 16bit bios is chucked out when the 32bit linux kernel boots, I don't 
> understand why this upsets anything?

Well, it looks like the serial port at 0x3f8 gets unmapped by the bios
when you set remote console=ENABLED.  The debug output you've sent all
points towards there being no physical port at 0x3f8.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      parent reply	other threads:[~2002-11-12 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 19:48 Andrew Walrond
2002-10-24 19:58 ` Andrew Walrond
2002-11-03 13:58 ` Russell King
2002-11-06 21:30   ` Andrew Walrond
2002-11-12 11:43   ` Andrew Walrond
2002-11-12 12:12     ` Andrew Walrond
2002-11-12 12:52       ` Andrew Walrond
     [not found]         ` <3DD106FA.5060809@walrond.org>
2002-11-12 14:33           ` Russell King [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=20021112143306.A14369@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome