Is it then possible to introduce another option - install only drm-kmod sources
and don't build a module, so that a user that builds a new kernel often can
build when he chooses to?
signature.asc
Description: PGP signature
On 8/16/19 5:33 PM, Rozhuk Ivan wrote:
> On Fri, 16 Aug 2019 17:23:08 -0700
> John Baldwin wrote:
>
>>> I use better way:
>>> /etc/make.conf:
>>> # Modules to build with kernel.
>>> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod
>>> graphics/gpu-firmware-kmod
>>
>> This doesn't work for folks who u
On Fri, Aug 16, 2019 at 6:37 PM John Baldwin wrote:
> On 8/16/19 2:51 PM, Rodney W. Grimes wrote:
> >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> >>> I've lost the original thread, but would the sources in
> /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
> And, now that
On 8/16/19 2:51 PM, Rodney W. Grimes wrote:
>> On 8/14/19 3:40 PM, Daniel Eischen wrote:
>>> I've lost the original thread, but would the sources in
>>> /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
>>> And, now that sources may be installed by a port, what is the meth
On Fri, 16 Aug 2019 17:23:08 -0700
John Baldwin wrote:
> > I use better way:
> > /etc/make.conf:
> > # Modules to build with kernel.
> > PORTS_MODULES+= graphics/drm-fbsd12.0-kmod
> > graphics/gpu-firmware-kmod
>
> This doesn't work for folks who use pre-built packages.
>
I update mine /usr/
On August 16, 2019 4:32:18 PM PDT, "Rodney W. Grimes"
wrote:
>> On Fri, 16 Aug 2019 15:40:24 -0700
>> Cy Schubert wrote:
>>
>> > On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
>> > wrote:
>> > >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
>> > >> > I've lost the original thread, but wo
On 8/16/19 3:52 PM, Rozhuk Ivan wrote:
> On Fri, 16 Aug 2019 15:40:24 -0700
> I use better way:
> /etc/make.conf:
> # Modules to build with kernel.
> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod graphics/gpu-firmware-kmod
This doesn't work for folks who use pre-built packages.
--
John Baldwin
On Fri, 16 Aug 2019 16:32:18 -0700 (PDT)
"Rodney W. Grimes" wrote:
> > > >> > I've lost the original thread, but would the sources in
> > > >/usr/local/sys/modules get built regardless of what
> > > >MAKEOBJDIRPREFIX is? And, now that sources may be installed by
> > > >a port, what is the me
> On Fri, 16 Aug 2019 15:40:24 -0700
> Cy Schubert wrote:
>
> > On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
> > wrote:
> > >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> > >> > I've lost the original thread, but would the sources in
> > >/usr/local/sys/modules get built regardless
On Fri, 16 Aug 2019 15:40:24 -0700
Cy Schubert wrote:
> On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
> wrote:
> >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> >> > I've lost the original thread, but would the sources in
> >/usr/local/sys/modules get built regardless of what MAKEOBJD
On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
wrote:
>> On 8/14/19 3:40 PM, Daniel Eischen wrote:
>> > I've lost the original thread, but would the sources in
>/usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX
>is? And, now that sources may be installed by a port, what
> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> > I've lost the original thread, but would the sources in
> > /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
> > And, now that sources may be installed by a port, what is the method for
> > _just_ updating the sources? Why
On 8/14/19 1:19 PM, Ian Lepore wrote:
> On Wed, 2019-08-14 at 13:59 -0600, Warner Losh wrote:
>> On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote:
>>
>>> On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
On 8/14/19 11:06 AM, Kyle Evans wrote:
> LOCAL_MODULES="" does seem like a sensi
On 8/14/19 3:40 PM, Daniel Eischen wrote:
> I've lost the original thread, but would the sources in
> /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
> And, now that sources may be installed by a port, what is the method for
> _just_ updating the sources? Why do I even
> On Aug 14, 2019, at 6:59 PM, Steve Kargl
> wrote:
>
>> On Wed, Aug 14, 2019 at 06:40:28PM -0400, Daniel Eischen wrote:
>> I've lost the original thread, but would the sources in
>> /usr/local/sys/modules get built regardless of what
>> MAKEOBJDIRPREFIX is? And, now that sources may be insta
On Wed, Aug 14, 2019 at 06:40:28PM -0400, Daniel Eischen wrote:
> I've lost the original thread, but would the sources in
> /usr/local/sys/modules get built regardless of what
> MAKEOBJDIRPREFIX is? And, now that sources may be installed
> by a port, what is the method for _just_ updating the sour
I've lost the original thread, but would the sources in /usr/local/sys/modules
get built regardless of what MAKEOBJDIRPREFIX is? And, now that sources may be
installed by a port, what is the method for _just_ updating the sources? Why
do I even need to build and install the port? Personally,
On August 14, 2019 11:04:20 AM PDT, Ian Lepore wrote:
>On Wed, 2019-08-14 at 19:55 +0200, Niclas Zeising wrote:
>> On 2019-08-14 19:23, Emmanuel Vadot wrote:
>> > On Wed, 14 Aug 2019 10:13:48 -0700
>> > John Baldwin wrote:
>> >
>> > > On 8/14/19 9:22 AM, Ian Lepore wrote:
>> > > > This all sound
On Wed, 2019-08-14 at 13:59 -0600, Warner Losh wrote:
> On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote:
>
> > On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
> > > On 8/14/19 11:06 AM, Kyle Evans wrote:
> > > > LOCAL_MODULES="" does seem like a sensible default when we're
> > > > not
> >
On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote:
> On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
> > On 8/14/19 11:06 AM, Kyle Evans wrote:
> > > LOCAL_MODULES="" does seem like a sensible default when we're not
> > > building a native kernel.
> >
> > Unfortunately kern.post.mk has no w
On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
> On 8/14/19 11:06 AM, Kyle Evans wrote:
> > LOCAL_MODULES="" does seem like a sensible default when we're not
> > building a native kernel.
>
> Unfortunately kern.post.mk has no way of knowing that as MACHINE_*
> are already set to the TARGET
On 8/14/19 11:04 AM, Ian Lepore wrote:
> On Wed, 2019-08-14 at 19:55 +0200, Niclas Zeising wrote:
> I can't understand what you guys are not-understanding. New machinery
> has been added that says "if some module source code exists in this
> absolute fixed location on the build machine, then whene
On 8/14/19 11:06 AM, Kyle Evans wrote:
> LOCAL_MODULES="" does seem like a sensible default when we're not
> building a native kernel.
Unfortunately kern.post.mk has no way of knowing that as MACHINE_*
are already set to the TARGET_* values by the time this target is
invoked. Also, the 'make tind
On 2019-08-14 11:04, Ian Lepore wrote:
I can't understand what you guys are not-understanding. New machinery
has been added that says "if some module source code exists in this
absolute fixed location on the build machine, then whenever you do any
kernel build for any OS version or any arch, reb
On Wed, 14 Aug 2019 11:04:03 -0700
John Baldwin wrote:
> On 8/14/19 10:23 AM, Emmanuel Vadot wrote:
> > On Wed, 14 Aug 2019 10:13:48 -0700
> > John Baldwin wrote:
> >
> >> On 8/14/19 9:22 AM, Ian Lepore wrote:
> >>> This all sounds vaguely wrong, backwards, to me. A developer who is
> >>> usin
On Wed, Aug 14, 2019 at 1:04 PM Ian Lepore wrote:
>
> On Wed, 2019-08-14 at 19:55 +0200, Niclas Zeising wrote:
> > On 2019-08-14 19:23, Emmanuel Vadot wrote:
> > > On Wed, 14 Aug 2019 10:13:48 -0700
> > > John Baldwin wrote:
> > >
> > > > On 8/14/19 9:22 AM, Ian Lepore wrote:
> > > > > This all s
On Wed, 2019-08-14 at 19:55 +0200, Niclas Zeising wrote:
> On 2019-08-14 19:23, Emmanuel Vadot wrote:
> > On Wed, 14 Aug 2019 10:13:48 -0700
> > John Baldwin wrote:
> >
> > > On 8/14/19 9:22 AM, Ian Lepore wrote:
> > > > This all sounds vaguely wrong, backwards, to me. A developer
> > > > who is
On 8/14/19 10:23 AM, Emmanuel Vadot wrote:
> On Wed, 14 Aug 2019 10:13:48 -0700
> John Baldwin wrote:
>
>> On 8/14/19 9:22 AM, Ian Lepore wrote:
>>> This all sounds vaguely wrong, backwards, to me. A developer who is
>>> using a given module on their build system might want that module to be
>>>
On Wed, 14 Aug 2019 19:55:02 +0200
Niclas Zeising wrote:
> On 2019-08-14 19:23, Emmanuel Vadot wrote:
> > On Wed, 14 Aug 2019 10:13:48 -0700
> > John Baldwin wrote:
> >
> >> On 8/14/19 9:22 AM, Ian Lepore wrote:
> >>> This all sounds vaguely wrong, backwards, to me. A developer who is
> >>> us
On 2019-08-14 19:23, Emmanuel Vadot wrote:
On Wed, 14 Aug 2019 10:13:48 -0700
John Baldwin wrote:
On 8/14/19 9:22 AM, Ian Lepore wrote:
This all sounds vaguely wrong, backwards, to me. A developer who is
using a given module on their build system might want that module to be
rebuilt automati
On Wed, 14 Aug 2019 10:13:48 -0700
John Baldwin wrote:
> On 8/14/19 9:22 AM, Ian Lepore wrote:
> > This all sounds vaguely wrong, backwards, to me. A developer who is
> > using a given module on their build system might want that module to be
> > rebuilt automatically, but only if the build para
CC @current, as I had originally intended.
On 2019-08-14 09:08, John Baldwin wrote:
1) You can set LOCALBASE to a different path either in a kernel config
(via makeoptions) or when invoking buildkernel.
For example, I mount my rpi's sdcard at /mnt on my amd64 laptop and
then cross-build into it
On 8/14/19 9:22 AM, Ian Lepore wrote:
> This all sounds vaguely wrong, backwards, to me. A developer who is
> using a given module on their build system might want that module to be
> rebuilt automatically, but only if the build parameters match those of
> the running build host system.
>
> If my
On Wed, 2019-08-14 at 09:08 -0700, John Baldwin wrote:
> On 8/13/19 3:17 PM, Ian Lepore wrote:
> > On Tue, 2019-08-13 at 14:58 -0700, John Baldwin wrote:
> > > For developers this means even if you are doing testing on a box
> > > that doesn't use DRM, you can install the package so that kernel
> >
On 8/13/19 3:17 PM, Ian Lepore wrote:
> On Tue, 2019-08-13 at 14:58 -0700, John Baldwin wrote:
>> For developers this means even if you are doing testing on a box
>> that doesn't use DRM, you can install the package so that kernel
>> builds will try to compile it and hopefully spot KPI/KBI changes
On 2019-08-14 00:35, Conrad Meyer wrote:
This is super cool, thank you! Is it feasible to integrate other
out-of-tree kmods in a similar way, e.g., nvidia-driver?
It should be possible to expand this to work with other ports that
install kmods. I think the plan is to have drm-current-kmod w
This is super cool, thank you! Is it feasible to integrate other
out-of-tree kmods in a similar way, e.g., nvidia-driver?
On Tue, Aug 13, 2019 at 2:58 PM John Baldwin wrote:
>
> With help from zeising@ in particular, I've just committed a change
> to the drm-current-kmod port that makes it insta
On Tue, 2019-08-13 at 14:58 -0700, John Baldwin wrote:
> For developers this means even if you are doing testing on a box
> that doesn't use DRM, you can install the package so that kernel
> builds will try to compile it and hopefully spot KPI/KBI changes
> before they land in the tree so that the
With help from zeising@ in particular, I've just committed a change
to the drm-current-kmod port that makes it install sources into
/usr/local/sys/modules by default. This will result in some behavior
changes on HEAD (and only head for now):
1) When you build a kernel after installing the updated
39 matches
Mail list logo
