[U-Boot] [PATCH] README: clean up and document the Freescale QE/FMAN firmware macros

[Timur Tabi <timur@freescale.com>]

Wolfgang Denk wrote:
> Dear Tabi Timur-B04825,
> 
> In message <CAOZdJXUUp6tA_J=_cvVDcd3bfqJMyYTg2s1DTX5mO2fWATNogA@mail.gmail.com> you wrote:
>>
>>> Note that some of the code managed by these macros have not yet been posted
> 
> s/have/has/ ?

Thanks.

>>> externally.  Such code will be posted, but properly documenting the macros
>>> is the first step.
>>
>> Wolfgang, if you're okay with the text in this patch, I will go ahead
>> and make the corresponding changes to the code.  I just want to make
>> sure that there are no objections to these definitions before I work
>> on the code itself.
> 
> Sorry, but I don't even understand this.  What does "post externally"
> mean?

Sorry, that's a term we use in Freescale.  We have in-house code that has not
yet been posted on this mailing list for the "official" U-Boot.  That's what I
mean by posting externally.  I guess I need a better term for that.  We also
call that "upstream".

> And why don't you add the documentation with the code?

I haven't written the code yet.  I want to make sure the idea is acceptable
before I start implementing it.  Plus, since our internal code is different than
our "external" code, I need to manage both code bases independently.

-- 
Timur Tabi
Linux kernel developer at Freescale