From: "Mark A. Greer" <mgreer@mvista•com>
To: Yuxiao Xi <xiyuxiao@harbournetworks•com>
Cc: Tom Rini <trini@kernel•crashing.org>,
"linuxppc-embedded@lists•linuxppc.org"
<linuxppc-embedded@lists•linuxppc.org>
Subject: Re: DINK32 R13.1 on Sandpoint X2
Date: Thu, 04 Sep 2003 13:47:46 -0700 [thread overview]
Message-ID: <3F57A4F2.5040405@mvista.com> (raw)
In-Reply-To: <200309040128.UAA25464@lists.linuxppc.org>
We have an 8139 and have successfully downloaded and run a kernel with
DINK version 13.1.1. I didn't do it but the instructions sent from the
person who did are:
To download via the network, DINK uses fixed IP
address and Realtek8139 NIC. The steps are:
1. do "ppr" verify NIC card has been identified vendor/device ID as
10EC/8139
2. do "env IO=COM1:9600@100, Then "reset".
3. do "ni -i " to set up your network parameters. For example:
DINK32[MPC7457] {1} >>ni
NETWORK INFORMATION
PCI CARD
Type 8139/10EC on slot 16
SETTINGS
SERVER(TFTP) : 192.168. 1. 1
GATEWAY : 192.168. 1. 1
NETMASK : 255.255.255. 0
DHCP : 192.168. 1. 1
CLIENT(DINK) : 192.168. 1. 7
DHCP: Disabled
SESSION TIMEOUT: Never
4. set up you tftp server at host side
5. The download command is "dl -nw -b -o800000 -fzImage.sandpoint"
6. "go 810000"
You can change IP addr, image name, to fit your setup.
As far as differences in the X2 vs. X3, yes there are important
differences. Does DINK v13.1.1 run successfully & download via the
network successfully on an X2? I don't know, you'll have to figure that
out for yourself or talk to Motorola.
Mark
--
Yuxiao Xi wrote:
>Hi,Tom,
> From the mailing lists,I know that someone use DINK32's tftp
>download function to download his image successfully on a Sandpoint X3
>board.Is there any important differences between Sandpoint X3 and X2
>board so that I can not use the DINK32's tftp function on X2 board?
>
>======= 2003-09-03 11:04:00 £º=======
>
>
>
>>On Tue, Sep 02, 2003 at 05:22:08PM +0800, Yuxiao Xi wrote:
>>
>>
>>
>>> Now I'm working on a Motorola Sandpoint X2 board with ppc8240.
>>>I use DINK32 r13.1 to boot my linux kernel image. From DINK32 r13.1
>>>user manual,I know that DINK32 r13.1 supports ethernet card Realtek
>>>8139,but after these steps:
>>>
>>>
>>What I would suggest is that instead of using the ethernet card
>>support, you use the serial support still. DINK32 r13.0.0 and newer
>>support 115200 baud, so loading a kernel via serial is now much less
>>painful than it used to be.
>>
>>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-04 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 1:37 DINK32 R13.1 on Sandpoint X2 Yuxiao Xi
2003-09-04 20:47 ` Mark A. Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 19:16 Milliorn Gary-rxcr80
2003-09-05 5:07 Yuxiao Xi
[not found] <200309040129.UAA29736@gate.crashing.org>
2003-09-04 1:54 ` Tom Rini
2003-09-02 9:22 Yuxiao Xi
2003-09-03 18:04 ` Tom Rini
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=3F57A4F2.5040405@mvista.com \
--to=mgreer@mvista$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=trini@kernel$(echo .)crashing.org \
--cc=xiyuxiao@harbournetworks$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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