On 2018-May-20, at 7:35 PM, Mark Millard wrote:
> ci.freebsd.org shows -r333945 built okay (ignoring riscv64) but
> later not ( -r333947 and later for most).
>
> --- all_subdir_usr.bin/top ---
> make[4]: make[4]: don't know how to make top.local.h. Stop
>
> make[4]: stopped in /usr/src/usr.bin/
ci.freebsd.org shows -r333945 built okay (ignoring riscv64) but
later not ( -r333947 and later for most).
--- all_subdir_usr.bin/top ---
make[4]: make[4]: don't know how to make top.local.h. Stop
make[4]: stopped in /usr/src/usr.bin/top
*** [all_subdir_usr.bin/top] Error code 2
> Author: eadler
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
>
>
> Then it wold be better t
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 Fri, May 18, 2018 at 09:14:24PM +
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
> >>>
> >>> ONLY
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
> https://github.com/FreeBSDDesktop/kms-drm/iss
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 Zeisi
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 wrote:
> > >
> > > > I
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 tweaking and updated
firmware modules before we
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 architectures like powerpc?
>
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 freebsd-x11@. Thanks! ]
> >>
> >>
> >> Hi!
> >>
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 any mail to "freebsd-
In message <24cc317e-3083-4e38-8497-aeaaf4f88...@yahoo.com>, Mark
Millard write
s:
> After -r333913 (by mmacy) fixed the builds,
> -r333919 seems to have broken them again
> (in a different way).
>
> On ci.freebsd.org various TARGET_ARCH's (mips, mips64,
> powerpc64, sparc64) are getting things li
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 it? (All parts of Fr
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?
>>
>> I use base packa
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:
> https://lists.freebsd.o
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
_
Updating poudriere jail from r331491 to r333924 fails with:
--- Sema/DelayedDiagnostic.o ---
In file included from
/usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/tools/clang/lib/Sema/DelayedDiagno
stic.cpp:17:
In file included from
/usr/local/poudriere/jails/head-amd64/usr/src/contri
After -r333913 (by mmacy) fixed the builds,
-r333919 seems to have broken them again
(in a different way).
On ci.freebsd.org various TARGET_ARCH's (mips, mips64,
powerpc64, sparc64) are getting things like:
--- all_subdir_lib/libmagic ---
softmagic.pico: In function `msetoffset':
/usr/src/contrib
19 matches
Mail list logo