mt7620 works!

Stanislav Galabov sgalabov at gmail.com
Sat Dec 26 05:15:37 UTC 2015


> On 26.12.2015 г., at 2:57, Rodney W. Grimes <freebsd at pdx.rh.CN85.chatusa.com> wrote:
> 
> ...
>>> But if you're trying to build a kernel for the WiTi board (MT7621) you won't be able to as the MT7621 bits are still not in -head.
>>> 
>>> The last commits by Adrian only support RT305x and introduce support for RT5350 (basic support) and MT7620. The MT7620 is substantially different than the MT7621, so it's not a straightforward thing to make it work (UART is different for one).
>>> 
>>> I'll continue working on Mediatek/Ralink support in the new year, so hopefully things are going to get easier then.
>> 
>> Sort of informative, but the page refers to 'oldlzma'.
>> Which I suspect is needed otherwise Uboot starts complaining about
>> during decompressing and aborts.
> 
> Also I see in the page where some of the magic 0x80xxxxxx addresses come from, but where
> did the magic number come from for these two commands:
> 
> tftpboot 0x80800000 DIR-620/kernel.oldlzma.uboot
> bootm 0x80800000
> 
> 
> -- 
> Rod Grimes                                                 rgrimes at freebsd.org

0x80800000 is u-boot's default value for the loadaddr environment variable on some Ralink/Mediatek boards. This is the address which is used for loading stuff via tftp for example.
In any case, it could be any valid memory address, which wouldn't cause overwriting u-boot itself while loading a file (kernel image in this case) via tftp. U-boot will then properly relocate the loaded file to the address inside the image header before booting the kernel as part of executing the bootm command.
I guess the page author didn't think it was necessary to add this information...


More information about the freebsd-mips mailing list