For everyone interested, you can follow my branch here: Multicast PR just please don't take anything for granted. I rebase and force-push this branch every once in a while to keep it based off of the latest "main".
As @htibosch mentioned earlier, supporting multicasts requires that the hardware be told which multicast addresses it needs to allow in. In the hardware that I'm working with ( SAME70 ) you can have up to 4 individual addresses + a hash table.
@Hunter-Phipps, if you decide to use the branch, you will have to provide your own add/remove functions and assign them to the interface... something like this:

NetworkInterface_t * pxSAM_FillInterfaceDescriptor( BaseType_t xEMACIndex,
                                                    NetworkInterface_t * pxInterface )
{
    .
    .
    .
	#if ( ipconfigSUPPORT_IP_MULTICAST != 0 )
		pxInterface->pfAddMulticastMAC = prvAddMulticastMACAddress;
		pxInterface->pfRemoveMulticastMAC = prvRemoveMulticastMACAddress;
	#endif
    .
    .
    .
}

Or you can always assign functions that don't do anything as a start and just configure your hardware to receive all multicasts.

@htibosch, you may be interested in how I did my DriverSAM/NetworkInterface.s and in particular the adding and removal of addresses. It attempts to keep track of how many sockets are using a particular hash and only remove the hash when no more sockets need it.
@htibosch, do you think I should just do a "work in progress PR" for this or do you think keeping it separate like it is now is cleaner.

[Feature Request] Multicast Support #962

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions