Re: In kernel mixing - audio cloning

> I do get some audible artifacts with this patch It was pointed out to me on IRC that this is not caused by your patch, so, never mind.

Re: History of disklables

On 2016-12-28 20:14, Edgar Fuß wrote: You must be misremembering something. Looks like it. So disklables are a BSD thing, not a DEC thing? Late into this discussion but anyway... DEC did disklabels in Ultrix, which is a different implementation than the disklabels in BSD, as far as I know.

Re: History of disklables

> You must be misremembering something. Looks like it. So disklables are a BSD thing, not a DEC thing?

Re: In kernel mixing - audio cloning

Date: Wed, 28 Dec 2016 14:05:58 +1100 From: Nathanial Sloss Please see ftp://ftp.netbsd.org/pub/NetBSD/misc/nat/audio-clone.diff The audio device is cloned and their is no longer a limitation of one device per process and file descriptors may be shared among

Re: spurious DIAGNOSTIC message "no disk label"

>> [I think] 4.3 did not have on-disk disklabels. > Just checked my copy of the 4.3-Tahoe The 4.3 I used was pre-Tahoe, pre-Lite, pre-Reno, pre-everything. We started with 4.1c, then, successively, 4.2, 4.3, and mtXinu's 4.3+NFS, then SunOS. (This was at a university with the relevant license;

Re: spurious DIAGNOSTIC message "no disk label"

mo...@rodents-montreal.org writes: > 4.3 did not have on-disk disklabels. Partition tables were built into > the drivers; changing partitioning required recompiling the relevant > driver. (I'm reasonably sure it worked that way for the disks we > actually had on our 4.3 machine(s), at least.)

Re: History of disklables

Hi Edgar, 4.3 did not have on-disk disklabels. Really? My first encounter with BSD was ~1983 on a VAX 11/750 which switched between VMS and 4.2BSD (or 4.3, definitely not 4.4) every other day and I think it had two disc packs with different partition layouts. I also remember ws@ (who was

Remove vget from global namespace

With the global vnode cache there is no longer a need for vget() (take the first reference on a vnode) to reside in global namespace. 1) Rename vget() to vcache_vget() and vcache_tryvget() respectively and move the definitions to sys/vnode_impl.h. 2) Vget() increments the v_usecount

Re: In kernel mixing - audio cloning

> The audio device is cloned and their is no longer a limitation of one device > per process and file descriptors may be shared among processes. Awesome! Cloning works, the volume-going-down-with-each-open(2) problem is gone. I do get some audible artifacts with this patch, though, at least for

Re: powerpc FPU emulation fails for single precision arithmetic (Was: kernel panic on ibm4xx-based powerpc box with DDB)

Rin Okuyama wrote: > By the way, I'd also like to fix port-powerpc/51368: > >http://gnats.netbsd.org/51368 > > FPU emulation for ppc gives wrong results for single precision > arithmetic. As described in the PR, I found the fix from FreeBSD: > > >

Re: powerpc FPU emulation fails for single precision arithmetic (Was: kernel panic on ibm4xx-based powerpc box with DDB)

On 2016/12/28 19:31, Simon Burge wrote: How exactly does single precision fail without this fix? I haven't looked, but is there any simple single precision IEEE test suite that shows this? I'm all for the fix BTW :) Cheers, Simon. Without this fix, the calculation results are clearly

powerpc FPU emulation fails for single precision arithmetic (Was: kernel panic on ibm4xx-based powerpc box with DDB)

On 2016/12/28 18:27, Matt Thomas wrote: On Dec 27, 2016, at 11:59 PM, Rin Okuyama wrote: Thank you for your kind explanation. I'm starting to understand. I will read again the reference manual from this point of view. So, could I commit the patch? Go commit it.

Re: kernel panic on ibm4xx-based powerpc box with DDB

> On Dec 27, 2016, at 11:59 PM, Rin Okuyama wrote: > > Thank you for your kind explanation. I'm starting to understand. > I will read again the reference manual from this point of view. > So, could I commit the patch? Go commit it.

Re: kernel panic on ibm4xx-based powerpc box with DDB

On 2016/12/28 16:01, Matt Thomas wrote: On Dec 27, 2016, at 10:49 PM, Rin Okuyama wrote: Thank you very much for your reply. I revised the patch accordingly, and it passed some stress tests on my OPENBLOCKS266. However, sorry for bothering you, but I don't