From: "Mark Chambers" <markc@mail.com>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>,
<linuxppc-embedded@ozlabs.org>
Subject: Re: Linux 2.6-10.rc3 8xx: debugging (over-writing) content of bd_in fo structure in the kernel booting code
Date: Tue, 18 Jan 2005 10:23:12 -0500 [thread overview]
Message-ID: <003e01c4fd71$a7fec540$0301a8c0@chuck2> (raw)
In-Reply-To: 313680C9A886D511A06000204840E1CF0A6474FD@whq-msgusr-02.pit.comms.marconi.com
>
> So what could go wrong here in terms of setting the baudrate for the
serial
> uart
> (which "presumably" causes printing 3 good characters and then garbage
> during kernel booting) ?
>
If you can get your hands on an oscilloscope and look at the TxD from your
board, you can get an exact measurement of your baudrate and make sure
you are on the right track. (Baudrate = 1/shortest-high-or-low-time)
Mark Chambers
next prev parent reply other threads:[~2005-01-18 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 15:01 Linux 2.6-10.rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code Povolotsky, Alexander
2005-01-18 15:23 ` Mark Chambers [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 11:45 Linux 2.6-10.rc3 8xx: debugging (over-writing) content of bd_in " Povolotsky, Alexander
2005-01-18 12:20 ` Hans Schillstrom
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='003e01c4fd71$a7fec540$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=Alexander.Povolotsky@marconi.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).