public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: hui liu <fubaiqun1@yahoo.com.cn>
To: yh@bizmail.com.au
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] 回复: Re: [ECOS] Re: Intel LXT971
Date: Thu, 20 Apr 2006 13:21:00 -0000	[thread overview]
Message-ID: <20060420132103.40018.qmail@web15403.mail.cnb.yahoo.com> (raw)
In-Reply-To: <1174.203.217.29.133.1145506497.squirrel@203.217.29.133>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312, Size: 2312 bytes --]

Maybe you should change some lines in your codes
because of the contorl register differences between
RTL820 and LXT971.You can find  in their documents.
--- yh@bizmail.com.auдµÀ:

> Thanks Gary. It is actually a ship set from Intel
> LXT971ABE A4 L549ID42.
> The Ethernet of our board worked when the RTL820 was
> used, but now the
> redboot cannot connect to the network since
> replacing to Intel LXT971.
> Sorry, I am new to the redboot. I thought to get
> some advices from experts
> on this list before plunging into the debug. Any
> more information and
> helps would be great appreciated.
> 
> Thank you.
> 
> Jim
> 
> > On Thu, 2006-04-20 at 11:36 +1000,
> yh@bizmail.com.au wrote:
> >> Hello,
> >>
> >> Does current redboot (ecos version 2.0) support
> Intel Ethernet chipset
> >> LXT971?
> >
> > eCos 2.0 is nearly 4 years old - hardly current.
> >
> > The LXT97x is an ethernet PHY (which is just the
> physical layer
> > used by some ethernet chips).  Normally, there is
> little (or nothing)
> > required to control these devices - they just do
> their job.  They do
> > have a control interface whereby you can set the
> hardware bit rate,
> > e.g. 100Mb or 10Mb, detect the presence of a
> carrier/cable, etc.
> > They are not [directly] responsible for passing
> ethernet data, that
> > job is handled by some other device.
> >
> > You need to figure out what the actual ethernet
> device is; depending
> > on the platform, this may be a separate device
> like an 82559 chip,
> > etc, or it may be builtin to the CPU (SOC), e.g.
> on the XScale devices.
> >
> > --
> >
>
------------------------------------------------------------
> > Gary Thomas                 |  Consulting for the
> > MLB Associates              |    Embedded world
> >
>
------------------------------------------------------------
> >
> >
> 
> 
> 
> -- 
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive:
> http://ecos.sourceware.org/ml/ecos-discuss
> 
> 



	

	
		
___________________________________________________________ 
ÑÅ»¢1GÃâ·ÑÓÊÏä°Ù·Ö°Ù·ÀÀ¬»øÐÅ 
http://cn.mail.yahoo.com/

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2006-04-20 13:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 22:24 [ECOS] fat filename length Scott Bailie
2006-04-20  1:24 ` [ECOS] Re: Intel LXT971 yh
2006-04-20  2:10   ` Gary Thomas
2006-04-20  4:03     ` yh
2006-04-20 13:21       ` hui liu [this message]
2006-04-20  9:31 ` [ECOS] fat filename length Nick Garnett

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=20060420132103.40018.qmail@web15403.mail.cnb.yahoo.com \
    --to=fubaiqun1@yahoo.com.cn \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=yh@bizmail.com.au \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).