On 21.12.2010 20:52, Wolfgang Denk wrote: > Dear Albert& friends, > > what is your opinion? Should we include the memory barrier patch into > the upcoming release (and eventually delay it for further testing), or > release as is and solve this issue in the next release? > > I tend to leave it as is, as I expect that most people will disappear > in the next few days for holidays, so no much testing will be done > anyway, and we then can solve this with less pressure in the next > release - but I'm not really sure if this is a good idea?
I somehow tend to leave it as is, too. We have issues with some recent compilers. For these we found a fix using the io.h somehow the same way the Linux kernel does. But this introduces new issues for us, we haven't found a proper fix yet (except changing the code to the 'old' io.h style). But we don't know where we might have this issue additionally, yet. I would like to talk with some tool chain guys about this, too. Could we add a readme or a note somewhere about the issues with the recent tool chains in this release? Best regards Dirk _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
