linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Dan.Geer@faa.gov
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BSE-IP
Date: Mon, 01 Feb 2010 13:06:54 -0600	[thread overview]
Message-ID: <4B67264E.3080100@freescale.com> (raw)
In-Reply-To: <OF7ADBC091.CA74BF20-ON852576BD.0065FA13-852576BD.00685848@faa.gov>

Dan.Geer@faa.gov wrote:
>> Has your firmware already set up the serial port?  cpm-serial doesn't
> make
>> assumptions about specific addresses, but it does assume that the BRG,
> pins,
>> etc. have been set up for the serial port to work.
> 
> Yes. Or, so I thought. First, I interrupt the bootstrap with <Esc>.  Then,
> I load the image into RAM with 'load simpleImage.bseip 200000' then 'go
> 200000'.  All of which is echo'd out the serial console by the firmware.
> I assumed that the low-level setups were complete.  However, in the old
> ppc/boot/m8xx_tty.c there is some initialization for SMC1 and the BRG
> (serial_init()).  Where should I do this in the new model?  Is
> platform_specific_init() the right place?

That'd be the place -- though it's also possible that it is already set up and 
the old code simply didn't assume it, and the problem is somewhere else.

If you don't have an external debugger, you may want to dump some registers from 
the firmware prompt and determine where it set up the tx ring, and use that for 
early debugging.

-Scott

  reply	other threads:[~2010-02-01 19:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 18:08 BSE-IP Dan.Geer
2010-02-01 18:24 ` BSE-IP Scott Wood
2010-02-01 18:59   ` BSE-IP Dan.Geer
2010-02-01 19:06     ` Scott Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-26 20:30 BSE-IP Dan.Geer
2010-01-26 21:03 ` BSE-IP Scott Wood
2010-01-26 22:04   ` BSE-IP Dan.Geer
2010-01-26 22:17     ` BSE-IP Scott Wood
2010-01-26 23:28       ` BSE-IP Dan.Geer

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=4B67264E.3080100@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Dan.Geer@faa.gov \
    --cc=linuxppc-dev@lists.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).