On 09/26/2011 01:09 PM, Wolfgang Denk wrote: > In message <[email protected]> you wrote: >> We need to enable reverting an env var to its original default >> definition. > > Do we? We have not had that feature for over a decade and nobody ever > really suffered from it. Now we have "env -f reset" for almost a > year, and guess how many percent of the users even know about this > command? And how many have ever actually used it yet?
I think he's saying that one shouldn't be prohibited by length from manually typing "setenv nfsboot ..." to set a value that is no longer than (or even is identical to) the default value. >> Perhaps over time the nfsboot norm setting should be migrated to >> something more modular in the board config files, but right now, >> users are complaining about simply expecting to being able to type >> two more characters on the command line. > > Then educate your users that a boot loader is a resource restricted > environment, and that there at least 10 different ways to do what they > want, at least 8 of them resulting in a much simpler and easier to > comprehend environment setup. What is the resource constraint here that prevents accepting longer console commands? This is a change to the config for a board that comes with multiple gigabytes of RAM. This is not code that runs prior to relocation. Whether the environment scripts could, in time, be structured better is a separate issue from whether there's a good reason to keep this arbitrary limit at its current value that prevents people from manually typing in what is currently being used. -Scott _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
