Poll: rndis or composite (ethernet + serial) gadget

Hi,

The standard angstrom kernel now uses composite gadget (ethernet + serial) so you can have networking and serial access over the same usb cable, bit it seems windows doesn't quite like the ethernet part. So:

* do you want rndis or composite gadget on by default for beagle?

regards,

Koen

PS: if someone knows how to get windows to like the composite gadget, please share your info

RNDIS.

One may use the serial to configure the board but then it is REALLY
handy to be able to run the 3" square card from just one USB cable!

- dan

A linux host has no problems recognizing the composite device?

A linux host has no problems recognizing the composite device?

No problems that I've noticed, it pops up an ethernet and a serial device :slight_smile:

regards,

Koen

I’d like to look into the windows compatibility issue. I’m a Beagle/Angstrom newbie, but have some experience with USB device firmware and host drivers. It’ll take me a while, so I’ll watch and see if anyone else comes up with a solution in the meantime.

Composite.

BTW, it has the potential to be really convenient since both uBoot and
the kernel can support usbtty. However, minicom doesn't seem to work
so well with this model. Any advice on terminal programs that will
automatically close/reopen the device?

Secondly, I would recommend giving the host side of the ethernet
gadget device a fixed hardware address, eg
'g_ether.host_addr=B6:A3:A1:7D:8F:F0'. This makes it much easier to
use with the connection sharing network manager feature.

Hi,

The standard angstrom kernel now uses composite gadget (ethernet + serial)
so you can have networking and serial access over the same usb cable, bit it
seems windows doesn't quite like the ethernet part. So:

* do you want rndis or composite gadget on by default for beagle?

Composite.

BTW, it has the potential to be really convenient since both uBoot and
the kernel can support usbtty

That's the reason composite is on by default :slight_smile:

. However, minicom doesn't seem to work
so well with this model. Any advice on terminal programs that will
automatically close/reopen the device?

Haven't found one yet.

Secondly, I would recommend giving the host side of the ethernet
gadget device a fixed hardware address, eg
'g_ether.host_addr=B6:A3:A1:7D:8F:F0'. This makes it much easier to
use with the connection sharing network manager feature.

We could use the omap serial number as mac address, to keep the beagles unique. Does anyone know how much work that would be, to get uboot to do that?

regards,

Koen

Hi,

The standard angstrom kernel now uses composite gadget (ethernet +
serial)
so you can have networking and serial access over the same usb cable, bit
it
seems windows doesn't quite like the ethernet part. So:

* do you want rndis or composite gadget on by default for beagle?

Composite.

BTW, it has the potential to be really convenient since both uBoot and
the kernel can support usbtty

That's the reason composite is on by default :slight_smile:

. However, minicom doesn't seem to work
so well with this model. Any advice on terminal programs that will
automatically close/reopen the device?

Haven't found one yet.

I made a small app that presents a pty/pts for minicom and then opens
a serial device and forwards information between them, if the serial
device goes away, it reopens it.

http://gitorious.org/projects/clonetty

Hello Russ,

Is the issue Koen mentioned with a composite gadget in windows resolved with the patches you posted to this board today 4/6/09?

Also - are these patches made to the OMAP branch of the kernel? Sorry if this is a dumb question.

Rich

Sorry, I re-read your first patch message and see these patches were to the OMAP kernel.

Since Windows users outnumber linux users, I prefer rndis.

If I want to compile my own image to have rndis, can you show me how
to do that?

Thanks

I prefer modules and scripts so that its easier for users to change their minds without needing a recompile…

Not when it comes to beagleboard users....