This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: BOOTP problem


On Mon, Feb 11, 2008 at 12:44:37PM +0600, Alexey Shusharin wrote:
> 
> ?? ??????, 08/02/2008 ?? 08:39 -0800, Jay Foster ??????????:
> > If you use the latest sources from CVS, you should enable the
> > CYGOPT_NET_FREEBSD_STACK_ACCEPT_UNICAST option to define BOOTP_COMPAT.  This
> > will permit BOOTP to work.  This assumes that you are using the Free BSD
> > network stack.
> > 
> > Jay
> 
> Hi,
> 
> It works! Thanks Jay!
> 
> I think this dependence should be declared in cdl script. What do
> network stack gurus think about adding new option to
> CYGHWR_NET_DRIVER_ETH0_BOOTP (and of course to eth1) component?
> 
> cdl_option CYGHWR_NET_DRIVER_ETH0_FREEBSD_BOOTP_COMPAT {
>     display "Enable FreeBSD stack option for bootp compatibility."
>     flavor  none
>     no_define
>     
>     active_if   CYGPKG_NET_FREEBSD_STACK
>     active_if   !CYGHWR_NET_DRIVER_ETH0_DHCP
>     
>     requires  	CYGOPT_NET_FREEBSD_STACK_ACCEPT_UNICAST
> }
> 
> If it's proper i will send a patch.

Hi Alexey, Jay

This a generic problem with all BOOTP server, or just some BOOTP
servers which don't behave as specified in the RFC?

        Andrew

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]