Re: [ECOS] FW: Ethernet init problem

[Jonathan Larmour <jifl at eCosCentric dot com>]

Gary D. Thomas wrote:
> On Thu, 2003-02-06 at 15:50, Jonathan Larmour wrote:
> > There shouldn't be any multicast addresses I'd have thought. And naturally 
> > it fails because the QUICC eth driver doesn't support multicast yet.
> Actually, it always makes this call, initially with an empty multicast
> list.  Also, this is only a warning - the upper layers ignore the fact
> that the driver can't handle multicast addresses and just continue.
It's output with a diag_printf which means it's always output for the vast 
majority of drivers without multicast support (and doesn't say it's a 
warning, not an error). Should this be conditional on net debugging 
instead? I'll arrange if so.

> > But another probably more promising line of attack is that "Init device 
> > 'quicc_eth'" doesn't necessarily mean your eth device itself was included. 
> > That init comes from the NETDEVTAB, but the eth0 instance is defined 
> > separately. Check if your program image includes quicc_eth0_sc.
>
> Or put an explicit diag_printf() call somewhere in the QUICC ethernet
> initialization, just to see if it gets there.
Probably worth checking, although he said eth_drv_init() is being called, 
and that's only called from the low level driver, so this probably isn't it.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


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