From owner-freebsd-arm@freebsd.org Wed Dec 19 06:14:44 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0259F134CC62; Wed, 19 Dec 2018 06:14:44 +0000 (UTC) (envelope-from bscott@bunyatech.com.au) Received: from ppp150-101-221-139.static.internode.on.net (2001-44b8-4170-0a00-0000-0000-0000-0002.static.ipv6.internode.on.net [IPv6:2001:44b8:4170:a00::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "150.101.221.139", Issuer "Bunya Technology Certification Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D3B36B627; Wed, 19 Dec 2018 06:14:41 +0000 (UTC) (envelope-from bscott@bunyatech.com.au) X-Clacks-Overhead: GNU Terry Pratchett Received: from DHCP.tawonga.bunyatech.com.au (DHCP.tawonga.bunyatech.com.au [10.0.1.78] (may be forged)) by cope.tawonga.bunyatech.com.au (8.15.2/8.15.2/MSA) with ESMTPS id wBJ6E7So005848 (version=TLSv1.2 cipher=AES128-SHA bits=128 verify=OK); Wed, 19 Dec 2018 17:14:08 +1100 (AEDT) (envelope-from bscott@bunyatech.com.au) Subject: Re: RPI3 sound for www/chromium, was Re: How much memory to compile www/chromium? To: Jan Beich , bob prohaska Cc: Jamie Landeg-Jones , freebsd-arm@freebsd.org, freebsd-ports@freebsd.org References: <20181212165313.GA84881@www.zefox.net> <20181212184149.ol44fon2unowu35q@squirrel.exwg.net> <20181212192115.GA85583@www.zefox.net> <20181212202504.4n3mhtx7grbeh6j7@squirrel.exwg.net> <20181214012733.GA92808@www.zefox.net> <20181218174903.GA41072@www.zefox.net> <201812182341.wBINfiX4052421@donotpassgo.dyslexicfish.net> <20181219014342.GA42859@www.zefox.net> From: Brian Scott Message-ID: <233863b5-f748-2c2e-976f-110ab49e4675@bunyatech.com.au> Date: Wed, 19 Dec 2018 17:14:07 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 06:14:44 -0000 On 19/12/18 4:49 pm, Jan Beich wrote: > bob prohaska writes: > >> On Tue, Dec 18, 2018 at 11:41:44PM +0000, Jamie Landeg-Jones wrote: >> >>> bob prohaska wrote: >>> >>>> Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile successfully over >>>> several days. The -DBATCH option was used, in hopes it'd fetch the right options. >>> Use "make config-recursive" before you start. It will present to you upfront all >>> the option screens that would appear during the build. >>> >>> I've noticed it sometimes misses some, if you add some dependency in one of the menus. >>> So to be sure, once it's finished its run, if you've made any option changes, run >>> it again, and again and again etc.. until you no longer get menus popping up. >>> >> That's a good idea provided one knows beforehand which options to select. I very >> seldom know which options apply, especially on the first try. After a few failures >> my guesses sometimes improve.... >> >> In the case of www/chromium it looks like the sound support is wrong, but so far >> it isn't obvious which sound option is correct. Would anybody hazard a guess >> as to what sound support works on a Pi3? >> >> The clearest hint so far is a report of >> ALSA lib pcm_oss.c:835:(_snd_pcm_oss_open) Cannot open device /dev/dsp >> when starting up chrome. > According to https://svnweb.freebsd.org/changeset/base/222980 sound(4) > was enabled by default only on x86 archs. 7 years later however things have thankfully progressed a little. Sound output works fine on other RPIs (in particular the original B that I have). I believe the problem now is that support for builtin sound on the RPI3 is still a work in progress (it goes through the HDMI subsystem and I think it was a 32 vs. 64 bit issue but is a mystery to me beyond that). USB based sound adapters work fine for the most part. There were some posts recently on the list about full speed/high speed devices and limitations in buffer size that you might want to have a look at. The RPIs don't have any native sound input so the USB solutions might be a better idea anyway if you need input. I'm looking forward to hearing how you go with chromium. I, and  I suspect a lot of other people would like to see a web browser better than lynx on the Raspberry Pi (even without sound but I suspect that will work with other hardware). Good luck with your work, Brian