Re: wait(2) and SIGCHLD

2020-09-09 Thread David Holland
On Sat, Aug 15, 2020 at 07:57:26PM -0400, Terry Moore wrote: > >> I would say so, especially since that would mean the child's parent is > >> no longer the process that forked it (which could break other use > >> cases). > > > > That depends on how you implement detaching, but I suppose

Re: fsck updating but not fixing filesystem

2020-09-09 Thread David Holland
On Fri, Aug 28, 2020 at 12:02:09PM -, Christos Zoulas wrote: > David Holland wrote: > > > Sounds like there is an in interesting fuzzing project in there for > > > someone - make a filesystem mage and the repeatedly damage it, then > > > see if fsck can fix it, then if you get a rump

Re: patch for am7930 audio

2020-09-09 Thread Mouse
>>> By the way, I'm not so familiar to sparc. >>> audioamd(4) has many assembly code (though they look very old stuff). >> [...] I see no assembly code in arch/sparc/dev/audioamd* on 5.2 [...] > It's in sparc/sparc/amd7930intr.s. Ah! Personally, I would be inclined to preserve that. It handles

Re: patch for am7930 audio

2020-09-09 Thread Izumi Tsutsui
> > By the way, I'm not so familiar to sparc. > > audioamd(4) has many assembly code (though they look very old stuff). > > For what it's worth...I don't know what "very old" means to you, but I > see no assembly code in arch/sparc/dev/audioamd* on 5.2 (the .c > datestamped 2010, the .h, 2005).

Re: patch for am7930 audio

2020-09-09 Thread Mouse
> By the way, I'm not so familiar to sparc. > audioamd(4) has many assembly code (though they look very old stuff). For what it's worth...I don't know what "very old" means to you, but I see no assembly code in arch/sparc/dev/audioamd* on 5.2 (the .c datestamped 2010, the .h, 2005). /~\ The

patch for am7930 audio

2020-09-09 Thread Tetsuya Isaki
I have improved am7930 family audio drivers to share more code among them: audioamd(4) on sparc, vsaudio(4) on vax, and bba(4). The patch is: http://www.netbsd.org/~isaki/20200904-am7930.diff vsaudio(4) and bba(4) were tested by naru@, tsutsui@. Both worked fine. (thanks!) By the way, I'm not