Re: make quickworld? (like in DragonFly)
On Wed, Aug 11, 2004 at 02:47:14PM +0200, Simon L. Nielsen wrote: On 2004.08.11 00:36:06 +0200, Geert Hendrickx wrote: Hi, is there any way (or could it be implemented) to rebuild only the changes in world and kernel sources after a cvsup? DragonFly BSD features make quickworld and make quickkernel which does exactly that. You can do that already: make buildworld buildkernel -DNOCLEAN I knew that flag, but I wasn't sure it does the exact same thing. Apparently it does, so it is what I was looking for, thanks! GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make quickworld? (like in DragonFly)
On Wed, Aug 11, 2004 at 04:07:40PM +, Sarunas Vancevicius wrote: To not to flood the list, here is why my /etc/make.conf looks like: ( I think full list can be found in /etc/defaults/make.conf or /usr/share/examples/etc/defaults/make.conf) # To avoid building various parts of the base system: #NO_CVS=true# do not build CVS #NO_CXX=true# do not build C++ and friends #NO_BIND= true# do not build BIND #NO_BLUETOOTH= true# do not build Bluetooth related stuff #NO_FORTRAN=true# do not build g77 and related libraries #NO_GDB=true# do not build GDB #NO_I4B=true# do not build isdn4bsd package #NO_IPFILTER= true# do not build IP Filter package #NO_PF= true# do not build PF firewall package #NO_AUTHPF= true# do not build and install authpf (setuid/gid) #NO_KERBEROS= true# do not build and install Kerberos 5 (KTH Heimdal) #NO_LPR=true# do not build lpr and related programs #NO_MAILWRAPPER=true# do not build the mailwrapper(8) MTA selector #NO_OBJC= true# do not build Objective C support #NO_OPENSSH=true# do not build OpenSSH #NO_OPENSSL=true# do not build OpenSSL (implies NO_KERBEROS and # NO_OPENSSH) #NO_SENDMAIL= true# do not build sendmail and related programs #NO_SHAREDOCS= true# do not build the 4.4BSD legacy docs #NO_TCSH= true# do not build and install /bin/csh (which is tcsh) #NO_VINUM= true# do not build Vinum utilities #NO_X= true# do not compile in XWindows support (e.g. doscmd) #NOCRYPT= true# do not build any crypto code #NOGAMES= true# do not build games (games/ subdir) #NOINFO=true# do not make or install info files #NOLIBC_R= true# do not build libc_r (re-entrant version of libc) #NOMAN= true# do not build manual pages #NOPROFILE= true# Avoid compiling profiled libraries #NOSHARE= true# do not go into the share subdir #NO_USB=true Just uncomment stuff you don't want to build. Yeah I know, but it's not my intention to disable building all this stuff, I just wanted to know whether it was possible to not have to rebuild them everytime (esp. when there are no changes in their sources). -DNOCLEAN seems to do the trick. Thanks for the suggestion, GH -- Sarunas Vancevicius ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No DRM kernel support for i830 ?
There is a working i830 DRM driver for Linux in the old dri cvs in the drm subdirectory. DRM is still using the old DRI tree CVS. Try current DRM CVS and see if it will build the i830 driver for BSD. I don't run BSD so I can't check. It might now be too much work to port the Linux one over to BSD in the DRM tree. cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvs/dri co drm --- Alexey Dokuchaev [EMAIL PROTECTED] wrote: Hi there, Judging from /sys/dev/drm/ contents, and listed kernel options in NOTES, there's currently evidence of support for i810/830 chips in FreeBSD, which (I suspect) is the probable reason why DRI is not enabled on my box (FreeBSD 5.2-CURRENT from yesterday, latest X.Org). I also found traces of i810/830 support in FDo CVS (http://freedesktop.org/cgi-bin/viewcvs.cgi/dri/drm/bsd/i830/), getting me to the fact that i8x0 files were removed from the BSD side, since they were not actually ported. (Unfinished? broken? unstable?) Googling also revealed that back in 2002, someone (namely, moto kawasaki [EMAIL PROTECTED]) was compiling FreeBSD's DRM with signs of i830 in it (https://lists.csociety.org/pipermail/freebsd-xfree86/2002-April/000189.html): %%% cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstr ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fform at-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contri b/ipfilter -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/drm/i830_dma.c ../../dev/drm/i830_dma.c: In function `i830_getbuf': ../../dev/drm/i830_dma.c:1506: `current' undeclared (first use in this function) ../../dev/drm/i830_dma.c:1506: (Each undeclared identifier is reported only once ../../dev/drm/i830_dma.c:1506: for each function it appears in.) *** Error Code 1 Stop in /usr/src/sys/compile/KAWASAKI %%% I would be most grateful to anyone that could shine a bit of light on current situation, or at least give authoritative and complete answer on whether I can or cannot use DRM/DRI on FreeBSD with i830 for today. On Eric's page (http://people.freebsd.org/~anholt/dri/) there's a TODO item that says Port the i810 driver. What is current status of this item? Is there anything I can help with? In case there something that can be done to hack it around and make it work, I'd really love to hear how. (Maybe there some untested or broken patches are floating around that one can make use of.) Thanks in advance. Any information/pointers are most welmome. ./danfe --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel = Jon Smirl [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No DRM kernel support for i830 ?
On Wed, 2004-08-11 at 13:01, Charles Sprickman wrote: On Wed, 11 Aug 2004, John Baldwin wrote: The i830 DRM stuff is ported in a branch of DRI, but it's not in DRI head because of a security problem with the code. Just out of curiousity, does this support the original i810 chipset? ie: agp0: Intel 82810E (i810E GMCH) SVGA controller mem 0xff00-0xff07,0xf400-0xf7ff irq 9 at device 1.0 on pci0 No, it doesnt. Actually, the Intel driver going forward currently is the i915 driver, which is going to be in the next X.Org release, is apparently secure, is ported to FreeBSD (untested iirc -- I'm setting up a machine now), and supports i830-i915. There's been a suggestion that i915 could be extended to support i810 as well, which would deal with the security model issues that I suspect are the same on i810 as i830. That would be the hardest but perhaps best option. The alternate route is to just port the i810 driver as-is. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No DRM kernel support for i830 ?
No, it doesnt. Actually, the Intel driver going forward currently is the i915 driver, which is going to be in the next X.Org release, is apparently secure, is ported to FreeBSD (untested iirc -- I'm setting up a machine now), and supports i830-i915. There's been a suggestion that i915 could be extended to support i810 as well, which would deal with the security model issues that I suspect are the same on i810 as i830. That would be the hardest but perhaps best option. The alternate route is to just port the i810 driver as-is. The i915 is ported to FreeBSD but I've hadn't the time or FreeBSD skills to actually get it working :-) (I'd suspect my pci_alloc_consistent port isn't correct, ...) porting the i810 driver probably isn't a huge amount of work but I doubt I'll have any time to do it Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No DRM kernel support for i830 ?
On Wed, Aug 11, 2004 at 12:20:11PM -0400, John Baldwin wrote: On Wednesday 11 August 2004 07:07 am, Alexey Dokuchaev wrote: Hi there, Judging from /sys/dev/drm/ contents, and listed kernel options in NOTES, there's currently evidence of support for i810/830 chips in FreeBSD, which (I suspect) is the probable reason why DRI is not enabled on my box (FreeBSD 5.2-CURRENT from yesterday, latest X.Org). I also found traces of i810/830 support in FDo CVS (http://freedesktop.org/cgi-bin/viewcvs.cgi/dri/drm/bsd/i830/), getting me to the fact that i8x0 files were removed from the BSD side, since they were not actually ported. (Unfinished? broken? unstable?) The i830 DRM stuff is ported in a branch of DRI, but it's not in DRI head because of a security problem with the code. Thanks. That's a good info to start with. May I ask you the details of security problem you've mentioned, or at least some pointer in this direction? Appropriate maillist and/or google reference would be fine, I guess. ./danfe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No DRM kernel support for i830 ?
John Baldwin wrote: On Wednesday 11 August 2004 07:07 am, Alexey Dokuchaev wrote: Hi there, Judging from /sys/dev/drm/ contents, and listed kernel options in NOTES, there's currently evidence of support for i810/830 chips in FreeBSD, which (I suspect) is the probable reason why DRI is not enabled on my box (FreeBSD 5.2-CURRENT from yesterday, latest X.Org). I also found traces of i810/830 support in FDo CVS (http://freedesktop.org/cgi-bin/viewcvs.cgi/dri/drm/bsd/i830/), getting me to the fact that i8x0 files were removed from the BSD side, since they were not actually ported. (Unfinished? broken? unstable?) The i830 DRM stuff is ported in a branch of DRI, but it's not in DRI head because of a security problem with the code. And there were some persistent issues with older hardware that I never resolved to my satisfaction. The new 'i915' code fixes these problems and is generally much cleaner - it should be the focus for intel chipset development from here out. I don't know any reason why it shouldn't be possible to apply the freebsd changes from the branch to this code on the head. Keith ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No DRM kernel support for i830 ?
Alexey Dokuchaev wrote: On Wed, Aug 11, 2004 at 12:20:11PM -0400, John Baldwin wrote: On Wednesday 11 August 2004 07:07 am, Alexey Dokuchaev wrote: Hi there, Judging from /sys/dev/drm/ contents, and listed kernel options in NOTES, there's currently evidence of support for i810/830 chips in FreeBSD, which (I suspect) is the probable reason why DRI is not enabled on my box (FreeBSD 5.2-CURRENT from yesterday, latest X.Org). I also found traces of i810/830 support in FDo CVS (http://freedesktop.org/cgi-bin/viewcvs.cgi/dri/drm/bsd/i830/), getting me to the fact that i8x0 files were removed from the BSD side, since they were not actually ported. (Unfinished? broken? unstable?) The i830 DRM stuff is ported in a branch of DRI, but it's not in DRI head because of a security problem with the code. Thanks. That's a good info to start with. May I ask you the details of security problem you've mentioned, or at least some pointer in this direction? Appropriate maillist and/or google reference would be fine, I guess. In general, don't bother with the i830.o kernel module or driver any longer, they're deprecated in favour of the new, cleaner implementation in the i915 drivers. Look at the changes on the i865-agp branch and pull those into the i915 driver. Keith ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No DRM kernel support for i830 ?
On Wednesday 11 August 2004 04:01 pm, Charles Sprickman wrote: On Wed, 11 Aug 2004, John Baldwin wrote: The i830 DRM stuff is ported in a branch of DRI, but it's not in DRI head because of a security problem with the code. Just out of curiousity, does this support the original i810 chipset? ie: agp0: Intel 82810E (i810E GMCH) SVGA controller mem 0xff00-0xff07,0xf400-0xf7ff irq 9 at device 1.0 on pci0 Not sure. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ALTQ + FreeBSD 4.10
Where can I find the ALTQ package to work with the FreeBSD 4.10 RELEASE? Someone knows any tool to mark the packets in IPTOS field? Thiago ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt 0x80 handling
Hi, giving a look to interrupt 0x80 handling code (i386/i386/exception.s), I've met FAKE_MCOUNT/MEXITCOUNT system. FAKE_MCOUNT in the end calls _mcount (libkern/mcount.c) function which seems to be used for profiling purposes IMHO. It seems (reading comments in sys/gmon.h) that sysctl could be used to manage syscall profiling (kernel profiling?): Somebody can confirm that or I've misunderstood? I would like to know another thing too: why interrupt 0x80 handler is implemented through a trap gate? An interrupt gate could not be more logical? thanks for answers, cheers rookie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt 0x80 handling
:Hi, :giving a look to interrupt 0x80 handling code (i386/i386/exception.s), I've :met FAKE_MCOUNT/MEXITCOUNT system. FAKE_MCOUNT in the end calls _mcount :(libkern/mcount.c) function which seems to be used for profiling purposes :IMHO. It seems (reading comments in sys/gmon.h) that sysctl could be used :to manage syscall profiling (kernel profiling?): Somebody can confirm that :or I've misunderstood? I would like to know another thing too: why interrupt :0x80 handler is implemented through a trap gate? An interrupt gate could :not be more logical? : :thanks for answers, :cheers : :rookie An interrupt gate will disable interrupts on entry (cli equivalent), while a trap gate does not. There is no reason to disable interrupts in a system call so a trap gate is used. -Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
