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

On Mon, 4 Jun 2018 at 22:36, Matthew Macy wrote: > > Implementing a callback in 140 different files for the sake of a handful of > out of tree drivers and people not reading updating is pretty prohibitive. 11 > may be more your cup of tea. This was the in tree wifi drivers.. :-) Dude, we're

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

Implementing a callback in 140 different files for the sake of a handful of out of tree drivers and people not reading updating is pretty prohibitive. 11 may be more your cup of tea. On Mon, Jun 4, 2018 at 22:27 Adrian Chadd wrote: > Hi, > > If there's an API that isn't being used then great,

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

Hi, If there's an API that isn't being used then great, I'll go find it and fix up pieces in my spare time to use it. But the last drive by cut/paste didn't do that; it just changed the code in place. :-) -adrian ___ freebsd-current@freebsd.org

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

On Mon, Jun 4, 2018 at 12:03 PM, Adrian Chadd wrote: > Hi, > > As a driver/framework developer - no, don't do that. > > It's worked mostly great for the video side of things because your > touch points are "the VM system" and "linuxkpi". And they're all in > one big driver pull from Linux. > >

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

Hi, As a driver/framework developer - no, don't do that. It's worked mostly great for the video side of things because your touch points are "the VM system" and "linuxkpi". And they're all in one big driver pull from Linux. For wifi as an example - it has a bunch of userland components, a

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

On Thu, May 31, 2018 at 09:04:25PM -0700, K. Macy wrote: > This is where culling older bug reports comes in. Well, even with doing that, the sheer number really doesn't help the S/N that much. It may make someone a bit neurotic like me feel a bit better, but that's all. > However, when I've

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

On Thu, May 31, 2018 at 10:25:10PM -0500, Matthew D. Fuller wrote: > because the incentives are rigged. A bad outside contribution brought > into ports more often yields "hey, you should have noticed" to the > committer and more opprobrium back to the submitter. I believe you're missing two

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

