From: Leonardo Pereira Santos <lsantos@pd3.com.br>
To: Thomas Andrews <tandrews@mindspring.co.za>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Development hardware
Date: Thu, 30 Jan 2003 10:03:11 -0200 [thread overview]
Message-ID: <200301301003.12610.lsantos@pd3.com.br> (raw)
In-Reply-To: <20030130090746.A5731@mindspring.co.za>
I was in the same situation as you're now, to only have acess to a FADS board.
We managed to make it work with a MPC850SAR. If you need any directions,
don't hesitate to drop a word.
On Thursday 30 January 2003 05:07, Thomas Andrews wrote:
> Hi Folks
>
> I see in the docs that the Motorola FADS board is to be avoided.
> Unfortunately this is all I have access to - Unless someone has
> an inexpensive alternative for me ? Suggestions ? I want to play
> with the 860T, which is what I currenly have on the FADS board.
>
> The BDM I have is an Ocdemon Raven. There is linux support for this on
> the ocdemon web site, but is there an open source bdm driver ? I really
> don't want to rely on binaries.
>
> Oh, and one more thing does anyone know if the Raven supports the MMU
> table-walk ?
>
> Many thanks,
> Thomas
>
- --
This is Linux country.
On a quiet night, you can hear Windows reboot.
Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Pará 330/202
(51) 3337 1237
Today Fortune tells us:
This fortune would be seven words long if it were six words shorter.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-30 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 7:07 Development hardware Thomas Andrews
2003-01-30 10:43 ` Frank Robbins
2003-01-30 11:12 ` Wolfgang Denk
2003-01-30 12:03 ` Leonardo Pereira Santos [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-30 7:32 Claus Gindhart
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=200301301003.12610.lsantos@pd3.com.br \
--to=lsantos@pd3.com.br \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tandrews@mindspring.co.za \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.