Skip to contentSkip to conversation

Schedule removal of non-CONFIG_NET_MULTI net driver API

PATCH New Ben Warren 4 participants 5 messages Apr 29, 2009 – May 15, 2009

lore
Share & tools
lore

Ben Warren

author
#0 lore raw

PATCH 1/1 Schedule removal of non-CONFIG_NET_MULTI net driver API

This will make CONFIG_NET_MULTI the only net driver configuration and we'll be able to remove this option.

---
 doc/feature-removal-schedule.txt |   19 +++++++++++++++++++
 1 files changed, 19 insertions(+), 0 deletions(-)
doc/feature-removal-schedule.txt +19 -0
index d966abb..deb89ed 100644
@@ -7,6 +7,25 @@ file.
 
 ---------------------------
 
+What:	CONFIG_NET_MULTI option
+When:	Release 2009-11
+
+Why:	U-boot currently implements two network driver APIs.  New drivers with
+	the older-style implementation have not been accepted for a while, and
+	this parallel system makes the code confusing and hard to augment. 
+
+	All existing in-tree boards will be converted to use CONFIG_NET_MULTI
+	over the span of two releases (2009-07 and 2009-09).
+	In the 2009-11 release, all code that is compiled when CONFIG_NET_MULTI
+	is not set will be removed, and all references to CONFIG_NET_MULTI
+	will be removed, effectively making it the only API.  This should
+	provide ample time for out-of-tree users to adjust, and for tools on
+	all architectures to be made to work with weak functions.
+
+Who:	Ben Warren <[email protected]>
+
+---------------------------
+
 What:	"autoscr" command
 When:	Release 2009-09
 
Signature · 1 line
1.5.6.3
#1 lore raw

PATCH 1/1 Schedule removal of non-CONFIG_NET_MULTI net driver API

Quoted 2 lines · Ben Warren

This will make CONFIG_NET_MULTI the only net driver configuration and we'll be able to remove this option.

Could we add a #warning somewhere to tell people who are not using CONFIG_NET_MULTI that they need to move forward?

Andy

#2 lore raw

PATCH 1/1 Schedule removal of non-CONFIG_NET_MULTI net driver API

Quoted 7 lines · Andy Fleming
Quoted 2 lines · Ben Warren

This will make CONFIG_NET_MULTI the only net driver configuration and we'll be able to remove this option.

Could we add a #warning somewhere to tell people who are not using CONFIG_NET_MULTI that they need to move forward?

good idea and it will avoid people to have a error if they do not read the removal or the ML when updating their patch for the mainline

Best Regards,
J.

author
#3 lore raw

PATCH 1/1 Schedule removal of non-CONFIG_NET_MULTI net driver API

In reply to Andy Fleming
Quoted 7 lines · Andy Fleming
Quoted 3 lines · Ben Warren

This will make CONFIG_NET_MULTI the only net driver configuration and we'll be able to remove this option.

Quoted 6 lines

Could we add a #warning somewhere to tell people who are not using CONFIG_NET_MULTI that they need to move forward?

Andy

Sure. Good idea.

regards,
Ben

#4 lore raw

PATCH 1/1 Schedule removal of non-CONFIG_NET_MULTI net driver API

In reply to Ben Warren

Dear Ben Warren,

Quoted 7 lines · In message <[email protected]> you…

This will make CONFIG_NET_MULTI the only net driver configuration and we'll be able to remove this option.

---
 doc/feature-removal-schedule.txt |   19 +++++++++++++++++++
 1 files changed, 19 insertions(+), 0 deletions(-)

Applied, thanks.

Best regards,

Wolfgang Denk

Signature · 3 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Quoted 1 line

Is there a way to determine Yesterday's date using Unix utilities?

echo "what is yesterday's date?" | /bin/mail root -- Randal L. Schwartz in <[email protected]>