From: "Tianjun-ZDK" <Tianjun@zcom.unimis.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: Re: Re: [ECOS] How to debug a Ethernet Device Driver via network
Date: Mon, 08 Aug 2005 02:29:00 -0000 [thread overview]
Message-ID: <NETWEB06w3q4RfEJ1Xw000524f9@netweb06.net.unimis> (raw)
>On Mon, 2005-08-08 at 09:42 +0800, Tianjun-ZDK wrote:
>> Hi, all
>>
>> I'm in progress of developing a Ethernet Device Driver.
>> And I want to connect the target Via Ethernet,but it seems
>> the network will down as long as my own NIC driver call
>>
>> (sc->funs->eth_drv->init)( sc, unsigned char *enaddr );
>
>I don't understand what you are saying here. This function needs
>to initialize your hardware and then tell the upper level driver
>that it's ready. Look at the existing drivers to see how it's done.
of cource I know this. I mean after my driver initialized,i cannot
debug via the ethernet(I use a intel i82559 NIC),it seems the network is down.
>
>>
>> can somebody tell me that whetherr eCos can support more than
>> one NIC or not.And if it supports,how to config the network.
>
>eCos certainly can support more then one interface. The builtin
>defaults easily handle a system with two and the simplified call
>"init_all_network_devices()" (called from a user application) will
>fully initialize and configure those 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
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-08-08 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 2:29 Tianjun-ZDK [this message]
2005-08-08 11:52 ` Gary Thomas
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=NETWEB06w3q4RfEJ1Xw000524f9@netweb06.net.unimis \
--to=tianjun@zcom.unimis.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
/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).