public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: Multi-cast support in Ethernet drivers
Date: Fri, 20 Jul 2007 19:44:00 -0000	[thread overview]
Message-ID: <f7r3aj$dk1$1@sea.gmane.org> (raw)
In-Reply-To: <20070720192200.GA28161@lunn.ch>

On 2007-07-20, Andrew Lunn <andrew@lunn.ch> wrote:
> On Thu, Jul 19, 2007 at 02:42:45PM +0400, Alexander Aganichev wrote:
>> On 7/17/07, Andrew Lunn <andrew@lunn.ch> wrote:
>>> > The stack sets up multi-cast MAC to 01:00:5e:00:00:01 and cannot talk
>>> > to my DHCP anymore.
>>>
>>> My first guess is that you are programming the filter incorrectly in
>>> your MAC chip. It could be you are blocking the broadcast address, or
>>> the unicast address for your device. Is the DHCP server broadcasting
>>> is response, or unicasting it?
>>
>> Shouldn't the upper layer provide broadcast address in the
>> list to ETH_DRV_SET_MC_LIST if it wants to receive broadcast
>> packets?

I've never seen that behavior.

>> My guess it is upper layer responsibility to do so, because of
>> otherwise I do not see any sense for that call...

I think it's there to allow multiple unicast addresses to be
used.  However, none of the drivers I've looked at implement
that.

> No, i would expect the default is that the upper layer expects
> the device to always receive broadcast.

Based on the Ethernet drivers I've worked on, that certainly
seems to be the case.

> However maybe your device does not?

If the Ethernet driver didn't pass on to the stack received
broadcast packetsARP wouldn't work, and you couldn't even ping
the device.

> It is at least something to test. Maybe take a look at the
> Linux driver and see what it does for its multicast call. You
> cannot directly use the code, since it is GPL, but you can
> look and see if it does anything interesting.

-- 
Grant Edwards                   grante             Yow!
                                  at               BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-
                               visi.com            


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

      reply	other threads:[~2007-07-20 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 13:06 [ECOS] " Alexander Aganichev
2007-07-08 18:51 ` Andrew Lunn
2007-07-09  6:59   ` Alexander Aganichev
2007-07-09  8:34     ` Andrew Lunn
2007-07-16 12:58       ` Alexander Aganichev
2007-07-17 16:00         ` Andrew Lunn
2007-07-19 10:42           ` Alexander Aganichev
2007-07-20 19:22             ` Andrew Lunn
2007-07-20 19:44               ` Grant Edwards [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='f7r3aj$dk1$1@sea.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).