kld problem at Atheros AR9132

[Mori Hiroki]

Hi

This is not boot issue. This is objcopy in elftoolchain issue.

Now objcopy is broken on big endian because of elftoolchain
objcopy is not same binutil objcopy.

Hiroki Mori


----- Original Message -----
> From: Adrian Chadd <adrian.chadd at gmail.com>
> To: Mori Hiroki <yamori813 at yahoo.co.jp>
> Cc: Alexander Kabaev <kabaev at gmail.com>; "freebsd-mips at freebsd.org" <freebsd-mips at freebsd.org>
> Date: 2017/6/18, Sun 12:52
> Subject: Re: kld problem at Atheros AR9132
> 
> hiya,
> 
> you're not booting an elf kernel, right? You're booting a binary only
> kernel with none of the elf bits included (ie, the header, other
> sections), etc? Right?
> 
> You can't do kldload if you're not booting an elf kernel because the
> kernel elf linker doesn't know how to handle it.
> 
> This is why freebsd-wifi-build boots elf kernels. :-)
> 
> 
> -a
> 
> 
> On 15 June 2017 at 06:15, Mori Hiroki <yamori813 at yahoo.co.jp> wrote:
>>  Hi.
>> 
>>  I still have this problem. I seem this is endian problem.
>> 
>>  microserver % cmp -l Onion_Omega_kernel.binutil.ok 
> Onion_Omega_kernel.elfcopy.ng
>>   | head
>>  3055349   0   3
>>  3055350   0  20
>>  3055351  20   0
>>  3055352   3   0
>>  3055353   0 111
>>  3055354   0  32
>>  3055355  32   0
>>  3055356 111   0
>>  3055357   0  21
>>  3055358   0  24
>> 
>>  Onion_Omega_kernel.binutil.ok made by objcopy(GNU objcopy 2.17.50 [FreeBSD] 
> 2007-07-03)
>> 
>> 
>>  Onion_Omega_kernel.elfcopy.ng made by objcopy (elftoolchain r3520M).
>> 
>> 
>>  Regards
>> 
>>  Hiroki Mori
>>  ----- Original Message -----
>>> From: Alexander Kabaev <kabaev at gmail.com>
>>> To: Adrian Chadd <adrian.chadd at gmail.com>
>>> Cc: Mori Hiroki <yamori813 at yahoo.co.jp>; 
> "freebsd-mips at freebsd.org" <freebsd-mips at freebsd.org>
>>> Date: 2017/2/15, Wed 11:46
>>> Subject: Re: kld problem at Atheros AR9132
>>> 
>>> On Tue, 14 Feb 2017 17:02:52 -0800
>>> Adrian Chadd <adrian.chadd at gmail.com> wrote:
>>> 
>>>>  Hiya,
>>>> 
>>>>  ok. why can't it boot ELF? Just set entry point to after the 
> ELF
>>>>  header.
>>>> 
>>>>  -adrian
>>>> 
>>> 
>>> We provide support support for wrapping the kernel and relevant
>>> metadata into a trampoline binary. Maybe it should be used here?
>>> 
>>> --
>>> Alexander Kabaev
>>> 
>>> 
>>> 
>