On Thu, May 31, 2018 at 11:34 PM Oliver Pinter < oliver.pin...@hardenedbsd.org> 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. >>

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: 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: [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: 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: [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: [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: [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: [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: [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: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

On 30 May 2018 at 18:08, Philip Homburg wrote: >>Strange. Can you try an updated test image of mine >>(https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz) Oops - that should have been https://people.freebsd.org/~emaste/mini-image-2018-05-28-amd64.xz But the most recent snapshot images

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

>Strange. Can you try an updated test image of mine >(https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz) That gives a 404. I have the strong suspision that your previous image doesn't get recognized as bootable because the C/H/S values are not filled in.

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 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote:

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

On Wed, May 30, 2018 at 08:29:57AM -0700, Rodney W. Grimes wrote: > > On 25 May 2018 at 04:51, Philip Homburg wrote: > > > > > > I have bad news and some good news. > > > > > > The bad news is that with this image the USB stick doesn't get recognized > > > as > > > a boot device. Same as with

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

> On 25 May 2018 at 04:51, Philip Homburg wrote: > > > > I have bad news and some good news. > > > > The bad news is that with this image the USB stick doesn't get recognized as > > a boot device. Same as with the 11.2-BETA2 images. > > At least it's not a regression. > > > The good news is

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

On 25 May 2018 at 04:51, Philip Homburg wrote: > > I have bad news and some good news. > > The bad news is that with this image the USB stick doesn't get recognized as > a boot device. Same as with the 11.2-BETA2 images. At least it's not a regression. > The good news is that if I completely

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

32b compat is quite different than i386 arch. It makes sense to maintain 32b compat for quite a while. On Wed, May 30, 2018 at 3:33 AM, Thomas Mueller wrote: >> Wow, this blew up quite a lot bigger than I anticipated. I'll try to >> summarize the discussion a bit below and then suggest a way

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

> Wow, this blew up quite a lot bigger than I anticipated. I'll try to > summarize the discussion a bit below and then suggest a way forward. > The primary reasons we want to do this is because there are conflicts between > the new drm drivers in ports, and the drm drivers in base, since they

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

On Tue, 29 May 2018 17:39:57 -0700 (PDT) "Rodney W. Grimes" wrote: >> Let's also remember about our handbooks and those two wiki page: >> * https://wiki.freebsd.org/Graphics >> * https://wiki.freebsd.org/Graphics/FAQ >This one has a bit rot on this claim: > "The i915kms kernel-side

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

[ Charset UTF-8 unsupported, converting... ] > On Tue, 29 May 2018 21:28:49 +0200 > Niclas Zeising wrote: > > >On 05/18/18 19:58, Niclas Zeising wrote: > >> [ Cross posted to freebsd-current@ and freebsd-x11@.? Please respect > >> reply-to and send all replies to freebsd-x11@.? Thanks! ] > >> >

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

On Tue, 29 May 2018 21:28:49 +0200 Niclas Zeising wrote: >On 05/18/18 19:58, Niclas Zeising wrote: >> [ Cross posted to freebsd-current@ and freebsd-x11@.  Please respect >> reply-to and send all replies to freebsd-x11@.  Thanks! ] >> >> [...] >> >> What does the community think?  Is there

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

On 05/18/18 19:58, Niclas Zeising wrote: [ Cross posted to freebsd-current@ and freebsd-x11@.  Please respect reply-to and send all replies to freebsd-x11@.  Thanks! ] Hi! I propose that we remove the old drm2 driver (sys/dev/drm2) from FreeBSD.  I suggest the driver is marked as deprecated

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

>Can you download the image from >https://people.freebsd.org/~emaste/mini-image.amd64.xz, uncompress and >write it to a USB stick and try on this system? This is a >MBR-partitioned dual-mode test image. It's not an installer - it >should just boot to a login prompt - but can be used to test this

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

> On 23 May 2018 at 17:51, Philip Homburg wrote: > > I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and > > FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 > > BIOS version 2.7.0. With both images, the USB stick is not recognized. > > Can

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

On Thu, May 24, 2018 at 2:11 PM Ed Maste wrote: > On 23 May 2018 at 17:51, Philip Homburg wrote: > > I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and > > FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 > > BIOS

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

-- Start of PGP signed section. > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > > >Also as the Moore's law curve flattens expect the life of these > > > > >older, but not so old, machines to live quiet

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

On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > >Also as the Moore's law curve flattens expect the life of these > > > >older, but not so old, machines to live quiet some time. I > > > >believe we are

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

> On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > >Also as the Moore's law curve flattens expect the life of these > > >older, but not so old, machines to live quiet some time. I > > >believe we are talking sandy bridge and earlier? If that is > > >corret Sandy bridge is

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

On 23 May 2018 at 17:51, Philip Homburg wrote: > I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and > FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 > BIOS version 2.7.0. With both images, the USB stick is not recognized. Can you download

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

On 05/24/18 08:16, M - Krasznai András wrote: I tried to set it to drm-stable-kmod as well as to drm-next-kmod, none was working, I got a fatal trap, kernel panic during boot. Did you build from source? Can you show the panic? drm-next-kmod should be loaded by /etc/rc.conf like this, can you

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

: 2018. május 23. 11:49 Címzett: Rodney W. Grimes Másolatot kap: K. Macy; A. Wilcox; FreeBSD Current Tárgy: Re: [RFC] Deprecation and removal of the drm2 driver >Also as the Moore's law curve flattens expect the life of these >older, but not so old, machines to live quiet some time. I >b

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 BIOS version 2.7.0. With both images, the USB stick is not recognized. For reference I tried an image for a random other OS and in that case the USB stick is

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

On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > >Also as the Moore's law curve flattens expect the life of these > >older, but not so old, machines to live quiet some time. I > >believe we are talking sandy bridge and earlier? If that is > >corret Sandy bridge is still a very

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

On 23 May 2018 at 05:48, Philip Homburg wrote: > > Turns out, you can't install FreeBSD using a USB stick image because the > BIOS only support MBR. No idea why MBR support was dropped for the USB images. We haven't "dropped" MBR support, and our amd64 memstick images

Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

On Wed, May 23, 2018 at 12:41 PM, Philip Homburg wrote: > >It's not that hard create a mbr based usb-stick. Far easier than to find a > >CD burner. > > 'Not hard' means > - undocumented. Or at least, if you start with release notes and install > instructions you

Re: UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver)

> On 23 May 2018, at 13:29, sth...@nethelp.no wrote: > > Hijacking a thread here, > >> Turns out, you can't install FreeBSD using a USB stick image because the >> BIOS only support MBR. No idea why MBR support was dropped for the USB >> images. >> >> In the end I had to find a CD burner, and

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

>It's not that hard create a mbr based usb-stick. Far easier than to find a >CD burner. 'Not hard' means - undocumented. Or at least, if you start with release notes and install instructions you won't find it. - Probably only works if you already have a FreeBSD system. And if it is indeed

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

On Wed, May 23, 2018 at 11:48 AM, Philip Homburg wrote: > >Also as the Moore's law curve flattens expect the life of these > >older, but not so old, machines to live quiet some time. I > >believe we are talking sandy bridge and earlier? If that is > >corret Sandy

UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver)

Hijacking a thread here, > Turns out, you can't install FreeBSD using a USB stick image because the > BIOS only support MBR. No idea why MBR support was dropped for the USB images. > > In the end I had to find a CD burner, and after a couple of tries managed to > install from CD. On a somewhat

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

>Also as the Moore's law curve flattens expect the life of these >older, but not so old, machines to live quiet some time. I >believe we are talking sandy bridge and earlier? If that is >corret Sandy bridge is still a very viable system. I noticed this lack of love for older systems recently.

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

On 05/22/18 18:12, Rodney W. Grimes wrote: it makes me giggle that people still think non-amd64 is "legacy". i386 is alive and well - new chips are being fabbed based on the 586 design with pci-e slots; not to mention things like the Talos and AmigaOne for PowerPC. Yes, some how we need to

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

On Tue, May 22, 2018 at 04:32:39PM -0700, K. Macy wrote: > Why are you running i386 on that? > I'm not. Just pointing out that drm2 runs on amd64 as well as i386. Also need to correct the dis-information that drm2 only applies to mid-Haswell and older. In the end, src committers will do what

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

On Tue, May 22, 2018 at 07:50:39AM +0100, Johannes Lundberg wrote: > On Mon, May 21, 2018 at 23:50 Steve Kargl > wrote: > > > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > > > I just ask. > > > > Or why not include drm-next to base svn

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

Why are you running i386 on that? On Tue, May 22, 2018 at 4:26 PM, Steve Kargl wrote: > On Tue, May 22, 2018 at 02:56:55PM -0700, K. Macy wrote: >> > >> > >> > it makes me giggle that people still think non-amd64 is "legacy". >> > >> > i386 is alive and well -

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

On Tue, May 22, 2018 at 02:56:55PM -0700, K. Macy wrote: > > > > > > it makes me giggle that people still think non-amd64 is "legacy". > > > > i386 is alive and well - new chips are being fabbed based on the 586 > > design with pci-e slots; not to mention things like the Talos and > > AmigaOne for

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

> > I am concerned about just shoving it out to ports, as that makes > > it rot even faster. > > > > I am still very concerned that our in base i9xx code is like 4 > > years old and everyone is told to go to kmod-next from ports > > as well. > > > > No, I do not have a solution, but I have not

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

> I am concerned about just shoving it out to ports, as that makes > it rot even faster. > > I am still very concerned that our in base i9xx code is like 4 > years old and everyone is told to go to kmod-next from ports > as well. > > No, I do not have a solution, but I have not tried hard to find

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

> > > > > > it makes me giggle that people still think non-amd64 is "legacy". > > > > i386 is alive and well - new chips are being fabbed based on the 586 > > design with pci-e slots; not to mention things like the Talos and > > AmigaOne for PowerPC. Yes, some how we need to shake off the idea

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

> > > it makes me giggle that people still think non-amd64 is "legacy". > > i386 is alive and well - new chips are being fabbed based on the 586 > design with pci-e slots; not to mention things like the Talos and > AmigaOne for PowerPC. DRM2 doesn't support anything later than mid-Haswell. The

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

> I just ask. > Or why not include drm-next to base svn repo and add some > option to make.conf to swith drm2/dem-next ? Even if it's not being built on amd64 we're still responsible for keeping it building on !amd64 so long as it's in base. This makes changing APIs

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

On 05/22/18 13:47, dpolyg wrote: I have one comment regarding usage of the drm2 on a "legacy" hardware. Excuse me in advance if I misunderstand something. For the last 2-3 years I'm playing with devices such as small form factor PCs from Shuttle:

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

On Tue, May 22, 2018 at 8:50 AM, Johannes Lundberg wrote: > On Mon, May 21, 2018 at 23:50 Steve Kargl edu> > wrote: > > > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > > > I just ask. > > > > Or why not include drm-next

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

On Mon, May 21, 2018 at 23:50 Steve Kargl wrote: > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > I just ask. > > > Or why not include drm-next to base svn repo and add some > > > option to make.conf to swith drm2/dem-next ? > > > > Even

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

On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > I just ask. > > Or why not include drm-next to base svn repo and add some > > option to make.conf to swith drm2/dem-next ? > > Even if it's not being built on amd64 we're still responsible for > keeping it building on !amd64 so long

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

> > I just ask. > Or why not include drm-next to base svn repo and add some > option to make.conf to swith drm2/dem-next ? Even if it's not being built on amd64 we're still responsible for keeping it building on !amd64 so long as it's in base. This makes changing APIs and universe runs more

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

On Mon, 21 May 2018 10:07:28 -0700 Steve Kargl wrote: > Why? "If it isn't broken, why fix it?" > > The conflict affects x86_64-*-freebsd aka amd64. The > conflict does not affect any other architecture. The > Makefile infrastructure can use MACHINE_ARCH to

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

On Mon, May 21, 2018 at 01:16:12PM -0700, K. Macy wrote: > On Mon, May 21, 2018 at 10:07 AM, Steve Kargl > wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 > >> Oliver Pinter

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

On Mon, May 21, 2018 at 10:07 AM, Steve Kargl wrote: > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >> On Sun, 20 May 2018 21:10:28 +0200 >> Oliver Pinter wrote: >> >> > > One of the reasons for the deprecation and

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

On 5/21/18, Oliver Pinter wrote: > On 5/21/18, Steve Kargl wrote: >> On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote: >>> >>> On 05/21/2018 10:07, Steve Kargl wrote: >>> > On Mon, May 21, 2018 at 02:40:50AM +0300,

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

On 5/21/18, Steve Kargl wrote: > On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote: >> >> On 05/21/2018 10:07, Steve Kargl wrote: >> > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >> >> On Sun, 20 May 2018 21:10:28 +0200 >> >> Oliver

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

On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote: > > On 05/21/2018 10:07, Steve Kargl wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 > >> Oliver Pinter wrote: > >> > One of the

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

On Mon, 21 May 2018 10:29:54 -0700 "Pete Wright" said On 05/21/2018 10:07, Steve Kargl wrote: > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >> On Sun, 20 May 2018 21:10:28 +0200 >> Oliver Pinter wrote: >> One of the

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

On 05/21/2018 10:07, Steve Kargl wrote: On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: On Sun, 20 May 2018 21:10:28 +0200 Oliver Pinter wrote: One of the reasons for the deprecation and removal of the drm2 bits is that they prevent us from

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

On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > On Sun, 20 May 2018 21:10:28 +0200 > Oliver Pinter wrote: > > > > One of the reasons for the deprecation and removal of the drm2 bits > > > is that they prevent us from automatically loading the > > >

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

On Sun, 20 May 2018 21:10:28 +0200 Oliver Pinter wrote: > > One of the reasons for the deprecation and removal of the drm2 bits > > is that they prevent us from automatically loading the > > drm-next/stable-kmod kernel modules, since the two collide. > > Regards

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

On Sunday, May 20, 2018, Niclas Zeising wrote: > On 05/20/18 18:40, Steve Kargl wrote: > >> On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: >> >>> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < >>> s...@troutmask.apl.washington.edu> wrote: >>> >>> On

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

On Sun, May 20, 2018 at 06:47:07PM +0200, Niclas Zeising wrote: > On 05/20/18 18:40, Steve Kargl wrote: > > On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > >>> > >>> % more /usr/ports/graphics/drm-next-kmod/Makefile > >>> > >>>

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

On Sun, 20 May 2018 16:32:50 +0100 Johannes Lundberg wrote: > Not in the current port. > I think it should be usable in 4.15 but need some more tweaking and > updated firmware modules before we can update the port. > Active development going on here >

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

On 05/20/18 18:40, Steve Kargl wrote: On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < s...@troutmask.apl.washington.edu> wrote: On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: On Fri, May 18, 2018, 20:00 Niclas

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

On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > > On Fri, May 18, 2018, 20:00 Niclas Zeising

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

On Sun, May 20, 2018 at 3:22 PM, Rozhuk Ivan wrote: > On Fri, 18 May 2018 21:12:26 +0100 > Johannes Lundberg wrote: > > Is Ryzen 2200G integrated graphic supported? > > Not in the current port. I think it should be usable in 4.15 but need some more

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

In message <20180520155229.73447...@kalimero.tijl.coosemans.org>, Tijl Cooseman s writes: > On Fri, 18 May 2018 14:03:32 -0600 Warner Losh wrote: > > So do people use i386 for desktop? And need the latest KMS stuff? > > I use radeonkms on i386. But what about other

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

In message , Jan Beich writes: > Slawa Olhovchenkov writes: > > > On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > > > >> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect > >> reply-to and send all replies to

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

On Fri, 18 May 2018 21:12:26 +0100 Johannes Lundberg wrote: Is Ryzen 2200G integrated graphic supported? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

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

On Fri, 18 May 2018 14:03:32 -0600 Warner Losh wrote: > So do people use i386 for desktop? And need the latest KMS stuff? I use radeonkms on i386. But what about other architectures like powerpc? If it's getting in the way, can't it be turned into a port instead of removing

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

20.05.2018 16:03, Johannes Lundberg пишет: > On Sun, May 20, 2018 at 1:36 PM, Boris Samorodov wrote: > >> 18.05.2018 20:58, Niclas Zeising пишет: >> >>> Is there anyone still using the drm2 driver on 12-CURRENT? If so, what >>> is preventing you from switching to the port? >> >>

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

On Sun, May 20, 2018 at 1:36 PM, Boris Samorodov wrote: > 18.05.2018 20:58, Niclas Zeising пишет: > > > Is there anyone still using the drm2 driver on 12-CURRENT? If so, what > > is preventing you from switching to the port? > > I use base packages and can not use port: >

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

18.05.2018 20:58, Niclas Zeising пишет: > Is there anyone still using the drm2 driver on 12-CURRENT?  If so, what > is preventing you from switching to the port? I use base packages and can not use port: https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069329.html -- WBR, bsam

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

On 18/05/2018 20:58, Niclas Zeising wrote: > [ Cross posted to freebsd-current@ and freebsd-x11@.  Please respect reply-to > and send all replies to freebsd-x11@.  Thanks! ] > > > Hi! > I propose that we remove the old drm2 driver (sys/dev/drm2) from FreeBSD.  I > suggest the driver is marked as

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

On Fri, May 18, 2018 at 04:19:21PM -0400, Daniel Eischen wrote: > I can easily imagine an embedded x86 kiosk type appliance. We need to evaluate the tradeoff of "what we can imagine someone will do with FreeBSD" vs. "what are people using with FreeBSD right now." mcl

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

On Sat, May 19, 2018 at 08:38:20PM +0200, Jan Beich wrote: > Slawa Olhovchenkov writes: > > > On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > > > >> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect > >> reply-to and send all replies to

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

Slawa Olhovchenkov writes: > On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > >> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect >> reply-to and send all replies to freebsd-x11@. Thanks! ] >> >> >> Hi! >> I propose that we remove the old

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

On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect > reply-to and send all replies to freebsd-x11@. Thanks! ] > > > Hi! > I propose that we remove the old drm2 driver (sys/dev/drm2) from > FreeBSD. I suggest

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

On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > > Check the Makefiles > > > > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > ONLY_FOR_ARCHS= amd64 > > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 > > > > Not to ia32 friendly. > > > > So do

  1   2   >