Re: [ECOS] How does the freebsd socket call the drivers?

["venice" <venice dot tu at live dot com>]

--------------------------------------------------
From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
Sent: Wednesday, March 26, 2008 8:30 PM
To: "venice" <venice.tu@live.com>; <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] How does  the freebsd socket call the drivers?

> venice wrote:
>
> > Hi, I'm writing a net driver and I have a driver template to do that
> > but I still do not know how the applications call the drivers through
> > the freebsd stack. So can you explain the calling functions of the
> > freebsd stack to the drivers?
> > eg:
> > HRDWR_send() can send data by the hardware but who will call this
> > function and provide the data buffer to be transported?
>
> Your driver implements it in
> ecos\packages\devs\eth\[family]\[platform]\current\src\xxx.c
> There a macro fills in the function pointer HRDWR_send(), in my case
> stdims_eth_send:
>
> ETH_DRV_SC(stdims_eth_sc0,
> (void*) &stdims_eth0,
> "eth0",
> stdims_eth_start,
> stdims_eth_stop,
> stdims_eth_control,
> stdims_eth_can_send,
> stdims_eth_send,
> stdims_eth_recv,
> stdims_eth_deliver,
> stdims_eth_poll,
> stdims_eth_intvector);
> NETDEVTAB_ENTRY(stdims_eth_netdev0,
> "stdims_eth0",
> stdims_eth_init,
> &stdims_eth_sc0);
>
> In the documentation you can read the calling order.
>
> Jürgen Lambrecht

Thank Jürgen. My template is something like yours', but I don't know which
function will call  "stdims_eth_send"?  you know the the function is
declared :

stdims_eth_send(struct eth_drv_sc *sc, struct eth_drv_sg *sg_list, int
sg_len,
             int total_len, unsigned long key)

 The function just sends data out by hardware, so there must be a data
buffer created by stack and if the stack want to send data it will put data
to the buffer and the  will call this function.
   Well, I haven't enough time to through out the source code of freebsd
stack but I think the stack will work in this way. But I don't know the
interface of the stack, maybe the data buffer? If I have more time I will
trace the stack for that.
   Anyway, thanks!

Regards,
Venice



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