From: mkhoyila@uci.edu
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] _control and _start are called several times in the begining
Date: Mon, 22 Aug 2005 21:43:00 -0000 [thread overview]
Message-ID: <27391.63.87.1.243.1124746992.squirrel@webmail.uci.edu> (raw)
Gentlemen
I have an issue (may be it is not an issue) about _control, _send and
_stop functions. As you see from below printout, above functions are
called three times before eCos settles down. Is this normal? Thanks for
your help.
eth0: MAC Address: 02:10:12:01:00:08
[cyg_net_init] Init: loopattach(0x00000000)
[cyg_net_init] Init: ifinit(0x00000000)
[cyg_net_init] Init: domaininit(0x00000000)
[cyg_net_init] Init: cyg_net_add_domain(0x800553e4)
New domain internet at 0x00000000
[cyg_net_init] Init: cyg_net_add_domain(0x80054e40)
New domain route at 0x00000000
[cyg_net_init] Init: cyg_route_init(0x00000000)
[cyg_net_init] Done
BOOTP[eth0] op: REPLY
htype: Ethernet
hlen: 6
hops: 0
xid: 0x0
secs: 0
flags: 0x0
hw_addr: 02:10:12:01:00:08
client IP: 192.168.1.8
my IP: 192.168.1.8
server IP: 192.168.1.10
gateway IP: 192.168.1.100
options:
subnet mask: 255.255.255.0
IP broadcast: 192.168.1.255
gateway: 192.168.1.100
inet_net() - entering...for network interface eth0
bcm63xx_start
xmit 42 bytes at 8007ad56 sg[1]
8007AD56: FF FF FF FF FF FF 02 10 12 01 00 08 08 06 00 01
|................|
8007AD66: 08 00 06 04 00 01 02 10 12 01 00 08 C0 A8 01 08
|................|
8007AD76: 00 00 00 00 00 00 C0 A8 01 08 |..........
|
bcm63xx_send
bcm63xx_control
bcm63xx_start
bcm63xx_control
bcm63xx_stop
bcm63xx_start
bcm63xx_control
--
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-22 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 21:43 mkhoyila [this message]
2005-08-22 21:57 ` 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=27391.63.87.1.243.1124746992.squirrel@webmail.uci.edu \
--to=mkhoyila@uci.edu \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).