This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: wavelan driver
- To: Jonathan Larmour <jlarmour at redhat dot com>
- Subject: Re: [ECOS] wavelan driver
- From: Andrea Acquaviva - DEIS-micrel (93785) <aacquaviva at deis dot unibo dot it>
- Date: Fri, 20 Jul 2001 04:05:04 +0200 (MET DST)
- Cc: aacquaviva at deis dot unibo dot it, ecos-discuss at sources dot redhat dot com
- References: <200107172048.WAA03080@promet1.deis.unibo.it> <3B54AB2A.B8242A3C@redhat.com>
- Reply-To: aacquaviva at deis dot unibo dot it
Quoting Jonathan Larmour <jlarmour@redhat.com>:
> "Andrea Acquaviva - DEIS-micrel (93785)" wrote:
> >
> > Hi,
> >
> > I'm in the process of writing an ecos driver for the
> > wavelan card, so I need some info about the tcp/ip
> > stack.
> >
> > In particular, looking at the driver_doc document, I
> > don't find where is the correct way to pass the IP
> > source and destination address to the card.
>
> The stack expects to just be able to fill that in and
send it as "data". If
> you need to pass an address to the card as well as the
data, you would
> probably need to extract the addresses back out from
the packet you've been
> passed to send.
>
> But FYI anyway, the header creation gets done in
ip_output.c
>
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK.
Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous
Huxley || Opinions==mine
> Come to the Red Hat TechWorld open source conference
in Brussels!
> Keynotes, techie talks and exhibitions
http://www.redhat-techworld.com/
>
Hi, I've a new question about the driver.
In eth_drv.c:
1- the eth_drv_recv function requires packet data to
be passed to it in order to fill the sg_list, so this
list will be filled with the whole packet except the
headers (802.11 and 802.3), is this correct?
If not, what is the content of the sg_list? In addition,
because of this function is expecting only a 802.3
header, I have to pass the packet lenght minus the
802.11 header size as "total_len" argument?
2- the eth_drv_send function fills the sg_list and calls
the HRDWR_send. What is the content of this list? More
precisely, where can I find the src and dst MAC
addresses? (I need to fill the 802.11 header with this
address)
Thank you,
Andrea.