linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Ann <ktdann@gmail.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: MPC8245 reboot
Date: Thu, 4 Aug 2005 09:16:23 +0900	[thread overview]
Message-ID: <9b7ca6570508031716786e73b0@mail.gmail.com> (raw)
In-Reply-To: <20050803183932.GA13789@mag.az.mvista.com>

Mark,

Guess I'll have to walk the uncharted area again :P
Thanks anyway tho. I'll start by looking at what that port 92
mechanism is first, and see where in our hw designer have put that in.

On 8/4/05, Mark A. Greer <mgreer@mvista.com> wrote:
> On Wed, Aug 03, 2005 at 03:40:18PM +0900, Daniel Ann wrote:
> > Absolutely not. Very much like sandpoint except, we dont use SIO at all=
.
> > FYI, most of sandpoint code from the kernel is function the board very
> > well at the moment. Only big issue lies with REBOOT at this stage:(
>=20
> Daniel,
>=20
> IIRC, the sandpoint uses the PC style port 92 mechanism to reset the boar=
d.
> You need to look at your hardware docs to see how your board can be reset=
.
> Don't expect the sandpoint reset code to work for you.
>=20
> Mark
>=20


--=20
Daniel

  reply	other threads:[~2005-08-04  0:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  5:40 MPC8245 reboot Daniel Ann
2005-08-03  5:47 ` Kumar Gala
2005-08-03  6:40   ` Daniel Ann
2005-08-03 18:39     ` Mark A. Greer
2005-08-04  0:16       ` Daniel Ann [this message]
2005-08-04  0:26         ` Mark A. Greer
  -- strict thread matches above, loose matches on Subject: below --
2005-08-04  9:29 Debora Liu
2005-08-04 10:18 ` Wolfgang Denk

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=9b7ca6570508031716786e73b0@mail.gmail.com \
    --to=ktdann@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mgreer@mvista.com \
    /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).