All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: Early serial port problems
Date: Wed, 30 Mar 2005 10:41:10 +0100	[thread overview]
Message-ID: <20050330104110.D6239@flint.arm.linux.org.uk> (raw)
In-Reply-To: <5895.1109773145@redhat.com>; from dhowells@redhat.com on Wed, Mar 02, 2005 at 02:19:05PM +0000

On Wed, Mar 02, 2005 at 02:19:05PM +0000, David Howells wrote:
>  (2) The boot console log lines for the serial ports and the proc tty listing
>      show an address of 0 because __frv_uart0.mapbase and __frv_uart1.mapbase
>      aren't set:
> 
> 	Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
> 	ttyS0 at MMIO 0x0 (irq = 1) is a 16550A
> 	ttyS1 at MMIO 0x0 (irq = 2) is a 16550A
> 	io scheduler noop registered
> 
>      If I set .mapbase as well as .membase before calling early_serial_setup(),
>      then I see the kernel console output appear, but userspace can't access
>      the serial ports, and the serial driver doesn't record the existence of
>      the ports in the console log:
> 
> 	Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
> 	io scheduler noop registered
> 
>      Adding in UPF_IOREMAP makes no difference.
> 
>      Unsetting .membase and just leaving .mapbase set and UPF_IOREMAP set means
>      that you don't even get kernel console output, though the kernel still
>      boots.
> 
> I wonder if (1) is related to (2).

Don't think so.  It sounds like a problem with claiming the MMIO resources.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

      reply	other threads:[~2005-03-30  9:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 14:19 Early serial port problems David Howells
2005-03-30  9:41 ` 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=20050330104110.D6239@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=dhowells@redhat.com \
    --cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.