Date: Sat, 24 Dec 2016 15:35:37 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: src-committers@FreeBSD.org, svn-src-all@FreeBSD.org, svn-src-stable@FreeBSD.org, svn-src-stable-10@FreeBSD.org Subject: Re: svn commit: r308371 - in stable/10: share/man/man4 sys/conf sys/dev/jedec_ts sys/modules/i2c sys/modules/i2c/jedec_ts Message-ID: <9c234848-2d27-b417-b78d-18bde988bc07@FreeBSD.org> In-Reply-To: <2547422.gn4y6NaJ31@ralph.baldwin.cx> References: <201611061356.uA6DuYcO079294@repo.freebsd.org> <1625245.4edrXav981@ralph.baldwin.cx> <912ba7fd-353c-006e-ef65-faa12b83de9f@FreeBSD.org> <2547422.gn4y6NaJ31@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/12/2016 18:55, John Baldwin wrote: > Yes. Well, it fixes linking of kernels at least. Now make tinderbox > on 10 fails for the following kernels: > > _.ia64.GENERIC: Maxmem is not available on ia64. It is spelled > paddr_max instead. The firewire code is trying to use Maxmem. > _.ia64.LINT: Same. > _.arm.LINT: Many link errors and warnings, though lack of 'kbd_*' symbols > seems to be the only actual errors. > > I suspect you recently MFC'd changes to fwohci.c that are using Maxmem. > However, I'm not sure it is worth fixing fwohci on ia64. The ia64 problem should be fixed now. I added Maxmem as we discussed. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9c234848-2d27-b417-b78d-18bde988bc07>