> The E2E response hints that we're running into an > organizational conflict of interest at TI.
the main thing I miss from TI's side is communication. All we've heard so far is, "We have this new toolchain thingy here. Like it or lump it." This is not open source development. It would be good, if TI could be more open and explain, what they're going to do, why and how. So that if a RH engineer shows up here, willing to help, he wouldn't receive all the blames. I remember an Atmel engineer doing this a couple of years ago with avr-gcc and I always found that very informative. Might be, that TI's ignorance of the previous community efforts happens for a reason, e.g. not getting in touch with poisonous code (license). But that's hard to believe. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
