From owner-freebsd-multimedia@freebsd.org Sun Dec 17 03:03:53 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A500BE9D9DB for ; Sun, 17 Dec 2017 03:03:53 +0000 (UTC) (envelope-from youngluc@gmail.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 701067FB89 for ; Sun, 17 Dec 2017 03:03:53 +0000 (UTC) (envelope-from youngluc@gmail.com) Received: by mail-io0-x243.google.com with SMTP id w127so6470886iow.11 for ; Sat, 16 Dec 2017 19:03:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=reply-to:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=6nVjoDa1scPMMXSf7QwbNEI7tZ9VjkMuXmfqs/uCLCQ=; b=GKhQRRh/4KjIn+4PJMDW3nGwBJBE4WOeLopVnDl21RyfEtNnX+LqPkaFyXYj4iSFJK EniAR3l67bguNiecC2fL+7yGDqJ7EiYYvR6FuMoKBamQXzVMaoa2sMqkaI/Bi4vEO8Sd o/R4gzMYzo6aImdEiscu8hNyhb88tTtM8SS9zpN/tTHf1VkdCj77qlac61YL/MvHft0l lTo55qn1z2aQ4m7U0pHRnQB/ouAeYkP6FQu3wZogFm+zRdKUs0Cl3Wh4m7D2I+A1g4q/ oCSJLGtjt5/hiJcffsoCeQ2u336dLx1N29GAZTaLEKf7xrhwTAXsf1/Nb8Lbt9Of5o9u ez5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=6nVjoDa1scPMMXSf7QwbNEI7tZ9VjkMuXmfqs/uCLCQ=; b=Nnzgt6atUnvTTDvI2gkNplsuF6sAxvIVZWZtBlmSub4xoL84amheD6Gi4e8WSstLCN d3yn2Rz1QVMmihOm5LcYtCG+DfkdZCDYWXrq7pbuP+BBDSar29RKCgdtVWKDhQTZTMlq cg4uv/ibDWB2vCft2nCc0j2TwQPo8YtErgYyQbQXzupwzgp0YnY03GmlYrgwYD3VbLPp yGhOSKPWRCwDf9/PsKm/PhmGy4AvDDfzXoldLP4iYh6pwgkzqbK+dK0kCk4qMt/vePFe i5VROiLufkcZ2qTcNL/OgkjuSnXy/NyaanIG7EGUGHAG0s9and/KSYZPwKY4vwzAx23n 67XQ== X-Gm-Message-State: AKGB3mK/l9YMR8apJilqbaZvogIJc4mxyNkb8H8A8Hy/A/1YmrPCyHUM XtjxyADfARLbDbcZjlrG9kDaFA== X-Google-Smtp-Source: ACJfBosyBGGlhIhBmM4lpasWaG8KWkSTVgGY9d1Zh3deOKpzd5O2ws+vZAs31V3J+mLoOyqf7hn88Q== X-Received: by 10.107.38.206 with SMTP id m197mr17842634iom.189.1513479832255; Sat, 16 Dec 2017 19:03:52 -0800 (PST) Received: from [10.40.8.62] (67-220-9-24.usiwireless.com. [67.220.9.24]) by smtp.gmail.com with ESMTPSA id b80sm5230079ioe.31.2017.12.16.19.03.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 16 Dec 2017 19:03:51 -0800 (PST) Reply-To: youngluc@gmail.com Subject: Re: webcamd-4.12.0.1 segfault when using WinTV-HV-950Q To: Hans Petter Selasky , freebsd-multimedia@freebsd.org References: <63966a1d-1244-4ea0-0bf8-15b485f63cd4@gmail.com> From: Lucas Young Message-ID: Date: Sat, 16 Dec 2017 21:03:45 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 03:03:53 -0000 Hans Petter Selasky wrote on 2017-12-16 10:50: > On 12/16/17 14:10, Lucas Young wrote: >> I am trying to get my WinTV-HV-950Q working on FreeBSD. I am running >> into, apparently, the same problem as described in the following link >> which is from this list about two years ago. >> [Hauppauge WinTV HVR >> 950Q](https://lists.freebsd.org/pipermail/freebsd-multimedia/2015-June/016273.html) >> >> >> This one sounds similar as well. >> [FreeBSD-10.3 and WinTV >> HVR-950Q](https://lists.freebsd.org/pipermail/freebsd-multimedia/2016-December/017525.html) >> >> >> Unfortunately, it does not appear that the solution to either of those >> previous issues was posted to the list so hoping that there is someone >> who is willing to rehash this for me. >> >> In short, webcamd is crashing with a segfault the first time that it >> is run. If it is run again, it usually starts but then consumes 100% >> of one CPU core. I have included the particulars from my system below. >> Note that I have already compiled webcamd from ports with the DEBUG >> turned on. I am not proficient in C or in using gdb so I need some >> help to know what to check next. >> >> # uname -mrs >> FreeBSD 11.1-RELEASE-p4 amd64 >> >> # pkg info -x webcamd >> webcamd-4.12.0.1 >> >> # md5 /boot/modules/dvb-fe-xc5000-1.6.114.fw >> MD5 (/boot/modules/dvb-fe-xc5000-1.6.114.fw) = >> b1ac8f759020523ebaaeff3fdf4789ed >> >> # usbconfig >> ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=SAVE (0mA) >> ugen0.1: <0x1022 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER >> (5.0Gbps) pwr=SAVE (0mA) >> ugen5.1: at usbus5, cfg=0 md=HOST spd=HIGH >> (480Mbps) pwr=SAVE (0mA) >> ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=SAVE (0mA) >> ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH >> (480Mbps) pwr=SAVE (0mA) >> ugen1.1: <0x1022 XHCI root HUB> at usbus1, cfg=0 md=HOST spd=SUPER >> (5.0Gbps) pwr=SAVE (0mA) >> ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH >> (480Mbps) pwr=ON (500mA) >> ugen3.2: at usbus3, >> cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) >> >> # usbconfig -d 0.2 dump_device_desc >> ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH >> (480Mbps) p >> wr=ON (500mA) >> >>    bLength = 0x0012 >>    bDescriptorType = 0x0001 >>    bcdUSB = 0x0200 >>    bDeviceClass = 0x0000  >>    bDeviceSubClass = 0x0000 >>    bDeviceProtocol = 0x0000 >>    bMaxPacketSize0 = 0x0040 >>    idVendor = 0x2040 >>    idProduct = 0x7200 >>    bcdDevice = 0x0005 >>    iManufacturer = 0x0001  >>    iProduct = 0x0002  >>    iSerialNumber = 0x000a  >>    bNumConfigurations = 0x0001 >> >> # cat /boot/loader.conf >> kern.geom.label.disk_ident.enable="0" >> kern.geom.label.gptid.enable="0" >> vfs.zfs.min_auto_ashift=12 >> zfs_load="YES" >> cuse_load="YES" >> >> # sysrc -a >> autofs_enable: YES >> dbus_enable: NO >> dumpdev: AUTO >> hald_enable: NO >> jackd_enable: NO >> mountd_enable: YES >> mountd_flags: -r >> moused_enable: NO >> mythbackend_enable: YES >> nfs_server_enable: YES >> ntpd_enable: YES >> powerd_enable: YES >> rpc_lockd_enable: YES >> rpc_statd_enable: YES >> rpcbind_enable: YES >> sshd_enable: YES >> webcamd_0_flags: -N Hauppauge-WinTV-HVR-950 -S unknown >> webcamd_1_flags: -N Chicony-Electronics-Co--Ltd--HP-Truevision-HD -S >> 0x0001 >> webcamd_enable: YES >> zfs_enable: YES >> >> >> When the host boots I find that the cuse module is loaded, there is a >> coredump in /, and dmesg indicates that it "exited on signal 11" >> during the boot. >> >> # kldstat >> Id Refs Address            Size     Name >>   1   17 0xffffffff80200000 1f67a88  kernel >>   2    1 0xffffffff82169000 316708   zfs.ko >>   3    2 0xffffffff82480000 cb78     opensolaris.ko >>   4    1 0xffffffff8248d000 e690     cuse.ko >>   5    1 0xffffffff82a31000 10913    snd_uaudio.ko >> >> # dmesg >> ... >> uaudio0 on uhub3 >> uaudio0: on usbus0 >> uaudio0: No playback. >> uaudio0: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. >> uaudio0: No MIDI sequencer. >> pcm2: on uaudio0 >> uaudio0: No HID volume keys found. >> pid 99972 (webcamd), uid 0: exited on signal 11 (core dumped) >> ... >> >> # gdb $(which webcamd) /webcamd.core >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and >> you are >> welcome to change it and/or distribute copies of it under certain >> conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB.  Type "show warranty" for >> details. >> This GDB was configured as "amd64-marcel-freebsd"... >> Core was generated by '/usr/local/sbin/webcamd -i 0 -d ugen0.2 -B -U >> webcamd -G webcamd'. >> Program terminated with signal 11, Segmentation fault. >> Reading symbols from /usr/local/lib/libhal.so...done. >> Loaded symbols for /usr/local/lib/libhal.so >> Reading symbols from /usr/local/lib/libdbus-1.so...done. >> Loaded symbols for /usr/local/lib/libdbus-1.so >> Reading symbols from /usr/lib/libusb.so.3...done. >> Loaded symbols for /usr/lib/libusb.so.3 >> Reading symbols from /lib/libthr.so.3...done. >> Loaded symbols for /lib/libthr.so.3 >> Reading symbols from /lib/libutil.so.9...done. >> Loaded symbols for /lib/libutil.so.9 >> Reading symbols from /usr/lib/libcuse.so.1...done. >> Loaded symbols for /usr/lib/libcuse.so.1 >> Reading symbols from /lib/libc.so.7...done. >> Loaded symbols for /lib/libc.so.7 >> Reading symbols from /usr/lib/libexecinfo.so.1...done. >> Loaded symbols for /usr/lib/libexecinfo.so.1 >> Reading symbols from /lib/libelf.so.2...done. >> Loaded symbols for /lib/libelf.so.2 >> Reading symbols from /lib/libgcc_s.so.1...done. >> Loaded symbols for /lib/libgcc_s.so.1 >> Reading symbols from /libexec/ld-elf.so.1...done. >> Loaded symbols for /libexec/ld-elf.so.1 >> #0  0x0000000000414e32 in timer_exec (arg=0x0) at >> kernel/linux_timer.c:142 >> 142                                     TAILQ_REMOVE(&timer_head, t, >> entry); >> (gdb) bt >> #0  0x0000000000414e32 in timer_exec (arg=0x0) at >> kernel/linux_timer.c:142 >> #1  0x00000008014c7bc5 in pthread_create () from /lib/libthr.so.3 >> #2  0x0000000000000000 in ?? () >> Current language:  auto; currently minimal >> (gdb) p &timer_head >> $1 = (struct timer_head *) 0xccee78 >> (gdb) p t >> $2 = (struct timer_list *) 0x802843130 >> >> >> Can someone point me in the direction of what to check next? > > Hi, > > I think the TAILQ_INIT() was called too late. Can you try this patch > inside webcamd sources after "make extract patch" ? > >> Index: kernel/linux_timer.c >> =================================================================== >> --- kernel/linux_timer.c    (revision 4030) >> +++ kernel/linux_timer.c    (working copy) >> @@ -27,7 +27,7 @@ >> >>  TAILQ_HEAD(timer_head, timer_list); >> >> -static struct timer_head timer_head; >> +static struct timer_head timer_head = >> TAILQ_HEAD_INITIALIZER(timer_head); >>  static pthread_t timer_thread; >>  static volatile int timer_thread_started; >>  static int timer_needed; >> @@ -206,8 +206,6 @@ >>  static int >>  timer_init(void) >>  { >> -    TAILQ_INIT(&timer_head); >> - >>      get_jiffies_64(); >> >>      if (pthread_create(&timer_thread, NULL, timer_exec, NULL)) { > > --HPS Hello Hans, Thank you for your prompt reply and for sending the patch. The problem persists even after the patch is applied, however. In case it helps, here is the output when running from the command line. # /usr/local/sbin/webcamd -i 0 -d ugen0.2 -U webcamd -G webcamd -m xc5000.debug=1 virtual DVB server adapter driver, version 1.0-hps, (c) 2011 Hans Petter Selasky Linux video capture interface: v2.00 IR NEC protocol handler initialized IR RC5(x/sz) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR SANYO protocol handler initialized IR LIRC bridge handler initialized IR XMP protocol handler initialized b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully USB Video Class driver (1.1.1) cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1 pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner pvrusb2: Debug mask is 31 (0x1f) USBVision USB Video Device Driver for Linux : 0.9.11 Attached to ugen0.2[0] au8522 128-0047: creating new instance au8522_decoder creating new instance... xc5000: xc5000_attach(128-0061) xc5000 128-0061: creating new instance xc5000: Successfully identified at address 0x61 xc5000: Firmware has not been loaded previously au8522 128-0047: attaching existing instance xc5000: xc5000_attach(128-0061) xc5000 128-0061: attaching existing instance xc5000: Successfully identified at address 0x61 xc5000: Firmware has not been loaded previously DBG: : dvb_register_frontend: INFO: : DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)... DBG: : dvb_frontend_clear_cache: Clearing cache for delivery system 11 INFO: rc0: au0828 IR (Hauppauge HVR950Q) as webcamd INFO: rc0: lirc_dev: driver ir-lirc-codec (au0828-input) registered at minor = 0 Registered IR keymap rc-hauppauge xc5000: xc5000_sleep() Creating /dev/video1 xc5000: xc5000_sleep() Creating /dev/video2 Creating /dev/dvb/adapter0/demux0 Creating /dev/dvb/adapter0/dvr0 DBG: : dvb_frontend_open: DBG: : dvb_frontend_release: Creating /dev/dvb/adapter0/frontend0 DBG: rc0: lirc_dev (ir-lirc-codec (au0828-input)[0]): open called Creating /dev/lirc0 Creating /dev/input/event0 Segmentation fault Here is the info from gdb from the above command (after the patch): # gdb $(which webcamd) ./webcamd.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by '/usr/local/sbin/webcamd -i 0 -d ugen0.2 -U webcamd -G webcamd -m xc5000.debug=1'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libhal.so.1...done. Loaded symbols for /usr/local/lib/libhal.so.1 Reading symbols from /usr/local/lib/libdbus-1.so.3...done. Loaded symbols for /usr/local/lib/libdbus-1.so.3 Reading symbols from /usr/lib/libusb.so.3...done. Loaded symbols for /usr/lib/libusb.so.3 Reading symbols from /lib/libthr.so.3...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libutil.so.9...done. Loaded symbols for /lib/libutil.so.9 Reading symbols from /usr/lib/libcuse.so.1...done. Loaded symbols for /usr/lib/libcuse.so.1 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/libexecinfo.so.1...done. Loaded symbols for /usr/lib/libexecinfo.so.1 Reading symbols from /lib/libelf.so.2...done. Loaded symbols for /lib/libelf.so.2 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 142 TAILQ_REMOVE(&timer_head, t, entry); (gdb) bt #0 0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 #1 0x00000008014cfbc5 in pthread_create () from /lib/libthr.so.3 #2 0x0000000000000000 in ?? () Current language: auto; currently minimal (gdb) p &timer_head $1 = (struct timer_head *) 0xc32bf8 (gdb) p t $2 = (struct timer_list *) 0x802843130 From owner-freebsd-multimedia@freebsd.org Sun Dec 17 09:42:59 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A4A1E846A6 for ; Sun, 17 Dec 2017 09:42:59 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B7646A831 for ; Sun, 17 Dec 2017 09:42:59 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 82E262601A5; Sun, 17 Dec 2017 10:42:56 +0100 (CET) Subject: Re: webcamd-4.12.0.1 segfault when using WinTV-HV-950Q To: youngluc@gmail.com, freebsd-multimedia@freebsd.org References: <63966a1d-1244-4ea0-0bf8-15b485f63cd4@gmail.com> From: Hans Petter Selasky Message-ID: Date: Sun, 17 Dec 2017 10:40:09 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 09:42:59 -0000 On 12/17/17 04:03, Lucas Young wrote: > #0  0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 > 142                                     TAILQ_REMOVE(&timer_head, t, > entry); > (gdb) bt > #0  0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 > #1  0x00000008014cfbc5 in pthread_create () from /lib/libthr.so.3 > #2  0x0000000000000000 in ?? () > Current language:  auto; currently minimal > (gdb) p &timer_head > $1 = (struct timer_head *) 0xc32bf8 > (gdb) p t > $2 = (struct timer_list *) 0x802843130 Instead of dumping &timer_head, can you dump "timer_head" and the tree of elements that follow? p timer_head p *t --HPS From owner-freebsd-multimedia@freebsd.org Sun Dec 17 13:33:38 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D681E8A003 for ; Sun, 17 Dec 2017 13:33:38 +0000 (UTC) (envelope-from youngluc@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 959A370C12 for ; Sun, 17 Dec 2017 13:33:37 +0000 (UTC) (envelope-from youngluc@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id b199so24914674wme.1 for ; Sun, 17 Dec 2017 05:33:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ly05Kd8DXs4jrG3ZF5hDkUFKVv2cQMOLa10v/XQqfQ4=; b=GfKqUlD72WnyEtu8+BDkvzJFNx9ykf6RVeBKhVM/DYNNFuSAK1DYzQsI9Yx8XtZsKd AGhh3rNZWLERx+EGlxGW8vqVlqbKZvicJeruGOiPE8oqovAmhuQypgSJrH8oRm6fSj91 5VDptQR9+HoMMKGw6Opx7qdEMCYuATcJxbOp1Je5OKBfbWCGcuKU4oULIJ85ElpyKnY7 bob6+eW7xB+r1QqQLucex64y8yr9sdYGCoCRUC7GUC7s9tjJC8Ju6k4rsd09IxeqLKa1 Q3zmm/iCacGvGC7+v2UjZT2oQh6+g7goJjB5iyfz1gmeI2ky5UmMsgFF0CJt/yCBAWGV kBHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ly05Kd8DXs4jrG3ZF5hDkUFKVv2cQMOLa10v/XQqfQ4=; b=iwL4kD4yqPpGO9WlK+CaFseykTaUWyQLq/lK51pVWoi/oQ1fwN4TVuwMvETu8Qn31j oy9MMIHuTxPtPlXSq7iraO/K0dgqJpE3QZrf2obG/SHRBhv9lLs4GnrpOpbV+oityuUh jluDFhmQ2+SQ++JW0W+QuvXNktcsgqBi+0mK/u4qz9T5TMfDnsPbDkW08Rxrys9x0/EI aV+HawpzZpP2q24qFX5HaAOV2ZU25+QSIum3/tF8ykY/Ek2E0UCz7BdPl9Hsvwv2n2NV Nyh9YGsO1AwWhIvDR+A020A+24gnvhsW/xdWHxXVhfy3kK/5IR9/xJqpBJinRKHoV6B8 SQzA== X-Gm-Message-State: AKGB3mIYwc6IPZB1nvauh+9tokgfUIygSlQlU/1UZ9+qBTehkAz2gS/L mXkIOOPj+050nqg9akkHpdCAAo2RGzLsSFuwNaeMeA== X-Google-Smtp-Source: ACJfBotH+6Z7YGh/5DV12kKz/BLVJ00a6xShV63r/ECeyijX3ppHPUHO+xldhtHqon2VotkrbhYzlLtzkoRyGB0nf2M= X-Received: by 10.28.236.28 with SMTP id k28mr9370487wmh.120.1513517615749; Sun, 17 Dec 2017 05:33:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.32.146 with HTTP; Sun, 17 Dec 2017 05:33:35 -0800 (PST) In-Reply-To: References: <63966a1d-1244-4ea0-0bf8-15b485f63cd4@gmail.com> From: Lucas Young Date: Sun, 17 Dec 2017 07:33:35 -0600 Message-ID: Subject: Re: webcamd-4.12.0.1 segfault when using WinTV-HV-950Q To: Hans Petter Selasky Cc: freebsd-multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 13:33:38 -0000 On Sun, Dec 17, 2017 at 3:40 AM, Hans Petter Selasky wrote: > On 12/17/17 04:03, Lucas Young wrote: >> >> #0 0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 >> 142 TAILQ_REMOVE(&timer_head, t, >> entry); >> (gdb) bt >> #0 0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 >> #1 0x00000008014cfbc5 in pthread_create () from /lib/libthr.so.3 >> #2 0x0000000000000000 in ?? () >> Current language: auto; currently minimal >> (gdb) p &timer_head >> $1 = (struct timer_head *) 0xc32bf8 >> (gdb) p t >> $2 = (struct timer_list *) 0x802843130 > > > Instead of dumping &timer_head, can you dump "timer_head" and the tree of > elements that follow? > > p timer_head > > p *t > > --HPS I sure can. Here is the output: #0 0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 142 TAILQ_REMOVE(&timer_head, t, entry); (gdb) set print pretty on Current language: auto; currently minimal (gdb) bt #0 0x0000000000415262 in timer_exec (arg=0x0) at kernel/linux_timer.c:142 #1 0x00000008014cfbc5 in pthread_create () from /lib/libthr.so.3 #2 0x0000000000000000 in ?? () (gdb) p &timer_head $1 = (struct timer_head *) 0xc32bf8 (gdb) p timer_head $2 = { tqh_first = 0x802843078, tqh_last = 0x802843130 } (gdb) p t $3 = (struct timer_list *) 0x802843130 (gdb) p *t $4 = { entry = { tqe_next = 0x802843130, tqe_prev = 0x0 }, function = 0x413260 , expires = 4494, data = 34401956120 } From owner-freebsd-multimedia@freebsd.org Mon Dec 18 03:01:31 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB70BE9ED0A for ; Mon, 18 Dec 2017 03:01:31 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D989067B1B for ; Mon, 18 Dec 2017 03:01:31 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mailman.ysv.freebsd.org (Postfix) id D8BE5E9ED09; Mon, 18 Dec 2017 03:01:31 +0000 (UTC) Delivered-To: multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8576E9ED08 for ; Mon, 18 Dec 2017 03:01:31 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C202967B19; Mon, 18 Dec 2017 03:01:31 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 024561204; Sun, 17 Dec 2017 21:01:30 -0600 (CST) Date: Sun, 17 Dec 2017 21:01:28 -0600 From: Mark Linimon To: multimedia@FreeBSD.org Cc: linimon@FreeBSD.org Subject: [linimon@FreeBSD.org: svn commit: r456580 - head/multimedia/avidemux] Message-ID: <20171218030128.GD21616@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 03:01:32 -0000 FYI ----- Forwarded message from Mark Linimon ----- Date: Mon, 18 Dec 2017 03:00:41 +0000 (UTC) From: Mark Linimon To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r456580 - head/multimedia/avidemux Author: linimon Date: Mon Dec 18 03:00:41 2017 New Revision: 456580 URL: https://svnweb.freebsd.org/changeset/ports/456580 Log: Mark broken on aarch64. It looks like this Makefile could use some modernizing. Approved by: portmgr (tier-2 blanket) Modified: head/multimedia/avidemux/Makefile.common Modified: head/multimedia/avidemux/Makefile.common ============================================================================== --- head/multimedia/avidemux/Makefile.common Mon Dec 18 02:41:24 2017 (r456579) +++ head/multimedia/avidemux/Makefile.common Mon Dec 18 03:00:41 2017 (r456580) @@ -71,7 +71,7 @@ PLIST_SUB+= NLS="@comment " QT_NLS="@comment " # for libexecinfo: (so that __builtin_frame_address() finds the top # of the stack) -.if ${ARCH} == "amd64" +.if ${ARCH} == amd64 CFLAGS+= -fno-omit-frame-pointer #MAKE_ENV+= ARCH=x86_64 #CONFIGURE_ENV+= ARCH=x86_64 @@ -271,8 +271,10 @@ LDFLAGS+= -lc++ USE_GCC= yes #.endif -.if ${ARCH} == "ia64" || ${ARCH} == "powerpc" || ${ARCH} == "sparc64" -BROKEN= Does not compile on ia64, powerpc, or sparc64 +.if ${ARCH} == aarch64 +BROKEN= cmake/admDetermineSystem.cmake:78: CPU not supported +.elif ${ARCH} == powerpc || ${ARCH} == sparc64 +BROKEN= Does not compile on powerpc or sparc64 .endif post-patch: ----- End forwarded message ----- From owner-freebsd-multimedia@freebsd.org Mon Dec 18 12:32:37 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C748CE85FC8 for ; Mon, 18 Dec 2017 12:32:37 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B2688784E3 for ; Mon, 18 Dec 2017 12:32:37 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id AED23E85FC7; Mon, 18 Dec 2017 12:32:37 +0000 (UTC) Delivered-To: multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE7E7E85FC6 for ; Mon, 18 Dec 2017 12:32:37 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F6EF784E2 for ; Mon, 18 Dec 2017 12:32:37 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id vBICWb5K059950 for ; Mon, 18 Dec 2017 12:32:37 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id vBICWb7s059944; Mon, 18 Dec 2017 12:32:37 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201712181232.vBICWb7s059944@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Mon, 18 Dec 2017 12:32:37 +0000 From: portscout@FreeBSD.org To: multimedia@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 12:32:37 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/multimedia@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ audio/faad | 2.8.6 | 2.8.8 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-multimedia@freebsd.org Mon Dec 18 15:16:47 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C641DE9266C for ; Mon, 18 Dec 2017 15:16:47 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A6B17F029 for ; Mon, 18 Dec 2017 15:16:47 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Mon, 18 Dec 2017 16:16:14 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1513610203; bh=5jCr24u3x5i97mKO+yzJfwuCXcwd8V/DJzfjwD9RPwo=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=3YhkxRoKilyBBGpUmWQ3aE80KtIFnKV2v1Cc6SvUMnfATwgxy8q9sqbhbC4WW6+eK KbwICl1x5/DagaR0vTviMWKHUYsolvuuKuEmoTAfLoRsJLWn8vIuLVAM2mfovzA2kV EIdjWBoch6LO9+7cmMJCBQJ5OEZjMY2oMzrIU6mXMvcVrzQXudTyUMMQQUKDLQO7U5 ZmfBqFBVYZj3a1NS2GuLcqzAwUUqYoFdiHmUFa/hEVny7vyNadDmAAaKLlbFvdZ2zT 1PMqyfk93hlLfXLEs8jpL1Rxm/id1wiDTSlwxPlQM6wQT2Ok8NPoUPruzejMogYCeE kYi2lIlOD8JSA== Message-ID: <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> From: Alexander Leidinger To: blubee blubeeme Cc: freebsd-multimedia@freebsd.org Subject: Re: FreeBSD amd64 GENERIC kernel References: <4c3ae20e-b6dd-d5db-0b93-2e1225daa658@selasky.org> <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_GgH9QUiP51JY2JR_BmNv504"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 15:16:47 -0000 This message is in MIME format and has been PGP signed. --=_GgH9QUiP51JY2JR_BmNv504 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting blubee blubeeme (from Sat, 16 Dec 2017=20=20 21:49:08=20+0800): > On Sat, Dec 16, 2017 at 9:33 PM, Alexander Leidinger < > Alexander@leidinger.net> wrote: > >> Quoting blubee blubeeme (from Sat, 16 Dec 2017 >> 09:39:04 +0800): >>> The whole point of implementing 4Front oss and not a FreeBSD for is to >>> K.I.S.S. >>> Here's why >>> 1)OSS v4 soundcard.h and code already hdandles ALL legacy applications = w/o >>> needing to implement special kernel kludges >>> >> >> You are mixing API (soundcard.h) with implementation (FreeBSD kernel sou= nd >> code) and ways to change its behavior (sysctl). I just had a look at our soundcard.h and their soundcard.h. Yes there are differences, but this is expected as it is not a copy=20=20 but=20another implementation of the same API. I had a look (well... more a glance) at the IOCTLs and other stuff (=3D=20= =20 the=20API). Most of them are the same. There are minor differences which=20= =20 most=20probably mean we are implementing the OSSv4 API in v4.0, while=20=20 4Front=20has moved on to OSSv4.2. Those few differences, can probably be=20= =20 implemented=20in FreeBSD by someone who is interested easily. The main=20= =20 point=20here is, are those differences that important? The parts you=20=20 complain=20about are not related to those differences of the API. [a lot of technical details and questions from me cut... you didn't=20=20 respond=20to any of the serious questions I've put there] > These are some blog posts from mid to late 2000; Please read it and > understand what's he's trying to express; Then look at the audio programs > and see how they continue to make the same exact mistakes in 2017 going o= n > 2018. > > https://web.archive.org/web/20111001142728/http://4front-tech.com/hannubl= og/?page_id=3D34 I've read this article. It talks about userland issues in=20=20 applications,=20not about issues we have in our kernel code. > Where are these audio app developers who should be chiming in? The few > applications that I've ported: audio/amsynth and audio/yoshimi > one has OSS support already, the other one I am developing. > Working on implementing the OSS support I am running into issues Feel free to open a new thread about your issues in multimedia@, maybe=20= =20 someone=20can point you in the right direction. > Instead of listening u guys keep repeating FreeBSD audio is Great.... I don't tell it is great. I tell you haven't managed yet to point out=20=20 where=20it is bad. Concrete examples instead of just telling it is bad.=20= =20 My=20questions you skipped were targeted to find out what is not OK. So=20= =20 far=20you haven't delivered an answer. I'm eager to see answers to them.=20= =20 So=20far I've seen you (at least to my understanding) mixing up=20=20 "implementation=20of an API" (=3D kernel code) and "API" (soundcard.h),=20= =20 and=20in the API mixing up "there are differences which don't matter for=20= =20 the=20API" (but matter for the ABI, but this is relevant for=20=20 compatibility=20between FreeBSD X and FreeBSD Y) with "this is not OSSv4=20= =20 API".=20You complained about optional parts in the sound system which=20=20 are=20disabled by default (sysctl) in a way I was understanding as that=20= =20 you=20complain that they are there at all (while the presence of the=20=20 possibility=20not being related or affecting the ABI nor can be=20=20 attributed=20to misbehavior). I'm sure we will be open "to do something", but only if there are=20=20 specific=20areas pointed out and validated to be bad, instead of just=20=20 telling=20"all is bad" mixing up things while talking about it and not=20= =20 being=20specific at all so that other people can validate that the parts=20= =20 you=20complain about do not work as intended. And if you reference to "linuxims" refers to the fact that we have=20=20 jack=20and portaudio and whatever in the ports collection... well, this=20= =20 is=20not related to the FreeBSD sound system at all, those are 3rd party=20= =20 applications.=20We will not restrict which program someone wants to use=20= =20 on=20FreeBSD, and if those using those programs are happy with it, it is=20= =20 not=20related to the FreeBSD project at all. Do I agree that programs=20=20 would=20be better of to use the FreeBSD native API instead of of some=20=20 intermediate=20layer? In a lot of cases surely yes. Is this a=20=20 responsibility=20of the FreeBSD project? Not at all. We are an open=20=20 source=20project which relies on contributions to get "linux-programs"=20= =20 up=20and running (=3D ported) to FreeBSD. If you find such a program which= =20=20 doesn't=20behave very good on FreeBSD, you can help fixing it (by=20=20 sending=20patches which make it work better on FreeBSD to the developers=20= =20 of=20the application in question), or find people in the FreeBSD=20=20 community=20which may be interested to help fixing those programs.=20=20 Removing=20those middle-layers from the ports collection is surely out=20= =20 of=20question as long as there is a program which depends upon one of=20=20 them. In=20short: if you want that people agree that something is not good,=20=20 you=20need to come with specific items and detailed instructions how to=20= =20 repeat=20what you see, so that it can be validated / repeated by someone=20= =20 else. Bye, Alexander. --=20 http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_GgH9QUiP51JY2JR_BmNv504 Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaN9u+AAoJEKrxQhqFIICEDtwP+QGA/OlYcRGFuhXxbZT85xS8 v0GY6dmzuR+e6PU07nbl+QafQ87FLUj0IAXhr/ucd4huSvZ+njJYUDzZ5YlZxhoI 5LSVQZi1qLkfTDegubm+T9eJzh+eGsDaPJ3g64/140LTGcnmudpAQ3r9sv9nHhaS p4pKR5R+L80aBHdwOciA9iGllf8zn6HMOfTyq4CjsPvJ6bkW1BV2XW2XEzqDsHIm W7SZ/0jO1jUczCRsMwltxpQ6TxOli9LoSUNZzQrwCqJJ9okYW+1hAEYs6991jvC2 t8dMTzCo6KfOc1uSHC/PVpapwDmC7gmCjw2ZYoiwr5yCBku/ycsD0YtWAHgv4pAn LdQNQ46RPxf7etSFBI1RaF+NwvdCufIrfLI+VVYu9EHH1raMQQpM9wn9bjDFb48F b4+y/8/hQzFUWz+mdO6o5cYZVnKV+oF6wx18fDxCOl8jY8DPl7BpYEPyedZakTdl VTE9MXRecoqgSH+i+PnknMoUrxelvJYvJvqfYC2bXB2DIIlg0TNiNoEYoLqv6Yh8 8G/owoVBauitmP6e+l3nve/F44diF2/OtGC4RQOxbzpFA8/5Lfo6Nak7es6yo/jU mtbPxwD427CqPzzucshN/7gRSOAMqJejoxe21l2XMW/4GzZ7QJfw2oIzlhnkFNzd Drmi77kdCBiu87uHCTvA =O6Fg -----END PGP SIGNATURE----- --=_GgH9QUiP51JY2JR_BmNv504-- From owner-freebsd-multimedia@freebsd.org Mon Dec 18 16:08:43 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97484E967A0 for ; Mon, 18 Dec 2017 16:08:43 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C14A12EE for ; Mon, 18 Dec 2017 16:08:43 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id l10so10316323ioc.3 for ; Mon, 18 Dec 2017 08:08:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eWSopTbk4UhjVfYw6Pb2U5XKiiaMhsL5HW2k761geA8=; b=YZCNA3EhhnsUO4emIFxz16LgifWiU4QkoQsOjWb8cqLqHWEwZLDY9yIfFuUJ+Lg7kh NcH8suun/QNgO3/kyGvvEzBcbPAdHm2dM+8nHbkjhnw8HXkrFaMBxajuRa29WPBbx3uW 5Ehm2uL2hRYKLgQyRUJTufDal1XZBA4ZfJkVkdsUkVwG8Jle6Sapvis6YKTMBlDhQ375 1MPE0WxFhdG7b0TT09juyD8hfBRlxGuUdd9Hd+zo1vhOe4wiqRcOFL1NkorHmba3g1E0 +1g8QDaUExIY/uzNAJs6/5iB42o6ln4hWdH5QxuP7evic7E4zbrkMdiKqA50hrYvTmCq jt2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eWSopTbk4UhjVfYw6Pb2U5XKiiaMhsL5HW2k761geA8=; b=YU1gXshuEbCan4X1X3j5VHnejgeZgdi1TNyno/VQkBl6YYuIIivXB70zpQMgWngy4y xI3EYVl20RGJ5UqDoXphFlmvHv3uTEfWIklzdSnlwpm9OBmw8AIAWWWmGOUp/K4NP8st KebsgBzEGJZPP4soXkVFUzKQE2KieQSVzvBr1lt+ZM8BmuSJg9UXQ4+3OhlF0OkonzKz 5G6K/auhxAF9/TlbSxcJVZHITXmfGZfeaU2WVY3JekvXdgE/xG//qTuBaYzHFlpuMSyt 0ulSASVvQ0cRiRJFFAfmExMsjuGjvcQDZ9VY//qoPuEz9yyB3di8zMv31YqNO3/atj6S c6mA== X-Gm-Message-State: AKGB3mKXgotKwHSu4XmH26Oe1HUlRFM/3Er3hDAoJnJ/iL60nhJuqrfb RSH0j/siUEwRdtZ2bEk9g6d5HqwR57LN7nHpD5O3gQ== X-Google-Smtp-Source: ACJfBosgRZIhYxpBwqTxID70v8XEHR1gckf3Sar2Iq6ICX4UWY5Xostpb4lPy5b1jL2h9r/qjAW18HexHolo/mjXONk= X-Received: by 10.107.157.82 with SMTP id g79mr304899ioe.296.1513613322238; Mon, 18 Dec 2017 08:08:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Mon, 18 Dec 2017 08:08:41 -0800 (PST) In-Reply-To: <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> References: <4c3ae20e-b6dd-d5db-0b93-2e1225daa658@selasky.org> <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> From: blubee blubeeme Date: Tue, 19 Dec 2017 00:08:41 +0800 Message-ID: Subject: Re: FreeBSD amd64 GENERIC kernel To: Alexander Leidinger Cc: freebsd-multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 16:08:43 -0000 On Mon, Dec 18, 2017 at 11:16 PM, Alexander Leidinger < Alexander@leidinger.net> wrote: > > Quoting blubee blubeeme (from Sat, 16 Dec 2017 > 21:49:08 +0800): > > On Sat, Dec 16, 2017 at 9:33 PM, Alexander Leidinger < >> Alexander@leidinger.net> wrote: >> >> Quoting blubee blubeeme (from Sat, 16 Dec 2017 >>> 09:39:04 +0800): >>> >> > The whole point of implementing 4Front oss and not a FreeBSD for is to >>>> K.I.S.S. >>>> Here's why >>>> 1)OSS v4 soundcard.h and code already hdandles ALL legacy applications >>>> w/o >>>> needing to implement special kernel kludges >>>> >>>> >>> You are mixing API (soundcard.h) with implementation (FreeBSD kernel >>> sound >>> code) and ways to change its behavior (sysctl). >>> >> > I just had a look at our soundcard.h and their soundcard.h. > Yes there are differences, but this is expected as it is not a copy but > another implementation of the same API. > > I had a look (well... more a glance) at the IOCTLs and other stuff (= the > API). Most of them are the same. There are minor differences which most > probably mean we are implementing the OSSv4 API in v4.0, while 4Front has > moved on to OSSv4.2. Those few differences, can probably be implemented in > FreeBSD by someone who is interested easily. The main point here is, are > those differences that important? The parts you complain about are not > related to those differences of the API. > > [a lot of technical details and questions from me cut... you didn't > respond to any of the serious questions I've put there] > > These are some blog posts from mid to late 2000; Please read it and >> understand what's he's trying to express; Then look at the audio programs >> and see how they continue to make the same exact mistakes in 2017 going on >> 2018. >> >> https://web.archive.org/web/20111001142728/http://4front-tec >> h.com/hannublog/?page_id=34 >> > > I've read this article. It talks about userland issues in applications, > not about issues we have in our kernel code. > > Where are these audio app developers who should be chiming in? The few >> applications that I've ported: audio/amsynth and audio/yoshimi >> one has OSS support already, the other one I am developing. >> Working on implementing the OSS support I am running into issues >> > > Feel free to open a new thread about your issues in multimedia@, maybe > someone can point you in the right direction. > > Instead of listening u guys keep repeating FreeBSD audio is Great.... >> > > I don't tell it is great. I tell you haven't managed yet to point out > where it is bad. Concrete examples instead of just telling it is bad. My > questions you skipped were targeted to find out what is not OK. So far you > haven't delivered an answer. I'm eager to see answers to them. So far I've > seen you (at least to my understanding) mixing up "implementation of an > API" (= kernel code) and "API" (soundcard.h), and in the API mixing up > "there are differences which don't matter for the API" (but matter for the > ABI, but this is relevant for compatibility between FreeBSD X and FreeBSD > Y) with "this is not OSSv4 API". You complained about optional parts in the > sound system which are disabled by default (sysctl) in a way I was > understanding as that you complain that they are there at all (while the > presence of the possibility not being related or affecting the ABI nor can > be attributed to misbehavior). > > I'm sure we will be open "to do something", but only if there are specific > areas pointed out and validated to be bad, instead of just telling "all is > bad" mixing up things while talking about it and not being specific at all > so that other people can validate that the parts you complain about do not > work as intended. > > And if you reference to "linuxims" refers to the fact that we have jack > and portaudio and whatever in the ports collection... well, this is not > related to the FreeBSD sound system at all, those are 3rd party > applications. We will not restrict which program someone wants to use on > FreeBSD, and if those using those programs are happy with it, it is not > related to the FreeBSD project at all. Do I agree that programs would be > better of to use the FreeBSD native API instead of of some intermediate > layer? In a lot of cases surely yes. Is this a responsibility of the > FreeBSD project? Not at all. We are an open source project which relies on > contributions to get "linux-programs" up and running (= ported) to FreeBSD. > If you find such a program which doesn't behave very good on FreeBSD, you > can help fixing it (by sending patches which make it work better on FreeBSD > to the developers of the application in question), or find people in the > FreeBSD community which may be interested to help fixing those programs. > Removing those middle-layers from the ports collection is surely out of > question as long as there is a program which depends upon one of them. > > In short: if you want that people agree that something is not good, you > need to come with specific items and detailed instructions how to repeat > what you see, so that it can be validated / repeated by someone else. > > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > I was actually having this conversation on both current mailing list and multimedia. The conversation is still on going on multimedia list somewhat. There seems to be a lot of misinformation out there about OSS that needs to be dispelled first. Then I wanted to get to the actual point of implementing the 4Front OSS and sticking to that API. Before things can be fixed, the problem has to be clearly defined and I've been looking at this issue for a while since I am interested in multimedia. My main purpose is simplicity. Here's a general overview of the problem as I see it. There's no real audio programming guide to speak of on FreeBSD, pointing me to OpenBSD doesn't cut it. Most of FreeBSD audio tools come from other platforms, even the OSS implementation is a fork of an earlier version of 4Front OSS. --sure FreeBSD was able to implement some features [virtual mixing, etc] before 4Front, then came sndio, pulse and all those other frontends that were basically copying Linuxisms right into FreeBSD. --Linux did the same thing with ALSA, then Jack1, Jack2, Pulse and whatever else the come up with next. They didn't understand the main issue and were trying to reduce latency when that's not really a concern for most devs or users. Then Hannu closed source his code to try to make a living off of his work, that didn't go so well and now we have; ALSA, JACK1, JACK2, PULSE, SNDIO and others that I don't care to look into. It doesn't matter how many times they create new sound architecture, unless the root issue of bad audio programming is rooted out, they'll just keep on coming up with the new next best thing. Remember that it was Hannu who created the first audio driver for Linux, it's that same legacy that everyone has been using to this day. This is how I think that all this could be simplified. 1) Get OSS 4.2 into FreeBSD kernel 2) create proper audio programming guide for the FreeBSD Handbook based on: http://manuals.opensound.com/developer/ making sure to remove all the depreciated API calls, the manual is very well documented. 3) 4Front OSS already supports many devices devices: https://sourceforge.net/p/opensound/git/ci/master/tree/devlists/FreeBSD there's also some legacy devices in the dir /attic/ if there are devices not supported by 4Font OSS, the FreeBSD drivers can be ported: http://manuals.opensound.com/sources/drv_index.html 4) refine the FreeBSD specific parts of the 4Front OSS backend: http://manuals.opensound.com/sources/kik.html look at the FreeBSD operating system links below. 5) 4Front OSS already has an ALSA emulator, collapse sndio to somehow use the updated programming guide. One of the nicest feature of 4Front OSS is that, without changing a line of code legacy OSS applications should just work. Since that's the case with legacy OSS applications, along with the ALSA emulation, there really isn't much else that's needed. I'm pretty sure I saw a 4Front OSS pulse wrapper as well. The main issue is that new audio programs are being written based on the legacy programming style. There are pieces that FreeBSD does best because everyone here develops FreeBSD, those fixes can be add Also I'd like to make sure to try to get these changes upstream as well. Once all of this is implemented, then there's a clean, straightforward API then additional features can be added as needed. This will take some work but w/o it being in the kernel why bother? Especially when people just have a knee jerk reaction to say OSS is a mess, our API is already compatible, we do it better, it's closed source license, etc.. Most of those are not true at best FreeBSD operating system Source Explanation FreeBSD/os_freebsd.h OS specific definitions for FreeBSD FreeBSD/bsddefs.h Definitions for routines and variables exported by osscore.c FreeBSD/os_freebsd.c Operating system abstraction functions for FreeBSDFiles used to build OSS and the drivers during install Source Explanation FreeBSD/bsdvirtual.inc Wrapper functions for virtual drivers under FreeBSD FreeBSD/osscore.c OSS core functions that need to be compiled in the target system FreeBSD/module.inc Generic OSS driver module interface for FreeBSD FreeBSD/devid.h Source file os_build/FreeBSD/devid.h FreeBSD/bsdpci.inc Wrapper functions for PCI drivers under FreeBSD I've been looking at the code, running the build script it first detects your OS copies or symlink OS specific files writes some configuration headers sets up includes then builds as usual. Most of that isn't necessary, just move the proper files into place write a kmod makefile and start testing. From owner-freebsd-multimedia@freebsd.org Mon Dec 18 17:34:51 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12E0AE9E37F for ; Mon, 18 Dec 2017 17:34:51 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 972AD661BC for ; Mon, 18 Dec 2017 17:34:50 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Mon, 18 Dec 2017 18:33:53 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1513618486; bh=+mX0fm3GMQ7mqbAJ56dmT65pa47Kisw2fLFEasmZPKM=; h=Date:From:To:Subject:References:In-Reply-To; b=xfH4HyqTPPjRnNtIHp7azojLTZsZvLtxY4cnhU/ibjaxMvTdsr8fa5c21fkwRRGSA thc+t5n66et+RYNCYSC9CXS473vrS+DC6sYPs9+e0FHD4h4JBmD/GEDPp6XlnyYWq3 kTyn7MD1/bIf7aUBogv/4RF/t12G7CqimpALrG+P0sW2ylSX9RZNI53Jgrm3cDR4MF 3tbCy58WZZ+Q+NHBY7Wpz4CalbfRbSI1MGSGyi5iAWx2SifZORzyYvZvCcsaMHzixz xFkle6uNky1PUOab4c/5CfGzfuoZE+++c3OTMFZjwihXDb6XsUz6LmUTPO3ZfGWvir 5HVvLLlF21wjA== Message-ID: <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-multimedia@freebsd.org Subject: Re: FreeBSD amd64 GENERIC kernel References: <4c3ae20e-b6dd-d5db-0b93-2e1225daa658@selasky.org> <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_ephHPOxRN0aWP4QZjDjQISA"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 17:34:51 -0000 This message is in MIME format and has been PGP signed. --=_ephHPOxRN0aWP4QZjDjQISA Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting blubee blubeeme (from Tue, 19 Dec 2017=20=20 00:08:41=20+0800): > On Mon, Dec 18, 2017 at 11:16 PM, Alexander Leidinger < > Alexander@leidinger.net> wrote: > >> >> Quoting blubee blubeeme (from Sat, 16 Dec 2017 >> 21:49:08 +0800): >> >> On Sat, Dec 16, 2017 at 9:33 PM, Alexander Leidinger < >>> Alexander@leidinger.net> wrote: >>> >>> Quoting blubee blubeeme (from Sat, 16 Dec 2017 >>>> 09:39:04 +0800): >>>> >>> >> The whole point of implementing 4Front oss and not a FreeBSD for is to >>>>> K.I.S.S. >>>>> Here's why >>>>> 1)OSS v4 soundcard.h and code already hdandles ALL legacy application= s >>>>> w/o >>>>> needing to implement special kernel kludges >>>>> >>>>> >>>> You are mixing API (soundcard.h) with implementation (FreeBSD kernel >>>> sound >>>> code) and ways to change its behavior (sysctl). >>>> >>> >> I just had a look at our soundcard.h and their soundcard.h. >> Yes there are differences, but this is expected as it is not a copy but >> another implementation of the same API. >> >> I had a look (well... more a glance) at the IOCTLs and other stuff (=3D = the >> API). Most of them are the same. There are minor differences which most >> probably mean we are implementing the OSSv4 API in v4.0, while 4Front ha= s >> moved on to OSSv4.2. Those few differences, can probably be implemented = in >> FreeBSD by someone who is interested easily. The main point here is, are >> those differences that important? The parts you complain about are not >> related to those differences of the API. >> >> [a lot of technical details and questions from me cut... you didn't >> respond to any of the serious questions I've put there] >> >> These are some blog posts from mid to late 2000; Please read it and >>> understand what's he's trying to express; Then look at the audio progra= ms >>> and see how they continue to make the same exact mistakes in 2017 going= on >>> 2018. >>> >>> https://web.archive.org/web/20111001142728/http://4front-tec >>> h.com/hannublog/?page_id=3D34 >>> >> >> I've read this article. It talks about userland issues in applications, >> not about issues we have in our kernel code. >> >> Where are these audio app developers who should be chiming in? The few >>> applications that I've ported: audio/amsynth and audio/yoshimi >>> one has OSS support already, the other one I am developing. >>> Working on implementing the OSS support I am running into issues >>> >> >> Feel free to open a new thread about your issues in multimedia@, maybe >> someone can point you in the right direction. >> >> Instead of listening u guys keep repeating FreeBSD audio is Great.... >>> >> >> I don't tell it is great. I tell you haven't managed yet to point out >> where it is bad. Concrete examples instead of just telling it is bad. My >> questions you skipped were targeted to find out what is not OK. So far y= ou >> haven't delivered an answer. I'm eager to see answers to them. So far I'= ve >> seen you (at least to my understanding) mixing up "implementation of an >> API" (=3D kernel code) and "API" (soundcard.h), and in the API mixing up >> "there are differences which don't matter for the API" (but matter for t= he >> ABI, but this is relevant for compatibility between FreeBSD X and FreeBS= D >> Y) with "this is not OSSv4 API". You complained about optional parts in = the >> sound system which are disabled by default (sysctl) in a way I was >> understanding as that you complain that they are there at all (while the >> presence of the possibility not being related or affecting the ABI nor c= an >> be attributed to misbehavior). >> >> I'm sure we will be open "to do something", but only if there are specif= ic >> areas pointed out and validated to be bad, instead of just telling "all = is >> bad" mixing up things while talking about it and not being specific at a= ll >> so that other people can validate that the parts you complain about do n= ot >> work as intended. >> >> And if you reference to "linuxims" refers to the fact that we have jack >> and portaudio and whatever in the ports collection... well, this is not >> related to the FreeBSD sound system at all, those are 3rd party >> applications. We will not restrict which program someone wants to use on >> FreeBSD, and if those using those programs are happy with it, it is not >> related to the FreeBSD project at all. Do I agree that programs would be >> better of to use the FreeBSD native API instead of of some intermediate >> layer? In a lot of cases surely yes. Is this a responsibility of the >> FreeBSD project? Not at all. We are an open source project which relies = on >> contributions to get "linux-programs" up and running (=3D ported) to Fre= eBSD. >> If you find such a program which doesn't behave very good on FreeBSD, yo= u >> can help fixing it (by sending patches which make it work better on Free= BSD >> to the developers of the application in question), or find people in the >> FreeBSD community which may be interested to help fixing those programs. >> Removing those middle-layers from the ports collection is surely out of >> question as long as there is a program which depends upon one of them. >> >> In short: if you want that people agree that something is not good, you >> need to come with specific items and detailed instructions how to repeat >> what you see, so that it can be validated / repeated by someone else. >> >> >> Bye, >> Alexander. >> >> -- >> http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF >> http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF >> > I was actually having this conversation on both current mailing list and > multimedia. > The conversation is still on going on multimedia list somewhat. > > There seems to be a lot of misinformation out there about OSS that needs = to > be dispelled first. > Then I wanted to get to the actual point of implementing the 4Front OSS a= nd > sticking to that API. > > Before things can be fixed, the problem has to be clearly defined and I'v= e > been looking at this issue > for a while since I am interested in multimedia. > > My main purpose is simplicity. > > Here's a general overview of the problem as I see it. > > There's no real audio programming guide to speak of on FreeBSD, pointing = me > to OpenBSD doesn't cut it. > Most of FreeBSD audio tools come from other platforms, even the OSS > implementation is a fork of an earlier > version of 4Front OSS. > --sure FreeBSD was able to implement some features [virtual mixing, etc] > before 4Front, then came sndio, pulse and all those other frontends > that were basically copying Linuxisms right into FreeBSD. > --Linux did the same thing with ALSA, then Jack1, Jack2, Pulse and whatev= er > else the come up with next. > > They didn't understand the main issue and were trying to reduce latency > when that's not really a concern for most devs or users. > Then Hannu closed source his code to try to make a living off of his work= , > that didn't go so well and now we have; > ALSA, JACK1, JACK2, PULSE, SNDIO and others that I don't care to look int= o. > > It doesn't matter how many times they create new sound architecture, unle= ss > the root issue of bad audio programming > is rooted out, they'll just keep on coming up with the new next best thin= g. I understand this as you say that the audio applications which make=20=20 use=20of no matter which sound architecture need to be fixed first. But=20= =20 then=20you start below with modifying the FreeBSD kernel... > Remember that it was Hannu who created the first audio driver for Linux, > it's that same legacy that everyone has been using > to this day. > > This is how I think that all this could be simplified. > 1) Get OSS 4.2 into FreeBSD kernel This can mean looking at what the differences between our OSSv4 and=20=20 the=204Front 4.2 API are, and then implementing them in the FreeBSD=20=20 code,=20or to take the 4 Front code and put it into FreeBSD. > 2) create proper audio programming guide for the FreeBSD Handbook > based on: http://manuals.opensound.com/developer/ > making sure to remove all the depreciated API calls, the manual is > very well documented. Given that with the OSSv4 API we implement, you can already program a=20=20 lot=20of audio applications without missing any functionality, why not=20= =20 first=20create such a documentation for the existing implementation, and=20= =20 then=20to look at changing the FreeBSD kernel. With this some=20=20 (interested)=20people could have already a look at improving audio=20=20 programs=20in parallel. This would fit what you write above about (as I=20= =20 understand=20it) first fixing the applications. As the API will be=20=20 mostly=20the same (let's say 95%) no matter which implementation is in=20= =20 the=20kernel, this seems to be a non-regret starting move in my opinion. Besides this, the FreeBSD handbook is not a programming manual, it is=20=20 more=20an operations guide / sysadmin tasks manual. As such what you=20=20 want=20to do doesn't really fit for the target audience of the FreeBSD=20= =20 handbook.=20What you talk about is more a developer manual (the=20=20 architecture=20manual may fit... to be evaluated). Right now we don't=20=20 really=20have a "one manual for all FreeBSD programming related things".=20= =20 As=20such I would suggest to have a "FreeBSD sound programming" (or=20=20 similar)=20document first. This could even be started in the FreeBSD wiki. Maybe you want to have a look at: https://wiki.freebsd.org/Sound > One of the nicest feature of 4Front OSS is that, > without changing a line of code legacy OSS applications should just work. This is the same for the FreeBSD sound code. > The main issue is that new audio programs are being written based on > the legacy programming style. And as FreeBSD implements the OSSv4 API, this looks again like work=20=20 should=20first be put into a programming manual instead into kernel code. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_ephHPOxRN0aWP4QZjDjQISA Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaN/wBAAoJEKrxQhqFIICEzEUQAIcxLIJfyHcTOp6110iVkhRT jBSzkhl53C9Ljb238Rpl2sY3bwmBGCR/doJQLscIz/DnC6HNFsdez39couL5z7JE DQaYiX4DW+Kni5EW3ytkM46zCiA7c1ixm307RzcCGsPcR4O7/Uf5IlKdP7JQImlt pXkdjFfgpDceoze/+0NdPzgFM/LLZ1SfW1d7j/SlBCeq/4oBfJ9TAyIXvkKcKKu/ I7dd+fOUpTN05zsRQK2vgurr+0TTSncQxjyitEISu6NWFLSqZ7KDkU0eYhsYVnnn vdgi5uPlPIMP5eHl6s83rTkmiTKYhFvTe3lvFnxYkZXShiri74sVEsVXTW4m5t6x oeW40Ex5QYbzYfuwG+yHmvOf3giRYOkEN4piMQAO3epGrhrSlcgY90QDUohY4vFS CvQ/dp8SFfqvO2yNDr0P5DJRr3Q+DRBag3vohC0PL8BwqQ0gHx1OBF2AE1SwD5+z RKewMm+iezmii5xfllCaMbIaijrIw3fwmVdMwkzDFt2yrEvCHnc9DSsjukvQo4Pi 7q+zJRLmHuMfy9ToRQuxkRNoVclgj+HjxIjcvansssmglp47UrVBzjF+uULgmt3P XcgRADM/K4YzNGL18nh+ETdoQd18Ft7t2HATzPSj4IQJ7eG8PztMpWv3OpIwfJJE 4hTM2kHMplahEVUW/cMv =UNRk -----END PGP SIGNATURE----- --=_ephHPOxRN0aWP4QZjDjQISA-- From owner-freebsd-multimedia@freebsd.org Mon Dec 18 17:46:11 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9390EE9F10C for ; Mon, 18 Dec 2017 17:46:11 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D50866974 for ; Mon, 18 Dec 2017 17:46:11 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x235.google.com with SMTP id p139so29308423itb.1 for ; Mon, 18 Dec 2017 09:46:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AyIXRtfp44UVRMfOhDjxIwjJiO0SqyQWEKPc12jWTKI=; b=BZugrJY36m3/OBO1I52EsipmiYumospsU9fV/fS2P+2asL4dvjHE3X87QlZD1Xj8m3 EaPNVby9FQGWcSd0EVTh8uoPUJgHNgFV5QBmmh5oB+pJj2j1CKMqYRqkzDXnQn2k6nww vY9bCuSQps+mMmI1UmoXX+ZHoW0IKKSrB9uIirrniKC0qlkvL2S/IaZ38WCsDSxE1N0t 7l0CoiuVhKwPXlvm2n5Gc1oLoKnwP9Pr3aKoAFA/gUmDBCuGSeD6TQ4WOZSZ7lApa1iY c7dnQFMHSugsOsbC01wslhNOp/TjWwD+79Bz7maYR8rFFvGK71PT7c9eyeL21L4D6jAf tTXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AyIXRtfp44UVRMfOhDjxIwjJiO0SqyQWEKPc12jWTKI=; b=eEM1h2Rub09mQ+wZfoiRGn7xdopflRYONxZ8D33odRbBskHliwrv2KLbZHxXviPLhi Gm/Voox81x+GFmP0dODIbkiyJ06WOwiEebHpXOAigpr8Nn9nCjd8bXl8uiHq8bquSylc HZGjIIyQ2rM+JBn4wksI6oseN7rHQMSJ7hFinmlFV9Pe/7pTSXn/23Ng9hgpWglaLSMY 1DMY7dAjPezw4TGfRzEMz/IEqX2Or3aonZVwUtb+fZrylIN8Uv0RFNb44pxfofImhN3N P/1CmpK0roZqPgJ8n79mrIeoqduV9JmZcuuvYAgCzwmFOGLhvzKj6cduWnSYQeCyBshF 1dJQ== X-Gm-Message-State: AKGB3mIT0/zKcvks5Tvi0aJ1Jdi7+ZFSbHUm5tujhanSUp8Ah8KdvHC9 +qQZqUi6MtGco1KRcRZt5x0tpagwnj9cpEfV1do9Ag== X-Google-Smtp-Source: ACJfBoviDisgFVIuYg05eCMyI/B+l2Q4tHpIVEfBre25X0DFqcU8a213sZVCyfCHBmCnwM+0uuMb68wcLWU879vTIls= X-Received: by 10.36.116.135 with SMTP id o129mr530797itc.119.1513619170436; Mon, 18 Dec 2017 09:46:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Mon, 18 Dec 2017 09:46:09 -0800 (PST) In-Reply-To: <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> References: <4c3ae20e-b6dd-d5db-0b93-2e1225daa658@selasky.org> <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> From: blubee blubeeme Date: Tue, 19 Dec 2017 01:46:09 +0800 Message-ID: Subject: Re: FreeBSD amd64 GENERIC kernel To: Alexander Leidinger Cc: freebsd-multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 17:46:11 -0000 On Tue, Dec 19, 2017 at 1:33 AM, Alexander Leidinger < Alexander@leidinger.net> wrote: > Quoting blubee blubeeme (from Tue, 19 Dec 2017 > 00:08:41 +0800): > > On Mon, Dec 18, 2017 at 11:16 PM, Alexander Leidinger < >> Alexander@leidinger.net> wrote: >> >> >>> Quoting blubee blubeeme (from Sat, 16 Dec 2017 >>> 21:49:08 +0800): >>> >>> On Sat, Dec 16, 2017 at 9:33 PM, Alexander Leidinger < >>> >>>> Alexander@leidinger.net> wrote: >>>> >>>> Quoting blubee blubeeme (from Sat, 16 Dec 2017 >>>> >>>>> 09:39:04 +0800): >>>>> >>>>> >>>> The whole point of implementing 4Front oss and not a FreeBSD for is to >>> >>>> K.I.S.S. >>>>>> Here's why >>>>>> 1)OSS v4 soundcard.h and code already hdandles ALL legacy applications >>>>>> w/o >>>>>> needing to implement special kernel kludges >>>>>> >>>>>> >>>>>> You are mixing API (soundcard.h) with implementation (FreeBSD kernel >>>>> sound >>>>> code) and ways to change its behavior (sysctl). >>>>> >>>>> >>>> I just had a look at our soundcard.h and their soundcard.h. >>> Yes there are differences, but this is expected as it is not a copy but >>> another implementation of the same API. >>> >>> I had a look (well... more a glance) at the IOCTLs and other stuff (= the >>> API). Most of them are the same. There are minor differences which most >>> probably mean we are implementing the OSSv4 API in v4.0, while 4Front has >>> moved on to OSSv4.2. Those few differences, can probably be implemented >>> in >>> FreeBSD by someone who is interested easily. The main point here is, are >>> those differences that important? The parts you complain about are not >>> related to those differences of the API. >>> >>> [a lot of technical details and questions from me cut... you didn't >>> respond to any of the serious questions I've put there] >>> >>> These are some blog posts from mid to late 2000; Please read it and >>> >>>> understand what's he's trying to express; Then look at the audio >>>> programs >>>> and see how they continue to make the same exact mistakes in 2017 going >>>> on >>>> 2018. >>>> >>>> https://web.archive.org/web/20111001142728/http://4front-tec >>>> h.com/hannublog/?page_id=34 >>>> >>>> >>> I've read this article. It talks about userland issues in applications, >>> not about issues we have in our kernel code. >>> >>> Where are these audio app developers who should be chiming in? The few >>> >>>> applications that I've ported: audio/amsynth and audio/yoshimi >>>> one has OSS support already, the other one I am developing. >>>> Working on implementing the OSS support I am running into issues >>>> >>>> >>> Feel free to open a new thread about your issues in multimedia@, maybe >>> someone can point you in the right direction. >>> >>> Instead of listening u guys keep repeating FreeBSD audio is Great.... >>> >>>> >>>> >>> I don't tell it is great. I tell you haven't managed yet to point out >>> where it is bad. Concrete examples instead of just telling it is bad. My >>> questions you skipped were targeted to find out what is not OK. So far >>> you >>> haven't delivered an answer. I'm eager to see answers to them. So far >>> I've >>> seen you (at least to my understanding) mixing up "implementation of an >>> API" (= kernel code) and "API" (soundcard.h), and in the API mixing up >>> "there are differences which don't matter for the API" (but matter for >>> the >>> ABI, but this is relevant for compatibility between FreeBSD X and FreeBSD >>> Y) with "this is not OSSv4 API". You complained about optional parts in >>> the >>> sound system which are disabled by default (sysctl) in a way I was >>> understanding as that you complain that they are there at all (while the >>> presence of the possibility not being related or affecting the ABI nor >>> can >>> be attributed to misbehavior). >>> >>> I'm sure we will be open "to do something", but only if there are >>> specific >>> areas pointed out and validated to be bad, instead of just telling "all >>> is >>> bad" mixing up things while talking about it and not being specific at >>> all >>> so that other people can validate that the parts you complain about do >>> not >>> work as intended. >>> >>> And if you reference to "linuxims" refers to the fact that we have jack >>> and portaudio and whatever in the ports collection... well, this is not >>> related to the FreeBSD sound system at all, those are 3rd party >>> applications. We will not restrict which program someone wants to use on >>> FreeBSD, and if those using those programs are happy with it, it is not >>> related to the FreeBSD project at all. Do I agree that programs would be >>> better of to use the FreeBSD native API instead of of some intermediate >>> layer? In a lot of cases surely yes. Is this a responsibility of the >>> FreeBSD project? Not at all. We are an open source project which relies >>> on >>> contributions to get "linux-programs" up and running (= ported) to >>> FreeBSD. >>> If you find such a program which doesn't behave very good on FreeBSD, you >>> can help fixing it (by sending patches which make it work better on >>> FreeBSD >>> to the developers of the application in question), or find people in the >>> FreeBSD community which may be interested to help fixing those programs. >>> Removing those middle-layers from the ports collection is surely out of >>> question as long as there is a program which depends upon one of them. >>> >>> In short: if you want that people agree that something is not good, you >>> need to come with specific items and detailed instructions how to repeat >>> what you see, so that it can be validated / repeated by someone else. >>> >>> >>> Bye, >>> Alexander. >>> >>> -- >>> http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF >>> http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF >>> >>> I was actually having this conversation on both current mailing list and >> multimedia. >> The conversation is still on going on multimedia list somewhat. >> >> There seems to be a lot of misinformation out there about OSS that needs >> to >> be dispelled first. >> Then I wanted to get to the actual point of implementing the 4Front OSS >> and >> sticking to that API. >> >> Before things can be fixed, the problem has to be clearly defined and I've >> been looking at this issue >> for a while since I am interested in multimedia. >> >> My main purpose is simplicity. >> >> Here's a general overview of the problem as I see it. >> >> There's no real audio programming guide to speak of on FreeBSD, pointing >> me >> to OpenBSD doesn't cut it. >> Most of FreeBSD audio tools come from other platforms, even the OSS >> implementation is a fork of an earlier >> version of 4Front OSS. >> --sure FreeBSD was able to implement some features [virtual mixing, etc] >> before 4Front, then came sndio, pulse and all those other frontends >> that were basically copying Linuxisms right into FreeBSD. >> --Linux did the same thing with ALSA, then Jack1, Jack2, Pulse and >> whatever >> else the come up with next. >> >> They didn't understand the main issue and were trying to reduce latency >> when that's not really a concern for most devs or users. >> Then Hannu closed source his code to try to make a living off of his work, >> that didn't go so well and now we have; >> ALSA, JACK1, JACK2, PULSE, SNDIO and others that I don't care to look >> into. >> >> It doesn't matter how many times they create new sound architecture, >> unless >> the root issue of bad audio programming >> is rooted out, they'll just keep on coming up with the new next best >> thing. >> > > I understand this as you say that the audio applications which make use of > no matter which sound architecture need to be fixed first. But then you > start below with modifying the FreeBSD kernel... > > Remember that it was Hannu who created the first audio driver for Linux, >> it's that same legacy that everyone has been using >> to this day. >> >> This is how I think that all this could be simplified. >> 1) Get OSS 4.2 into FreeBSD kernel >> > > This can mean looking at what the differences between our OSSv4 and the > 4Front 4.2 API are, and then implementing them in the FreeBSD code, or to > take the 4 Front code and put it into FreeBSD. > > 2) create proper audio programming guide for the FreeBSD Handbook >> based on: http://manuals.opensound.com/developer/ >> making sure to remove all the depreciated API calls, the manual is >> very well documented. >> > > Given that with the OSSv4 API we implement, you can already program a lot > of audio applications without missing any functionality, why not first > create such a documentation for the existing implementation, and then to > look at changing the FreeBSD kernel. With this some (interested) people > could have already a look at improving audio programs in parallel. This > would fit what you write above about (as I understand it) first fixing the > applications. As the API will be mostly the same (let's say 95%) no matter > which implementation is in the kernel, this seems to be a non-regret > starting move in my opinion. > > Besides this, the FreeBSD handbook is not a programming manual, it is more > an operations guide / sysadmin tasks manual. As such what you want to do > doesn't really fit for the target audience of the FreeBSD handbook. What > you talk about is more a developer manual (the architecture manual may > fit... to be evaluated). Right now we don't really have a "one manual for > all FreeBSD programming related things". As such I would suggest to have a > "FreeBSD sound programming" (or similar) document first. This could even be > started in the FreeBSD wiki. > Maybe you want to have a look at: > https://wiki.freebsd.org/Sound > > > One of the nicest feature of 4Front OSS is that, >> without changing a line of code legacy OSS applications should just work. >> > > This is the same for the FreeBSD sound code. > > The main issue is that new audio programs are being written based on >> the legacy programming style. >> > > And as FreeBSD implements the OSSv4 API, this looks again like work should > first be put into a programming manual instead into kernel code. > > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > The whole goal of starting this discussion was to get this started. There's no "Audio Programming Guide" in FreeBSD and that's a problem since the applications just get ported over and instead of implementing the OSS API people do a patchwork of kludges to get audio sorta kinda working on FreeBSD; We can do better and send the patches upstream to see if they can get accepted, if not keep them in FreeBSD. Is it possible to get FreeBSD soundcard.h in line with the one from: https://sourceforge.net/p/opensound/git/ci/master/tree/include/soundcard.h I was writing some test programs based on the documentation and a surprising amount of audio formats were not defined in FreeBSD's soundcard.h From owner-freebsd-multimedia@freebsd.org Tue Dec 19 11:30:21 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D781EA14C2 for ; Tue, 19 Dec 2017 11:30:21 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E693273CB4 for ; Tue, 19 Dec 2017 11:30:19 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Tue, 19 Dec 2017 12:29:52 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1513683016; bh=cjWhpqak04EWJ8cXX6m3Jf9i2WHSNwOReDV6apAlpto=; h=Date:From:To:Subject:References:In-Reply-To; b=RFudo/7Ljj0wRMhI5YdrNdkNCoJTc0XDvuWWl+APA8riwpbV8DACS/7vJIL2RDfUg HssS83MpbHlalvkmyCRBZvvjRv/c24+/lLh4paeF3V881D/8CGTFS43Vdx8Rua7Lm9 OyWG4FLCHd8ZGMbEQ50ZaZRoD4+iMCnNvd0lSvt4gNuIqvlKenW4l48gR8C0xwRkuE hAoBPqlL3tHib5vtPsOCGTuc5nXd6zDq+uwybiVBxZOrPItv4iziYND+pd9+1497AP +uF9GuTEPm3wBpYRxfOiRamM0pjixzIJw3jeLwxV10lI+VFxNBqySErleWveLB9NIY M7Tvx8r+mbaCA== Message-ID: <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-multimedia@freebsd.org Subject: Re: FreeBSD amd64 GENERIC kernel References: <4c3ae20e-b6dd-d5db-0b93-2e1225daa658@selasky.org> <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_475R0lQQXW064M5W4w4znoA"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 11:30:21 -0000 This message is in MIME format and has been PGP signed. --=_475R0lQQXW064M5W4w4znoA Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting blubee blubeeme (from Tue, 19 Dec 2017=20=20 01:46:09=20+0800): > Is it possible to get FreeBSD soundcard.h in line with the one from: > https://sourceforge.net/p/opensound/git/ci/master/tree/include/soundcard.= h > > I was writing some test programs based on the documentation > and a surprising amount of audio formats were not defined in FreeBSD's > soundcard.h We can not simply copy the file over (there are licensing=20=20 implications,=20and surely implementation details =3D API is the same but= =20=20 the=20ABI is different). There are implications also for just adding=20=20 "values".=20Maybe adding something into the include file requires=20=20 support=20for this inside the kernel. So yes, adding something (like audio formats) is possible, but=20=20 requires=20analysis and testing by someone. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_475R0lQQXW064M5W4w4znoA Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaOPgwAAoJEKrxQhqFIICEiVoQAIYuikTmoA25Vlc6MudF8SFX Sobj1u8Jh9uGRPtU/eG5QCSui3KRyuwCjWwAHs04jpEXm9qF8l115RzhlBUaqLu8 PpcKWqzuzx6IK0WieZJmZsrD9+Fo79k/yZrSLLA31xwIEH8nl4v4Yd2IC6roTrTJ DW22HK2IBJqYM5wLqSk87tRrUBDLc/l3YvffJSY4Rxg0ih5Kttz9sdVOud6TCUYJ TIycBKclPdJGz1uaNEjFNdouaDUKf6WdmnhVs1MzX9Opzw1y6auXYV4P/+PvwLku R3gXvFrWxfLB7Jc9RWJFolJHb6I/hAM2i2MBhCPnuQ7RmAL/9SlpPWVLt4Xl5Obd 4T3BaPh4XSTmxcsnCFuCJX3za9WcQPQ6yePG/Pf+M/Ue33hvgpeag6OkAtNtm+b6 dtCKn31zrfD7tsB+ADwEw+i0ETB5IPW5J+yoP98eDql04OsnRWO5Td82BdCiwLnB L7pU2F+Z3kSntFuqln8FiZGKYEa3ipwFJKZibP0wF7/cp9OaUn4/bNrfvycZ0Wsv Joorn98V7U0xNenIf7n+nl5qYEEJ01DcxuYnPX8Zoi0RtAf0ORQTIgdsr6P6qKv6 UkxhnGqNG7jJR1pS03+hYV0HTbdk7dIQrQpbWeVRLHA82q1It9/Wf0yy8dcI3CZ+ +GVKkoR/jkp2qD1WLd4s =oSjT -----END PGP SIGNATURE----- --=_475R0lQQXW064M5W4w4znoA-- From owner-freebsd-multimedia@freebsd.org Tue Dec 19 12:00:11 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FEAEEA34AB for ; Tue, 19 Dec 2017 12:00:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF3AE750C1 for ; Tue, 19 Dec 2017 12:00:10 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 27E042606D0; Tue, 19 Dec 2017 13:00:09 +0100 (CET) Subject: Re: FreeBSD amd64 GENERIC kernel To: Alexander Leidinger , freebsd-multimedia@freebsd.org References: <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> From: Hans Petter Selasky Message-ID: Date: Tue, 19 Dec 2017 12:57:21 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 12:00:11 -0000 On 12/19/17 12:29, Alexander Leidinger wrote: > > So yes, adding something (like audio formats) is possible, but requires > analysis and testing by someone. Hi Blubee, Can you list the formats you think are missing from soundcard.h? I see no important formats missing from my brief check. --HPS From owner-freebsd-multimedia@freebsd.org Tue Dec 19 12:18:11 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6046CEA49F8 for ; Tue, 19 Dec 2017 12:18:11 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B16D75D0F for ; Tue, 19 Dec 2017 12:18:11 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x236.google.com with SMTP id e204so13377564iof.12 for ; Tue, 19 Dec 2017 04:18:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=g0LNeAhMcwrJURg6S0LA8q9lUcP3+53ddrxMymouQsQ=; b=R9+aBypbv1cvUrVTB6+8ar9dT+R5CeDWx6yY3+ZYvJ3qtrq6JF1DaQwu0trIJua2Ip B6TaaTDW/xT6I63YMwKUuu5IRHQ09MeudOHpVn2JBdIBPRfdNKnYBGbjjorXh1oH8tHU PV8bkZYt1+M8BsFECp58LwiAtAqvx8EiGTYYB1oPeB5R1GOtTt31gzyTdAS4zlWCN2fj w9PIOeyIgT8VVnt1PxP5szxFaizY9AYUnClr/aUF+UtXmtTg43VFDF+M+fC52lSFGZkQ zEQLBOPjMJEH8HggaEnM9UTYsmT9MIN7L7hyRXyfhf8vvq4xajgvwGeQRjP1UXejCq0h hEPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=g0LNeAhMcwrJURg6S0LA8q9lUcP3+53ddrxMymouQsQ=; b=FPF+T6vxGKAWwZQO/cz7VqpbW0JzMwezh4qghhu+ijS0L/FI9i4WC6dsWA+aic5rGK uelBWmhkkpWjcm9gjdOwzsBNEDoTfEInwr5oS15XMMtaaI9BNwAgawdL+2WuLiDY+5uT RMxJ4pLzBrBMdjixNLfEmUm08ZT/QDCyzRmKhqtCMxyNNPH4Izv9k0gLDv9PdYs+0qBD +kv8NWMQx/z/RvbWX5h1/TDxQGmjGBftNbEwaBIpwbzzUKwrSLTAX38+4um7iimlg9hT K1cFyvIwBKpZ/GqFFukeDsR75L3In1DB/uDzHdNyHmv5ijb4pD366nu1NLBZN1lGIoFb YCqw== X-Gm-Message-State: AKGB3mLSihuh8Qcgtihhax7BB5N2EFzzMx1V+Uy418kdfMdX5BzntD7z OvHMv4jn6Gd9Pe40yX5thuJDs8jYwAfXSKCWBRHrfQ== X-Google-Smtp-Source: ACJfBosgGK68p4lcQ57h4N/nSM8hsE+kI7PeKOl6M7TEOGoiq1QoeJA182Wwfdm7t7CDel6SPtE4afMYMcS/cVa1FoI= X-Received: by 10.107.18.35 with SMTP id a35mr3822269ioj.291.1513685889831; Tue, 19 Dec 2017 04:18:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Tue, 19 Dec 2017 04:18:08 -0800 (PST) In-Reply-To: References: <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> From: blubee blubeeme Date: Tue, 19 Dec 2017 20:18:08 +0800 Message-ID: Subject: Re: FreeBSD amd64 GENERIC kernel To: Hans Petter Selasky Cc: Alexander Leidinger , freebsd-multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 12:18:11 -0000 On Tue, Dec 19, 2017 at 7:57 PM, Hans Petter Selasky wrote: > On 12/19/17 12:29, Alexander Leidinger wrote: > >> >> So yes, adding something (like audio formats) is possible, but requires >> analysis and testing by someone. >> > > Hi Blubee, > > Can you list the formats you think are missing from soundcard.h? I see no > important formats missing from my brief check. > > --HPS > _______________________________________________ > freebsd-multimedia@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-multimedia > To unsubscribe, send any mail to "freebsd-multimedia-unsubscrib > e@freebsd.org" > A sample mixer program, these aren't included: MIXT_MONOSLIDER16 MIXT_STEREOSLIDER16 MIXF_CENTIBEL From owner-freebsd-multimedia@freebsd.org Tue Dec 19 12:46:27 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44379E8054E for ; Tue, 19 Dec 2017 12:46:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0686E76FE6 for ; Tue, 19 Dec 2017 12:46:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 6238A2606D0; Tue, 19 Dec 2017 13:46:24 +0100 (CET) Subject: Re: FreeBSD amd64 GENERIC kernel To: blubee blubeeme Cc: Alexander Leidinger , freebsd-multimedia@freebsd.org References: <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> From: Hans Petter Selasky Message-ID: <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> Date: Tue, 19 Dec 2017 13:43:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 12:46:27 -0000 On 12/19/17 13:18, blubee blubeeme wrote: > On Tue, Dec 19, 2017 at 7:57 PM, Hans Petter Selasky > wrote: > >> On 12/19/17 12:29, Alexander Leidinger wrote: >> >>> >>> So yes, adding something (like audio formats) is possible, but requires >>> analysis and testing by someone. >>> >> >> Hi Blubee, >> >> Can you list the formats you think are missing from soundcard.h? I see no >> important formats missing from my brief check. >> >> --HPS Hi, > A sample mixer program, these aren't included: > MIXT_MONOSLIDER16 > MIXT_STEREOSLIDER16 > MIXF_CENTIBEL These are not audio formats :-( They are mixer types. What is the meaning behind this: "a surprising amount of audio formats were not defined in FreeBSD's soundcard.h". Can you explain? --HPS From owner-freebsd-multimedia@freebsd.org Tue Dec 19 12:57:52 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1D60E80FAA for ; Tue, 19 Dec 2017 12:57:52 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 830CE77648 for ; Tue, 19 Dec 2017 12:57:52 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id v186so13487543iod.7 for ; Tue, 19 Dec 2017 04:57:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=31fCUKHNjcyaqEHK6JuHN34UibBiZfNEHUrn7tcS0uk=; b=buzgp0cQ3rTeI+k9SgTlbC+gJlgzCW/nMMffw/bHJC++RA3/geOP0t+jquwpcD7LJh FV0PtC/C5qOP0RV2JjGTfkm52i1PVHlD9FeQ76z44CF4FhSydzlmOyl+/glbTBDuc6uD WwO4vbmfL6uJXhb2yIbYK6Zh+qlMbP9/bro3Uzmo3PIWzNizcg7tXUoSAqKZxOyqaVRm B2xd277hOtn5uKRt7OPxQiYP5BJArHxq0MM1u7I81yAz+STv5U8kPusaMkdi2JouKwn9 NgMZN4UIO+8VlbN6FNQdJEQy9MG95NQMjOpWYlzym/1GaRyp4V5JLtbCpYwjH/lXtPQt YoMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=31fCUKHNjcyaqEHK6JuHN34UibBiZfNEHUrn7tcS0uk=; b=B7bFUWQEVV5PsCzlZKXI0KsgypwwaPEc/Pcqhp9qqz1elh7G+Oz9Zkhc0BTegO/eZP TNljKBTrLVEg9iS8m9Q+H70Q0RM/QJu8KgDEdhHYkpcSyqXi3W7TXdoXTb1rD0LvlTGN lBUNjlTpJndn1f8N0ZCWq1dQA+vqkzVaaQzgg3JFk3DQ0LfL3hgXJ3Fe4VcxPHBOTIHZ PqPdbI7ELxllq/xJusveEggBRSk1G/F9QZxpGzq+pXo9o8YALyk4NQOp/hj8a1VbMN1a NCYTnZBGdGQi8M3UrRdcmB8m/EtTJb6wt3emRyU+dPIXOJfVBHl2wwnGDksJqc3aXKiZ 3c8Q== X-Gm-Message-State: AKGB3mI6g0PFQDlnNXHvFpMc34G84vJtr0umrFkdnnUIRWu2E2V5JwAs qHR7xksGPmBynqpA7QKjledVbfpjPlac25iFRCU= X-Google-Smtp-Source: ACJfBouEdSJwk3eNvAMC0+q+oH9e5THPryMdEjsNHjGuzN75ygSKY+BhguWsqqpnzAxTpOe8dUg4ZAeYtY/UCYJxeKc= X-Received: by 10.107.18.35 with SMTP id a35mr3956714ioj.291.1513688271750; Tue, 19 Dec 2017 04:57:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Tue, 19 Dec 2017 04:57:50 -0800 (PST) In-Reply-To: <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> References: <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> From: blubee blubeeme Date: Tue, 19 Dec 2017 20:57:50 +0800 Message-ID: Subject: Re: FreeBSD amd64 GENERIC kernel To: Hans Petter Selasky Cc: Alexander Leidinger , freebsd-multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 12:57:52 -0000 On Tue, Dec 19, 2017 at 8:43 PM, Hans Petter Selasky wrote: > On 12/19/17 13:18, blubee blubeeme wrote: > >> On Tue, Dec 19, 2017 at 7:57 PM, Hans Petter Selasky >> wrote: >> >> On 12/19/17 12:29, Alexander Leidinger wrote: >>> >>> >>>> So yes, adding something (like audio formats) is possible, but requires >>>> analysis and testing by someone. >>>> >>>> >>> Hi Blubee, >>> >>> Can you list the formats you think are missing from soundcard.h? I see no >>> important formats missing from my brief check. >>> >>> --HPS >>> >> > Hi, > > A sample mixer program, these aren't included: >> MIXT_MONOSLIDER16 >> MIXT_STEREOSLIDER16 >> MIXF_CENTIBEL >> > > These are not audio formats :-( They are mixer types. > > What is the meaning behind this: "a surprising amount of audio formats > were not defined in FreeBSD's soundcard.h". Can you explain? > > --HPS > > Yes, it means that as I go through the sample programs and documentation about writing audio programs I run into issues with the built in soundcard.h file. That's the whole reason why I brought up this issue in the first place. That still leaves my last question unanswered, where does one start if they want to program audio applications on FreeBSD? From owner-freebsd-multimedia@freebsd.org Tue Dec 19 13:56:01 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8E05E845CE for ; Tue, 19 Dec 2017 13:56:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 97EC9797F2 for ; Tue, 19 Dec 2017 13:56:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 88854261A94; Tue, 19 Dec 2017 14:55:52 +0100 (CET) Subject: Re: FreeBSD amd64 GENERIC kernel To: blubee blubeeme Cc: Alexander Leidinger , freebsd-multimedia@freebsd.org References: <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> From: Hans Petter Selasky Message-ID: Date: Tue, 19 Dec 2017 14:53:04 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 13:56:01 -0000 On 12/19/17 13:57, blubee blubeeme wrote: > That still leaves my last question unanswered, where does one start > if they want to program audio applications on FreeBSD? Hi, You should start by looking at existing OSSv4 compatible audio applications already in FreeBSD ports and in FreeBSD base and compare how they use the OSSv4 interface(s). I have the impression you already know how various IOCTLs and defines are named in "sys/soundcard.h" and you can simply grep for the occurrence of these. Even just looking for the string "#include " might be good enough for a start. For example if you have some gigabytes of disk space, run "make fetch extract" in all subfolders inside "/usr/ports/audio" and then grep through the extracted sources. --HPS From owner-freebsd-multimedia@freebsd.org Tue Dec 19 14:19:36 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84FE0E85C4C for ; Tue, 19 Dec 2017 14:19:36 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54D547A628 for ; Tue, 19 Dec 2017 14:19:36 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x235.google.com with SMTP id z6so2921661iti.4 for ; Tue, 19 Dec 2017 06:19:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=N4LFEma+s5qMNir6pSgCwVUNToFKLqcjsg04HJ+iH6M=; b=QZFbp+spA6BUiYXyq+y8JMrKvTsAVwn5Guwvudbxopdj/+9ukJ+7Fpl7/FEFOrz6eN ApE2tlo/EJOydhjf8CnHbEzNNOfZsdgUYLYrV11chWWOD01yZC/tfpJ3X/xWttBCxe28 nGZeWuMChBNW2jnBJlnIoPT3hADpBQG/9DDzrAsSpxDSWfawi7F78lWiIThwG6iBy8YG qyc9zgEtxDBJ1YRa7f0Yhdy1HgmDHmDTBbriak9eELBqBb5KKjBBU+RUTZj1HYEVVHsK XTbKGrek7f2xVOgbI0kNLD36yijBoX+0bAWbQzYvqc/MOvx/xJVFSfeSqHoAG4rcguqj IYYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=N4LFEma+s5qMNir6pSgCwVUNToFKLqcjsg04HJ+iH6M=; b=OaVnCRsUZRrXlBmmTQlhMGyVbH/4bNkD2/Mjnzmd5axJS0bJ+2YmvlNZXJ5UnFOKkh tM4wnQMdopW4s5CEiUPL0KxBQJU6AHQEi3tqqIkt4oA1dyiL98ZyKahW7/9a7LXvWnuY 0aeb/rfbZJCziAbpquPZw83iCj4BwESozGS8igkg3bFJ2lNqwMODJgv31pOMJklUPYJ6 x/Q3wC/5tGn5LRbgJHpGkgAyLJr8FQwbSea4iasuNzoBzvZ7KpIMFqkFoPWw1GvWu5fR 609YTlO1FnMW7sMFmY06neCc8eHwuANNrTDhI4XSOnZ2j97lQkTeAeCN9Oxv/77004mX 1VNg== X-Gm-Message-State: AKGB3mLPYG94cgsFJ6MVYbMOXJQfJabE2497WHm6XOrhVzdswQAF4bFc 1hcwi90GMGGiOuaafPyXdNVtGChLBQ0C6sW+F/Y= X-Google-Smtp-Source: ACJfBosTCavvskWF6EfXmD3CaKXC5RmhDjaoQg759+XeDyfHJAHoidQssCYMdIwkBdz95U8v7+I3sgFP3EtnSek0clM= X-Received: by 10.36.167.77 with SMTP id s13mr3394936iti.51.1513693175458; Tue, 19 Dec 2017 06:19:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Tue, 19 Dec 2017 06:19:34 -0800 (PST) In-Reply-To: References: <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net> <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> From: blubee blubeeme Date: Tue, 19 Dec 2017 22:19:34 +0800 Message-ID: Subject: Re: FreeBSD amd64 GENERIC kernel To: Hans Petter Selasky Cc: Alexander Leidinger , freebsd-multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 14:19:36 -0000 On Tue, Dec 19, 2017 at 9:53 PM, Hans Petter Selasky wrote: > On 12/19/17 13:57, blubee blubeeme wrote: > >> That still leaves my last question unanswered, where does one start >> if they want to program audio applications on FreeBSD? >> > > Hi, > > You should start by looking at existing OSSv4 compatible audio > applications already in FreeBSD ports and in FreeBSD base and compare how > they use the OSSv4 interface(s). > > I have the impression you already know how various IOCTLs and defines are > named in "sys/soundcard.h" and you can simply grep for the occurrence of > these. Even just looking for the string "#include " might > be good enough for a start. For example if you have some gigabytes of disk > space, run "make fetch extract" in all subfolders inside "/usr/ports/audio" > and then grep through the extracted sources. > > --HPS > If my only option was to reverse engineer audio programs to learn then API i'd probably take that route. It's obvious there's issues that need to be sorted out here. From owner-freebsd-multimedia@freebsd.org Tue Dec 19 15:05:50 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D1E5E88CEF for ; Tue, 19 Dec 2017 15:05:50 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay105.isp.belgacom.be (mailrelay105.isp.belgacom.be [195.238.20.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98AA27C60D for ; Tue, 19 Dec 2017 15:05:49 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3Atpd0RRXxsBB+SLlhwwObcChD+6HV8LGtZVwlr6E/?= =?us-ascii?q?grcLSJyIuqrYbBGPt8tkgFKBZ4jH8fUM07OQ7/i5HzRYqb+681k6OKRWUBEEjc?= =?us-ascii?q?hE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRo?= =?us-ascii?q?LerpBIHSk9631+ev8JHPfglEnjWwba9vIBmssQndqtQdjJd/JKo21hbHuGZDdf?= =?us-ascii?q?5MxWNvK1KTnhL86dm18ZV+7SleuO8v+tBZX6nicKs2UbJXDDI9M2Ao/8LrrgXM?= =?us-ascii?q?TRGO5nQHTGoblAdDDhXf4xH7WpfxtTb6tvZ41SKHM8D6Uaw4VDK/5KpwVhTmlD?= =?us-ascii?q?kIOCI48GHPi8x/kqRboA66pxdix4LYeZyZOOZicq/Ye94RWGhPUdtLVyFZDI2y?= =?us-ascii?q?b5UBAfcCM+laoYnyqEcBoxSlCAmwBu7j1iNEimPq0aEk1ekqDAHI3BYnH9ILqH?= =?us-ascii?q?nastT1NKUWUeuo0qTIyjLDb+hI1jf48ofIdAshquyLULJscMrRy00vGhjFgFWK?= =?us-ascii?q?t4PqIS6Y2PkDvWSB6OpgT+2vhnchpgpsrDavwcIshZPIhoIT0l3E+z95z5grKt?= =?us-ascii?q?KjU050fMSoEJxKtyGVMYZ9X8AsQ3lwtSs517EKo4C3cScIxZg92RLTceKLfoeL?= =?us-ascii?q?7x/lSe2fOy13hGh/d7K6nxuy9E+gxfDiWcSsy1ZKqzZFksHLtnAQyxzf8siHRe?= =?us-ascii?q?V5/kemwTuP1Brc6uVFIUAxi6XbMZkhzqQslpoSs0TDGjX6l1nxjK+RbUUr5O2o?= =?us-ascii?q?5P7hYrX9vJOcMJV0ig7mPqQvnMywH/g4PxANUmSG4+iwyrLu8E/jTLlUlPE6jK?= =?us-ascii?q?bUvZPCKcQevKG5AgtV0og56xa4CjeryMgYnXgFLFJBYx+HgZLpNE/QL//jFvew?= =?us-ascii?q?nk6gkDBxx/DJJrHhGInCLmDfkLf9erZw81JRyA4twtFQ/Z1UDKwOL+zpWkLqsN?= =?us-ascii?q?zXEB45PBG1w+bhB9VyyJkeVXiJAqCHLKPYqUWI6f43I+mQeI8Vvy7wK/g95/71?= =?us-ascii?q?lnI5gkESfa2z0psMa3C5Hu5qI0KDYXrj0Z89FjIqtwwlBNTnlEGPS3ZoanK7RK?= =?us-ascii?q?EtrmU7EJmOForHT5uukfqGxijtTbNMYWUTNlGOFT/DcIKfVvIFbjnadtNgkDgs?= =?us-ascii?q?e6KsRqUa+VeprgCsmOkvFfbd5iBN7cGr79Ny/eCG0EhqrTE=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2AcAgD7KTla//gC91FcGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM+VhB0J48bjhcBAYIBNAGZBC2FDgoChQ1EFAEBAQEBAQEBAQF?= =?us-ascii?q?qKII4JAGCRwEFOhwjEAsYCSUPKh4GE4ovDKttinABAQEBAQEBAwEBAQEBAR0Fg?= =?us-ascii?q?26IfYMwh2cFo0KIAI0ggQCBCpF5jRyLGDYigU9MMAiCZYRYQDeKSwEBAQ?= X-IPAS-Result: =?us-ascii?q?A2AcAgD7KTla//gC91FcGQEBAQEBAQEBAQEBAQcBAQEBAYM?= =?us-ascii?q?+VhB0J48bjhcBAYIBNAGZBC2FDgoChQ1EFAEBAQEBAQEBAQFqKII4JAGCRwEFO?= =?us-ascii?q?hwjEAsYCSUPKh4GE4ovDKttinABAQEBAQEBAwEBAQEBAR0Fg26IfYMwh2cFo0K?= =?us-ascii?q?IAI0ggQCBCpF5jRyLGDYigU9MMAiCZYRYQDeKSwEBAQ?= Received: from 248.2-247-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.247.2.248]) by relay.skynet.be with ESMTP; 19 Dec 2017 16:04:14 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id vBJF4D2f025999; Tue, 19 Dec 2017 16:04:13 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Tue, 19 Dec 2017 16:04:13 +0100 From: Tijl Coosemans To: Hans Petter Selasky Cc: blubee blubeeme , freebsd-multimedia@freebsd.org, Alexander Leidinger Subject: Re: FreeBSD amd64 GENERIC kernel Message-ID: <20171219160413.4055d734@kalimero.tijl.coosemans.org> In-Reply-To: References: <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 15:05:50 -0000 On Tue, 19 Dec 2017 14:53:04 +0100 Hans Petter Selasky wrote: > On 12/19/17 13:57, blubee blubeeme wrote: >> That still leaves my last question unanswered, where does one start >> if they want to program audio applications on FreeBSD? > > You should start by looking at existing OSSv4 compatible audio > applications already in FreeBSD ports and in FreeBSD base and compare > how they use the OSSv4 interface(s). This recent commit suggests that some of the mixer related ioctls are missing: https://svnweb.freebsd.org/changeset/ports/456640 From owner-freebsd-multimedia@freebsd.org Tue Dec 19 16:58:46 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D51BEE90134 for ; Tue, 19 Dec 2017 16:58:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BC89781607 for ; Tue, 19 Dec 2017 16:58:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B907EE90133; Tue, 19 Dec 2017 16:58:46 +0000 (UTC) Delivered-To: multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8A9AE90132 for ; Tue, 19 Dec 2017 16:58:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6C0281606 for ; Tue, 19 Dec 2017 16:58:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBJGwk7S003108 for ; Tue, 19 Dec 2017 16:58:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 224464] audio/faad installs incorrect include/neaacdec.h, which breaks multimedia/libquicktime Date: Tue, 19 Dec 2017 16:58:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mi@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 16:58:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224464 Bug ID: 224464 Summary: audio/faad installs incorrect include/neaacdec.h, which breaks multimedia/libquicktime Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: mi@FreeBSD.org CC: multimedia@FreeBSD.org CC: multimedia@FreeBSD.org The ${LOCALBASE}/include/neaacdec.h installed by audio/faad defines the FAAD2_VERSION as "unknown". This breaks the FAAD2-option of multimedia/libquicktime, because the configure-script tries to parse the FAAD2_VERSION: if(sscanf(FAAD2_VERSION, "%d.%d", &faad_major, &faad_minor) < 2) return -1; The above test fails and the configure declares faad to be unavailable. It = then proceeds to build libquicktime without faad (instead erroring-out) and the = port fails to install, because ${STAGEDIR}${PREFIX}/lib/libquicktime/lqt_faad2.so does not exist. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-multimedia@freebsd.org Tue Dec 19 17:30:29 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9818E92502 for ; Tue, 19 Dec 2017 17:30:29 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A0671F68; Tue, 19 Dec 2017 17:30:29 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id b5so3636467itc.3; Tue, 19 Dec 2017 09:30:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XwsbMY4mp02pzv4BBTSqpxGxptVGqXrY9/OT2qcUwR4=; b=EtPhJBXhPtf9/XWdRW0XQAdJSxk9oxY5d2yqoM9fyO5Yk5QmRc6uQp/PdlS+3BYSHf RuLlHGtNvp2hPYDfO0lhtVVhPlNbDv/p60d2WJXWk9xtaM9hIFdmQ1eNf6iI2pD6TQja tH8NfD6B267WXYIHhuSX0ifWyFgxz+vc/LFGyyeOvTW6VDCuCyIcmmQLUWw462hbg1iR g7XCakxLcZ7l+jF1l+hzo2y5mdwDRqww95t15LkLfay7ayTkPMi7W/sFllFbMGDYkOjl i7694iofT+vq6izqmai0N2eocDJReqD/qhVMce2kTproj5fNdMz97WI+ryNtyoyGJS23 0WiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XwsbMY4mp02pzv4BBTSqpxGxptVGqXrY9/OT2qcUwR4=; b=FXBegdvX5EiTjODftCd8CbV+mhBN9eFCnaWDXGrlFAArKDUfDhqhLUE+bEe+8CEB01 tTPA/c3jhHP2GnN5Pqgmld7KbTy+G7pkU9QF0gj6h+GghqSyi4f9HD912FXBWcRzzxFQ FCVrKfkX22vLTxYSbd1+PMAeok5RCjcb8T7WXta+UeHZRufV+wOI8qKsZjQWTrPV/kfZ 1GPkckCvr2ExgLQTTidDvjmlIRjmkLtcQ6Ng/lONhiGDtxPt55UCI2oXeSplDD9os8Pr z/bEVFKgIsjXmtPJ1ILloFtMF3E5+f19FidYX7N1weFnNdDyR/uWyOebdpm8b0BR+rUU NTpg== X-Gm-Message-State: AKGB3mKbT1X8mdQ8kYXblupF+4boyvUIaB1hlRrum0TYjytzCLGcl4Je C8ZRofCWjn3wzdcXxvlCWA19z56EEgV46gC1pEe+fg== X-Google-Smtp-Source: ACJfBov4IcD5j5zw1Sdz7BE/oISD1DVQYndLh0VDe/54yIdIR3G+xs4pq0PJKeoeNR1eFus2BJ29SHuEH+lYG0biCC8= X-Received: by 10.36.167.77 with SMTP id s13mr4148300iti.51.1513704628244; Tue, 19 Dec 2017 09:30:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Tue, 19 Dec 2017 09:30:26 -0800 (PST) In-Reply-To: <20171219160413.4055d734@kalimero.tijl.coosemans.org> References: <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> <20171219160413.4055d734@kalimero.tijl.coosemans.org> From: blubee blubeeme Date: Wed, 20 Dec 2017 01:30:26 +0800 Message-ID: Subject: Re: FreeBSD amd64 GENERIC kernel To: Tijl Coosemans Cc: Hans Petter Selasky , freebsd-multimedia@freebsd.org, Alexander Leidinger Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 17:30:29 -0000 On Tue, Dec 19, 2017 at 11:04 PM, Tijl Coosemans wrote: > On Tue, 19 Dec 2017 14:53:04 +0100 Hans Petter Selasky > wrote: > > On 12/19/17 13:57, blubee blubeeme wrote: > >> That still leaves my last question unanswered, where does one start > >> if they want to program audio applications on FreeBSD? > > > > You should start by looking at existing OSSv4 compatible audio > > applications already in FreeBSD ports and in FreeBSD base and compare > > how they use the OSSv4 interface(s). > > This recent commit suggests that some of the mixer related ioctls are > missing: https://svnweb.freebsd.org/changeset/ports/456640 > so, this commit message: https://github.com/Maato/volumeicon/pull/70 Why not start from what 4Front OSS provides and then add the features that are missing, instead of re-implementing everything that 4Front provides? From owner-freebsd-multimedia@freebsd.org Tue Dec 19 18:25:44 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64121E96207 for ; Tue, 19 Dec 2017 18:25:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4AB9864757 for ; Tue, 19 Dec 2017 18:25:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 450A1E96205; Tue, 19 Dec 2017 18:25:44 +0000 (UTC) Delivered-To: multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 449DDE96204 for ; Tue, 19 Dec 2017 18:25:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3216D64756 for ; Tue, 19 Dec 2017 18:25:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBJIPhWh098417 for ; Tue, 19 Dec 2017 18:25:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 224464] audio/faad installs incorrect include/neaacdec.h, which breaks multimedia/libquicktime Date: Tue, 19 Dec 2017 18:25:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mi@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 18:25:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224464 --- Comment #1 from Mikhail Teterin --- Created attachment 188978 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188978&action= =3Dedit Explicitly set FAAD2_VERSION, upgrade FWIW, I filed a ticket with the upstream: https://sourceforge.net/p/faac/bugs/236/ Meanwhile, this patch both brute-force fixes this problem and upgrades the = port from the current 2.8.6 to 2.8.8 (the latest upstream release at this time). --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-multimedia@freebsd.org Tue Dec 19 18:26:11 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48EB3E962A3 for ; Tue, 19 Dec 2017 18:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 301DD647D7 for ; Tue, 19 Dec 2017 18:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2F67FE962A1; Tue, 19 Dec 2017 18:26:11 +0000 (UTC) Delivered-To: multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F0E9E962A0 for ; Tue, 19 Dec 2017 18:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1832B647D6 for ; Tue, 19 Dec 2017 18:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBJIQAKL099093 for ; Tue, 19 Dec 2017 18:26:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 224464] audio/faad installs incorrect include/neaacdec.h, which breaks multimedia/libquicktime Date: Tue, 19 Dec 2017 18:26:11 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: easy, patch-ready X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mi@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 18:26:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224464 Mikhail Teterin changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |easy, patch-ready --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-multimedia@freebsd.org Tue Dec 19 19:13:11 2017 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4DDBE9900A for ; Tue, 19 Dec 2017 19:13:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 771E0669F7; Tue, 19 Dec 2017 19:13:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id D30202601A5; Tue, 19 Dec 2017 20:13:07 +0100 (CET) Subject: Re: FreeBSD amd64 GENERIC kernel To: blubee blubeeme , Tijl Coosemans Cc: freebsd-multimedia@freebsd.org, Alexander Leidinger References: <20171216143349.Horde.VJOddyv79ydlAmvsvoTRhMP@webmail.leidinger.net> <20171218161614.Horde.rLEhw6yp6nTppNjkXU-WxBF@webmail.leidinger.net> <20171218183353.Horde.xayrSeFXKKiQwenaLS-GOsK@webmail.leidinger.net> <20171219122952.Horde.2UnAC3-TFrteTTD2_YJXPpJ@webmail.leidinger.net> <603cca63-2689-432e-dd07-d08bf8e1ee4c@selasky.org> <20171219160413.4055d734@kalimero.tijl.coosemans.org> From: Hans Petter Selasky Message-ID: <4744f602-85fb-2dc9-af17-77e815ef81e7@selasky.org> Date: Tue, 19 Dec 2017 20:10:19 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 19:13:11 -0000 On 12/19/17 18:30, blubee blubeeme wrote: > Why not start from what 4Front OSS provides and then add the features that > are missing, > instead of re-implementing everything that 4Front provides? Hi Blubee, Try to answer the questions already presented in this e-mail thread. --HPS