[openbeosnetteam] Re: Directory Structure...
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Fri, 8 Feb 2002 15:02:01 -0000
You can email me it directly :)
Or I can give some space via ftp on my server....
It'd be cool to know how we interact with the nic's... It's the one thing
that has me a little worried at the moment...
david
----- Original Message -----
From: "Emmanuel Jacobs" <emmanuel.jacobs@xxxxxxxxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Sent: Friday, February 08, 2002 2:57 PM
Subject: [openbeosnetteam] Re: Directory Structure...
>
> Yes I was, I tried to...
>
> I tried to buil two things:
> 1) a "dummy" driver. Each packet sent for output to the driver should
> trigger a "packet received" event, loopbacking the packet to the handler.
> 2) a program to interface directly with ethernet drivers to begin to play
> with all the things you listed in your previous mail.
>
> I couldn't find the time to finish those, none were working when I
stopped.
> But I have some valuable information about drivers and how to write those.
> I also heve the source code of Axel for a device driver he wrote.
>
> I have to take the time to organize that information and to upload the
> result somewhere.
> So the question is where can I upload that stuff ?
>
> Regards,
>
> Emmanuel
>
> ----- Original Message -----
> From: "David Reid" <dreid@xxxxxxxxxxxx>
> To: <openbeosnetteam@xxxxxxxxxxxxx>
> Sent: Friday, February 08, 2002 3:43 PM
> Subject: [openbeosnetteam] Re: Directory Structure...
>
>
> >
> > Did Jean say you were looking at how net_server talks to the network
> cards?
> > That's really the first thing we need before we can go anywhere real...
> >
> > I think once we have that piece of information this is what we should
> do...
> >
> > o build a simple net_server that can talk to the cards, get input, send
> > output
> > o write the ethernet module
> > o write a very simple arp module that just prints it's findings
> > o write a very simple wrapper for ip that again just prints it's
findings
> > o statically link all these together and hard code the links between
them
> > o make sure it's all working
> >
> > Viola! We now have our test bed for doing the module/linking/loading etc
> > stuff. At least this way we start from a know basis with actual code to
> work
> > with. Spending too much time on how we link the modules etc together
> before
> > that is interesting, but not very practical.
> >
> > BTW, I estimate the above will take about 2-3 hours :)
> >
> > david
> >
> > ----- Original Message -----
> > From: "Emmanuel Jacobs" <emmanuel.jacobs@xxxxxxxxxxxx>
> > To: <openbeosnetteam@xxxxxxxxxxxxx>
> > Sent: Friday, February 08, 2002 2:34 PM
> > Subject: [openbeosnetteam] Re: Directory Structure...
> >
> >
> > >
> > > Fine for me :-)
> > >
> > > Emmanuel
> > >
> > > ----- Original Message -----
> > > From: "David Reid" <dreid@xxxxxxxxxxxx>
> > > >
> > > > As we want to have all "parts" as modules are we happy with this...
> > > >
> > > > server/
> > > > /net - basic net_server module
> > > > /arp
> > > > /ethernet
> > > > /include
> > > > /ipv4
> > > > /ppp
> > > > /tcp
> > > > /udp
> > > >
> > > > Include files should stay with their module as closely as possible,
> with
> > > > anything that's global being in include.
> > > >
> > > > The main / directory is used to store all sorts of silly general
> things
> > at
> > > > present, so maybe we move all those to a seperate "util" directory?
> > > >
> > > > david
> > > >
> > >
> > >
> > >
> >
>
>
>
Other related posts:
