Re: [RFC] Deprecation and removal of the drm2 driver

On Fri, Jun 1, 2018, 07:42 Oliver Pinter wrote: > On Friday, June 1, 2018, Pete Wright wrote: > > > > > > > On 05/31/2018 15:34, Oliver Pinter wrote: > > > >> On Thursday, May 31, 2018, Johannes Lundberg > wrote: > >> > >> On Thu, May 31, 2018 at 4:34 PM Joe Maloney > >>> wrote: > >>> > >>> I

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

> > I wrote up a couple more paragraphs about why I think it happens and > what we'd need to do to import more of that sense over into src. But > it was way longer than it needs to be. We get a lot more man-hours in > ports/ acting as conduits for the "outside patches -> svn" pipeline > because

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

Hello Glen, On Wed, 30 May 2018 15:50:39 +, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked.

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

On Thu, May 31, 2018 at 03:49:46PM -0500 I heard the voice of Mark Linimon, and lo! it spake thus: > > We do slightly better turning over ports PRs -- due to the fact that > we attach a maintainer field to each port. This doesn't completely > solve the problem, but it goes some distance. >From

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

On Wed, May 30, 2018 at 9:50 AM, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most

Re: [RFC] Deprecation and removal of the drm2 driver

On Friday, June 1, 2018, Pete Wright wrote: > > > On 05/31/2018 15:34, Oliver Pinter wrote: > >> On Thursday, May 31, 2018, Johannes Lundberg wrote: >> >> On Thu, May 31, 2018 at 4:34 PM Joe Maloney >>> wrote: >>> >>> I personally wish that more drivers, and firmware were separated from

Re: [RFC] Deprecation and removal of the drm2 driver

On 05/31/2018 15:34, Oliver Pinter wrote: On Thursday, May 31, 2018, Johannes Lundberg wrote: On Thu, May 31, 2018 at 4:34 PM Joe Maloney wrote: I personally wish that more drivers, and firmware were separated from base. I'm not a committer If you are not a committer, how and

Re: [RFC] Deprecation and removal of the drm2 driver

On Thursday, May 31, 2018, Johannes Lundberg wrote: > On Thu, May 31, 2018 at 4:34 PM Joe Maloney > wrote: > > > I personally wish that more drivers, and firmware were separated from > > base. > > > > > I'm not a committer > > If you are not a committer, how and why want to remove drm2 from

Re: ``make buildkernel'' fails when /usr/obj is empty

On 01/06/2018 03:41, Warner Losh wrote: > On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: > >> On 31 May 2018, at 18:04, Benjamin Kaduk wrote: >>> >>> On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: On Thu, 31 May 2018 09:52:22 +0200 Gary Jennejohn wrote:

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

Straying off-topic from the Subject line ... On Thu, May 31, 2018 at 11:34:18AM -0400, Joe Maloney wrote: > Technically since I was using PC-BSD, and was a committer for that > project I had no real dire need to reach out to FreeBSD about the > [wireless driver issue]. I was simply trying to

Re: hwpmc - wither ppro and p4

On Thu, May 31, 2018 at 03:23:56PM -0500, Mark Linimon wrote: > On Thu, May 31, 2018 at 12:58:23PM -0700, Steve Kargl wrote: > > On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > > > > > Based on the i386 discussion I recognize that there's a great deal of > > > sentimental

Re: hwpmc - wither ppro and p4

On Thu, May 31, 2018 at 12:58:23PM -0700, Steve Kargl wrote: > On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > > > Based on the i386 discussion I recognize that there's a great deal of > > sentimental attachment to older hardware. However, there's very few > >

Re: hwpmc - wither ppro and p4

On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > Based on the i386 discussion I recognize that there's a great deal of > sentimental attachment to older hardware. However, there's very few s/sentimental/practical -- Steve ___

Re: ``make buildkernel'' fails when /usr/obj is empty

On Thu, May 31, 2018 at 08:19:20PM +0200, Dimitry Andric wrote: > On 31 May 2018, at 20:11, Warner Losh wrote: > > > > On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: > > On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn

Re: ``make buildkernel'' fails when /usr/obj is empty

On 31 May 2018, at 20:11, Warner Losh wrote: > > On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: > On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > >> On Thu, 31 May 2018 09:52:22 +0200 > >> Gary Jennejohn wrote: ...

Re: ``make buildkernel'' fails when /usr/obj is empty

On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: > On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > >> On Thu, 31 May 2018 09:52:22 +0200 > >> Gary Jennejohn wrote: > >> > >>> There's something totally screwy about

hwpmc - wither ppro and p4

Intel now provides comprehensive tables for all performance counters and the various valid configuration permutations as text .json files. I've converted libpmc to use these and simplified the hwpmc_core to pass the values through. I'd like to remove all the existing Intel tables from the kernel.

Re: [RFC] Deprecation and removal of the drm2 driver

On Thu, May 31, 2018 at 4:34 PM Joe Maloney wrote: > I personally wish that more drivers, and firmware were separated from > base. > > I'm not a committer but as I understand there's not pre-commit integration tests.. If one had that, plus that it would test build kmod ports against the

Re: ``make buildkernel'' fails when /usr/obj is empty

On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: >> On Thu, 31 May 2018 09:52:22 +0200 >> Gary Jennejohn wrote: >> >>> There's something totally screwy about trying to build a kernel when >>> /usr/obj is not populated. >>> >>>

Re: [RFC] Deprecation and removal of the drm2 driver

On Thu, 31 May 2018 18:02:26 +0200, "Ronald Klop" wrote: > On Thu, 31 May 2018 17:34:18 +0200, Joe Maloney > wrote: > > > I personally wish that more drivers, and firmware were separated from > > base. > > > > For example wireless firmware: > > > >

Re: [RFC] Deprecation and removal of the drm2 driver

On 05/31/18 16:21, Rodney W. Grimes wrote: I do remeber for a long time this was a -current only modules, is that still true, or can I load it on 11.0, 11.1 and 11.2Beta3 now? drm-stable-kmod works on 11.2 (including the betas) and later. We can't backport the needed changes to the lkpi to

Re: ``make buildkernel'' fails when /usr/obj is empty

On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > On Thu, 31 May 2018 09:52:22 +0200 > Gary Jennejohn wrote: > > > There's something totally screwy about trying to build a kernel when > > /usr/obj is not populated. > > > > I ran ``make clean'' in /usr/src and then ``make

Fwd: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137

cross-post to -current to get more feedback --- Forwarded message --- From: "Ronald Klop" To: freebsd-...@freebsd.org Cc: Subject: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 Date: Thu, 31 May 2018 17:53:12 +0200 I had a crash on mu

Re: [RFC] Deprecation and removal of the drm2 driver

On 31/05/2018 18:34, Joe Maloney wrote: > I personally wish that more drivers, and firmware were separated from > base. I would agree with you IF FreeBSD had a defined and stable Device Driver Interface. Or Thirdparty Module Interface. Or whatever the name. -- Andriy Gapon

Re: [RFC] Deprecation and removal of the drm2 driver

On Thu, 31 May 2018 17:34:18 +0200, Joe Maloney wrote: I personally wish that more drivers, and firmware were separated from base. For example wireless firmware: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 That was a ticket which I chimed in on about a firmware I needed to

Re: [RFC] Deprecation and removal of the drm2 driver

I personally wish that more drivers, and firmware were separated from base. For example wireless firmware: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 That was a ticket which I chimed in on about a firmware I needed to make my wireless adapter work. I went through numerous efforts

Re: [RFC] Deprecation and removal of the drm2 driver

On Thu, 31 May 2018, Konstantin Belousov wrote: On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: We're not replacing anything. We are moving the older drm1 and drm2 from kernel to ports to make it easier for the majority of the users to load the correct driver without

Re: [RFC] Deprecation and removal of the drm2 driver

> > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA512 > > > > > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > > > "Rodney W. Grimes" schrieb: > > > > > > > -- Start of PGP signed section. > > > > > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > > > > > > On Wed, May

Re: ``make buildkernel'' fails when /usr/obj is empty

