Date: Sun, 24 Apr 2005 11:19:29 -0700 From: Eric Anholt <eta@lclark.edu> To: None <imachine@lazir.toya.net.pl> Cc: freebsd-current@freebsd.org Subject: Re: mgadrm fail in -CURRENT Message-ID: <1114366769.965.0.camel@leguin> In-Reply-To: <20050423160713.GA24432@lazir.toya.net.pl> References: <20050423005715.G16129@it.hackers> <1114212379.955.15.camel@leguin> <20050423184110.O37477@it.hackers> <20050423160713.GA24432@lazir.toya.net.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2005-04-23 at 18:07 +0200, None wrote: > On Sat, Apr 23, 2005 at 06:43:00PM +0400, Nguyen Tam Chinh wrote: > > On Fri, 22 Apr 2005, Eric Anholt wrote: > > > > >On Sat, 2005-04-23 at 01:01 +0400, Nguyen Tam Chinh wrote: > > >>Hello All, > > >>I've just compiled -CURRENT (cvsup some hours ago) and the magdrm seemed > > >>to be fail. > > >>Last week's -CURRENT build was okay. > > > > > >Do you have device drm in your kernel? > > >Did you do a clean build? > > > > > > > Aha, I checked the config/NOTES and noticed that the new line: device drm > > Thank you :) > > > > >There's no real reason to be building the drm into the kernel that I can > > >see, as it's automatically loaded for you by the X Server. > > i might be off here, and dont intend to cause any offtopicness, altho i > was informed perhaphs wrongly, that kernel-builtin drivers are having > some speed improvements compared to loaded modules? I've never seen any measurements showing that that's the case, and would highly doubt there being any measurable effect. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1114366769.965.0.camel>