linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: ppcembed <linuxppc-embedded@ozlabs.org>
Subject: Re: What's wrong with the serial port?
Date: Tue, 16 Aug 2005 18:53:53 -0700	[thread overview]
Message-ID: <c3d0340b05081618535468581e@mail.gmail.com> (raw)
In-Reply-To: <c3d0340b050811154148164691@mail.gmail.com>

> When the kernel is booting, it gets to the point where console_init()
> is called, which calls individual early console initialization
> functions. In my case it's serial8250_console_init(). Before
> register_console() is called in serial8250_console_init(), everything
> seems fine because the debugging logs are printed on the serial port.
> But once register_console() is called, the serial port continues
> spitting out =E0. See the following message. What's wrong?

FYI. The problem was caused by the endianess of io mem access. My
16550-compatible uart port is on a 32-bit bus. The io mem is big
endian. The current serial8250 driver always call read*/write*() to
access uart control registers. These functions are implemented for
little endian access only. So I have to add some awful #ifdef in the
driver to call big endian access functions.

Regards,
-Shawn.

  parent reply	other threads:[~2005-08-17  1:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 22:41 What's wrong with the serial port? Shawn Jin
2005-08-11 23:14 ` Eugene Surovegin
2005-08-11 23:17   ` Eugene Surovegin
2005-08-12 21:28     ` Shawn Jin
2005-08-12 21:38       ` Shawn Jin
2005-08-17  1:53 ` Shawn Jin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-12  5:01 Debora Liu

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=c3d0340b05081618535468581e@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).