> There's something totally screwy about trying to build a kernel when > /usr/obj is not populated. > > I ran ``make clean'' in /usr/src and then ``make buildkernel''. This > fails with > make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel > requires linker ifunc support

Re: evdev + ps/2 dell touchpad weirdness

On Thu, May 31, 2018 at 1:11 PM Hans Petter Selasky wrote: > On 05/31/18 13:39, Johannes Lundberg wrote: > > EV_REL is for pushing events. For evdev_push_rel(), use REL_{axis}. > > Does this work: > https://svnweb.freebsd.org/changeset/base/334422 Perfect. Thanks! > > > --HPS >

Re: evdev + ps/2 dell touchpad weirdness

On 05/31/18 13:39, Johannes Lundberg wrote: EV_REL is for pushing events. For evdev_push_rel(), use REL_{axis}. Does this work: https://svnweb.freebsd.org/changeset/base/334422 --HPS ___ freebsd-current@freebsd.org mailing list

Re: evdev + ps/2 dell touchpad weirdness

On Thu, May 31, 2018 at 9:32 AM Johannes Lundberg wrote: > > > On Thu, May 31, 2018 at 8:45 AM Johannes Lundberg > wrote: > >> Hi >> >> I could swear this was working a couple of months ago but since >> installing new kernel+world a couple of times and revisiting using Weston >> or X with

Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0

On Thu, May 31, 2018 at 10:10:40AM +0300, Andriy Gapon wrote: > On 31/05/2018 05:04, Jonathan T. Looney wrote: > > On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon > > wrote: > > > > > > [ping] > > > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > > >

Re: [RFC] Deprecation and removal of the drm2 driver

On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: > On Wed, May 30, 2018 at 10:57 PM O. Hartmann wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > > "Rodney W. Grimes" schrieb: > > > > > -- Start of PGP signed

Re: evdev + ps/2 dell touchpad weirdness

On Thu, May 31, 2018 at 8:45 AM Johannes Lundberg wrote: > Hi > > I could swear this was working a couple of months ago but since installing > new kernel+world a couple of times and revisiting using Weston or X with > udev+evdev+libinput I can't get all the events. > > Using

Re: ``make buildkernel'' fails when /usr/obj is empty

On Thu, 31 May 2018 09:52:22 +0200 Gary Jennejohn wrote: > There's something totally screwy about trying to build a kernel when > /usr/obj is not populated. > > I ran ``make clean'' in /usr/src and then ``make buildkernel''. This > fails with > make[2]: "/usr/src/sys/conf/kern.pre.mk"

``make buildkernel'' fails when /usr/obj is empty

There's something totally screwy about trying to build a kernel when /usr/obj is not populated. I ran ``make clean'' in /usr/src and then ``make buildkernel''. This fails with make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel requires linker ifunc support This is

evdev + ps/2 dell touchpad weirdness

Hi I could swear this was working a couple of months ago but since installing new kernel+world a couple of times and revisiting using Weston or X with udev+evdev+libinput I can't get all the events. Using libinput-debug-events on my dell laptop touchpad (psm driver with hw.psm.synaptics=1) I get

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

Hi Tested both images in both modes on: Supermicro X9SCL-F E3-1230 CPU Work perfectly Glen Barber wrote: GB> Hi, GB> GB> Could folks please help boot-test the most recent 12.0-CURRENT amd64 GB> memstick images on various hardware? Note, this is not a request to GB> install 12.0-CURRENT,

Re: [RFC] Deprecation and removal of the drm2 driver

On Wed, May 30, 2018 at 10:57 PM O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > "Rodney W. Grimes" schrieb: > > > -- Start of PGP signed section. > > > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > >

Re: [RFC] Deprecation and removal of the drm2 driver

On 05/30/18 23:51, O. Hartmann wrote: Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up in a trap 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does load without crashing the system - but the console is stuck in the clumsy 80x25 mode. So why

Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0

On 31/05/2018 05:04, Jonathan T. Looney wrote: > On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon > wrote: > > > [ping] > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > FreeBSD 12.0-CURRENT amd64 r332472 > > Does this panic ring a bell to anyone?