Date: Mon, 13 Apr 2020 02:14:24 -0700 From: Chris <bsd-lists@BSDforge.com> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD X11 <x11@freebsd.org>, Niclas Zeising <zeising@freebsd.org>, Alexey Dokuchaev <danfe@freebsd.org> Subject: Re: Ars Technica article Message-ID: <8b5ff406206a0c2f67475269a752127d@udns.ultimatedns.net> In-Reply-To: <CANCZdfqfkVGDGssHC%2Bts6df7QeiCsA68CQnjOAAXdH2JsDMTaQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Apr 2020 01:11:30 -0600 Warner Losh imp@bsdimp=2Ecom said > On Sun, Apr 12, 2020, 11:24 PM Alexey Dokuchaev <danfe@freebsd=2Eorg> wrote= : >=20 > > [ setting CC to a more appropriate -x11@ list ] > > > > On Sat, Apr 11, 2020 at 12:43:00AM +0000, Niclas Zeising wrote: =2E=2E=2Ebig snip=2E=2E=2E > in this part of the stack: the drm-kmod maintainer's job shifted so he's > had to resign from that role=2E We have nobody to even update to newer Linu= x > driver versions (though we might have a promising person in the wings)=2E > There's literally nobody that has the time, the hardware, the docs and th= e > expertise to help with this older video hardware (at least as evidence of > it's remaining broken for a long, long time)=2E Until that person shows up, > you will unfortunately be out of luck=2E OK I've bit my tongue as long as I can on this=2E=2E=2E How is importing yet more Linux code into FreeBSD a better thing? Or how is it *fixing* anything regarding FreeBSD=2E For clarity; I don't dislike Linux=2E I just prefer to use (Free)BSD=2E I'm frankly alarmed with the apparen= t volume that Linux code is entering the FreeBSD code base=2E I noticed much of the UEFI bits are also converted Linux bits=2E I suppose for a quick needed stop-gap solution it might be reasonable=2E But it appears that a tremendous amount of time, and effort has gone into all this, and given the previously mentioned lack of man-power=2E It seems unlikely that any of this will be replaced with a FreeBSD equivalent=2E I'm not blowing smoke here=2E I earmarked some time that I wouldn't be taking contracts so that I could invest some time on FreeBSD concerning "nits" I had that I thought could improve things a bit=2E I looked into taking the time to make it nearly/fully POSIX complain= t=2E Browsing the code=2E It was clear I wouldn't stand a chance unless I started at ~9=2Ex where it starts to go sideways in fairly rapid succession=2E So I decided to look elsewhere=2E I've had some nits with the Graphics dept=2E so I thought I'd look to see where I could best spend my efforts=2E Then the new Xorg landed=2E Well that's going a *completely* different direction than it was, and I don't think I want to participate in that new direction=2E I've finally landed on working on bolstering sc/syscons in an effort to provide graphics mode switching and detection to it=2E Sorry if I've usurped this thread=2E But it's really been bothering me, and I think others=2E So I just said it=2E Thank you for your indulgence=2E --Chris Oh! I'm *not* directing this at you Warner=2E Just responding in the thread=2E >=20 > Warner >=20 > =2E/danfe > > > > *) https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D237642 > > _______________________________________________ > > freebsd-x11@freebsd=2Eorg mailing list > > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd=2Eorg" > > > _______________________________________________ > freebsd-x11@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd=2Eorg"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8b5ff406206a0c2f67475269a752127d>