Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 17 Oct 2020 20:56:15 +0000
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        "Sean Bruno" <sbruno@freebsd.org>
Cc:        "Alexander V. Chernikov" <melifaro@ipfw.ru>, "Emmanuel Vadot" <manu@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r366372 - in head/sys: compat/linuxkpi/common/include/linux compat/linuxkpi/common/src conf
Message-ID:  <6597658A-EED5-4A13-9F1D-42F6F405DCF1@lists.zabbadoz.net>
In-Reply-To: <ce1cb370-16cf-2888-38cf-33cbfd6e8b17@freebsd.org>
References:  <202010021826.092IQfdj023808@repo.freebsd.org> <44421602932538@mail.yandex.ru> <e99c4eb7-2fdc-c5b4-3f48-acb2ef7f4866@freebsd.org> <B5A0232A-48C8-4D12-83B8-A1E801D4BE5B@lists.zabbadoz.net> <ce1cb370-16cf-2888-38cf-33cbfd6e8b17@freebsd.org>

index | next in thread | previous in thread | raw e-mail

On 17 Oct 2020, at 20:48, Sean Bruno wrote:

>>> Same buildfailure with GENERIC-NODEBUG.
>>
>> Seems different.
>>
>>
>>> https://people.freebsd.org/~sbruno/backlight.txt
>>
>> HEAD with which version of the drm port/package?
>>
>> /bz
>
> sbruno@alice:~ % pkg info |grep kmod
> drm-current-kmod-4.16.g20200320 DRM modules for the linuxkpi-based KMS
> components
> drm-kmod-g20190710             Metaport of DRM modules for the
> linuxkpi-based KMS components
> gpu-firmware-kmod-g20200503    Firmware modules for the linuxkpi-based
> KMS components

You may want to have to update this to recent and try again;  if that 
still breaks I assume either Hans or I will be happy to help until manu 
is back.

I’d assume with more linuxkpi bits implemented in HEAD the conflicts 
in head will stay … and port/package updates will have to happen once 
in a while (*).

https://svnweb.freebsd.org/base?view=revision&revision=366374
https://svnweb.freebsd.org/ports?view=revision&revision=551266

/bz

(*) manu is making sure that after the commit to head the new port keeps 
compiling with older kernels for a while using __FreeBSD_version; I may 
have a partial solution that might allow us to update the port first but 
neither won’t help with old ports like in this case.



home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6597658A-EED5-4A13-9F1D-42F6F405DCF1>