On Wed, May 31, 2017 at 01:51:30PM +0900, Masahiro Yamada wrote:
> Hi Tom
>
> 2017-05-23 10:27 GMT+09:00 Tom Rini :
>
> >> >
> >> >
> >> >
> >> >> I can do this, but
> >> >> I'd like to move forward synced with Linux.
> >> >>
> >> >>
> >> >> Yesterday, I took some time to write patches
> >> >> a
Hi Tom
2017-05-23 10:27 GMT+09:00 Tom Rini :
>> >
>> >
>> >
>> >> I can do this, but
>> >> I'd like to move forward synced with Linux.
>> >>
>> >>
>> >> Yesterday, I took some time to write patches
>> >> and sent them to Linux ML.
>> >>
>> >>
>> >> Plan A:
>> >> https://lkml.org/lkml/2017/4/21/6
On Tue, May 23, 2017 at 09:57:10AM +0900, Masahiro Yamada wrote:
> Hi Denys,
>
>
> 2017-05-23 2:23 GMT+09:00 Denys Dmytriyenko :
> > On Sat, Apr 22, 2017 at 02:30:09PM +0900, Masahiro Yamada wrote:
> >> >>> On Tuesday 28 March 2017 03:14 AM, Nishanth Menon wrote:
> >> >>> > Hi,
> >> >>> >
> >> >>
Hi Denys,
2017-05-23 2:23 GMT+09:00 Denys Dmytriyenko :
> On Sat, Apr 22, 2017 at 02:30:09PM +0900, Masahiro Yamada wrote:
>> >>> On Tuesday 28 March 2017 03:14 AM, Nishanth Menon wrote:
>> >>> > Hi,
>> >>> >
>> >>> > we've kind of run into an interesting situation recently, but might be
>> >>> >
On Sat, Apr 22, 2017 at 02:30:09PM +0900, Masahiro Yamada wrote:
> >>> On Tuesday 28 March 2017 03:14 AM, Nishanth Menon wrote:
> >>> > Hi,
> >>> >
> >>> > we've kind of run into an interesting situation recently, but might be
> >>> > of interest for various folks trying to reduce the image sizes.
2017-04-10 4:27 GMT+09:00 Simon Glass :
> Hi Tom,
>
> On 4 April 2017 at 13:06, Tom Rini wrote:
>> On Tue, Mar 28, 2017 at 11:37:45AM +0530, Lokesh Vutla wrote:
>>> + more folks.
>>>
>>> On Tuesday 28 March 2017 03:14 AM, Nishanth Menon wrote:
>>> > Hi,
>>> >
>>> > we've kind of run into an intere
Hi Tom,
On 4 April 2017 at 13:06, Tom Rini wrote:
> On Tue, Mar 28, 2017 at 11:37:45AM +0530, Lokesh Vutla wrote:
>> + more folks.
>>
>> On Tuesday 28 March 2017 03:14 AM, Nishanth Menon wrote:
>> > Hi,
>> >
>> > we've kind of run into an interesting situation recently, but might be
>> > of inter
Dear Tom,
In message <20170404190647.GH19897@bill-the-cat> you wrote:
>
> Why? I'm not sure that in most cases __FILE__ is providing any more
> useful infomration on top of what we have from __func__ and __LINE__.
Is there not quite a lot of functions that are implemented in many
files? I exp
On Tue, Mar 28, 2017 at 11:37:45AM +0530, Lokesh Vutla wrote:
> + more folks.
>
> On Tuesday 28 March 2017 03:14 AM, Nishanth Menon wrote:
> > Hi,
> >
> > we've kind of run into an interesting situation recently, but might be
> > of interest for various folks trying to reduce the image sizes.
> >
2017-03-28 20:47 GMT+09:00 Felipe Balbi :
>
> Hi,
>
> Nishanth Menon writes:
>> Hi Masahiro-san,
>>
>> On Tue, Mar 28, 2017 at 1:29 AM, Masahiro Yamada
>> wrote:
>> [...]
>>>
>>> When O= is given, the build system runs in the object tree,
>>> not in the source tree.
>>> (This is the same as Linux
On Tue, Mar 28, 2017 at 6:47 AM, Felipe Balbi
wrote:
>
> have you tried using __BASE_FILE__ instead of __FILE__? You could also
https://gcc.gnu.org/onlinedocs/gcc-4.1.2/cpp/Common-Predefined-Macros.html
__BASE_FILE__This macro expands to the name of the main input file, in
the form of a C string
Hi,
Nishanth Menon writes:
> Hi Masahiro-san,
>
> On Tue, Mar 28, 2017 at 1:29 AM, Masahiro Yamada
> wrote:
> [...]
>>
>> When O= is given, the build system runs in the object tree,
>> not in the source tree.
>> (This is the same as Linux.)
>>
>> If you see the top Makefile:
>>
>> ifeq ($(KBUIL
Hi Masahiro-san,
On Tue, Mar 28, 2017 at 1:29 AM, Masahiro Yamada
wrote:
[...]
>
> When O= is given, the build system runs in the object tree,
> not in the source tree.
> (This is the same as Linux.)
>
> If you see the top Makefile:
>
> ifeq ($(KBUILD_SRC),)
> # building in the source tre
Hi Nishanth,
2017-03-28 6:44 GMT+09:00 Nishanth Menon :
> Hi,
>
> we've kind of run into an interesting situation recently, but might be of
> interest for various folks trying to reduce the image sizes.
>
> our AM335x device has a limited amount of sram.. and the SPL tries to fit
> into it (a bit
+ more folks.
On Tuesday 28 March 2017 03:14 AM, Nishanth Menon wrote:
> Hi,
>
> we've kind of run into an interesting situation recently, but might be
> of interest for various folks trying to reduce the image sizes.
>
> our AM335x device has a limited amount of sram.. and the SPL tries to
> fi
Hi,
we've kind of run into an interesting situation recently, but might be
of interest for various folks trying to reduce the image sizes.
our AM335x device has a limited amount of sram.. and the SPL tries to
fit into it (a bit tricky given the restricted space we have on it on
certain class
16 matches
Mail list logo
