From: Florian Fainelli <florian@openwrt.org>
To: myuboot@fastmail.fm
Cc: linux-kernel@vger.kernel.org, "linux-mips" <linux-mips@linux-mips.org>
Subject: Re: serial port 8250 messed up after coverting from little endian to big endian on kernel 2.6.31
Date: Tue, 20 Oct 2009 08:17:23 +0200 [thread overview]
Message-ID: <200910200817.24018.florian@openwrt.org> (raw)
In-Reply-To: <1255996564.10560.1340920621@webmail.messagingengine.com>
[-- Attachment #1: Type: Text/Plain, Size: 1116 bytes --]
Hi,
Le mardi 20 octobre 2009 01:56:04, myuboot@fastmail.fm a écrit :
> I am trying to bringup a MIPS32 board using 2.6.31. It is working in
> little endian mode. After changing the board's hardware from little
> endian to bit endian, the serial port print messed up. It prints now
> something like - "àààààààààààààààà" on the screen. When I trace the
> execution, I can see the string the kernel is trying print is correct -
> "Linux version 2.6.31 ..." and etc.
>
> I guess it means the initialization of the serial port is not properly
> done. But I am not sure where I should check for the problem. The serial
> port device I am using is 8250. Please give me some advise.
If the same initialization routine used to work in little-endian, check how
you actually write and read characters from the UART FIFO and especially if
your hardware requires you to do word or byte access to these registers.
You can have a look at AR7, which has the same code working for Little and Big
Endian modes in arch/mips/ar7/prom.c lines 272 to the end of the file. It also
uses a 8250-compatible UART.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-20 6:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1255735395.30097.1340523469@webmail.messagingengine.com>
2009-10-16 23:50 ` 2.6.31 kernel for mips compile failure - war.h:12:17: error: war.h: No such file or directory David Daney
2009-10-19 23:49 ` myuboot
2009-10-19 23:56 ` serial port 8250 messed up after coverting from little endian to big endian on kernel 2.6.31 myuboot
2009-10-20 6:17 ` Florian Fainelli [this message]
2009-10-20 15:52 ` myuboot
2009-10-27 20:40 ` myuboot
2009-10-28 8:35 ` Shmulik Ladkani
2009-10-28 11:04 ` Sergei Shtylyov
2009-10-28 19:36 ` myuboot
2009-10-29 8:26 ` Shmulik Ladkani
2009-11-02 23:54 ` myuboot
2009-12-04 1:52 ` PIR OFFSET for AR7 myuboot
2009-12-04 16:03 ` Thomas Bogendoerfer
2009-12-04 17:30 ` myuboot
2009-11-11 0:22 ` Kernel panic - not syncing: Attempted to kill init! myuboot
[not found] ` <4AFA6B7F.10404@walsimou.com>
2009-11-11 15:48 ` myuboot
2009-11-17 0:21 ` problem bring up initramfs and busybox myuboot
2009-11-17 9:33 ` Ralf Baechle
2009-11-17 17:39 ` myuboot
2009-11-17 17:48 ` Florian Fainelli
2009-11-17 21:09 ` myuboot
2009-11-17 21:02 ` Kevin D. Kissell
2009-11-17 21:54 ` Chris Dearman
2009-11-18 0:31 ` myuboot
2009-11-18 0:39 ` Florian Fainelli
2009-11-18 0:58 ` myuboot
2009-11-18 1:03 ` David VomLehn
2009-11-18 16:11 ` myuboot
2009-11-18 16:29 ` myuboot
2009-11-26 0:24 ` myuboot
2009-11-26 8:45 ` Florian Fainelli
2009-11-26 18:23 ` myuboot
2009-12-05 0:18 ` myuboot
2010-01-19 19:51 ` loadable kernel module link failure - endianness incompatible with that of the selected emulation myuboot
2010-01-19 23:47 ` David Daney
2010-01-20 16:10 ` myuboot
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=200910200817.24018.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=myuboot@fastmail.fm \
/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).