Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
>
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and i386.
>
> A subsequent patch will move all rel
Angelo writes:
> > > > If that's the case, then it would be good if we can keep speaker(4).
> > > > I have multiple headless systems at home which start to beep under
> > > > certain conditions, to alert me.
Just as an aside, in the mid-90s I hacked FreeBSD's morse(6) to
send the real thing out /
On Fri, Apr 29, 2022 at 06:33:04PM +0200, Mark Kettenis wrote:
> > From: Scott Cheloha
> > Date: Fri, 29 Apr 2022 11:13:19 -0500
> >
> > > On Apr 29, 2022, at 09:33, Angelo wrote:
> > >
> > > Hello
> > >
> > >> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> > >> speaker(4) i
> From: Scott Cheloha
> Date: Fri, 29 Apr 2022 11:13:19 -0500
>
> > On Apr 29, 2022, at 09:33, Angelo wrote:
> >
> > Hello
> >
> >> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> >> speaker(4) is a whimsical thing, but I don't think we should have a
> >> dedicated chiptune i
> On Apr 29, 2022, at 10:40, Jeremie Courreges-Anglas wrote:
>
> On Thu, Apr 28 2022, Scott Cheloha wrote:
>> speaker(4) is a whimsical thing, but I don't think we should have a
>> dedicated chiptune interpreter in the kernel.
>
>> This patch unhooks the driver and the manpage from the build.
> On Apr 29, 2022, at 09:33, Angelo wrote:
>
> Hello
>
>> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
>> speaker(4) is a whimsical thing, but I don't think we should have a
>> dedicated chiptune interpreter in the kernel.
>>
>> This patch unhooks the driver and the manpage f
> On Apr 29, 2022, at 10:06, j...@entropicblur.com wrote:
>
> On 2022-04-29 08:31, Angelo wrote:
>> Hello
>>> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
>>> speaker(4) is a whimsical thing, but I don't think we should have a
>>> dedicated chiptune interpreter in the kernel.
>>
On Thu, Apr 28 2022, Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and i386.
>
> A subsequent patch
On 2022-04-29 08:31, Angelo wrote:
Hello
On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
speaker(4) is a whimsical thing, but I don't think we should have a
dedicated chiptune interpreter in the kernel.
This patch unhooks the driver and the manpage from the build. The
driver is
Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
>
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and i386.
>
> A subsequent patch will move all rel
Hello
On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
>
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and
On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
>
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and i386.
speaker(4) is a whimsical thing, but I don't think we should have a
dedicated chiptune interpreter in the kernel.
This patch unhooks the driver and the manpage from the build. The
driver is built for alpha, amd64, and i386.
A subsequent patch will move all relevant files to the attic and clean
u
13 matches
Mail list logo
