Date: Sat, 17 Dec 2005 07:45:03 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Melvyn Sopacua <freebsd.stable@melvyn.homeunix.org> Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: Release schedule for 2006 Message-ID: <20051216204503.GR77268@cirb503493.alcatel.com.au> In-Reply-To: <200512162120.45053.freebsd.stable@melvyn.homeunix.org> References: <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <20051216184149.GC58262@thought.org> <20051216194255.GB31497@soaustin.net> <200512162120.45053.freebsd.stable@melvyn.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2005-Dec-16 21:20:44 +0100, Melvyn Sopacua wrote: >Features=0xa7e9f9bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE> >+ Features2=0x180<EST,TM2> > >Q: What are those extra features and are they useful? ;-) This is just printing out the CPU features bitmasks. The difference is that the CPU identification code in 6.x looks at the bitmap returned in %ecx after a cpuid 1. The features were always there, 6.x just prints them out. As for usefulness... EST - Enhanced SpeedStep TM2 - Thermal Monitor 2 >+uhci0: [GIANT-LOCKED] >+uhci1: [GIANT-LOCKED] >+uhci2: [GIANT-LOCKED] > >Q: Again - is this formatting or are these (and the ones below) still under >Giant in 6.x but not in 5.x? No. 6.x is just more verbose. I thought these had all been hidden behind 'verbose' as they are primarily hints to the developers. >-pci0: <serial bus, USB> at device 29.7 (no driver attached) >+ehci0: <Intel 82801DB/DBL/DBM (ICH4) USB 2.0 controller> mem >0xf4fffc00-0xf4ffffff irq 11 at device 29.7 on pci0 >+ehci0: [GIANT-LOCKED] > >Kudos! I'm still trying to get my USB2 to do anything more than probe :-( >-Timecounter "TSC" frequency 1398819442 Hz quality 800 >-Timecounters tick every 10.000 msec >+Timecounter "TSC" frequency 1398819606 Hz quality 800 >+Timecounters tick every 1.000 msec > >Q: This is a big scarey difference :p This isn't a printf bug I presume? Which bit? The TSC is notoriously unstable and a relative change of 1.2e-7 can be ignored. If you look at kern.clockrate, you'll see that hz now defaults to 1000. >-acd0: CDRW <HL-DT-STCD-RW/DVD-ROM GCC-4241N/A100> at ata1-master PIO4 >+acd0: CDRW <HL-DT-STCD-RW/DVD-ROM GCC-4241N/A100> at ata1-master UDMA33 > >That's *very* nice! Again, that's just a change in defaults. Problems were found with DMA to ATAPI devices so the decision was made to default to PIO4 in 5.x. You can set hw.ata.atapi_dma to 1 in 5.x if you want to (see acd(4)). -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051216204503.GR77268>