public inbox for
 help / color / mirror / Atom feed
Subject: [ECOS] How to attach higher ethernet stacks to the MAC driver
Date: Thu, 21 May 2015 16:39:00 -0000	[thread overview]
Message-ID: <trinity-be733170-2ed6-4341-8c2b-ddbde63e67d7-1432226343047@3capp-webde-bs14> (raw)

Hi all,
I have a question regarding the connection between a mac-/phy-driver and a third
party tcp / ip stack. In the mac layer I have functions like
y_eth_isr, y_eth_init, y_eth_send, y_eth_recv, ... and many more.
In y_eth_init I attached an ISR (y_eth_isr) and the default DSR (eth_drv_dsr).
As far as I understood, the data flow is as follows:
1) The MAC (Hardware) receives an ethernet frame and creates an interrupt
2) y_eth_isr is called ( ret = (CYG_ISR_HANDLED | CYG_ISR_CALL_DSR); )
3) The default eth_drv_dsr is called
4) y_eth_deliver is called
5) y_eth_poll is called
6) The default eth_drv_recv is called
7) y_eth_recv in the mac driver is called
This is not what I really could proove but what I investigated by reading the
documentation and source code. Now.. my consideration was that I simply have to
add the call to the receive function of the tcp/ip stack in y_eth_recv. Is this
the right approach?
Another point: how can I reliable test the function of my hardware? I plugged in
my device into an ethernet switch which says that there is a link. Using ipconfig
under Windows just says -not connected-. Using ping is not a solution of course,
because I have no ip address...
And a third question: in the send function of the tcp/ip stack I have to forward
the send buffer to y_eth_send in the mac layer. I simply do this by calling
y_eth0_sc.funs->send(...). Is this the suitable way?
Kind Regards,

Before posting, please read the FAQ:
and search the list archive:

             reply	other threads:[~2015-05-21 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 16:39 Incubus84 [this message]
     [not found] <>
2015-05-26  8:15 ` lesc

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-be733170-2ed6-4341-8c2b-ddbde63e67d7-1432226343047@3capp-webde-bs14 \ \ \

* 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).