linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ron Bianco" <ronb@junction.net>
To: mgreer@mvista.com, "Sébastien Côté" <scote1@matrox.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Stability of MontaVista's 2.4.0-test2-1.2.2-1
Date: Fri, 30 Mar 2001 16:25:54 -0800	[thread overview]
Message-ID: <000a01c0b979$25c93aa0$4d012ac7@warp-speed> (raw)
In-Reply-To: <3AC5146D.CB770D1B@mvista.com>


Check out:

http://www.mot.com/SPS/PowerPC/teksupport/tools/DINK32/VERSION12/dinkindex.htm

Most of DINK source code is easily downloadable, and the full source is obtainable thru a Motorola rep.
Not sure if that link is to the most current version.

Cheers, Ron

> -----Original Message-----

> > Anyway, I have another question.  In the header from
> > arch/ppc/kernel/sandpoint_setup.c,I see the following comment:
> >  * The firmware on the sandpoint is called DINK (not my acronym :).  This
> > port
> >  * depends on DINK to do some basic initialization (e.g., initialize the
> > memory
> >  * ctlr) and to ensure that the processor is using MAP B (CHRP map).
> >
> > Since I don't really have a Sandpoint, and I don't have the DINK which
> > comes with it, I guess I will run into trouble.
> > Is there a place where I could find info on what I should do I exactly as
> > far as initialization goes?!?
>
> No, I don't know of any place you can go that would tell you what you have to
> init.  You could look at some of the open source firmwares that are out there
> which should give you a good idea.  If you have a JTAG probe, you can put it
> on a board similar to yours with known good firmware and look the host-bridge
> regs, etc to how it sets everything up.  I dunno...
>
> You will definitely need to have the PCI arbiter, power mgmt, memory
> controller, and certain bits in HID0 and L2CR (if you have an L2 ctlr on your
> processor) all set up correctly.  Maybe some board regs too.
>
> Mark
>
>
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2001-03-31  0:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-24  1:13 Flash Device Driver kingseft
2001-03-28 19:26 ` Stability of MontaVista's 2.4.0-test2-1.2.2-1 Sébastien Côté
2001-03-28 21:10   ` Mark A. Greer
2001-03-29 14:33     ` Alex Shnitman
2001-03-29 15:28       ` Tom Rini
2001-03-29 16:40       ` Sébastien Côté
2001-03-29 18:11         ` Mark A. Greer
2001-03-29 17:29       ` Mark A. Greer
2001-03-30  1:08         ` Alex Shnitman
2001-03-30 22:52     ` Sébastien Côté
2001-03-30 23:19       ` Mark A. Greer
2001-03-30 23:29         ` Mark A. Greer
2001-03-31  0:25         ` Ron Bianco [this message]

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='000a01c0b979$25c93aa0$4d012ac7@warp-speed' \
    --to=ronb@junction.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mgreer@mvista.com \
    --cc=scote1@matrox.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).