linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: anu k <anuk_mv@rediffmail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem with EEPro100 and Sandpoint board
Date: Thu, 14 Aug 2003 15:35:32 -0700	[thread overview]
Message-ID: <3F3C0EB4.9010101@mvista.com> (raw)
In-Reply-To: <20030814190819.31581.qmail@webmail35.rediffmail.com>


anu k wrote:

>The BooTP server seems to be responding to the requests, but the packets are getting lost at the client end. Not quite sure if its a driver problem or has something to do with the new Sandpoint board revision.\x13
>Regds,
>Anuk
>
>
What kind of board and what's the serial number on it if its an X3(B)?
I just became aware that ones >6000 have had their switch settings
changed when they come from the factory.

Mark


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

      reply	other threads:[~2003-08-14 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14 19:08 Problem with EEPro100 and Sandpoint board anu  k
2003-08-14 22:35 ` Mark A. Greer [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=3F3C0EB4.9010101@mvista.com \
    --to=mgreer@mvista.com \
    --cc=anuk_mv@rediffmail.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).