This is the mail archive of the 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: lwIP upgrade to CVS HEAD

Hi Simon

John Dallaway wrote:

> I will review the CDL.

The CDL is looking good so far.

There's some scope for improving the dependency info. For example,

   requires { CYGINT_ISO_MEMALLOC != 0 }
   default_value { CYGINT_ISO_MEMALLOC != 0 }

Many of the protocol components and options are also likely to "require"

There may also be some scope for active_if constraints to clarify the
relevance of certain options. For example, could CYGPKG_LWIP_NETCONF be
made "active_if !CYGPKG_LWIP_DHCP"? This may not be possible if the
static networking address definitions are still required for correct
compilation when DHCP is enabled.

Finally, I would make the display strings of the numerous protocol
support components and options just a little more verbose. For example:

  "DHCP" -> "DHCP support"
  "ICMP" -> "ICMP support"

and so on.

There are currently 27 items directly under the lwIP package node in the
tree. Perhaps there is some scope for further grouping of these nodes to
give the tree more depth and less breadth. For example, a "Protocol
support" component of "flavor none" containing the various protocol

>> The sequential API is required for the socket API and desirable in its
>> own right as it provides a good compromise between ease of use and
>> memory footprint. John Eigelaar has indicated that he would be willing
>> to help with this and already has a copyright assignment in place.
> Any help is appreciated. I will gladly help testing and do work on this
> too, when there is need. But I would like to have John Eigelaar commit
> his changes and go from there instead of going from scratch.
>> We will need more functionality in place before we can replace the
>> existing lwIP port in the eCos repository trunk. We could use your own
>> tree or we could cut a branch in the eCos repository. I would prefer to
>> branch the eCos repository as this would enhance visibility within the
>> eCos community, gives a better sense of shared ownership, and allows the
>> eCos maintainers to monitor progress more easily. Be assured that I am
>> keen to support this lwIP port update and will ensure that patches are
>> committed to the branch quickly.
> I think that's a good idea.

OK. Send me a tarball of the updated package when you're ready to start
collaborating and I'll check it in on a new branch.

John Dallaway

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