Add four main boot methods to developer build

include/configs/chromeos/developer.h

Index: include/configs/chromeos/developer.h
diff --git a/include/configs/chromeos/developer.h b/include/configs/chromeos/developer.h
index f6cfa2d97dbc27c3b87057d05c97d6dc4e3ee93a..0c07e04ade8fb90eda4e814f332cb3ed3ff1e3d9 100644
--- a/include/configs/chromeos/developer.h
+++ b/include/configs/chromeos/developer.h
@@ -44,6 +44,8 @@
 #define CONFIG_CMDLINE_EDITING          1
 #define CONFIG_COMMAND_HISTORY          1
 #define CONFIG_AUTOCOMPLETE             1
+#define CONFIG_SYS_HUSH_PARSER          1
+#define	CONFIG_SYS_PROMPT_HUSH_PS2      "> "
 
 /*
  * Recovery, normal and stub configs define CONFIG_ENV_IS_NOWHERE, but this
@@ -75,4 +77,19 @@
 #define CONFIG_BOOTP_HOSTNAME
 #define CONFIG_BOOTP_BOOTPATH
 
+#define CONFIG_IPADDR		10.0.0.2

[vb, 2011/02/17 18:00:20]

why is this default setting required? You mention some DHCP server problems
without much elaborating, but giving out ip addreses/masks/dns/gateway configs
are very basic features of pretty much any DHCP server.

It is going to be a mess when several targets on the same network try using the
default IP config.

[sjg, 2011/02/17 18:55:47]

The problem is not DHCP server support, but access to it. For example at many
companies it is difficult to get the DHCP server to do what we want. It can
provide an IP address but everything else it sends is bogus.

I agree this is horrible, but we do have to work in this situation.

[vb, 2011/02/17 19:07:24]

I am almost splitting hairs here, but it could be a config flag for places where
the DHCP server is so deficient, all others should just work without any static
config. It sure would work just fine here.

[sjg, 2011/02/17 19:35:51]

Sadly it doesn't work here.

It is pretty common for a DHCP server to be set up for pxelinux for example. In
any case we typically want our local workstation to be the tfto and NFS server,
which the DHCP will not know about.

+#define CONFIG_SERVERIP		10.0.0.1
+#define CONFIG_BOOTFILE		uImage
+
+/*
+ * We decorate the nfsroot name so that multiple users / boards can easily
+ * share an NFS server:
+ *   user - username, e.g. 'frank'
+ *   board - board, e.g. 'seaboard'
+ *   serial - serial number, e.g. '1234'
+ */
+#define CONFIG_ROOTPATH		"/export/nfsroot-${user}-${board}-${serial#}"

[vb, 2011/02/17 18:00:20]

how about pulling these from build environment? 

[sjg, 2011/02/17 18:55:47]

Can you explain that, please? Not sure what you mean. I am wanting a standard
format for this root path which serve multiple users at a site.

[vb, 2011/02/17 19:07:24]

What I mean to say is that ${user} could be ${USER} from the build environment
and ${board} could be CONFIG_IMAGE_NAME generated by mkconfig. This way even a
default env would point at a specific directory.
 
Of course it should be possible to overwrite these with explicit environment
settings.

[sjg, 2011/02/17 19:35:51]

OK I see. I think this is a good idea. However U-Boot doesn't have USER or BOARD
in its config - CONFIG_IMAGE_NAME is 'chromeos/tegra2/seaboard/developer' which
is not suitable as a tftp filename (we just want 'seaboard'.

Do you want to add these things to U-Boot's mkconfig? If so I am happy to come
back later and move to using it. But I am a little concerned about what upstream
might think.

+
+
+
 #endif //__configs_chromeos_developer_h__