In message 20040628105102.GB14287@pengutronix.de you wrote:
On Mon, Jun 28, 2004 at 11:35:01AM +0200, Wolfgang Denk wrote:
In U-Boot we just split in "cpu" and "board".
Which is no good idea. CPU is ARM920T and each and every board copies everything it needs from other boards.
Feel free to make a suggestion how to deal with this in a better way.
Is there any activity to work on a "next generation u-boot" which avoids all the design glitches we currently have? It's nearly impossible to
Maybe as a first step we should start collecting such design glitches?
restructure things in a tree which is supposed to be production code. I think of things like config frontend, everybody-is-alowed-to-add-tons- of-trailing-whitespace-if-he-is-not-robert, layered drivers which hold their pointers to the hardware in structures instead of 1001 ifdefs etc.
Re config frontend: is there any new stuff available that I don't know of? We had this discusssion a couple of times before, but I haven't seen any working code or implementation example yet. I cannot make comments on things I have never seen.
Re everybody-is-alowed-to-add-tons-of-trailing-whitespace-if-he-is-not-robert: I can understand that you feel frustrated, as you hold the record of having patches rejected because of violating the Coding Style. To make it clear: there are no exceptions from the rules. The coding style applies to everybody. For small patches I may decide to perform the cleanup myself, especially for people submitting their first few patches. This is mostly to encourage them to go on contributing their work back to the community. From netheads like you I expect a little more. OK, everybody can miss a thing here or there. But your patches violate the Coding Style in a density that I can only call ignorance. I am not in the mood to accept an attitude like "it is difficult to audit this patch for trailing whitespace as the patch context contains that much" - there is only a single file in the CVS which contains trailing while space (and this is the automatically generated include/bmp_logo.h). Sorry - the context is clean, so please cleanup your patch, too.
Re layered drivers: Please feel free to submit patches.
Best regards,
Wolfgang Denk