On 4/9/15 05:10, Chen Gang wrote:
>
> After this patch, blackfin can pass allmodconfig building (if we treat
> it as allmodconfig). And next, I shall try to:
>
> - Send all related patches v2 for blackfin kernel within this month.
>
> - Fix blackfin gcc/binutils related issues within this
On 4/9/15 05:10, Chen Gang wrote:
>
> After this patch, blackfin can pass allmodconfig building (if we treat
> it as allmodconfig). And next, I shall try to:
>
> - Send all related patches v2 for blackfin kernel within this month.
>
> - Fix blackfin gcc/binutils related issues within this
On 4/9/15 05:10, Chen Gang wrote:
After this patch, blackfin can pass allmodconfig building (if we treat
it as allmodconfig). And next, I shall try to:
- Send all related patches v2 for blackfin kernel within this month.
- Fix blackfin gcc/binutils related issues within this month.
On 4/9/15 05:10, Chen Gang wrote:
After this patch, blackfin can pass allmodconfig building (if we treat
it as allmodconfig). And next, I shall try to:
- Send all related patches v2 for blackfin kernel within this month.
- Fix blackfin gcc/binutils related issues within this month.
On 4/24/15 16:20, Steven Miao wrote:
> On Thu, Apr 23, 2015 at 10:30 PM, Chen Gang
> wrote:
>>
>> OK, thanks. I guess your meaning is:
>>
>> - If the kernel is too big, it may let the pc which wants to call L1
>>space fail.
>>
>> - So the kernel is too big to cause this issue, but it is
On Thu, Apr 23, 2015 at 10:30 PM, Chen Gang wrote:
> On 4/23/15 10:51, Steven Miao wrote:
>> On Wed, Apr 22, 2015 at 10:32 PM, Chen Gang
>> wrote:
>>> On 4/22/15 17:00, Steven Miao wrote:
Hi,
On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang
wrote:
> l1_text is at
On Thu, Apr 23, 2015 at 10:30 PM, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 4/23/15 10:51, Steven Miao wrote:
On Wed, Apr 22, 2015 at 10:32 PM, Chen Gang xili_gchen_5...@hotmail.com
wrote:
On 4/22/15 17:00, Steven Miao wrote:
Hi,
On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang
On 4/24/15 16:20, Steven Miao wrote:
On Thu, Apr 23, 2015 at 10:30 PM, Chen Gang xili_gchen_5...@hotmail.com
wrote:
OK, thanks. I guess your meaning is:
- If the kernel is too big, it may let the pc which wants to call L1
space fail.
- So the kernel is too big to cause this issue,
On 4/23/15 10:51, Steven Miao wrote:
> On Wed, Apr 22, 2015 at 10:32 PM, Chen Gang
> wrote:
>> On 4/22/15 17:00, Steven Miao wrote:
>>> Hi,
>>>
>>> On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang
>>> wrote:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big,
On 4/23/15 10:51, Steven Miao wrote:
On Wed, Apr 22, 2015 at 10:32 PM, Chen Gang xili_gchen_5...@hotmail.com
wrote:
On 4/22/15 17:00, Steven Miao wrote:
Hi,
On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang xili_gchen_5...@hotmail.com
wrote:
l1_text is at L1_CODE_START (e.g. for bf533,
On Wed, Apr 22, 2015 at 10:32 PM, Chen Gang wrote:
> On 4/22/15 17:00, Steven Miao wrote:
>> Hi,
>>
>> On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang
>> wrote:
>>> l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
>>> is too big, it may be overwritten, the related issue:
>>>
On 4/22/15 17:00, Steven Miao wrote:
> Hi,
>
> On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang wrote:
>> l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
>> is too big, it may be overwritten, the related issue:
>>
>> LD init/built-in.o
>> init/built-in.o: In function
Hi,
On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang wrote:
> l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
> is too big, it may be overwritten, the related issue:
>
> LD init/built-in.o
> init/built-in.o: In function `do_early_param':
>
On 4/22/15 17:00, Steven Miao wrote:
Hi,
On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang xili_gchen_5...@hotmail.com wrote:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
On Wed, Apr 22, 2015 at 10:32 PM, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 4/22/15 17:00, Steven Miao wrote:
Hi,
On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang xili_gchen_5...@hotmail.com
wrote:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be
Hi,
On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang xili_gchen_5...@hotmail.com wrote:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
Am 09.04.2015 um 15:28 schrieb Chen Gang:
> On 4/9/15 05:12, Richard Weinberger wrote:
>> Am 08.04.2015 um 23:10 schrieb Chen Gang:
>>>
>>> After this patch, blackfin can pass allmodconfig building (if we treat
>>> it as allmodconfig). And next, I shall try to:
>>>
>>> - Send all related patches
On 4/9/15 05:12, Richard Weinberger wrote:
> Am 08.04.2015 um 23:10 schrieb Chen Gang:
>>
>> After this patch, blackfin can pass allmodconfig building (if we treat
>> it as allmodconfig). And next, I shall try to:
>>
>> - Send all related patches v2 for blackfin kernel within this month.
>>
>> -
On 4/9/15 05:19, Richard Weinberger wrote:
> Am 08.04.2015 um 23:16 schrieb Chen Gang:
>> On 4/9/15 05:10, Richard Weinberger wrote:
>>> Am 08.04.2015 um 23:05 schrieb Chen Gang:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten,
On 4/9/15 05:12, Richard Weinberger wrote:
Am 08.04.2015 um 23:10 schrieb Chen Gang:
After this patch, blackfin can pass allmodconfig building (if we treat
it as allmodconfig). And next, I shall try to:
- Send all related patches v2 for blackfin kernel within this month.
- Fix blackfin
On 4/9/15 05:19, Richard Weinberger wrote:
Am 08.04.2015 um 23:16 schrieb Chen Gang:
On 4/9/15 05:10, Richard Weinberger wrote:
Am 08.04.2015 um 23:05 schrieb Chen Gang:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related
Am 09.04.2015 um 15:28 schrieb Chen Gang:
On 4/9/15 05:12, Richard Weinberger wrote:
Am 08.04.2015 um 23:10 schrieb Chen Gang:
After this patch, blackfin can pass allmodconfig building (if we treat
it as allmodconfig). And next, I shall try to:
- Send all related patches v2 for blackfin
Am 08.04.2015 um 23:16 schrieb Chen Gang:
> On 4/9/15 05:10, Richard Weinberger wrote:
>> Am 08.04.2015 um 23:05 schrieb Chen Gang:
>>> l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
>>> is too big, it may be overwritten, the related issue:
>>>
>>> LD
On 4/9/15 05:10, Richard Weinberger wrote:
> Am 08.04.2015 um 23:05 schrieb Chen Gang:
>> l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
>> is too big, it may be overwritten, the related issue:
>>
>> LD init/built-in.o
>> init/built-in.o: In function
Am 08.04.2015 um 23:10 schrieb Chen Gang:
>
> After this patch, blackfin can pass allmodconfig building (if we treat
> it as allmodconfig). And next, I shall try to:
>
> - Send all related patches v2 for blackfin kernel within this month.
>
> - Fix blackfin gcc/binutils related issues within
After this patch, blackfin can pass allmodconfig building (if we treat
it as allmodconfig). And next, I shall try to:
- Send all related patches v2 for blackfin kernel within this month.
- Fix blackfin gcc/binutils related issues within this month.
Thanks.
On 4/9/15 05:03, Chen Gang wrote:
Am 08.04.2015 um 23:05 schrieb Chen Gang:
> l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
> is too big, it may be overwritten, the related issue:
>
> LD init/built-in.o
> init/built-in.o: In function `do_early_param':
> init/main.c:(.init.text+0xe0):
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
Am 08.04.2015 um 23:16 schrieb Chen Gang:
On 4/9/15 05:10, Richard Weinberger wrote:
Am 08.04.2015 um 23:05 schrieb Chen Gang:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
After this patch, blackfin can pass allmodconfig building (if we treat
it as allmodconfig). And next, I shall try to:
- Send all related patches v2 for blackfin kernel within this month.
- Fix blackfin gcc/binutils related issues within this month.
Thanks.
On 4/9/15 05:03, Chen Gang wrote:
Am 08.04.2015 um 23:05 schrieb Chen Gang:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation
On 4/9/15 05:10, Richard Weinberger wrote:
Am 08.04.2015 um 23:05 schrieb Chen Gang:
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
is too big, it may be overwritten, the related issue:
LD init/built-in.o
init/built-in.o: In function `do_early_param':
init/main.c:(.init.text+0xe0): relocation truncated to fit: R_BFIN_PCREL24
against symbol
Am 08.04.2015 um 23:10 schrieb Chen Gang:
After this patch, blackfin can pass allmodconfig building (if we treat
it as allmodconfig). And next, I shall try to:
- Send all related patches v2 for blackfin kernel within this month.
- Fix blackfin gcc/binutils related issues within this
40 matches
Mail list logo
