Re: CVS commit: src/sys/arch/evbarm/conf
Although I confirmed that all kernels of evbearmv7hf-el had no binary changes after this change, I am a bit confused by [1]. According to [1], at that time, this linker script was used by hpcboot (of hpcarm?). Now I see that hpcarm doesn't seem to use linker script at all. Anyway, load addresses, set in the ELF program header, are for external boot loaders. Which means that linker script should be used depending on a boot loader used for a built kernel. There is also a need for linker scripts to be shared as much as possible. Thus separating the SECTIONS command to program load addresses should have some sense. [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/evbarm/conf/ldscript.evbarm?rev=1.5content-type=text/x-cvsweb-markup
Re: CVS commit: src/sys/kern
In article cadbf7eesqk_em_byggw_5d4x8hsewh_8or+wgyb15ffsfya...@mail.gmail.com, Masao Uebayashi uebay...@gmail.com wrote: On Fri, Aug 21, 2015 at 3:55 PM, Christos Zoulas chris...@netbsd.org wrote: Module Name:src Committed By: christos Date: Fri Aug 21 06:55:25 UTC 2015 Modified Files: src/sys/kern: kern_ksyms.c Log Message: we don't need ioconf.h if we don't have the ksyms pseudo-device This is OK for now but ... quite opposite of modularity. Indeed, but we need config fixes to do this right... christos
Re: CVS commit: src/sys/arch/netwinder/conf
netwinder is strange in that it wants .data aligned to 0x8000, but it also specifies physical/virtual load addresses as 0xc000/0xf000c000, that are obviously not aligned to 0x8000! Can someone check if other load addresses work? For example 0x0001/0xf001?
