From: "Yuxiao Xi" <xiyuxiao@harbournetworks.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: DINK32 R13.1 on Sandpoint X2
Date: Thu, 4 Sep 2003 09:37:40 +0800 [thread overview]
Message-ID: <200309040128.UAA25464@lists.linuxppc.org> (raw)
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.
= = = = = = = = = = = = = = = = = = = =
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Yuxiao Xi
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡xiyuxiao@harbournetworks.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-09-04
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-09-04 1:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 1:37 Yuxiao Xi [this message]
2003-09-04 20:47 ` DINK32 R13.1 on Sandpoint X2 Mark A. Greer
-- 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=200309040128.UAA25464@lists.linuxppc.org \
--to=xiyuxiao@harbournetworks.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 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.