This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: dynamic creation of ethernet instances ?


Good point .. 

I was reading the docs on how to create a driver. But they apply only 
to physical drivers.
  
What should be done in order to create and hook a virtual driver to the stack 
? 

Would I just need to create an instance of struct eth_drv_sc, fill it in with 
the right callbacks and call if_attach ?

Philippe


On Wednesday 19 February 2003 09:27 pm, Gary D. Thomas wrote:
> On Wed, 2003-02-19 at 19:22, Philippe Moutarlier wrote:
> > Well, I guess I am a little confused :-(
> >
> > NETDEVTAB is used all over the place in eth_drv.c, notably
> > in  eth_drv_run_deliveries which is directly called by the delivery
> > thread.
>
> This is true, but this is only for calling the DSR (delivery)
> code for a physical driver.  I thought you were asking about
> virtual drivers (like VLAN) which would not need such (I don't
> think).
>
> If you're asking for the ability to just add a physical device
> dynamically, the stack and indeed eCos is not really set up
> for this.  eCos is designed for static embedded systems and
> dynamic entities are not part of the plan.
>
> --
> .--------------------------------------------------------.
>
> |       Mind: Embedded Linux and eCos Development        |
> |--------------------------------------------------------|
> | Gary Thomas              email:  gary dot thomas at mind dot be   |
> | Mind ( http://mind.be )  tel:    +1 (970) 229-1963     |
> | gpg: http://www.chez-thomas.org/gary/gpg_key.asc       |
>
> '--------------------------------------------------------'


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]