[okl4-developer] networking on gumstix

[Geoffrey Lee]

On Sat, Aug 23, 2008 at 04:26:57AM -0400, Ashish Bijlani wrote:
> how much effort is needed to having vnet infrastructure in iguana? how
> do i go about it? thanks

Hi Ashish

You will need to implement a vnet server and the client side for
vnet,  as well as the specific networking driver for your platform.
How much work will depend on how complex and what features
you choose to support with vnet.

> 
> -ashish

	-gl

> 
> On Sat, Aug 23, 2008 at 4:00 AM, Jean-Christophe Dubois
> <jcd at tribudubois.net> wrote:
> > Le Saturday 23 August 2008 00:34:55 Ashish Bijlani, vous avez écrit :
> >> does that mean there is no virtualization support for networking in
> >> okl4? in tools/release_notes I could see "vnet", what's the status of
> >> vnet in current release of okl4?
> >
> > It seems there used to be an OKL4 network device (CONFIG_IG_NET) but this one
> > is broken in the actual OKL4 2.1.
> >
> >> also, i change the l4linux_config_gumstix to include SMC91X, however
> >> upon booting wombat doesn't load the network driver. Am I missing
> >> anything? I'm taking about single instance of wombat here.
> >
> > I am not sure about the ARM/gumstix option but on an x86 platform enabling
> > pcnet32 or another driver supported by qemu does bring you the network
> > connectivity (oklinux handles the network device directly).
> >
> > JC
> >
> >> please help.
> >>
> >> thanks,
> >> ashish
> >>
> >> On Fri, Aug 22, 2008 at 5:55 PM, Jean-Christophe Dubois
> >>
> >> <jcd at tribudubois.net> wrote:
> >> > Le Friday 22 August 2008 11:31:14 Ashish Bijlani, vous avez écrit :
> >> >> Hi,
> >> >>
> >> >> I'm trying to setup networking between two wombats running on emulated
> >> >> gumstix environment. however, i think network driver is missing in
> >> >> wombat code. afaik, gumstix uses smc91x driver for ethernet, right?
> >> >> how do i bring up networking in wombats?
> >> >
> >> > The oklinux configuration explicitly removed most/all network driver
> >> > support from the linux kernel. So you need to change the .config of your
> >> > oklinux to add support for the network device you are targeting. Then,
> >> > recompile the all thing.
> >> >
> >> > Now in your case with 2 oklinux running on the same hardware (it seems
> >> > this is what you are targeting), I guess you could run into some trouble
> >> > if both instances try to take control of the single network device. I
> >> > don't think you will succeed in making the 2 oklinux speak together
> >> > through the ethernet device if they are on the same gumstix ... You
> >> > should use the OKL4 IPC for this kind of thing.
> >> >
> >> > There might be a way to tell OKL4 to forbid hardware access for one of
> >> > the oklinux instance in order to give exclusive access to the device to
> >> > the other oklinux. At least this would allow one of the oklinux to speak
> >> > to the outer world.
> >> >
> >> > JC
> >> >
> >> >> Thanks,
> >> >> Ashish
> >> >>
> >> >> _______________________________________________
> >> >> Developer mailing list
> >> >> Developer at okl4.org
> >> >> https://lists.okl4.org/mailman/listinfo/developer
> >> >
> >> > _______________________________________________
> >> > Developer mailing list
> >> > Developer at okl4.org
> >> > https://lists.okl4.org/mailman/listinfo/developer
> >
> >
> >
> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> 

--