From owner-freebsd-arm@freebsd.org Sun Jun 2 02:44:31 2019 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 D523315A809E for ; Sun, 2 Jun 2019 02:44:31 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 257DE87901 for ; Sun, 2 Jun 2019 02:44:31 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id x522Vbpp062921 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 Jun 2019 19:31:39 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x522VYrv062918; Sat, 1 Jun 2019 19:31:34 -0700 (PDT) (envelope-from fbsd) Date: Sat, 1 Jun 2019 19:31:34 -0700 From: bob prohaska To: Jack Raats Cc: FreeBSD ARM Subject: Re: Updating FreeBSD 12.0 on a raspberry pi 3 B+ Message-ID: <20190602023134.GA61533@www.zefox.net> References: <84111DA7-4313-4DF7-A7F8-1E613499AE4F@nlned.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84111DA7-4313-4DF7-A7F8-1E613499AE4F@nlned.nl> User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 257DE87901 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.04 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.81)[0.813,0]; IP_SCORE(0.10)[ip: (0.40), ipnet: 50.1.16.0/20(0.20), asn: 7065(-0.03), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.69)[0.694,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: www.zefox.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.54)[0.540,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[] 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: Sun, 02 Jun 2019 02:44:32 -0000 On Sat, Jun 01, 2019 at 10:33:00PM +0200, Jack Raats wrote: > Hi > > > > I want to update FreeBSD on a raspberry pi 3 B+ > > > Or is there another way? > Have you considered building from source? It's a hassle, but it does work, at least most of the time..... 8-) bob prohaska From owner-freebsd-arm@freebsd.org Sun Jun 2 03:29:05 2019 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 445E115A95EC for ; Sun, 2 Jun 2019 03:29:05 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [104.236.120.189]) (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 4E7E888FDE for ; Sun, 2 Jun 2019 03:29:04 +0000 (UTC) (envelope-from karl@denninger.net) Received: from denninger.net (ip68-1-57-197.pn.at.cox.net [68.1.57.197]) by colo1.denninger.net (Postfix) with ESMTP id D1BA9211080 for ; Sat, 1 Jun 2019 23:28:57 -0400 (EDT) Received: from [192.168.10.30] (unknown [192.168.10.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id 41A4FF4A2B for ; Sat, 1 Jun 2019 22:28:57 -0500 (CDT) Subject: Re: Updating FreeBSD 12.0 on a raspberry pi 3 B+ To: freebsd-arm@freebsd.org References: <84111DA7-4313-4DF7-A7F8-1E613499AE4F@nlned.nl> From: Karl Denninger Openpgp: preference=signencrypt Autocrypt: addr=karl@denninger.net; prefer-encrypt=mutual; keydata= mQINBFIX1zsBEADRcJfsQUl9oFeoMfLPJ1kql+3sIaYx0MfJAUhV9LnbWxr0fsWCskM1O4cV tHm5dqPkuPM4Ztc0jLotD1i9ubWvCHOlkLGxFOL+pFbjA+XZ7VKsC/xWmhMwJ3cM8HavK2OV SzEWQ/AEYtMi04IzGSwsxh/5/5R0mPHrsIomV5SbuiI0vjLuDj7fo6146AABI1ULzge4hBYW i/SHrqUrLORmUNBs6bxek79/B0Dzk5cIktD3LOfbT9EAa5J/osVkstMBhToJgQttaMIGv8SG CzpR/HwEokE+7DP+k2mLHnLj6H3kfugOF9pJH8Za4yFmw//s9cPXV8WwtZ2SKfVzn1unpKqf wmJ1PwJoom/d4fGvQDkgkGKRa6RGC6tPmXnqnx+YX4iCOdFfbP8L9rmk2sewDDVzHDU3I3ZZ 8hFIjMYM/QXXYszRatK0LCV0QPZuF7LCf4uQVKw1/oyJInsnH7+6a3c0h21x+CmSja9QJ+y0 yzgEN/nM89d6YTakfR+1xkYgodVmMy/bS8kmXbUUZG/CyeqCqc95RUySjKT2ECrf9GhhoQkl +D8n2MsrAUSMGB4GQSN+TIq9OBTpNuvATGSRuF9wnQcs1iSry+JNCpfRTyWp83uCNApe6oHU EET4Et6KDO3AvjvBMAX0TInTRGW2SQlJMuFKpc7Dg7tHK8zzqQARAQABtCNLYXJsIERlbm5p bmdlciA8a2FybEBkZW5uaW5nZXIubmV0PokCPAQTAQIAJgUCUhfXOwIbIwUJCWYBgAYLCQgH AwIEFQIIAwQWAgMBAh4BAheAAAoJEG6/sivc5s0PLxQP/i6x/QFx9G4Cw7C+LthhLXIm7NSH AtNbz2UjySEx2qkoQQjtsK6mcpEEaky4ky6t8gz0/SifIfJmSmyAx0UhUQ0WBv1vAXwtNrQQ jJd9Bj6l4c2083WaXyHPjt2u2Na6YFowyb4SaQb83hu/Zs25vkPQYJVVE0JX409MFVPUa6E3 zFbd1OTr3T4yNUy4gNeQZfzDqDS8slbIks2sXeoJrZ6qqXVI0ionoivOlaN4T6Q0UYyXtigj dQvvhMt0aNowKFjRqrmSDRpdz+o6yg7Mp7qEZ1V6EZk8KqQTH6htpCTQ8i79ttK4LG6bstSF Re6Fwq52nbrcANrcdmtZXqjo+SGbUqJ8b1ggrxAsJ5MEhRh2peKrCgI/TjQo+ZxfnqEoR4AI 46Cyiz+/lcVvlvmf2iPifS3EEdaH3Itfwt7MxFm6mQORYs6skHDw3tOYB2/AdCW6eRVYs2hB RMAG4uwApZfZDKgRoE95PJmQjeTBiGmRPcsQZtNESe7I7EjHtCDLwtJqvD4HkDDQwpzreT6W XkyIJ7ns7zDfA1E+AQhFR6rsTFGgQZRZKsVeov3SbhYKkCnVDCvb/PKQCAGkSZM9SvYG5Yax 8CMry3AefKktf9fqBFg8pWqtVxDwJr56dhi0GHXRu3jVI995rMGo1fLUG5fSxiZ8L5sAtokh 9WFmQpyl Message-ID: <2b195029-6ce8-8e55-aa0f-93de140a98a3@denninger.net> Date: Sat, 1 Jun 2019 22:28:56 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <84111DA7-4313-4DF7-A7F8-1E613499AE4F@nlned.nl> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms040202080701010909030905" X-Rspamd-Queue-Id: 4E7E888FDE X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.52 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[px.denninger.net]; NEURAL_HAM_SHORT(-0.70)[-0.704,0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-2.60)[ip: (-9.88), ipnet: 104.236.64.0/18(-4.25), asn: 14061(1.17), country: US(-0.06)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:14061, ipnet:104.236.64.0/18, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[197.57.1.68.zen.spamhaus.org : 127.0.0.11]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; SIGNED_SMIME(-2.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[denninger.net]; R_SPF_NA(0.00)[] X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sun, 02 Jun 2019 03:29:05 -0000 This is a cryptographically signed message in MIME format. --------------ms040202080701010909030905 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 6/1/2019 15:33, Jack Raats wrote: > Hi > =20 > > I want to update FreeBSD on a raspberry pi 3 B+ > > > On a VPS with lots of cores and RAM I build FreeBSD using crochet. Ever= y night I make an image, which can be downloaded at www.jarasoft.net/rpi > > The raspberry pi is running FreeBSD 12.0-STABLE build a fee weeks ago a= nd now I want to update this working FreeBSD. > > I could make a new image and install everything from the start but that= will take a lot of time or can this be automated? > > On the other end I could use the builded binaries from my VPS, copy the= m to the Pi and run make install kernel and make install world? > > Is this being done???=20 > > Or is there another way? > IF all of the below are true: 1. Both old and new are built with Crochet. 2. The size of the system partition is the same, and the packages, if any, that are included are compatible. 3. Local changes are all saved to the mounted configuration directory, which is copied to RAMdisk on boot. THEN You can replace the system image with a new one, OR you can copy the /cfg directory from the old to the new image, and perform the update this way. I do this with a production distribution.=C2=A0 Note that all three of th= e above have to be true or unexpected things are likely to happen. Crochet builds typically do not have a "ping-pong" system partition (that is, two of them with one set to be the active, booted one) so you can't update "in place" without special consideration.=C2=A0 If you DO bu= ild with a "ping-pong" configuration, and have a system that can boot from the "active" set one, then you can do it this way as well (load the new system image in the not-active system partition, change the active, reboot) but the above three considerations apply (the new build has to fit in the space available, basically.) --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms040202080701010909030905 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC DdgwggagMIIEiKADAgECAhMA5EiKghDOXrvfxYxjITXYDdhIMA0GCSqGSIb3DQEBCwUAMIGL MQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJTmljZXZpbGxlMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExITAf BgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQTAeFw0xNzA4MTcxNjQyMTdaFw0yNzA4 MTUxNjQyMTdaMHsxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkwFwYDVQQKDBBD dWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExJTAjBgNVBAMMHEN1 ZGEgU3lzdGVtcyBMTEMgMjAxNyBJbnQgQ0EwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIK AoICAQC1aJotNUI+W4jP7xQDO8L/b4XiF4Rss9O0B+3vMH7Njk85fZ052QhZpMVlpaaO+sCI KqG3oNEbuOHzJB/NDJFnqh7ijBwhdWutdsq23Ux6TvxgakyMPpT6TRNEJzcBVQA0kpby1DVD 0EKSK/FrWWBiFmSxg7qUfmIq/mMzgE6epHktyRM3OGq3dbRdOUgfumWrqHXOrdJz06xE9NzY vc9toqZnd79FUtE/nSZVm1VS3Grq7RKV65onvX3QOW4W1ldEHwggaZxgWGNiR/D4eosAGFxn uYeWlKEC70c99Mp1giWux+7ur6hc2E+AaTGh+fGeijO5q40OGd+dNMgK8Es0nDRw81lRcl24 SWUEky9y8DArgIFlRd6d3ZYwgc1DMTWkTavx3ZpASp5TWih6yI8ACwboTvlUYeooMsPtNa9E 6UQ1nt7VEi5syjxnDltbEFoLYcXBcqhRhFETJe9CdenItAHAtOya3w5+fmC2j/xJz29og1KH YqWHlo3Kswi9G77an+zh6nWkMuHs+03DU8DaOEWzZEav3lVD4u76bKRDTbhh0bMAk4eXriGL h4MUoX3Imfcr6JoyheVrAdHDL/BixbMH1UUspeRuqQMQ5b2T6pabXP0oOB4FqldWiDgJBGRd zWLgCYG8wPGJGYgHibl5rFiI5Ix3FQncipc6SdUzOQIDAQABo4IBCjCCAQYwHQYDVR0OBBYE FF3AXsKnjdPND5+bxVECGKtc047PMIHABgNVHSMEgbgwgbWAFBu1oRhUMNEzjODolDka5k4Q EDBioYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJ TmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5 c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYIJAKxAy1WBo2kY MBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4IC AQCB5686UCBVIT52jO3sz9pKuhxuC2npi8ZvoBwt/IH9piPA15/CGF1XeXUdu2qmhOjHkVLN gO7XB1G8CuluxofOIUce0aZGyB+vZ1ylHXlMeB0R82f5dz3/T7RQso55Y2Vog2Zb7PYTC5B9 oNy3ylsnNLzanYlcW3AAfzZcbxYuAdnuq0Im3EpGm8DoItUcf1pDezugKm/yKtNtY6sDyENj tExZ377cYA3IdIwqn1Mh4OAT/Rmh8au2rZAo0+bMYBy9C11Ex0hQ8zWcvPZBDn4v4RtO8g+K uQZQcJnO09LJNtw94W3d2mj4a7XrsKMnZKvm6W9BJIQ4Nmht4wXAtPQ1xA+QpxPTmsGAU0Cv HmqVC7XC3qxFhaOrD2dsvOAK6Sn3MEpH/YrfYCX7a7cz5zW3DsJQ6o3pYfnnQz+hnwLlz4MK 17NIA0WOdAF9IbtQqarf44+PEyUbKtz1r0KGeGLs+VGdd2FLA0e7yuzxJDYcaBTVwqaHhU2/ Fna/jGU7BhrKHtJbb/XlLeFJ24yvuiYKpYWQSSyZu1R/gvZjHeGb344jGBsZdCDrdxtQQcVA 6OxsMAPSUPMrlg9LWELEEYnVulQJerWxpUecGH92O06wwmPgykkz//UmmgjVSh7ErNvL0lUY UMfunYVO/O5hwhW+P4gviCXzBFeTtDZH259O7TCCBzAwggUYoAMCAQICEwCg0WvVwekjGFiO 62SckFwepz0wDQYJKoZIhvcNAQELBQAwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3Jp ZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBD QTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExMQyAyMDE3IEludCBDQTAeFw0xNzA4MTcyMTIx MjBaFw0yMjA4MTYyMTIxMjBaMFcxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRswGQYDVQQDDBJrYXJsQGRlbm5pbmdlci5uZXQw ggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC+HVSyxVtJhy3Ohs+PAGRuO//Dha9A 16l5FPATr6wude9zjX5f2lrkRyU8vhCXTZW7WbvWZKpcZ8r0dtZmiK9uF58Ec6hhvfkxJzbg 96WHBw5Fumd5ahZzuCJDtCAWW8R7/KN+zwzQf1+B3MVLmbaXAFBuKzySKhKMcHbK3/wjUYTg y+3UK6v2SBrowvkUBC+jxNg3Wy12GsTXcUS/8FYIXgVVPgfZZrbJJb5HWOQpvvhILpPCD3xs YJFNKEPltXKWHT7Qtc2HNqikgNwj8oqOb+PeZGMiWapsatKm8mxuOOGOEBhAoTVTwUHlMNTg 6QUCJtuWFCK38qOCyk9Haj+86lUU8RG6FkRXWgMbNQm1mWREQhw3axgGLSntjjnznJr5vsvX SYR6c+XKLd5KQZcS6LL8FHYNjqVKHBYM+hDnrTZMqa20JLAF1YagutDiMRURU23iWS7bA9tM cXcqkclTSDtFtxahRifXRI7Epq2GSKuEXe/1Tfb5CE8QsbCpGsfSwv2tZ/SpqVG08MdRiXxN 5tmZiQWo15IyWoeKOXl/hKxA9KPuDHngXX022b1ly+5ZOZbxBAZZMod4y4b4FiRUhRI97r9l CxsP/EPHuuTIZ82BYhrhbtab8HuRo2ofne2TfAWY2BlA7ExM8XShMd9bRPZrNTokPQPUCWCg CdIATQIDAQABo4IBzzCCAcswPAYIKwYBBQUHAQEEMDAuMCwGCCsGAQUFBzABhiBodHRwOi8v b2NzcC5jdWRhc3lzdGVtcy5uZXQ6ODg4ODAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIF oDAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMDMGCWCG SAGG+EIBDQQmFiRPcGVuU1NMIEdlbmVyYXRlZCBDbGllbnQgQ2VydGlmaWNhdGUwHQYDVR0O BBYEFLElmNWeVgsBPe7O8NiBzjvjYnpRMIHKBgNVHSMEgcIwgb+AFF3AXsKnjdPND5+bxVEC GKtc047PoYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UE BwwJTmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRh IFN5c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYITAORIioIQ zl6738WMYyE12A3YSDAdBgNVHREEFjAUgRJrYXJsQGRlbm5pbmdlci5uZXQwDQYJKoZIhvcN AQELBQADggIBAJXboPFBMLMtaiUt4KEtJCXlHO/3ZzIUIw/eobWFMdhe7M4+0u3te0sr77QR dcPKR0UeHffvpth2Mb3h28WfN0FmJmLwJk+pOx4u6uO3O0E1jNXoKh8fVcL4KU79oEQyYkbu 2HwbXBU9HbldPOOZDnPLi0whi/sbFHdyd4/w/NmnPgzAsQNZ2BYT9uBNr+jZw4SsluQzXG1X lFL/qCBoi1N2mqKPIepfGYF6drbr1RnXEJJsuD+NILLooTNf7PMgHPZ4VSWQXLNeFfygoOOK FiO0qfxPKpDMA+FHa8yNjAJZAgdJX5Mm1kbqipvb+r/H1UAmrzGMbhmf1gConsT5f8KU4n3Q IM2sOpTQe7BoVKlQM/fpQi6aBzu67M1iF1WtODpa5QUPvj1etaK+R3eYBzi4DIbCIWst8MdA 1+fEeKJFvMEZQONpkCwrJ+tJEuGQmjoQZgK1HeloepF0WDcviiho5FlgtAij+iBPtwMuuLiL shAXA5afMX1hYM4l11JXntle12EQFP1r6wOUkpOdxceCcMVDEJBBCHW2ZmdEaXgAm1VU+fnQ qS/wNw/S0X3RJT1qjr5uVlp2Y0auG/eG0jy6TT0KzTJeR9tLSDXprYkN2l/Qf7/nT6Q03qyE QnnKiBXWAZXveafyU/zYa7t3PTWFQGgWoC4w6XqgPo4KV44OMYIFBzCCBQMCAQEwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBglghkgBZQMEAgMFAKCCAkUw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTkwNjAyMDMyODU2 WjBPBgkqhkiG9w0BCQQxQgRAk9ahgQFGPk8+3OQs2ydUfr2daLtU+69TDbigPAvkr2tbVbgB Q1GeA4IgKKN7eQLCtdo3W39CWSdUjaLrLs7Y5TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFl AwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3 DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGjBgkrBgEEAYI3EAQxgZUwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTCBpQYLKoZIhvcNAQkQAgsxgZWg gZIwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lz dGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0 ZW1zIExMQyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBgkqhkiG9w0BAQEF AASCAgCjrk2MrymLysbbbmkNeQ7232Psge/9AdjJEW6pljxcZltovOO4g6k2wlhEyKZR4gC+ MrOv8P6Ik4WrZa6IcRprszz1TNc+njFld4PRChIzyaNa82IrkV8nPjFmBgxW1A2VKcf6HHCg RGuxTNFpSWOZrAoN9fMUC/mIxPdLMVkZSp/TvjwyMzTEMIPb9Ii4ZmKobWyrl2kMwThx+GpA w8iK69wNLYn5yhZBT2e34fyez0H6rXmsqroFBj0UKmOcCCmjFS/b2M0yXuCamFV/tMV6o5iv Vw8IEdL+EzyyBf9zSVgzmiyTwUekkXEEvan2HR0FNviDpSyQH4i4mr62Z04rkG+OzaciwsQ4 HVY0tudS99+K8n9WZPNoz4ZApPKDawyClh/t29oEwQauqfwr4lz6EU5i+GQxPRodQ/Vl3sbO CApvmshjnGoLRjd4OBuWGx6Iexko2ACBfrIWwlY9fc9GpKB/xqzQayvMxn2ZM+XcJabCCf5L 25KLJAIcZVJIb2QUMcCiaPTI87IXp+NYHtjx3AoB6OndZym17mrueG6YccP1HL+Unc6URjOW /u8u9y3kjvfx0On8njzwIOuNVnpjJ03OXZD83zCjE6Vn3zH2ZqpTZFILcuX+5V7YiYC2lErd YRBloF3iDslPrbYx7vEQFSeS5XDeUmPoCj5xIpGpxAAAAAAAAA== --------------ms040202080701010909030905-- From owner-freebsd-arm@freebsd.org Sun Jun 2 16:40:53 2019 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 754BD15B9DD0 for ; Sun, 2 Jun 2019 16:40:53 +0000 (UTC) (envelope-from deepcore.dk@gmail.com) Received: from mail-ed1-x542.google.com (mail-ed1-x542.google.com [IPv6:2a00:1450:4864:20::542]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 34DC46EE30 for ; Sun, 2 Jun 2019 16:40:52 +0000 (UTC) (envelope-from deepcore.dk@gmail.com) Received: by mail-ed1-x542.google.com with SMTP id r18so22179512edo.7 for ; Sun, 02 Jun 2019 09:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=u0Cxy3NDUxJsOckiqmzZyNf6V2a+WO28aOMw4XgMqwQ=; b=GA2PcQk/XR2bCAmr3uo1z8Q766n9lJ94olfq0NvxAgbRv7EIk7A7DSvWMyAYpGzeKg CRDKb7mlyswnTRFEIY69B9AvOkERHLsGH+bTtkld2l8fExoBmLBmSijAePZ1FuZ17dj6 YARarRR0yLe3vJ69g+ofp48xkU1mNhaq1s81PG2IDseAw2QwmRRjENB19LasTcgAtRlN 8v0clsde4UqURvtGEt4AsxNW3cnI6eJHx79CuhhL26eGf5H9G79AvSW1oTtCROuPNN85 ZxQm8ncRxcHN6fIwX8z6ML9S1Ud0XhuJbKxtLGB7DKiul32uGWE+/pmtcEoBiosPxhRA SDug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=u0Cxy3NDUxJsOckiqmzZyNf6V2a+WO28aOMw4XgMqwQ=; b=hbMeYjjRa9s404kDEjt/TNj6BeC7esMy9P2EroV+294K0FI+HgGEz6SSp0f56ZqQAA G21a0/87Wm7yIg/Nv7k2XzouNM+KsoMMIVKNSE+u159b4ung6m+vXaZ7o8b1vI3chCWq FP3sJhw7oPm8uybXlXZ7pnutcZZ4kmemVqENkVqLQ6mWJb083BUDDt+z/CFaXiw6F5va SdFEGXvsEKQ9CNq1y1NcVtdLsCUCFh/a6aFV/wpoTwtyArFcyRv1vLIFT2WhG+Mfp5it XUvkJH0aJSHb/xU8fOZX0dQdOaukJJ/xo1QbR9/Y3gfmQ/5ftG7sb1StwjF49CfLrKDl UeYA== X-Gm-Message-State: APjAAAVtvDGvueurhO4a3iRH5R4JNr6xXwxMP00szOE8wbi4TUHe2kxn a3gHMJgba48dJhuzutZyYd5LHJEP X-Google-Smtp-Source: APXvYqyyBAcJrto35FKgME75E/q0DfZ+iagXLnDYuoBFwQ3BjXnAU9ZL1azTnPMZ9rO4bKPKvjceRA== X-Received: by 2002:a17:906:6a87:: with SMTP id p7mr358808ejr.277.1559493651046; Sun, 02 Jun 2019 09:40:51 -0700 (PDT) Received: from mac.deepcore.dk ([85.27.186.9]) by smtp.gmail.com with ESMTPSA id d24sm2111038ejt.12.2019.06.02.09.40.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Jun 2019 09:40:49 -0700 (PDT) From: "=?utf-8?Q?S=C3=B8ren_Schmidt?=" X-Google-Original-From: =?utf-8?Q?S=C3=B8ren_Schmidt?= Message-Id: <7CDBFAF1-C36F-4A2D-8D80-CFF1F03CD2B9@deepcore.dk> Content-Type: multipart/signed; boundary="Apple-Mail=_9E72E6D9-85C3-491E-9568-2C3A87BE4C54"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Espressobin anyone ? Date: Sun, 2 Jun 2019 18:40:48 +0200 In-Reply-To: <9B48E915-C705-4582-837B-C92B40AD63EB@westryn.net> Cc: "freebsd-arm@freebsd.org" , James Shuriff , Marcin Wojtas To: Kim Shrier References: <334C83B6-1F12-436A-866B-947977A34D4D@deepcore.dk> <051F7682-B3EC-49D8-B52A-2A8C75BEE757@gmail.com> <9B48E915-C705-4582-837B-C92B40AD63EB@westryn.net> X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 34DC46EE30 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=GA2PcQk/; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of deepcoredk@gmail.com designates 2a00:1450:4864:20::542 as permitted sender) smtp.mailfrom=deepcoredk@gmail.com X-Spamd-Result: default: False [-5.51 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; HAS_ATTACHMENT(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.93)[-0.928,0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-0.97)[ip: (-0.31), ipnet: 2a00:1450::/32(-2.20), asn: 15169(-2.28), country: US(-0.06)] X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sun, 02 Jun 2019 16:40:54 -0000 --Apple-Mail=_9E72E6D9-85C3-491E-9568-2C3A87BE4C54 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi I managed to get it to boot with the following: setenv fdt_name 'efi/boot/armada-3720-espressobin.dtb' setenv image_name 'efi/boot/bootaa64.efi' setenv bootmmc 'mmc dev 0; fatload mmc 0:1 $kernel_addr = $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $kernel_addr = $fdt_addr' run bootmmc Then when the FreeBSD loader fails to load the kernel enter: set currdev=3Ddisk0p2 Boot That will boot the kernel: /boot/kernel/kernel text=3D0x92aab0 data=3D0x190f48+0x84ab1c = syms=3D[0x8+0x137580+0x8+0x12372b] Using DTB provided by EFI at 0x8000000. ---<>--- KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2019 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-CURRENT r348210 GENERIC arm64 FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on = LLVM 8.0.0) WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. Starting CPU 1 (1) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs arc4random: WARNING: initial seeding bypassed the cryptographic random = device because it was not yet seeded and the knob = 'bypass_before_seeding' was enabled. random: entropy device external interface MAP 3e679000 mode 2 pages 1 MAP 3ffa6000 mode 2 pages 1 kbd0 at kbdmux0 ofwbus0: simplebus0: on ofwbus0 simplebus1: on simplebus0 psci0: on ofwbus0 gic0: mem = 0x1d00000-0x1d0ffff,0x1d40000-0x1d7ffff irq 37 on simplebus1 generic_timer0: irq 0,1,2,3 on ofwbus0 Timecounter "ARM MPCore Timecounter" frequency 12500000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 12500000 Hz quality 1000 cpulist0: on ofwbus0 cpu0: on cpulist0 cpu1: on cpulist0 uart0: mem 0x12000-0x123ff irq 8 on = simplebus1 uart0: console (115200,n,8,1) mvneta0: mem 0x30000-0x33fff irq 10 on simplebus1 mvneta0: version is 10 mvneta0: Ethernet address: f0:ad:4e:08:61:5e mvneta1: mem 0x40000-0x43fff irq 11 on simplebus1 mvneta1: Failed to acquire PHY mode from FDT. device_attach: mvneta1 attach returned 6 xhci0: mem 0x58000-0x5bfff irq 31 on = simplebus1 xhci0: 32 bytes context size, 32-bit DMA usbus0 on xhci0 ehci0: mem 0x5e000-0x5ffff irq = 33 on simplebus1 usbus1: EHCI version 1.0 usbus1 on ehci0 sdhci_xenon0: mem = 0xd0000-0xd02ff,0x1e808-0x1e80b irq 34 on simplebus1 sdhci_xenon1: mem = 0xd8000-0xd82ff,0x17808-0x1780b irq 35 on simplebus1 ahci0: mem 0xe0000-0xe1fff irq 36 on simplebus1 ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with FBS ahcich0: at channel 0 on ahci0 cryptosoft0: Timecounters tick every 1.000 msec mvneta0: link state changed to UP usbus0: 5.0Gbps Super Speed USB v3.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on = usbus0 ugen1.1: at usbus1 uhub1: on = usbus1 Release APs...done CPU 0: ARM Cortex-A53 r0p4 affinity: 0 Instruction Set Attributes 0 =3D Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]... Instruction Set Attributes 1 =3D <> Root mount waiting for: Processor Features 0 =3D = usbus1 Processor Features 1 =3D <0> usbus0 Memory Model Features 0 =3D <4k Granule,64k Granule,S/NS = Mem,MixedEndian,16bit ASID,1TB PA> Memory Model Features 1 =3D <> Memory Model Features 2 =3D <32b CCIDX,48b VA> Debug Features 0 =3D <2 CTX Breakpoints,4 Watchpoints,6 = Breakpoints,PMUv3,Debug v8> Debug Features 1 =3D <0> Auxiliary Features 0 =3D <0> Auxiliary Features 1 =3D <0> CPU 1: ARM Cortex-A53 r0p4 affinity: 1 WARNING: WITNESS option enabled, expect reduced performance. uhub0: 2 ports with 2 removable, self powered uhub1: 1 port with 1 removable, self powered mountroot: waiting for device /dev/ufs/FreeBSD_Install... Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. Loader variables: vfs.root.mountfrom=3Dufs:/dev/ufs/FreeBSD_Install vfs.root.mountfrom.options=3Dro,noatime Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:zroot/ROOT/default cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> However, the MMC/SDcard fails to be found so it will stop at mounting = root. Having a disk on the SATA port can make it work from there though. The etherswitch is not found, but the single =E2=80=9Cnata=E2=80=9D port = does show up.. All in all the support is barely enough to boot a kernel, but a long way = from being useful. You can use 12-stable as well, the same support seems to be present = there, and its much more stable, -current as is today panics=E2=80=A6 Oh, and you need to get the =E2=80=9Cright=E2=80=9D .dtb file, otherwise = you get panic=E2=80=99s etc. YMMV=E2=80=A6 -S=C3=B8ren --Apple-Mail=_9E72E6D9-85C3-491E-9568-2C3A87BE4C54 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkC0kEuD0Me2xEj5EGvRMAY4qbRsFAlzz/BAACgkQGvRMAY4q bRvEPRAAjqAYdCM5LbGNvUew7bJSPlA6SqQ0NGpPl5bhWJenlXgE4tnTAkkjZ0Mx tEzBOQhX7RE0HXNQzjQcI7jfA8lSlu03EI+2AAyULqTqs3wfja1LMizVRsfjxx/Y eT4Xuls8LYmgawcJumyX4OlXyM4vEj2zn/d5vX50pm1ZrXgjpKhHvbKSikE91M1P z98Lt6OIP50oYzciEf67ZkXXQyBhddEdq/99RWlVM7QtesIxM9+glniXXborwa2r 28vSCwh8IYXpTOvbQJuTXUOjaYMSis3AHNAqDhiv6NQRUxk8pWgApYwTbmZFPj9Y kgTVpE3afAl/DFotJwkNRiOccD7LO5X5z1xM5Ys/x5WMTw8G8fMMsCLWNTr0h2+9 lLQyL3W3Xh4Jax5FpuEVj228lK82pe6hLUAJxrsCyMehq3FHVvz/XcIoFjy9HGfw Gla3hekWPBoHorhynIQdzjKvu0bwyD1R3UQ8ouAJgfw2cPJq2ypZ663EJ5KWgdoA oSXOMJ5mBfaMATa6pjeOi6MMmDws6MAU/ycSmP1DavQ7efZHgFy5INtTT5okXO96 E/Z6HJ2qnLZC+OECHD7P2jJaf+nItM2zeXa7YMNBtWBHlo1Br1OBsREb0xa+ZjM6 iMQAikZuYxkpZcmJLTx3VpVW4c3C3aXGkyprzFKszG4TWE1JJc8= =68/B -----END PGP SIGNATURE----- --Apple-Mail=_9E72E6D9-85C3-491E-9568-2C3A87BE4C54-- From owner-freebsd-arm@freebsd.org Sun Jun 2 21:34:20 2019 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 B021315C1131 for ; Sun, 2 Jun 2019 21:34:20 +0000 (UTC) (envelope-from kim@westryn.net) Received: from mail.westryn.net (mail.westryn.net [199.48.135.251]) (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 6231781F05 for ; Sun, 2 Jun 2019 21:34:19 +0000 (UTC) (envelope-from kim@westryn.net) Received: from client20.westryn.net (225x169.ouraynet.com [204.16.225.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.westryn.net (Postfix) with ESMTPSA id 01E10943258; Sun, 2 Jun 2019 15:34:10 -0600 (MDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Espressobin anyone ? From: Kim Shrier In-Reply-To: <7CDBFAF1-C36F-4A2D-8D80-CFF1F03CD2B9@deepcore.dk> Date: Sun, 2 Jun 2019 15:34:09 -0600 Cc: "freebsd-arm@freebsd.org" , James Shuriff , Marcin Wojtas Content-Transfer-Encoding: quoted-printable Message-Id: <12BC81D2-C7E8-4F76-97C4-AA1DC7FA4E66@westryn.net> References: <334C83B6-1F12-436A-866B-947977A34D4D@deepcore.dk> <051F7682-B3EC-49D8-B52A-2A8C75BEE757@gmail.com> <9B48E915-C705-4582-837B-C92B40AD63EB@westryn.net> <7CDBFAF1-C36F-4A2D-8D80-CFF1F03CD2B9@deepcore.dk> To: =?utf-8?Q?S=C3=B8ren_Schmidt?= X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: 6231781F05 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of kim@westryn.net designates 199.48.135.251 as permitted sender) smtp.mailfrom=kim@westryn.net X-Spamd-Result: default: False [-3.24 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:199.48.135.251]; MV_CASE(0.50)[]; MX_GOOD(-0.01)[mail.westryn.net]; NEURAL_HAM_SHORT(-0.97)[-0.967,0]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:36236, ipnet:199.48.132.0/22, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[westryn.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-1.46)[ipnet: 199.48.132.0/22(-3.35), asn: 36236(-3.88), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] 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: Sun, 02 Jun 2019 21:34:21 -0000 > On Jun 2, 2019, at 10:40 AM, S=C3=B8ren Schmidt = wrote: >=20 > Hi >=20 > I managed to get it to boot with the following: >=20 > setenv fdt_name 'efi/boot/armada-3720-espressobin.dtb' > setenv image_name 'efi/boot/bootaa64.efi' > setenv bootmmc 'mmc dev 0; fatload mmc 0:1 $kernel_addr = $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $kernel_addr = $fdt_addr' > run bootmmc >=20 > Then when the FreeBSD loader fails to load the kernel enter: >=20 > set currdev=3Ddisk0p2 > Boot >=20 > That will boot the kernel: >=20 > /boot/kernel/kernel text=3D0x92aab0 data=3D0x190f48+0x84ab1c = syms=3D[0x8+0x137580+0x8+0x12372b] > Using DTB provided by EFI at 0x8000000. > ---<>--- > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2019 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, = 1994 > The Regents of the University of California. All rights = reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 13.0-CURRENT r348210 GENERIC arm64 > FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on = LLVM 8.0.0) > WARNING: WITNESS option enabled, expect reduced performance. > VT: init without driver. > Starting CPU 1 (1) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > arc4random: WARNING: initial seeding bypassed the cryptographic random = device because it was not yet seeded and the knob = 'bypass_before_seeding' was enabled. > random: entropy device external interface > MAP 3e679000 mode 2 pages 1 > MAP 3ffa6000 mode 2 pages 1 > kbd0 at kbdmux0 > ofwbus0: > simplebus0: on ofwbus0 > simplebus1: on simplebus0 > psci0: on ofwbus0 > gic0: mem = 0x1d00000-0x1d0ffff,0x1d40000-0x1d7ffff irq 37 on simplebus1 > generic_timer0: irq 0,1,2,3 on ofwbus0 > Timecounter "ARM MPCore Timecounter" frequency 12500000 Hz quality = 1000 > Event timer "ARM MPCore Eventtimer" frequency 12500000 Hz quality 1000 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > cpu1: on cpulist0 > uart0: mem 0x12000-0x123ff irq 8 on = simplebus1 > uart0: console (115200,n,8,1) > mvneta0: mem 0x30000-0x33fff irq 10 on simplebus1 > mvneta0: version is 10 > mvneta0: Ethernet address: f0:ad:4e:08:61:5e > mvneta1: mem 0x40000-0x43fff irq 11 on simplebus1 > mvneta1: Failed to acquire PHY mode from FDT. > device_attach: mvneta1 attach returned 6 > xhci0: mem 0x58000-0x5bfff irq 31 on = simplebus1 > xhci0: 32 bytes context size, 32-bit DMA > usbus0 on xhci0 > ehci0: mem 0x5e000-0x5ffff irq = 33 on simplebus1 > usbus1: EHCI version 1.0 > usbus1 on ehci0 > sdhci_xenon0: mem = 0xd0000-0xd02ff,0x1e808-0x1e80b irq 34 on simplebus1 > sdhci_xenon1: mem = 0xd8000-0xd82ff,0x17808-0x1780b irq 35 on simplebus1 > ahci0: mem 0xe0000-0xe1fff irq 36 on simplebus1 > ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with = FBS > ahcich0: at channel 0 on ahci0 > cryptosoft0: > Timecounters tick every 1.000 msec > mvneta0: link state changed to UP > usbus0: 5.0Gbps Super Speed USB v3.0 > usbus1: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on = usbus0 > ugen1.1: at usbus1 > uhub1: on = usbus1 > Release APs...done > CPU 0: ARM Cortex-A53 r0p4 affinity: 0 > Instruction Set Attributes 0 =3D > Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]... > Instruction Set Attributes 1 =3D <> > Root mount waiting for: Processor Features 0 =3D = > usbus1 Processor Features 1 =3D <0> > usbus0 Memory Model Features 0 =3D <4k Granule,64k Granule,S/NS = Mem,MixedEndian,16bit ASID,1TB PA> >=20 > Memory Model Features 1 =3D <> > Memory Model Features 2 =3D <32b CCIDX,48b VA> > Debug Features 0 =3D <2 CTX Breakpoints,4 Watchpoints,6 = Breakpoints,PMUv3,Debug v8> > Debug Features 1 =3D <0> > Auxiliary Features 0 =3D <0> > Auxiliary Features 1 =3D <0> > CPU 1: ARM Cortex-A53 r0p4 affinity: 1 > WARNING: WITNESS option enabled, expect reduced performance. > uhub0: 2 ports with 2 removable, self powered > uhub1: 1 port with 1 removable, self powered > mountroot: waiting for device /dev/ufs/FreeBSD_Install... > Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. >=20 > Loader variables: > vfs.root.mountfrom=3Dufs:/dev/ufs/FreeBSD_Install > vfs.root.mountfrom.options=3Dro,noatime >=20 > Manual root filesystem specification: > : [options] > Mount using filesystem > and with the specified (optional) option list. >=20 > eg. ufs:/dev/da0s1a > zfs:zroot/ROOT/default > cd9660:/dev/cd0 ro > (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) >=20 > ? List valid disk boot devices > . Yield 1 second (for background tasks) > Abort manual input >=20 > mountroot>=20 >=20 > However, the MMC/SDcard fails to be found so it will stop at mounting = root. >=20 > Having a disk on the SATA port can make it work from there though. >=20 > The etherswitch is not found, but the single =E2=80=9Cnata=E2=80=9D = port does show up.. >=20 > All in all the support is barely enough to boot a kernel, but a long = way from being useful. >=20 > You can use 12-stable as well, the same support seems to be present = there, and its much more stable, -current as is today panics=E2=80=A6 >=20 > Oh, and you need to get the =E2=80=9Cright=E2=80=9D .dtb file, = otherwise you get panic=E2=80=99s etc. >=20 > YMMV=E2=80=A6 >=20 > -S=C3=B8ren >=20 >=20 My milage varies. I have experimented with many permutations of commands and nothing has = worked so far. The main difference I see between what I am doing and what you are doing = is that I am trying to boot from a usb stick, not a sdcard. It appears that after bootaa64.efi starts running, it does not see the = usb interface or the usb stick plugged in to it. I have also tried plugging in a sata drive that I built with an EFI = partition and a freebsd-ufs partition that I had installed freebsd into. In all cases, after bootaa64.efi is running, it seems determined to look = on the sdcard for the kernel and it completely ignores the presence of = the usb stick and the sata drive. At the loader prompt, it appears that bootaa64.efi does not know about = either of these devices. OK lsdev net devices: net0: I suspect that there may be something wrong in the = armada-3720-community-v7.dtb file but I don=E2=80=99t know how to = investigate that or correct it. Pointers would be appreciated. Thanks, Kim From owner-freebsd-arm@freebsd.org Mon Jun 3 06:56:24 2019 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 CC9DF15A6A29 for ; Mon, 3 Jun 2019 06:56:23 +0000 (UTC) (envelope-from maverick.kuo@gmail.com) Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E49986A326 for ; Mon, 3 Jun 2019 06:56:22 +0000 (UTC) (envelope-from maverick.kuo@gmail.com) Received: by mail-oi1-x236.google.com with SMTP id w196so2532436oie.7 for ; Sun, 02 Jun 2019 23:56:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xgnlaYAphtvdt+n4ywzdRZA1BIiT0SyhLbMKphLJFTw=; b=lY5OAq1LFpi5Y8s9ffG+/BR8D+l8suBII7OYLtIzLHHdEaIUSr7jvr04NhqFdwuRIJ vhclXB7ANo90usRi0RDJuZ74A1Iv3cWY6EsE3BicCUWRqV1ErzfzMl+UJgBskyRIzDZF 38rMPVlc6lNN4jbhLYMyeHovnsQw/T8qDcmZjuYCoZcjAMUSdMDtCJVxzbfCTAd31uom VApi/P4+x4cqhEhWV4q+a73xJOqw6YNqEu8qwLySw+mlV4jUDQ8Py7iaMHfM4NZgUgDt gG5NRDdPjwlTkSkGcpq7I8o4tPL38xaEtl58DyR8UaeU1i/SjuYjl8HYxbgzD1IpLHNv noRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xgnlaYAphtvdt+n4ywzdRZA1BIiT0SyhLbMKphLJFTw=; b=FkVm8LYuChtCEaa6Y1HzB8xLkLBcrFwucEAnDRt0MFKhUct0Hy6TMRaH1XBDXZNeW8 6BmMbhcoABWuxg3e1jQWy1G/9SHCwfwj1eMsGCPfonh7iF0E+G7xhtuIOi1gCzXyih72 Wsr5hvtaRx2iVt7BWjahy6AoqvXZ4r3YyJo1TgvbWT2X6F5zpjoILP2gsyxZ3+aJsYRm wJmB+SPsgTQO9nzuPEIcizbuLhBw1JMt/CEQmgbSeQpfjKKTYe6+0LPX0oJ0CuGw+jaW pwblixCPc58y02tGHnQnnGDS8V0ueiywWmx/I4jz5XOj0Cyg3dGUT+6MUnVjG+6AI6Zs J6dQ== X-Gm-Message-State: APjAAAUsDTIp2TVPfPCzpwEYHtXmTjDa7Q/zd+GpFAx3SSYqTxoqAIcJ KIp0oHRRbPjJiJzudHBhHUH3OcSLDZptg4Mv54xu9Yuq X-Google-Smtp-Source: APXvYqy4U2KTeRe1ilXUxg+8sn7IU4Dv7srndpfxSNBRh1pQAKwO205fin9zPKhXaUdOG6ZnU6SiaytBD7SEmFdpsMg= X-Received: by 2002:aca:4404:: with SMTP id r4mr54042oia.130.1559544981334; Sun, 02 Jun 2019 23:56:21 -0700 (PDT) MIME-Version: 1.0 From: Maverick Kuo Date: Mon, 3 Jun 2019 14:56:10 +0800 Message-ID: Subject: User space interface for GPIO interrupts To: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: E49986A326 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=lY5OAq1L; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of maverickkuo@gmail.com designates 2607:f8b0:4864:20::236 as permitted sender) smtp.mailfrom=maverickkuo@gmail.com X-Spamd-Result: default: False [-6.67 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.69)[-0.687,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; IP_SCORE(-3.03)[ip: (-9.53), ipnet: 2607:f8b0::/32(-3.26), asn: 15169(-2.28), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[6.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Mon, 03 Jun 2019 06:56:24 -0000 Hi, i am running 12.0-STABLE r348448 arm64 on raspberry pi3 b+. Look at the kernel and it seems that all the functions related to gpio interrupt are available. System startup process Bcm_gpio_intr_attach =>> Bus_setup_intr ?? bcm_gpio_intr_bank[0,1] ?? bcm_gpio_intr_internal It seems that BCM_GPIO_GPEDS (Event Status) will be read in the bcm_gpio_intr_internal function but it is not executed there. am I missed that part?? Let users use kqueue/kevent to monitor gpio interrupt to reduce cpu load. Regards, Chris From owner-freebsd-arm@freebsd.org Mon Jun 3 08:00:30 2019 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 95D6F15A805E for ; Mon, 3 Jun 2019 08:00:30 +0000 (UTC) (envelope-from maverick.kuo@gmail.com) Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 836716C027 for ; Mon, 3 Jun 2019 08:00:29 +0000 (UTC) (envelope-from maverick.kuo@gmail.com) Received: by mail-ot1-x32c.google.com with SMTP id z23so242210ote.13 for ; Mon, 03 Jun 2019 01:00:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2KcCBBo2Agw/wBtQEw2kYEhYek3CPN9wP60y7lBABxM=; b=CS7MEOmLNBu7WnipxahuAuqV72oV6Y6YdGuiS31QYcdpSnuvo0OKlwIm85ykbloFZ8 Qs4RAO4+eF9YdIxLBbGLD8nD8vCltGJc7MC9PqhzJZnNnEkViDzRVfMBrfSBJMgD9P3y Wv7zy17N2VEMTk/tbDxiQNtxekDNmlkcgwU2k6e0ZvECMAGUW966i8xbkUlAW9DZ9dS6 91AUOr2ZeA9Sq+W+xMIpdyBDYB24LhfeROYW+lmZAUBxwAR3gJ/rYYYHYSLr3mQPtlCG JwjZgy4b6TXc/QJIxYs7sfjwvkCp6dptScu8tPIcTR3FpzqR5pNRo4QksvyGJ77KBOEF kTpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2KcCBBo2Agw/wBtQEw2kYEhYek3CPN9wP60y7lBABxM=; b=CIoBV6E50rN4DdIyBOCv+Vgs/rTxmlt+5Xf65oP9IdnqIVTU7yuHsTDg3IOXLDBNpM QiH3sCNqKZNtFu7PGVmyfLlkCHAgaXN8MjuCh8Pul0c82EVmr67/hb6r0p9bVUofTrQT K9/B69lOoCjhkzce3NPEDUudy7PpA1Xrmdn3uEf9FV98jjdjAO0jg52pPAFswbKw/Wsk uLcwRLoGtDrRfNpm5o2jdXErxtlk1Obi9/p9pF8m2VQWl51v8aukcgV8xHdqY3vXSAug RzwV1oNcJ3Q0ZBkzX+gA/UBFi+deYQPB5t5+W71PBZ5/xZH3yoU2XEowRey9EYrwjGxQ b5pQ== X-Gm-Message-State: APjAAAXyKHsoZmPNihvRXBbwJjNRArxqH67YWTPYBC75ph7GhB6NiAkk gk3AcPJOFspbCFR0U5YtmR/p+Abst4KdqLlfOFT8Bnw8 X-Google-Smtp-Source: APXvYqzGhGXaYYSSU24mVdK9kFpkxf05Sq5jmdwpX1JqeIuGJZR2kswyHDA1cOZLVJOVrhwsTRcnM3I97CZkIfrrTQw= X-Received: by 2002:a9d:6312:: with SMTP id q18mr216435otk.45.1559548828122; Mon, 03 Jun 2019 01:00:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Maverick Kuo Date: Mon, 3 Jun 2019 16:00:17 +0800 Message-ID: Subject: Re: User space interface for GPIO interrupts To: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 836716C027 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=CS7MEOmL; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of maverickkuo@gmail.com designates 2607:f8b0:4864:20::32c as permitted sender) smtp.mailfrom=maverickkuo@gmail.com X-Spamd-Result: default: False [-6.79 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.87)[-0.875,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; IP_SCORE(-2.95)[ip: (-9.15), ipnet: 2607:f8b0::/32(-3.26), asn: 15169(-2.28), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[c.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Mon, 03 Jun 2019 08:00:30 -0000 Hi, Good News !! after cvs to 12.0-STABLE #0 r348527M GPIO Interrupt with kqueue Works !!! Thanks to the developers :) Regards, Chris Maverick Kuo =E6=96=BC 2019=E5=B9=B46=E6=9C=883=E6= =97=A5 =E9=80=B1=E4=B8=80 =E4=B8=8B=E5=8D=882:56=E5=AF=AB=E9=81=93=EF=BC=9A > Hi, > > i am running 12.0-STABLE r348448 arm64 on raspberry pi3 b+. > > Look at the kernel and it seems that all the functions related to gpio > interrupt are available. > > System startup process > Bcm_gpio_intr_attach =3D>> > Bus_setup_intr > ?? bcm_gpio_intr_bank[0,1] > ?? bcm_gpio_intr_internal > > It seems that BCM_GPIO_GPEDS (Event Status) will be read in the > bcm_gpio_intr_internal function but it is not executed there. > > am I missed that part?? > > Let users use kqueue/kevent to monitor gpio interrupt to reduce cpu load. > > Regards, > Chris > From owner-freebsd-arm@freebsd.org Mon Jun 3 09:46:28 2019 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 1897215AA98A for ; Mon, 3 Jun 2019 09:46:28 +0000 (UTC) (envelope-from maverick.kuo@gmail.com) Received: from mail-ot1-x341.google.com (mail-ot1-x341.google.com [IPv6:2607:f8b0:4864:20::341]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0884B6FA02 for ; Mon, 3 Jun 2019 09:46:27 +0000 (UTC) (envelope-from maverick.kuo@gmail.com) Received: by mail-ot1-x341.google.com with SMTP id i8so15418082oth.10 for ; Mon, 03 Jun 2019 02:46:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=zlB0H4qH+ysB5loQzCcqkX4epNH2ZoHUxz84roYfPgw=; b=mtD5lq3VHZkXmm3tK72oxGgg9Bys7U/OrTs3iw8k/nRFCz5xkCD4wmr7cgygaPB3bo SWEIG+0kyv9MoLeFzuBlB8AkTzHUhCs1M9OzS+KIgAJ1h92bhUesN5kq8tLLazJcdApd s2DHwOGQWV7Ix/GnAECb6rKiVjuQhnUYfueTt1g0IGbJ6PlbjgkWittmN+YZsWbXOPEB G2H6E5IhJDu4V9SBXTOAIef+asxUEr3rkcgE9Y3M+ZNLUIgCmBvdUiMGN3hvWyaJ2g51 UJJvtZKd55qp7d3yjDt9Zkc7KttsAzYBSPMHmH8zDDaN/C+x9xqabFXQgrj4tkHkpVrE cM8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=zlB0H4qH+ysB5loQzCcqkX4epNH2ZoHUxz84roYfPgw=; b=CS8JSt7WoBTUlhfsizcZAuF30wIn0uTRHyCMYDk3dA3er05lpO/b4lezZNdicU83YB Hqy9ImZ4Qca/axLWliFp5o4pqdL+kkLyKAgGBRHQ05R2uSVC7WkiGE/IJlb/mHFmbczA KkXXXdGGSo0Xee1hYWTxzPODta9Tgw/AOtPgQyUcXhocLEHc3S6f4IlnThIMX8Io/Dpl MPqp8HYO3UYhlkNKdfWrKeg3L4NlWSOkKlN8xVVcgh5G+n18/Xu1Sl53pyWdc53a15iy e1Vo6bw6s6rZCeHKCjOKz3QyrAgdrYhYfu0LNSrDOO1dxhVzIuN1lSjlJTe/nYl8rawm E7aA== X-Gm-Message-State: APjAAAV4Oi9esVK0O5Wwn4m1XpZ1RabuLzzdId+adRfnqRHQAzFCuHdM awZqQbzuUNLFdjuI3uOw/Z8RqZ7PB6bDL2ff7eX22Skf X-Google-Smtp-Source: APXvYqw1sLkXT78TpmmNCSqjYpBx8IB+q3oopOKmHVZZZzAYgdJHGcGL0mt2E5InYqK/Av8qA51IKb0tI7rbpKx1RYU= X-Received: by 2002:a05:6830:11c3:: with SMTP id v3mr472486otq.326.1559555185846; Mon, 03 Jun 2019 02:46:25 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Maverick Kuo Date: Mon, 3 Jun 2019 17:46:15 +0800 Message-ID: Subject: Re: User space interface for GPIO interrupts To: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 0884B6FA02 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=mtD5lq3V; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of maverickkuo@gmail.com designates 2607:f8b0:4864:20::341 as permitted sender) smtp.mailfrom=maverickkuo@gmail.com X-Spamd-Result: default: False [-4.67 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.85)[-0.855,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.86)[ip: (1.32), ipnet: 2607:f8b0::/32(-3.26), asn: 15169(-2.28), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Mon, 03 Jun 2019 09:46:28 -0000 Sorry, I got it wrong, gpio interrupt is really available, BUT I forgot, I have a patched from https://github.com/ckraemer/freebsd/tree/gsoc2018 Just after the comparison was revised, I found out that I apologize again. Regards, Chris Maverick Kuo =E6=96=BC 2019=E5=B9=B46=E6=9C=883=E6= =97=A5 =E9=80=B1=E4=B8=80 =E4=B8=8B=E5=8D=884:00=E5=AF=AB=E9=81=93=EF=BC=9A > Hi, > > Good News !! > > after cvs to 12.0-STABLE #0 r348527M GPIO Interrupt with kqueue Works !!! > > Thanks to the developers :) > > Regards, > Chris > > Maverick Kuo =E6=96=BC 2019=E5=B9=B46=E6=9C=883= =E6=97=A5 =E9=80=B1=E4=B8=80 =E4=B8=8B=E5=8D=882:56=E5=AF=AB=E9=81=93=EF=BC= =9A > >> Hi, >> >> i am running 12.0-STABLE r348448 arm64 on raspberry pi3 b+. >> >> Look at the kernel and it seems that all the functions related to gpio >> interrupt are available. >> >> System startup process >> Bcm_gpio_intr_attach =3D>> >> Bus_setup_intr >> ?? bcm_gpio_intr_bank[0,1] >> ?? bcm_gpio_intr_internal >> >> It seems that BCM_GPIO_GPEDS (Event Status) will be read in the >> bcm_gpio_intr_internal function but it is not executed there. >> >> am I missed that part?? >> >> Let users use kqueue/kevent to monitor gpio interrupt to reduce cpu load= . >> >> Regards, >> Chris >> > From owner-freebsd-arm@freebsd.org Mon Jun 3 11:54:15 2019 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 49C1015AE5B6 for ; Mon, 3 Jun 2019 11:54:15 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh602-vm1.bullet.mail.ssk.yahoo.co.jp (nh602-vm1.bullet.mail.ssk.yahoo.co.jp [182.22.90.26]) by mx1.freebsd.org (Postfix) with SMTP id 741E074AAA for ; Mon, 3 Jun 2019 11:54:06 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.104] by nh602.bullet.mail.ssk.yahoo.co.jp with NNFMP; 03 Jun 2019 11:50:44 -0000 Received: from [182.22.91.133] by t602.bullet.mail.ssk.yahoo.co.jp with NNFMP; 03 Jun 2019 11:50:44 -0000 Received: from [127.0.0.1] by omp606.mail.ssk.yahoo.co.jp with NNFMP; 03 Jun 2019 11:50:44 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 19538.90256.bm@omp606.mail.ssk.yahoo.co.jp X-YMail-OSG: MmKVLGMVM1kmL75OE76nZ2nuFtupWF8pgO1whyL._gxcvM8EtRRFzCe1W7ayUUr p0joYfAMaflP8blB9xr4DN1fy_LoSswbkXWV2fmnXtU2x8cVxB8XIxlwRrI8iCotH74ec78z.Shc nuPvkPJDAYzctdgAdCbEpeD1285ps6BbQNo8IoMYo.1HQP7.bp0L4UCu3WJEQypzvMcHfTQ3FDFo 4h8PUm_Ykg6aIuXqJFF7jAQRDI6eZ15zua6CS4CDi8cWDMzbMvzAWoWoPHtmRuVREb_8LoZxd4kD nCDUsDI98hm7He_ung2E0QN_P3VY.IvojzqJ03KHBwuLsaWM5bRBvQ8N9Yh85r4t1NwNKfpteL0m 25RvULvfYXCOLTbSQayathUTM_LsfTZa4zcuBUG2ewTmx8kUmTgwsRsohWw1Ms5Y2H89d2CKSXdp KeE3_0ezeCMx17FEAE1oRsGj_LoPcZEOYkip.s8Z_Qqwnlte1UDWX77Xo7SVUZULM7QQPGgZpnnj cxJm7RC21Rs886nenfpoZCbg8VIrymIKBwX2wHrbl6N3sWlK8IxMotxPWGqNhBY_BCmaiFhgC0dN 7p7mB5_xkrUbfN.iJ24w8s7mWAk49mN5tFFWPdiiKDA-- Received: from jws704001.mail.kks.yahoo.co.jp by sendmailws501.mail.kks.yahoo.co.jp; Mon, 03 Jun 2019 20:50:43 +0000; 1559562643.314 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1559562643; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=za/YlCigJQBbz1QzIXI+evUMB4bv/0GWC7r23dnUrHs=; b=hOJxPY9wGQ13TWCl64u7EaIrDJAuoZXyAUmImUK5j44BoubofbXHAsDB4TlcKLRk HtYnhfJO01x02UcRG/oSUeUa/9/tawn7moKRyUqIyAr1iMpCdaSjP5/QOoFRCR8e0xr 65lxZLqHaPYGUG7037mBvte1ft7R6fIgJChvboHM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=V6gJZ9WC0CTR34Y6Nk57QoyPB1Up68B1mCTz0hf+SXFnT21U9Z/bw3ZDiOWhVVBE fKPQRqzD4GlegllakEJrtstl/fWz+BV40LhhI7O6Sgy+kh9O3qzINk7d9b5s47Lyre2 32eLbcqr80hq4Pt5e3Fpf3aVjesph2uzGOvt5XVk=; Date: Mon, 3 Jun 2019 20:50:42 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: Ronald Klop , "freebsd-arm@freebsd.org" , "freebsd-stable@freebsd.org" Message-ID: <1442525240.1981975.1559562642958.JavaMail.yahoo@jws704001.mail.kks.yahoo.co.jp> In-Reply-To: References: Subject: Re: boot 11.3-BETA1 hangs om armv5 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 741E074AAA X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=hOJxPY9w; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 182.22.90.26 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [-2.43 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:182.22.90.0/23]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; MX_GOOD(-0.01)[mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp,mx3.mail.yahoo.co.jp,mx5.mail.yahoo.co.jp,mx1.mail.yahoo.co.jp,mx2.mail.yahoo.co.jp]; NEURAL_HAM_SHORT(-0.60)[-0.596,0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:23816, ipnet:182.22.0.0/17, country:JP]; IP_SCORE(0.68)[ipnet: 182.22.0.0/17(1.92), asn: 23816(1.53), country: JP(-0.05)]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.64)[-0.637,0]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; REPLYTO_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-0.97)[-0.967,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[26.90.22.182.list.dnswl.org : 127.0.5.0] 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: Mon, 03 Jun 2019 11:54:15 -0000 Hi. I build and flash on arm/ralink today by CURRENT. arm/ralink is hangup at same point too. Hiroki Mori ----- Original Message ----- > From: Ronald Klop > To: freebsd-arm@freebsd.org; "freebsd-stable@freebsd.org" > Cc:=20 > Date: 2019/5/28, Tue 05:00 > Subject: boot 11.3-BETA1 hangs om armv5 >=20 > Was running "FreeBSD 11.2-RELEASE-p4 (SHEEVAPLUG) #4 r339336M: Sat Oct 13= =C2=A0=20 > 23:31:51 CEST 2018". > Compiled 11.3-BETA1, installed kernel.bin in /boot/msdos and started it.= =C2=A0=20 > Output below. It hangs. I guess in starting the random/entropy stuff. >=20 > Any thoughts or advise? > Don't spend to much time on it, I'm happy to phase it out. >=20 > Regards, > Ronald. >=20 >=20 > Rebooting... >=20 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 __=C2=A0 __=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 _ _ > =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 \/=C2=A0 | __ _ _ ____=C2=A0 _____|= | | > =C2=A0 =C2=A0 =C2=A0 =C2=A0 | |\/| |/ _` | '__\ \ / / _ \ | | > =C2=A0 =C2=A0 =C2=A0 =C2=A0 | |=C2=A0 | | (_| | |=C2=A0 \ V /=C2=A0 __/= | | > =C2=A0 =C2=A0 =C2=A0 =C2=A0 |_|=C2=A0 |_|\__,_|_|=C2=A0 =C2=A0 \_/ \___|= _|_| > =C2=A0 _=C2=A0 _=C2=A0 =C2=A0 ____=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 _ > | | | |=C2=A0 | __ )=C2=A0 ___=C2=A0 ___ | |_ > | | | |___|=C2=A0 _ \ / _ \ / _ \| __| > | |_| |___| |_) | (_) | (_) | |_ > =C2=A0 \___/=C2=A0 =C2=A0 |____/ \___/ \___/ \__| > =C2=A0 ** MARVELL BOARD: SHEEVA PLUG LE >=20 > U-Boot 1.1.4 (Mar 19 2009 - 16:06:59) Marvell version: 3.4.16 >=20 > U-Boot code: 00600000 -> 0067FFF0=C2=A0 BSS: -> 006CEE80 >=20 > Soc: 88F6281 A0 (DDR2) > CPU running @ 1200Mhz L2 running @ 400Mhz > SysClock =3D 400Mhz , TClock =3D 200Mhz >=20 > DRAM CAS Latency =3D 5 tRP =3D 5 tRAS =3D 18 tRCD=3D6 > DRAM CS[0] base 0x00000000=C2=A0 size 256MB > DRAM CS[1] base 0x10000000=C2=A0 size 256MB > DRAM Total size 512MB=C2=A0 16bit width > Flash:=C2=A0 0 kB > Addresses 8M - 0M are saved for the U-Boot usage. > Mem malloc Initialization (8M - 7M): Done > NAND:512 MB >=20 > CPU : Marvell Feroceon (Rev 1) >=20 > Streaming disabled > Write allocate disabled >=20 >=20 > USB 0: host mode > PEX 0: interface detected no Link. > Net:=C2=A0 egiga0 [PRIME], egiga1 > Hit any key to stop autoboot:=C2=A0 0 > (Re)start USB... > USB:=C2=A0 scanning bus for devices... 4 USB Device(s) found > =C2=A0 =C2=A0 =C2=A0 =C2=A0 scanning bus for storage devices... 1 Storage= Device(s) found > reading kernel.bin > . > .........................................................................= ...........................................................................= ...........................................................................= ...........................................................................= ...........................................................................= ................................................... >=20 > 4345316 bytes read > ## Starting application at 0x00900000 ... > Copyright (c) 1992-2019 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > =C2=A0=C2=A0=C2=A0 The Regents of the University of California. All right= s reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.3-BETA1 #0 r348277M: Sun May 26 14:17:08 CEST 2019 > =C2=A0 =C2=A0 builder@rpi3:/data/src/obj-11.3/arm.arm/data/src/11.3/sys/S= HEEVAPLUG=C2=A0=20 > arm > FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLV= M=C2=A0=20 > 8.0.0) > CPU: Feroceon 88FR131 rev 1 (**unknown 4** core) > =C2=A0 Little-endian DC enabled IC disabled WA disabled DC streaming ena= bled > =C2=A0 BTB disabled L2 enabled L2 prefetch enabled > =C2=A0 WB enabled LABT branch prediction disabled > =C2=A0 16KB/32B 4-way instruction cache > =C2=A0 16KB/32B 4-way write-back-locking-C data cache > real memory=C2=A0 =3D 536866816 (511 MB) > avail memory =3D 518778880 (494 MB) > SOC: Marvell 88F6281 rev A0, TClock 200MHz > =C2=A0 Instruction cache prefetch enabled, data cache prefetch enabled > =C2=A0 256KB 4-way set-associative write-through unified L2 cache > random: entropy device external interface > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm=20 > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20 From owner-freebsd-arm@freebsd.org Tue Jun 4 16:49:57 2019 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 E36F115B6EFF for ; Tue, 4 Jun 2019 16:49:56 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from forward101p.mail.yandex.net (forward101p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:101]) (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 5D12B72382 for ; Tue, 4 Jun 2019 16:49:55 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mxback14j.mail.yandex.net (mxback14j.mail.yandex.net [IPv6:2a02:6b8:0:1619::90]) by forward101p.mail.yandex.net (Yandex) with ESMTP id 7D93332806DC for ; Tue, 4 Jun 2019 19:49:44 +0300 (MSK) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [2a02:6b8:0:801::ab]) by mxback14j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 3w0LORxkF8-niQqIBxs; Tue, 04 Jun 2019 19:49:44 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler.com; s=mail; t=1559666984; bh=v4PosTP26yd20/XCGOqITgvif0aCfnXP1mn/kQ+FvmE=; h=Subject:To:From:Date:Message-ID; b=l80BCxPtN9yXPkMSX55eNcbquBHUisTvQW5xioYTmba/rtNkKVFMi44vfHoLUi26O sn9u4syqKh++1Ns+6M4AxXBQSUawNwwXEedS81OLtEaW90VHNCKGa/oczM6zPHD/qN nTHc+vfLp6ZxeANYzvipsrgKkcCZkR2zwxE3XggE= Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id TEGJ2KCzhm-ngnmsmqM; Tue, 04 Jun 2019 19:49:43 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Date: Tue, 4 Jun 2019 10:49:39 -0600 From: Sergey Manucharian To: FreeBSD-ARM Subject: DTS files in /usr/src and sysutils/u-boot-* Message-ID: <20190604164939.GC13546@eldorado> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 5D12B72382 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ara-ler.com header.s=mail header.b=l80BCxPt; spf=pass (mx1.freebsd.org: domain of sm@ara-ler.com designates 2a02:6b8:0:1472:2741:0:8b7:101 as permitted sender) smtp.mailfrom=sm@ara-ler.com X-Spamd-Result: default: False [-6.67 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[ara-ler.com:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1000::/52]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[ara-ler.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[ara-ler.com:+]; MX_GOOD(-0.01)[mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net]; NEURAL_HAM_SHORT(-0.95)[-0.951,0]; IP_SCORE(-3.60)[ip: (-9.50), ipnet: 2a02:6b8::/32(-4.74), asn: 13238(-3.80), country: RU(0.01)]; RCVD_IN_DNSWL_LOW(-0.10)[1.0.1.0.7.b.8.0.0.0.0.0.1.4.7.2.2.7.4.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; MIME_TRACE(0.00)[0:+] 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: Tue, 04 Jun 2019 16:49:57 -0000 What's the reason the FDT source files in the subject are slightly different? Are there any critical adjustments specific to FreeBSD? Would anybody point to a good source of information? Thanks, Ϟϻ From owner-freebsd-arm@freebsd.org Wed Jun 5 15:49:31 2019 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 5181C15B1B73 for ; Wed, 5 Jun 2019 15:49:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3EE188623 for ; Wed, 5 Jun 2019 15:49:30 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 015BBBFD8 for ; Wed, 5 Jun 2019 15:49:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x55FnT9d088144 for ; Wed, 5 Jun 2019 15:49:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x55FnTAP088143 for freebsd-arm@FreeBSD.org; Wed, 5 Jun 2019 15:49:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 227974] libfdt reverses order of child devices in overlays Date: Wed, 05 Jun 2019 15:49:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ian@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cc bug_status 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-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, 05 Jun 2019 15:49:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227974 Ian Lepore changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug CC| |ian@FreeBSD.org Status|New |Closed --- Comment #1 from Ian Lepore --- The names of FDT device nodes do not necessarily have any relationship to t= he names of devices instantiated by freebsd. By FDT convention, a device node name is formed as devicetype@regaddr; it's just a coincidence in the case of spi that the register addresses are single-digit integers that seem to vagu= ely correspond with freebsd device names. (And it should be noted that the nam= es in the example shown do not follow the FDT rules and would generate a warni= ng with the modern gnu dtc compiler because they should be spigen@0 not spigen= 0). The root problem is that a user of spi devices needs some way to identify w= hich /dev/spigenX device corresponds to which device described in the FDT data. = We ultimately solved that problem by naming spigen devices in devfs after their bus and chip select number, instead of just using sequential 0-n numbers. = So instead of spigen0 and spigen1, the example overlay would now create /dev/spigen0.0 and /dev/spigen0.1 (assume they were on spi bus zero), and s= ince it's based on the chip select number it comes out the same name matter what order the nodes appear in. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Jun 5 18:26:36 2019 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 F254615B529D for ; Wed, 5 Jun 2019 18:26:35 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from forward106o.mail.yandex.net (forward106o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::609]) (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 2BB088DBB3 for ; Wed, 5 Jun 2019 18:26:34 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mxback10g.mail.yandex.net (mxback10g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:171]) by forward106o.mail.yandex.net (Yandex) with ESMTP id CD51E5061F6F for ; Wed, 5 Jun 2019 21:26:22 +0300 (MSK) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [2a02:6b8:0:1619::15:6]) by mxback10g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id rangftRXeg-QMVCwTrc; Wed, 05 Jun 2019 21:26:22 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler.com; s=mail; t=1559759182; bh=c1qapDLFXTISrSLTxFKCWH0nH22NJKZJyr09saseHJA=; h=In-Reply-To:Subject:To:From:References:Date:Message-ID; b=oE4g8Z+dXx9zyNS4AFccSIdAp7Q36QL7ZKZhPYVEelYnGtQqtxc/f9J0I6YaeF8uT +VzTEhlPE5vEKVq0V9HoGLzrYPmXgMOyx8fhdIMAQAJtWpls+wrct+vdif10yBzs9N oZgorKIvA8AlF+pHjQXeVxZbf2hlDB5omYr/BtaM= Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id fzS3sXnS5H-QLR4oFcg; Wed, 05 Jun 2019 21:26:21 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Date: Wed, 5 Jun 2019 12:26:18 -0600 From: Sergey Manucharian To: FreeBSD-ARM Subject: Re: Default serial console Message-ID: <20190605182618.GD13546@eldorado> References: <20190601175753.GN33704@dendrobates> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190601175753.GN33704@dendrobates> User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 2BB088DBB3 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ara-ler.com header.s=mail header.b=oE4g8Z+d; spf=pass (mx1.freebsd.org: domain of sm@ara-ler.com designates 2a02:6b8:0:1a2d::609 as permitted sender) smtp.mailfrom=sm@ara-ler.com X-Spamd-Result: default: False [-2.42 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[ara-ler.com:s=mail]; NEURAL_HAM_MEDIUM(-0.98)[-0.982,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1a2d::/64]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[ara-ler.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[ara-ler.com:+]; MX_GOOD(-0.01)[mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net]; NEURAL_HAM_SHORT(-0.33)[-0.332,0]; RCVD_IN_DNSWL_LOW(-0.10)[9.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.d.2.a.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+] 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, 05 Jun 2019 18:26:36 -0000 Excerpts from Sergey Manucharian's message from Sat 01-Jun-19 11:57: > How to change the default serial console? I couldn't find any reference. > In my BeagleBone Black the boot messages and login prompt go to /dev/ttyu0. > With the peripherals I use, that port is not physically accessible, and I'd > like to use /dev/ttyu1 instead. I posted the solution in this Forums' thread: https://forums.freebsd.org/threads/default-serial-console-to-login.70957 -- Ϟϻ From owner-freebsd-arm@freebsd.org Thu Jun 6 19:33:14 2019 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 6EC4B15BE02E for ; Thu, 6 Jun 2019 19:33:14 +0000 (UTC) (envelope-from nmingotti@gmail.com) Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77D1C84946 for ; Thu, 6 Jun 2019 19:33:13 +0000 (UTC) (envelope-from nmingotti@gmail.com) Received: by mail-pg1-x52c.google.com with SMTP id a3so1916774pgb.3 for ; Thu, 06 Jun 2019 12:33:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:cc:message-id:date:user-agent:mime-version :content-language; bh=ZHWxtAUKf1euOIgYFHRYsIYRrtuzJBkuCuqt4ziAfvo=; b=Z+Yx8kXLhurTP/Ah9VDPu+iWbIrm5HCq7Sfaq+7WDu6OTzPn2JU1uuk9Symlg6Rjxw E9catqrkEp0bRKgTAoUZDZbj1qAYIVmjhmR1vMU1LAZObB9OtW+dDvi5Nw58zOnYvnUc NV27VbmAV2ceHBDtMo0tGvIdahBC1OBJWxj3OVVLudpj4cZwhpmg/pqg6TLax6vVWivj xA7mCIEP8J6iM1GM8je4fEWs3BBa8jWAMqQVBepwWI6HXyAKUslLPTSGwISOvLf0YQM6 4l+ZXmC8n6L69oS1ul+nNj4v1V8FjMBY6qB0DQholVAI/Xp/cg0rHXyHg8w1dfS8sXJg dy/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:message-id:date:user-agent :mime-version:content-language; bh=ZHWxtAUKf1euOIgYFHRYsIYRrtuzJBkuCuqt4ziAfvo=; b=fRfYXwX44gnVa/CUb/AVuETfNf2UvdlgzLm53PD9My9Nx+16V298Pa5yaGXNu2Aq1C h1IN43RFJG1w6fd5mCkf57xoAfv4gFhxGOpc8JFMSUaxOIjfkCmMpKNNp9TfSPcdsZGz jTsvAdx5G99gL7x4EJBKk7xZ+5/9m3nCUIsO2x4CHT9/wKjPJzQzdYlcwXgaprvdXQAC JbADgePbIl4FwiswK2ez4SmtQ8grxbB+3sMVfDrDJzeh+cZkw49KcPugU86qPL3E1/gn YG2h8tiFYOwLY+5Kib/oa5XoBIkfqRgUYgkIjojuygfOh7T5MmS/Gue8+GnPJ1HuqbRj 89YA== X-Gm-Message-State: APjAAAWJm9itP9NAANRntR8oJyPsSQ/p1ILt7j2ikuV8LaIIx2l3UhUF l5b1TYxS+4e5Bscd9ODO90E= X-Google-Smtp-Source: APXvYqzN7yXK3CT6ArPIsOeMyrnTO+3J+mBe6xxQmUYR7ukjJczf+ERkLhIyLleWTtg0DAwK+GOqEA== X-Received: by 2002:aa7:824b:: with SMTP id e11mr53115293pfn.33.1559849591685; Thu, 06 Jun 2019 12:33:11 -0700 (PDT) Received: from [172.16.144.128] (dhcp-visitor-216-182.slac.stanford.edu. [198.129.216.182]) by smtp.gmail.com with ESMTPSA id m5sm2608006pgc.84.2019.06.06.12.33.09 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jun 2019 12:33:10 -0700 (PDT) From: Nicola Mingotti Subject: How to set PWM tunable name to ehrpwm.1 ? To: freebsd-arm@freebsd.org Cc: nmingott@gmail.com Message-ID: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> Date: Thu, 6 Jun 2019 12:33:08 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Language: en-US X-Rspamd-Queue-Id: 77D1C84946 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Z+Yx8kXL; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of nmingotti@gmail.com designates 2607:f8b0:4864:20::52c as permitted sender) smtp.mailfrom=nmingotti@gmail.com X-Spamd-Result: default: False [-5.93 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[c.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_CC(0.00)[gmail.com]; IP_SCORE(-2.94)[ip: (-9.11), ipnet: 2607:f8b0::/32(-3.22), asn: 15169(-2.29), country: US(-0.06)] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Thu, 06 Jun 2019 19:33:14 -0000 Hi, In my BeagleBone Black, FreeBSD-12 RELEASE, i created two overlays, pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 and respectively p9.14, p9.16. DTSO files are below. If I load both the DTBO at boot I see correctly|ehrpwm.0|and|ehrpwm.1|, associated to the correct pins. But, if i remove the overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which is not what i want, i would like to see the name|ehrpwm.1|. This is important because i must be 100% sure a certain pin corresponds the a certain tunable.This must be true even if i remove non relevant overlays in the future. I guess there must be some parameter in the DTSO which i don't know, i hope you can give me some directions about that. bye Nicola -------- pwm.dtso ----------------- |/dts-v1/; /plugin/; / { compatible = "ti,am335x-bone-black", "ti,am335x-bone", "ti,am33xx"; exclusive-use = "P9.21","P9.22","ehrpwm0_AB"; }; &am33xx_pinmux { ehrpwm0_AB_pins: pinmux_ehrpwm0_AB_pins { pinctrl-single,pins = < 0x154 0x03 /* P9.21 */ 0x150 0x03 /* P9.22 */ >; }; }; &ehrpwm0 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&ehrpwm0_AB_pins>; }; &epwmss0 { status = "okay"; }; &ecap0 { status = "okay"; }; ----------------------------------------------------------- --------------------- pwm1.dtso -------------------------- | ||/dts-v1/; /plugin/; / { compatible = "ti,am335x-bone-black", "ti,am335x-bone", "ti,am33xx"; exclusive-use = "P9.14","P9.16","ehrpwm1_AB"; }; &am33xx_pinmux { ehrpwm1_AB_pins: pinmux_ehrpwm1_AB_pins { pinctrl-single,pins = < 0x048 0x06 /* P9.14 */ 0x04C 0x06 /* P9.16 */ >; }; }; &ehrpwm1 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&ehrpwm1_AB_pins>; }; &epwmss1 { status = "okay"; }; &ecap1 { status = "okay"; }; |----------------------------------------------------------- | From owner-freebsd-arm@freebsd.org Thu Jun 6 22:06:58 2019 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 3C4C915C1A61 for ; Thu, 6 Jun 2019 22:06:58 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from forward102p.mail.yandex.net (forward102p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:102]) (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 B7A318A221 for ; Thu, 6 Jun 2019 22:06:56 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mxback8j.mail.yandex.net (mxback8j.mail.yandex.net [IPv6:2a02:6b8:0:1619::111]) by forward102p.mail.yandex.net (Yandex) with ESMTP id ADA1F1D40019; Fri, 7 Jun 2019 01:06:44 +0300 (MSK) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [2a02:6b8:0:1a2d::27]) by mxback8j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id jG0Yoxfcko-6ik0jfs2; Fri, 07 Jun 2019 01:06:44 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler.com; s=mail; t=1559858804; bh=L1P+mCMF0l6Am6H118of8b+BzRdP9P2Hw5WkquvAF1Y=; h=In-Reply-To:Subject:Cc:To:From:References:Date:Message-ID; b=tWQhULNSvqug9s4hAHou41aPUh3PeplxCJwBkZhUSaqCsFFDgPCPmhSquqfwfpXdc aDPf11R9bhN8NpF13aeBDBPOIrtLCWIRbxJ25J047yn35yKlbHHObBScQ0TxSIubNS QjZgtqcoLNwalvcSRiP5mZpewa3kSa6MTJUIQS1g= Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id YbgJy6EzAr-6gLmiNvM; Fri, 07 Jun 2019 01:06:43 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Date: Thu, 6 Jun 2019 16:06:39 -0600 From: Sergey Manucharian To: Nicola Mingotti Cc: freebsd-arm@freebsd.org, nmingott@gmail.com Subject: Re: How to set PWM tunable name to ehrpwm.1 ? Message-ID: <20190606220639.GE13546@eldorado> References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: B7A318A221 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ara-ler.com header.s=mail header.b=tWQhULNS; spf=pass (mx1.freebsd.org: domain of sm@ara-ler.com designates 2a02:6b8:0:1472:2741:0:8b7:102 as permitted sender) smtp.mailfrom=sm@ara-ler.com X-Spamd-Result: default: False [-5.70 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[ara-ler.com:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1000::/52]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[ara-ler.com]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[ara-ler.com:+]; MX_GOOD(-0.01)[mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; IP_SCORE(-3.59)[ip: (-9.45), ipnet: 2a02:6b8::/32(-4.74), asn: 13238(-3.79), country: RU(0.01)]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[2.0.1.0.7.b.8.0.0.0.0.0.1.4.7.2.2.7.4.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[] 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: Thu, 06 Jun 2019 22:06:58 -0000 Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two overlays, > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 and > respectively p9.14, p9.16. DTSO files are below. > > If I load both the DTBO at boot I see correctly|ehrpwm.0|and|ehrpwm.1|, > associated to the correct pins. But, if i remove the > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which is not > what i want, i would like to see the name|ehrpwm.1|. > > This is important because i must be 100% sure a certain pin corresponds > the a certain tunable.This must be true even if i remove non relevant > overlays in the future. I guess there must be some parameter in the DTSO > which i don't know, i hope you can give me some directions about that. It is not related to your DTBO's. That's how everything works (at least by default). You will see the same naming issue with serial ports, for example. And not just in BBB. E.g. when I have enabled uart0 and uart2 they are named ttyu0 and ttyu1, if I have only uart2, it becomes ttyu0. It's easier if there is a device node in /dev, so you can create a symlink with a fixed name (I have a script called by devd for my multiple serial ports). However, that's not the case with PWM... Maybe there is an option to use persistent names for devices that somebody can point to. S. > /dts-v1/; > /plugin/; > > / { > compatible = "ti,am335x-bone-black", "ti,am335x-bone", "ti,am33xx"; > exclusive-use = > "P9.21","P9.22","ehrpwm0_AB"; > }; > > &am33xx_pinmux { > ehrpwm0_AB_pins: pinmux_ehrpwm0_AB_pins { > pinctrl-single,pins = < > 0x154 0x03 /* P9.21 */ > 0x150 0x03 /* P9.22 */ > >; > }; > }; > > &ehrpwm0 { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <&ehrpwm0_AB_pins>; }; > &epwmss0 { > status = "okay"; > }; > &ecap0 { > status = "okay"; > }; > > /dts-v1/; > /plugin/; > / { > compatible = "ti,am335x-bone-black","ti,am335x-bone", "ti,am33xx"; > exclusive-use = > "P9.14","P9.16","ehrpwm1_AB"; > }; > > &am33xx_pinmux { > ehrpwm1_AB_pins: pinmux_ehrpwm1_AB_pins { > pinctrl-single,pins = < > 0x048 0x06 /* P9.14 */ > 0x04C 0x06 /* P9.16 */ > >; > }; > }; > > &ehrpwm1 { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <&ehrpwm1_AB_pins>; > }; > > &epwmss1 { > status = "okay"; > }; > > &ecap1 { > status = "okay"; > }; From owner-freebsd-arm@freebsd.org Thu Jun 6 22:40:48 2019 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 CF7D115C210A for ; Thu, 6 Jun 2019 22:40:48 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (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 217C48AD82 for ; Thu, 6 Jun 2019 22:40:48 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1559860846; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=r0Uw4+b8UhW/z+cV5MFRXqH93y/T74kaZvU1dBlFNXyn/2x9uz59ivr/XmQNGgR7BX16Aw9TaFzo2 9MWvLUJ4spv9D1ZOU2wa8cu1UotULPXNM4sjB63V1LnzYTQJyThv5NYB64ax7iM/G+C9fI4pxuhXLc 71gqPvlPTHG68NPiAA+lhQ79dVgAMPOk9e/pEl4pXb17OLczL2hPwDXBHXHfCLsdXrhTCquYO/c9m9 m6PsBk1SW857vNy3Osmo31nRj7rmDShLqt/tB0p0A3AbpdozB7FawSlUYmq7SKBDCs8NViWME/nEPQ yOUnIdhl/napCsIatx4gMffoQXf29XA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=Hkhkx0Z5xNWZXUC8fGbaeFb8k1D0v22sLE/+TbFJftE=; b=FKPYQyLRdSTuyJ1eU6AYNTi1ls7/3IiobQLe3xPfGxMFWgtOd+SaCbu0QT25VPtUgwhSbQGkNXNHH 9dqh2Fio0kJLEFJWpTSVuujyAPN1EQdoVSvjRcT/U9KaG+uqXv15AeQcT2f8NtSi4brZMzv9/7kzb3 YBAdz5unpe4i0kkvr5tr5611nys0e2z7CjATQUwrjb/1X2jwyGR6K0elni6q+eeZLnzQi/Mit1ZaQN KieVyBLdXJpjFqXlZFpgq31UzbbdSxck85bMOIr6N2MsX3TEivG3Si3aNtUTsgoH5DxrL5+mN3+/l8 Y/Tw6/2dPhHZRgQB1BQqrTUS9weTChg== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=Hkhkx0Z5xNWZXUC8fGbaeFb8k1D0v22sLE/+TbFJftE=; b=ayDSD056gHAlsRXTK7QxjoGaGHqhA6w83hDxTkBRk3XDjmC8+I0dZo4Za9M62X7bSD5s+105U1RXa X1H5Vki5+C2GUyeHuOgCTHO6bwun6scp4SyaVJIP1l9LaO519X5rtQ5ovwHBhjI0VEElAmQTY0dz0P aElLgY7jtjthUrchg91aWpNmxEVgu6vSUDaOVexH20RlkiXbOnB6EcwT7MUhgOvQbnzWpo2f1udmqj v5RA6yQeDPjXnsyr0g3V1OIij+uSooWC5hwwe1Kkaca+2fzSmnEdFeF85IXDJgnYD2zsWgXjrb8Kqo eH8SCfAr9J2S8nsdKB+7/Mc9nYkVr3g== X-MHO-RoutePath: aGlwcGll X-MHO-User: 1e422d72-88ac-11e9-b39a-9d2c53d3dedb X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 1e422d72-88ac-11e9-b39a-9d2c53d3dedb; Thu, 06 Jun 2019 22:40:44 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x56Meh7T069990; Thu, 6 Jun 2019 16:40:43 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> Subject: Re: How to set PWM tunable name to ehrpwm.1 ? From: Ian Lepore To: Sergey Manucharian , Nicola Mingotti Cc: nmingott@gmail.com, freebsd-arm@freebsd.org Date: Thu, 06 Jun 2019 16:40:43 -0600 In-Reply-To: <20190606220639.GE13546@eldorado> References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 217C48AD82 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Thu, 06 Jun 2019 22:40:49 -0000 On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: > > > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > > overlays, > > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 and > > respectively p9.14, p9.16. DTSO files are below. > > > > If I load both the DTBO at boot I see > > correctly|ehrpwm.0|and|ehrpwm.1|, > > associated to the correct pins. But, if i remove the > > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which is > > not > > what i want, i would like to see the name|ehrpwm.1|. > > > > This is important because i must be 100% sure a certain pin > > corresponds > > the a certain tunable.This must be true even if i remove non > > relevant > > overlays in the future. I guess there must be some parameter in the > > DTSO > > which i don't know, i hope you can give me some directions about > > that. > > It is not related to your DTBO's. That's how everything works (at > least > by default). You will see the same naming issue with serial ports, > for > example. And not just in BBB. > > E.g. when I have enabled uart0 and uart2 they are named ttyu0 and > ttyu1, > if I have only uart2, it becomes ttyu0. > > It's easier if there is a device node in /dev, so you can create a > symlink > with a fixed name (I have a script called by devd for my multiple > serial > ports). However, that's not the case with PWM... > > Maybe there is an option to use persistent names for devices that > somebody > can point to. > Nope, there's no magic thing you're missing that fixes this. Devices get named-and-numbered based on the order of instantiation. Since what really matters here is the sysctl names, we could change the driver to install the sysctl nodes using the fdt device node names instead of the freebsd newbus device names. Hmm, actually, since people may be relying on the current names, I guess what we'd have to do is install another set of sysctl names based on fdt name (basically a set of alias names). -- Ian From owner-freebsd-arm@freebsd.org Fri Jun 7 09:08:42 2019 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 DD47F15CCC88 for ; Fri, 7 Jun 2019 09:08:41 +0000 (UTC) (envelope-from nmingotti@gmail.com) Received: from mail-pg1-x541.google.com (mail-pg1-x541.google.com [IPv6:2607:f8b0:4864:20::541]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF9FB6BF3E; Fri, 7 Jun 2019 09:08:40 +0000 (UTC) (envelope-from nmingotti@gmail.com) Received: by mail-pg1-x541.google.com with SMTP id f25so820241pgv.10; Fri, 07 Jun 2019 02:08:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=CUxQDDCBeKwzSy6hBlFmJDBS3CutEd7CvdrpmUEAQZM=; b=MrszRZ48AqcbrYuf+2CztxEYQi/lGvbTAuIGeDkmGobKTkcgQm096C8kQWdZOT5MgQ fIfIHuz7XCg4xtEq0oU+4c3bwUaK9cJsH/U6JggwRHCI77ER6BHrInDM3KZhgXu+wy1D OMaUZEkRGv3duUs0idT4MBFLdSd3cCrAIlvJIxY7hFayjAwR9P6ZwwsNcGBqqtOFV0Q3 bfOdTrAQ+KD2h84JJ+KlJRwJKGBDL09fqJkJP+AcyVrsm4SiT5wd7SZtI45oPQWgw0GD TFXOKSqaKDwc57HNcqPr1XoG82G9HhWniecFaZ7QhIvoBPH3CVdUHnxzWWAvbLmFx6o3 DZJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=CUxQDDCBeKwzSy6hBlFmJDBS3CutEd7CvdrpmUEAQZM=; b=ohI342LJflf/NXkGHQKR+ERirGTN9FPSc66RqgIa3ve9rXr4e1dLITzEp6P9oFU9Hz w0jRu8Ixn7ReiQogdShnLjHMTIaHJPKedcog8SLIFpdY9Rp2H3QD2zQDYoUOcQDiifYE hLXIE/VqEaiikzD7T4o8xexXHmU75QXXm7DFSDPbxWyIEKIO3DPf0BSCrCa4imyRsBZu o0HLBotpgec2lFhU78FKU+IhnOHB8IIB2smu/S+9ZYx2Tx7KQdIIHicK4/WUcoPcOyoU XzZtZCC+7Cg/PDNbq/9uCo2+Q9C7JGHL15fag84pTYdzBgPPUqh54hzHZbVCuxQuUDr0 orwg== X-Gm-Message-State: APjAAAVTkErNrJvGNfv4OU7U0Qf1hPJ7ii2SleRT2XXS5WUqxJpxdMOp kUHKmm4UP8uyRBe8B+43y/BoGp5FVcE= X-Google-Smtp-Source: APXvYqwoqnVux5jSUZwpOoaSwolUJQdNMpnJSYloyCpezemSYGRoAFzfmbsb4TVI88R8CZYPLIETqw== X-Received: by 2002:a63:fb02:: with SMTP id o2mr1795406pgh.357.1559898518629; Fri, 07 Jun 2019 02:08:38 -0700 (PDT) Received: from [172.16.144.128] (c-73-158-18-93.hsd1.ca.comcast.net. [73.158.18.93]) by smtp.gmail.com with ESMTPSA id y19sm1842431pfe.150.2019.06.07.02.08.33 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jun 2019 02:08:37 -0700 (PDT) Subject: Re: How to set PWM tunable name to ehrpwm.1 ? To: Ian Lepore , Sergey Manucharian Cc: nmingott@gmail.com, freebsd-arm@freebsd.org References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> From: Nicola Mingotti Message-ID: <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> Date: Fri, 7 Jun 2019 02:08:32 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> Content-Language: en-US X-Rspamd-Queue-Id: AF9FB6BF3E X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=MrszRZ48; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of nmingotti@gmail.com designates 2607:f8b0:4864:20::541 as permitted sender) smtp.mailfrom=nmingotti@gmail.com X-Spamd-Result: default: False [-4.01 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.97)[-0.969,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_CC(0.00)[gmail.com]; IP_SCORE(-1.03)[ip: (0.40), ipnet: 2607:f8b0::/32(-3.22), asn: 15169(-2.30), country: US(-0.06)] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Fri, 07 Jun 2019 09:08:42 -0000 On 6/6/19 3:40 PM, Ian Lepore wrote: > On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: >> Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: >>> In my BeagleBone Black, FreeBSD-12 RELEASE, i created two >>> overlays, >>> pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 and >>> respectively p9.14, p9.16. DTSO files are below. >>> >>> If I load both the DTBO at boot I see >>> correctly|ehrpwm.0|and|ehrpwm.1|, >>> associated to the correct pins. But, if i remove the >>> overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which is >>> not >>> what i want, i would like to see the name|ehrpwm.1|. >>> >>> This is important because i must be 100% sure a certain pin >>> corresponds >>> the a certain tunable.This must be true even if i remove non >>> relevant >>> overlays in the future. I guess there must be some parameter in the >>> DTSO >>> which i don't know, i hope you can give me some directions about >>> that. >> It is not related to your DTBO's. That's how everything works (at >> least >> by default). You will see the same naming issue with serial ports, >> for >> example. And not just in BBB. >> >> E.g. when I have enabled uart0 and uart2 they are named ttyu0 and >> ttyu1, >> if I have only uart2, it becomes ttyu0. >> >> It's easier if there is a device node in /dev, so you can create a >> symlink >> with a fixed name (I have a script called by devd for my multiple >> serial >> ports). However, that's not the case with PWM... >> >> Maybe there is an option to use persistent names for devices that >> somebody >> can point to. >> > Nope, there's no magic thing you're missing that fixes this. Devices > get named-and-numbered based on the order of instantiation. > > Since what really matters here is the sysctl names, we could change the > driver to install the sysctl nodes using the fdt device node names > instead of the freebsd newbus device names. Hmm, actually, since > people may be relying on the current names, I guess what we'd have to > do is install another set of sysctl names based on fdt name (basically > a set of alias names). > > -- Ian > I see, I agree changing the default naming scheme may damage who is relaying on it. It is not a good idea. Maybe it could be implemented in release 13. To Sergey. I used devd in the past, it works well. But i would prefer not to use it in this case, even if I had a /dev/xyz file available. The reason is that the /dev/xyz file would appear before the the devd daemon starts up (i guess), so the case would not stricly be covered by what the devd man page says devd should do. $> man devd => " ... Whenever a device is added to or removed from the device tree ... " To Ian. The idea of the alias seems good. I don't know at all what you can manage to do at the kernel level with the tunables. I imagine something like |dev.alias.am335x_ehrpwm.1| which actually refers to |EHRPWM1| not the second |ehrpwm| that got plugged into the system via overlay. Thank you for your answers goodbye Nicola From owner-freebsd-arm@freebsd.org Fri Jun 7 11:33:01 2019 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 68A6215AA0E1 for ; Fri, 7 Jun 2019 11:33:01 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 08FFD6FC30; Fri, 7 Jun 2019 11:32:59 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x57BONlU048106 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 7 Jun 2019 13:24:24 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1559906665; bh=YabiD4CcdmfXy/2jDrIPnY80329AGjmTKhY7RhRdfEw=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=MsEnLBEC1HkXu/hXzeYZgoR06vZFE3mzhYo733mK49HjZgCsIsQEpMY5T8JVpZjrs /eX8PUJGiqvc800pwO/KvYTd3e0KRyFE+hev8gugz8topY3YZ1Ln+jFsVBlNQb5bTu ICFDas7ii6WLPL/K6c1RSk4Q55oXF9ST92ukdvRw= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x57BOB9G067732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jun 2019 13:24:11 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x57BOAfk080100; Fri, 7 Jun 2019 13:24:10 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x57BO9oa080099; Fri, 7 Jun 2019 13:24:09 +0200 (CEST) (envelope-from ticso) Date: Fri, 7 Jun 2019 13:24:09 +0200 From: Bernd Walter To: Nicola Mingotti Cc: Ian Lepore , Sergey Manucharian , nmingott@gmail.com, freebsd-arm@freebsd.org Subject: Re: How to set PWM tunable name to ehrpwm.1 ? Message-ID: <20190607112409.GO40697@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: 08FFD6FC30 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=MsEnLBEC X-Spamd-Result: default: False [-0.98 / 15.00]; HAS_REPLYTO(0.00)[ticso@cicely.de]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; RCPT_COUNT_FIVE(0.00)[5]; DKIM_TRACE(0.00)[cicely.de:+]; MX_GOOD(-0.01)[mx1.bwct.de]; NEURAL_HAM_SHORT(-0.40)[-0.404,0]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.858,0]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.90)[-0.904,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-0.00)[country: DE(-0.01)]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; R_SPF_NA(0.00)[] 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: Fri, 07 Jun 2019 11:33:01 -0000 On Fri, Jun 07, 2019 at 02:08:32AM -0700, Nicola Mingotti wrote: > > > On 6/6/19 3:40 PM, Ian Lepore wrote: > >On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > >>Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: > >>>In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > >>>overlays, > >>>pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 and > >>>respectively p9.14, p9.16. DTSO files are below. > >>> > >>>If I load both the DTBO at boot I see > >>>correctly|ehrpwm.0|and|ehrpwm.1|, > >>>associated to the correct pins. But, if i remove the > >>>overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which is > >>>not > >>>what i want, i would like to see the name|ehrpwm.1|. > >>> > >>>This is important because i must be 100% sure a certain pin > >>>corresponds > >>>the a certain tunable.This must be true even if i remove non > >>>relevant > >>>overlays in the future. I guess there must be some parameter in the > >>>DTSO > >>>which i don't know, i hope you can give me some directions about > >>>that. > >>It is not related to your DTBO's. That's how everything works (at > >>least > >>by default). You will see the same naming issue with serial ports, > >>for > >>example. And not just in BBB. > >> > >>E.g. when I have enabled uart0 and uart2 they are named ttyu0 and > >>ttyu1, > >>if I have only uart2, it becomes ttyu0. > >> > >>It's easier if there is a device node in /dev, so you can create a > >>symlink > >>with a fixed name (I have a script called by devd for my multiple > >>serial > >>ports). However, that's not the case with PWM... > >> > >>Maybe there is an option to use persistent names for devices that > >>somebody > >>can point to. > >> > >Nope, there's no magic thing you're missing that fixes this. Devices > >get named-and-numbered based on the order of instantiation. > > > >Since what really matters here is the sysctl names, we could change the > >driver to install the sysctl nodes using the fdt device node names > >instead of the freebsd newbus device names. Hmm, actually, since > >people may be relying on the current names, I guess what we'd have to > >do is install another set of sysctl names based on fdt name (basically > >a set of alias names). > > > >-- Ian > > > > I see, I agree changing the default naming scheme may damage who is > relaying on it. It is not a good idea. Maybe it could be implemented in > release 13. > > To Sergey. I used devd in the past, it works well. But i would prefer > not to use it in this case, even if I had a /dev/xyz file available. The > reason is that the /dev/xyz file would appear before the the devd daemon > starts up (i guess), so the case would not stricly be covered by what > the devd man page says devd should do. > $> man devd > => " ... Whenever a device is added to or removed from the device tree ... " > > To Ian. The idea of the alias seems good. I don't know at all what you > can manage to do at the kernel level with the tunables. I imagine > something like |dev.alias.am335x_ehrpwm.1| which actually refers to > |EHRPWM1| not the second |ehrpwm| that got plugged into the system via > overlay. > > Thank you for your answers I don't know if it would work for you, but I'm a happy user of devd for such things. This is devinfo -rv on a Pine64: ... uart0 pnpinfo name=serial@1c28000 compat=snps,dw-apb-uart ... I assume it is similar to what you should see on the beaglebone. It should be easy to identify a specific device via the name= entry. Messages to devd gets queued up and it shouldn't matter if the device is already attached when devd starts. This is what I use for USB uarts: attach 0 { device-name "uftdi[0-9]+"; match "sernum" "FTYY82HD"; match "interface" "0"; action "rm /dev/manson_psu5; ln -s /dev/cua$ttyname /dev/manson_psu5"; }; Since uart(4) doen't offer a nice $ttyname, you have to convert the device-name into the matching cuau* entry. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Jun 7 14:58:59 2019 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 60AE315AF19C for ; Fri, 7 Jun 2019 14:58:59 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1.eu.mailhop.org (outbound1.eu.mailhop.org [52.28.251.132]) (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 8601D75999 for ; Fri, 7 Jun 2019 14:58:58 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1559919535; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=RI3rqtDnS5UIO2RsacffYp3JiM4TcRMTw0uYgdf4Q5PGr5U9jKwiSrdiVloVuhWPV81UleqmloKfL 5SmdIVrBEHAbhKI+cf7CnfbBJD4yZATK8LjK7bFre+tWCEBb9NvWb1nZVXFA4vTdjyRQt7IGBo6Ziu F3RK2+Y3pDhY/WOImvQGpUP46JgCWcw+MbCCwZ9YScUlhZTi0a21oIsMjLpzCFCQ26j7Sc07ApEedG WPAtkBsskjrmQTw7Ceu113odDOYxfHY4sR3+4V4lCeVZTUpJKz7567OO+TCEHtnTpJgkjABNz4EAFW bav76wJwo8ns6wSHBspOc8MzKtfYZDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=TiCtm3a7Ks8jR/y79BZaWJG3Ce0VONxE4JblJd9/+qY=; b=NmfN8W4Fn9cVThl8NtpFweECjIpH/5wTTs0W1lJyoeCtTFdFsVS3O9dkYRYBmbWyR6tlvazya4dlT P1ZoTsYcbFQcOOlYvcxUGNhvb8iCRUn1G7b3CbeOdFunXv0d8fe02GOf3Oup57ofJ1i0yX/NBSXFi/ eg4Q/npqiFPUA4lOifHwiYuBTwuOahEgVRgi3vHFhLnV26u7IB+BSGHCPz+2li+oV/cpX7lPIY6Mxm wbCF8rMOk4v2WHiGeoV6w7i1XG3JmeVIYpAXdpZhzv6mwmaIrn4GsfY++cm8988jlC97BxJYGQIRx4 w0S/H/FL/XB2NRdD4Lh9lIwn4pZEbsg== ARC-Authentication-Results: i=1; outbound3.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=TiCtm3a7Ks8jR/y79BZaWJG3Ce0VONxE4JblJd9/+qY=; b=ZKXbhoKau6Udi6YIXhNNDURfCY0136YkaEUpNo9xk+jkyVyDVW7U3F1xI06/M1FBxenwYE399e/Bt CwS9kFB9MrTsKca4M2mnPuzRZArZTqKxkZVsFLxVI1SkVRdlIkZfetb+Kpbl45Itq3YJhCBDrbs51/ MSboFpzZg9IdkYY2+71rBWX4iZjiXqsI/Vnp4zA5nrhpfaLuRpNdVrpouK0gyH8kcpXXJjCAc0ytdC DxV2LCbpEEfT5yAlfRznCZ64YA8PbLKTZqJBXJ4CbmtvWrQR3iywPxAx2O6bFIm0poyERFx3CPg6xj GMzCutWbKNLHW6+YFWxo1pnnzy2+cVg== X-MHO-RoutePath: aGlwcGll X-MHO-User: c25e393b-8934-11e9-91aa-b56e4e6b5865 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.eu.mailhop.org (Halon) with ESMTPSA id c25e393b-8934-11e9-91aa-b56e4e6b5865; Fri, 07 Jun 2019 14:58:52 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x57EwnCK072893; Fri, 7 Jun 2019 08:58:49 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: How to set PWM tunable name to ehrpwm.1 ? From: Ian Lepore To: Nicola Mingotti , Sergey Manucharian Cc: nmingott@gmail.com, freebsd-arm@freebsd.org Date: Fri, 07 Jun 2019 08:58:49 -0600 In-Reply-To: <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 8601D75999 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country: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: Fri, 07 Jun 2019 14:58:59 -0000 On Fri, 2019-06-07 at 02:08 -0700, Nicola Mingotti wrote: > > On 6/6/19 3:40 PM, Ian Lepore wrote: > > On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > > > Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: > > > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > > > > overlays, > > > > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 > > > > and > > > > respectively p9.14, p9.16. DTSO files are below. > > > > > > > > If I load both the DTBO at boot I see > > > > correctly|ehrpwm.0|and|ehrpwm.1|, > > > > associated to the correct pins. But, if i remove the > > > > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which > > > > is > > > > not > > > > what i want, i would like to see the name|ehrpwm.1|. > > > > > > > > This is important because i must be 100% sure a certain pin > > > > corresponds > > > > the a certain tunable.This must be true even if i remove non > > > > relevant > > > > overlays in the future. I guess there must be some parameter in > > > > the > > > > DTSO > > > > which i don't know, i hope you can give me some directions > > > > about > > > > that. > > > > > > It is not related to your DTBO's. That's how everything works (at > > > least > > > by default). You will see the same naming issue with serial > > > ports, > > > for > > > example. And not just in BBB. > > > > > > E.g. when I have enabled uart0 and uart2 they are named ttyu0 and > > > ttyu1, > > > if I have only uart2, it becomes ttyu0. > > > > > > It's easier if there is a device node in /dev, so you can create > > > a > > > symlink > > > with a fixed name (I have a script called by devd for my multiple > > > serial > > > ports). However, that's not the case with PWM... > > > > > > Maybe there is an option to use persistent names for devices that > > > somebody > > > can point to. > > > > > > > Nope, there's no magic thing you're missing that fixes > > this. Devices > > get named-and-numbered based on the order of instantiation. > > > > Since what really matters here is the sysctl names, we could change > > the > > driver to install the sysctl nodes using the fdt device node names > > instead of the freebsd newbus device names. Hmm, actually, since > > people may be relying on the current names, I guess what we'd have > > to > > do is install another set of sysctl names based on fdt name > > (basically > > a set of alias names). > > > > -- Ian > > > > I see, I agree changing the default naming scheme may damage who is > relaying on it. It is not a good idea. Maybe it could be implemented > in > release 13. > > To Sergey. I used devd in the past, it works well. But i would > prefer > not to use it in this case, even if I had a /dev/xyz file available. > The > reason is that the /dev/xyz file would appear before the the devd > daemon > starts up (i guess), so the case would not stricly be covered by > what > the devd man page says devd should do. > $> man devd > => " ... Whenever a device is added to or removed from the device > tree ... " > > To Ian. The idea of the alias seems good. I don't know at all what > you > can manage to do at the kernel level with the tunables. I imagine > something like |dev.alias.am335x_ehrpwm.1| which actually refers to > > EHRPWM1| not the second |ehrpwm| that got plugged into the system > > via > > overlay. > > Thank you for your answers > > The dev.* hierarchy is managed by newbus; what I was picturing was something like hw.ehrpwm1.freq and so on, settable as either tunable or sysctl. But it turns out ehrpwm1 is just a label in the dts, not accessible at runtime. The actual node name is just 'pwm' and really, nothing prevents upstream from changing that name on a whim next time we import new dts files. (And linux sure seems to have a lot of arbitrary whims when it comes to changing dts.) Since an overlay is required to use this stuff anyway, I'm now thinking a custom property in the overlay that names the sysctl nodes might be a good option. So you'd add a property like: &ehrpwm0 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&ehrpwm0_AB_pins>; freebsd,sysctl = "backlight"; }; And that would make it install names like hw.backlight.freq and hw.backlight.period and so on. If you don't add that property, it just installs the names it uses now (dev.ehrpwm.*) for compatibility. -- Ian From owner-freebsd-arm@freebsd.org Fri Jun 7 15:03:19 2019 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 695E115AF52A for ; Fri, 7 Jun 2019 15:03:19 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1.eu.mailhop.org (outbound1.eu.mailhop.org [52.28.251.132]) (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 C555375E3A for ; Fri, 7 Jun 2019 15:03:18 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1559919796; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=a7zmsqCK212jKzKGgFu3hIZ5tOKnm1GxpuJVpXl8nc++KMU2GSKg0wvPFdY0bvznyW9p+L4oiASJr xH02nwL1NAs/Cwv9aWfpsIwQx7CyTqQUUI1nUjCWUupDpUcUEorhpPuLX7wBi0GmytuRArIcrp/2+O RfhaP5sKkGhfBVcXyZWPOHIwjMflg8e22h0s+7b0OhM+GvjEtD1ytLm9iai3qkBff9gEljuDan3nv5 YmDJVpLJ68QsLrcVNAeJTwI9EI7CY5LV0mXwt3YzQGB1BatTjhLpM5Cvk/Yao8lWZ1oZwn8nZPN7Q2 qVI/VUa3hcZgJsBAA8z3Li+YsXhSeqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=QThXsXKlFX8hRj962zCUdzPC9rTAlhwrm3D23kHLWNk=; b=JFqDJVn27/NTNMtQpCK4iIEcPOnph+WN60NPUR0h4HNRwFyJC0s/ewDA8+uMuUKXc8vXjccNrGXP8 LYpZlB8AjKP4cKihY7Ttfp4bTXX5+x3tazuRCiNumwCN6nAesxy3HQcetrxDwrBDxRR0UKx4/nO6IR 0hqssAygFfFv5naWnMgsjgyU+Cy+EL09dD33keYY3VNiqg89/3I+Lpu+OMIbUskDzYr2GPHhpHX/cd r9w3Hr5ddRvZxt7Kk4EP8WbYPwEg25YDwHH9Cfl5JwyJeM9gG4dl6edD4LJ5rQw/Ya0bNsGhdDx/ws 8DflUhYfSCYh8hUzPjeX2sn6pp/5ubw== ARC-Authentication-Results: i=1; outbound3.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=QThXsXKlFX8hRj962zCUdzPC9rTAlhwrm3D23kHLWNk=; b=bP0n4f/u9+wGL0lU2SzwErCNYffOsF96cGQhn3+hKP95ebPH5EaqSoyAngyclzHrxeNN5deLfnLY8 TN28J01R3lzQdLzYAl/EWKA1p5ZrXz+5jIzrLm5cTNVkgcTPZK9g1jmvi6y04B+r/1J3pNGZ7iIbHE fQrcaJ+W+LSgiu5NTqPzkCkN6z4JHMusSgGGpJr3YZnCZcXS1PQpBiegQequ7GjNOwH145KmptHdfy 4KnaZx13X0SNNPwtHwWxiFM2PH7EgSYC/ItLe3ooWKVTG3x9aRQcOKAxD8q0uP5LVc5hNV+GXtg7+i cFLNBZDajanpz+SX/Ed4vbPFuV0xICg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 5e1960bf-8935-11e9-91aa-b56e4e6b5865 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.eu.mailhop.org (Halon) with ESMTPSA id 5e1960bf-8935-11e9-91aa-b56e4e6b5865; Fri, 07 Jun 2019 15:03:13 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x57F3B3s072922; Fri, 7 Jun 2019 09:03:11 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <42216eebac3c497b09f83f29faf68b0c74f903ce.camel@freebsd.org> Subject: Re: How to set PWM tunable name to ehrpwm.1 ? From: Ian Lepore To: ticso@cicely.de, Nicola Mingotti Cc: freebsd-arm@freebsd.org Date: Fri, 07 Jun 2019 09:03:11 -0600 In-Reply-To: <20190607112409.GO40697@cicely7.cicely.de> References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> <20190607112409.GO40697@cicely7.cicely.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: C555375E3A X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Fri, 07 Jun 2019 15:03:19 -0000 On Fri, 2019-06-07 at 13:24 +0200, Bernd Walter wrote: > On Fri, Jun 07, 2019 at 02:08:32AM -0700, Nicola Mingotti wrote: > > > > > > On 6/6/19 3:40 PM, Ian Lepore wrote: > > > On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > > > > Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 > > > > 12:33: > > > > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > > > > > overlays, > > > > > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 > > > > > and > > > > > respectively p9.14, p9.16. DTSO files are below. > > > > > > > > > > If I load both the DTBO at boot I see > > > > > correctly|ehrpwm.0|and|ehrpwm.1|, > > > > > associated to the correct pins. But, if i remove the > > > > > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, > > > > > which is > > > > > not > > > > > what i want, i would like to see the name|ehrpwm.1|. > > > > > > > > > > This is important because i must be 100% sure a certain pin > > > > > corresponds > > > > > the a certain tunable.This must be true even if i remove non > > > > > relevant > > > > > overlays in the future. I guess there must be some parameter > > > > > in the > > > > > DTSO > > > > > which i don't know, i hope you can give me some directions > > > > > about > > > > > that. > > > > > > > > It is not related to your DTBO's. That's how everything works > > > > (at > > > > least > > > > by default). You will see the same naming issue with serial > > > > ports, > > > > for > > > > example. And not just in BBB. > > > > > > > > E.g. when I have enabled uart0 and uart2 they are named ttyu0 > > > > and > > > > ttyu1, > > > > if I have only uart2, it becomes ttyu0. > > > > > > > > It's easier if there is a device node in /dev, so you can > > > > create a > > > > symlink > > > > with a fixed name (I have a script called by devd for my > > > > multiple > > > > serial > > > > ports). However, that's not the case with PWM... > > > > > > > > Maybe there is an option to use persistent names for devices > > > > that > > > > somebody > > > > can point to. > > > > > > > > > > Nope, there's no magic thing you're missing that fixes > > > this. Devices > > > get named-and-numbered based on the order of instantiation. > > > > > > Since what really matters here is the sysctl names, we could > > > change the > > > driver to install the sysctl nodes using the fdt device node > > > names > > > instead of the freebsd newbus device names. Hmm, actually, since > > > people may be relying on the current names, I guess what we'd > > > have to > > > do is install another set of sysctl names based on fdt name > > > (basically > > > a set of alias names). > > > > > > -- Ian > > > > > > > I see, I agree changing the default naming scheme may damage who > > is > > relaying on it. It is not a good idea. Maybe it could be > > implemented in > > release 13. > > > > To Sergey. I used devd in the past, it works well. But i would > > prefer > > not to use it in this case, even if I had a /dev/xyz file > > available. The > > reason is that the /dev/xyz file would appear before the the devd > > daemon > > starts up (i guess), so the case would not stricly be covered by > > what > > the devd man page says devd should do. > > $> man devd > > => " ... Whenever a device is added to or removed from the device > > tree ... " > > > > To Ian. The idea of the alias seems good. I don't know at all what > > you > > can manage to do at the kernel level with the tunables. I imagine > > something like |dev.alias.am335x_ehrpwm.1| which actually refers > > to > > > EHRPWM1| not the second |ehrpwm| that got plugged into the system > > > via > > > > overlay. > > > > Thank you for your answers > > I don't know if it would work for you, but I'm a happy user of devd > for > such things. > This is devinfo -rv on a Pine64: > ... > uart0 pnpinfo name=serial@1c28000 compat=snps,dw-apb-uart > ... > I assume it is similar to what you should see on the beaglebone. > It should be easy to identify a specific device via the name= entry. > Messages to devd gets queued up and it shouldn't matter if the device > is > already attached when devd starts. > > This is what I use for USB uarts: > attach 0 { > device-name "uftdi[0-9]+"; > match "sernum" "FTYY82HD"; > match "interface" "0"; > action "rm /dev/manson_psu5; ln -s > /dev/cua$ttyname /dev/manson_psu5"; > }; > > Since uart(4) doen't offer a nice $ttyname, you have to convert the > device-name into the matching cuau* entry. > Not quite the same thing. You're using a devd rule to manipulate things in devfs. We're talking about sysctl nodes which are named after the newbus device. It would be the equivelent of making the ftdi driver install sysctl nodes that were named something other than dev.uftdi.*. -- Ian From owner-freebsd-arm@freebsd.org Fri Jun 7 15:10:14 2019 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 CBE1215AF695 for ; Fri, 7 Jun 2019 15:10:14 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 85A8276030; Fri, 7 Jun 2019 15:10:12 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id b00fca33; Fri, 7 Jun 2019 17:10:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=y56/r21YRFMO1h2KtzmwvBj3aIs=; b=Zlu13qa7YqpGsaG6t5l6tG+8yOtN sabu8G/71K2ZOw+Beldn17w41I65B+9HaVB7pxCsAr8qcGTUahBf4cVbJ31En3GB bQLRfnj/EHt7lK3D77Tyvl8lZzubB6QvXHhPXjetagtUVZd1Si7hDTTAp7wKUAvY bmRP4gL844kg4EA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=eRdO4okYw72dylT99kd/7Co288yDZJwF2j7OWK2Uve07OU3DPKmJj9c9 wlL1yGwvJBqjaLZ9TXjpmVl36uKHNSV5N7EkHHe2PmrNN3yWxPKWC6sbDEo9w5h9 cz4Nij540p0wzFQ3onYZFj8jMEfChEI4GKP1X5oUSEGf8qV3888= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 98bfa341 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Fri, 7 Jun 2019 17:10:04 +0200 (CEST) Date: Fri, 7 Jun 2019 17:10:01 +0200 From: Emmanuel Vadot To: Ian Lepore Cc: Nicola Mingotti , Sergey Manucharian , nmingott@gmail.com, freebsd-arm@freebsd.org Subject: Re: How to set PWM tunable name to ehrpwm.1 ? Message-Id: <20190607171001.636efb2598ab9c88635973b6@bidouilliste.com> In-Reply-To: References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 85A8276030 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=Zlu13qa7; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [2.06 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; NEURAL_HAM_MEDIUM(-0.01)[-0.015,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.58)[0.581,0]; DKIM_TRACE(0.00)[bidouilliste.com:+]; MX_GOOD(-0.01)[mx-backup.blih.net,mail.blih.net]; NEURAL_SPAM_LONG(0.12)[0.118,0]; IP_SCORE(0.29)[ip: (-1.18), ipnet: 212.83.160.0/19(2.86), asn: 12876(-0.23), country: FR(-0.01)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Fri, 07 Jun 2019 15:10:15 -0000 On Fri, 07 Jun 2019 08:58:49 -0600 Ian Lepore wrote: > On Fri, 2019-06-07 at 02:08 -0700, Nicola Mingotti wrote: > > > > On 6/6/19 3:40 PM, Ian Lepore wrote: > > > On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > > > > Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: > > > > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > > > > > overlays, > > > > > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 > > > > > and > > > > > respectively p9.14, p9.16. DTSO files are below. > > > > > > > > > > If I load both the DTBO at boot I see > > > > > correctly|ehrpwm.0|and|ehrpwm.1|, > > > > > associated to the correct pins. But, if i remove the > > > > > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which > > > > > is > > > > > not > > > > > what i want, i would like to see the name|ehrpwm.1|. > > > > > > > > > > This is important because i must be 100% sure a certain pin > > > > > corresponds > > > > > the a certain tunable.This must be true even if i remove non > > > > > relevant > > > > > overlays in the future. I guess there must be some parameter in > > > > > the > > > > > DTSO > > > > > which i don't know, i hope you can give me some directions > > > > > about > > > > > that. > > > > > > > > It is not related to your DTBO's. That's how everything works (at > > > > least > > > > by default). You will see the same naming issue with serial > > > > ports, > > > > for > > > > example. And not just in BBB. > > > > > > > > E.g. when I have enabled uart0 and uart2 they are named ttyu0 and > > > > ttyu1, > > > > if I have only uart2, it becomes ttyu0. > > > > > > > > It's easier if there is a device node in /dev, so you can create > > > > a > > > > symlink > > > > with a fixed name (I have a script called by devd for my multiple > > > > serial > > > > ports). However, that's not the case with PWM... > > > > > > > > Maybe there is an option to use persistent names for devices that > > > > somebody > > > > can point to. > > > > > > > > > > Nope, there's no magic thing you're missing that fixes > > > this. Devices > > > get named-and-numbered based on the order of instantiation. > > > > > > Since what really matters here is the sysctl names, we could change > > > the > > > driver to install the sysctl nodes using the fdt device node names > > > instead of the freebsd newbus device names. Hmm, actually, since > > > people may be relying on the current names, I guess what we'd have > > > to > > > do is install another set of sysctl names based on fdt name > > > (basically > > > a set of alias names). > > > > > > -- Ian > > > > > > > I see, I agree changing the default naming scheme may damage who is > > relaying on it. It is not a good idea. Maybe it could be implemented > > in > > release 13. > > > > To Sergey. I used devd in the past, it works well. But i would > > prefer > > not to use it in this case, even if I had a /dev/xyz file available. > > The > > reason is that the /dev/xyz file would appear before the the devd > > daemon > > starts up (i guess), so the case would not stricly be covered by > > what > > the devd man page says devd should do. > > $> man devd > > => " ... Whenever a device is added to or removed from the device > > tree ... " > > > > To Ian. The idea of the alias seems good. I don't know at all what > > you > > can manage to do at the kernel level with the tunables. I imagine > > something like |dev.alias.am335x_ehrpwm.1| which actually refers to > > > EHRPWM1| not the second |ehrpwm| that got plugged into the system > > > via > > > > overlay. > > > > Thank you for your answers > > > > > > The dev.* hierarchy is managed by newbus; what I was picturing was > something like hw.ehrpwm1.freq and so on, settable as either tunable or > sysctl. But it turns out ehrpwm1 is just a label in the dts, not > accessible at runtime. The actual node name is just 'pwm' and really, > nothing prevents upstream from changing that name on a whim next time > we import new dts files. (And linux sure seems to have a lot of > arbitrary whims when it comes to changing dts.) Relying on the name is clearly not a good idea, especially for TI since they change stuff A LOT. > Since an overlay is required to use this stuff anyway, I'm now thinking > a custom property in the overlay that names the sysctl nodes might be a > good option. So you'd add a property like: > > &ehrpwm0 { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <&ehrpwm0_AB_pins>; > freebsd,sysctl = "backlight"; > }; > > And that would make it install names like hw.backlight.freq and > hw.backlight.period and so on. If you don't add that property, it just > installs the names it uses now (dev.ehrpwm.*) for compatibility. > > -- Ian What would be better is to add support to the pwm(9) api for this driver and make the api and pwm(8) using the "pwm-names" property which is a standard one from the bindings. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Fri Jun 7 15:17:14 2019 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 0017515AF922 for ; Fri, 7 Jun 2019 15:17:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2809176432 for ; Fri, 7 Jun 2019 15:17:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x729.google.com with SMTP id a27so1467500qkk.5 for ; Fri, 07 Jun 2019 08:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2a0Tyx7cPlSJw50p1bW3ju/+ZP6YEf+Dgr7tN3Ph+OE=; b=1BGoD2uDXx/hXcWBGCnLdMS6dUUDI9u9FfDsgfyNJ+8m2jCG5QPcXPmgZVjGNlQHT+ 0A4IMARg+TXK7mVeAnEXU6Cw4ej1RG/I3mQaz4Ctza7u929N+r/umk8C56B1CsWnUD89 az1mPIqQHbBPrSKYEW60BzbXt+PEBKbJPQ7Txk62voqb8c0z1a01JYhENHQEoHEKyJ3V otVphLxAaabI5aox+Cq/2gwNNVFsYCJTGLv7utUSbqCg3oz9LMZbjzlp3MfWNNESfth6 P18G80TjmSh5Qu/cBaz6v2Zl8lhmAGHAe6wGrmWtAxD3dtUIMpNND8BnogeQ36RBum+8 HJDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2a0Tyx7cPlSJw50p1bW3ju/+ZP6YEf+Dgr7tN3Ph+OE=; b=KC4wLZIG5r+0Xf6/F6QnSnkaUmIwJJX6Uc9DzvBqCjUe9KSm7eqJDy6CT8tzhnyEcn peWav4dCw215XCWf/s/iX92saCsn57CcniWI3Zyhx3Wrgo1nXSImxpjobbXW0kZPlQKp 0me2rAc5iN1VskMybHKCKa39FKcDcO/FgL3g1bNdzBDbt/wAj4FSkZ//7XYnbgCJmBbA WqmVUORFAlqKCzlrcB2b41i8FyannGw21P1HtFlmw7XH/r/kqkXpfw9DKJEk3y/DXRBF 8bE92h87bajS0pB6DJXmb2+2YKl1BoUaMD8zWkWr9ZnOxwhoiEUVZySFzNhUlUICU5JP l+MA== X-Gm-Message-State: APjAAAX2wJJehvtFZIpP1mYPeMJ3rl64qkY8iBJSGKOLiJGfuASGDtb4 EHU5PDR4l6H0ysHuXABBoKg5R87d+IFxj9H86b+OLQ== X-Google-Smtp-Source: APXvYqxuTXPMwz33oKpfulrQcFybYL8xgNNN7P9jlGtUuosRHKli+ywwEHaBrFQKk7oLI6UKOhmAo+ZHV5wJy0LA+3k= X-Received: by 2002:a37:5942:: with SMTP id n63mr31799666qkb.69.1559920632156; Fri, 07 Jun 2019 08:17:12 -0700 (PDT) MIME-Version: 1.0 References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> <20190607171001.636efb2598ab9c88635973b6@bidouilliste.com> In-Reply-To: <20190607171001.636efb2598ab9c88635973b6@bidouilliste.com> From: Warner Losh Date: Fri, 7 Jun 2019 09:17:01 -0600 Message-ID: Subject: Re: How to set PWM tunable name to ehrpwm.1 ? To: Emmanuel Vadot Cc: Ian Lepore , nmingott@gmail.com, "freebsd-arm@freebsd.org" X-Rspamd-Queue-Id: 2809176432 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=1BGoD2uD X-Spamd-Result: default: False [-4.92 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; IP_SCORE(-2.99)[ip: (-9.39), ipnet: 2607:f8b0::/32(-3.22), asn: 15169(-2.30), country: US(-0.06)]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[9.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.92)[-0.917,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Fri, 07 Jun 2019 15:17:14 -0000 On Fri, Jun 7, 2019 at 9:11 AM Emmanuel Vadot wrote: > On Fri, 07 Jun 2019 08:58:49 -0600 > Ian Lepore wrote: > > > On Fri, 2019-06-07 at 02:08 -0700, Nicola Mingotti wrote: > > > > > > On 6/6/19 3:40 PM, Ian Lepore wrote: > > > > On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > > > > > Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: > > > > > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > > > > > > overlays, > > > > > > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 > > > > > > and > > > > > > respectively p9.14, p9.16. DTSO files are below. > > > > > > > > > > > > If I load both the DTBO at boot I see > > > > > > correctly|ehrpwm.0|and|ehrpwm.1|, > > > > > > associated to the correct pins. But, if i remove the > > > > > > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which > > > > > > is > > > > > > not > > > > > > what i want, i would like to see the name|ehrpwm.1|. > > > > > > > > > > > > This is important because i must be 100% sure a certain pin > > > > > > corresponds > > > > > > the a certain tunable.This must be true even if i remove non > > > > > > relevant > > > > > > overlays in the future. I guess there must be some parameter in > > > > > > the > > > > > > DTSO > > > > > > which i don't know, i hope you can give me some directions > > > > > > about > > > > > > that. > > > > > > > > > > It is not related to your DTBO's. That's how everything works (at > > > > > least > > > > > by default). You will see the same naming issue with serial > > > > > ports, > > > > > for > > > > > example. And not just in BBB. > > > > > > > > > > E.g. when I have enabled uart0 and uart2 they are named ttyu0 and > > > > > ttyu1, > > > > > if I have only uart2, it becomes ttyu0. > > > > > > > > > > It's easier if there is a device node in /dev, so you can create > > > > > a > > > > > symlink > > > > > with a fixed name (I have a script called by devd for my multiple > > > > > serial > > > > > ports). However, that's not the case with PWM... > > > > > > > > > > Maybe there is an option to use persistent names for devices that > > > > > somebody > > > > > can point to. > > > > > > > > > > > > > Nope, there's no magic thing you're missing that fixes > > > > this. Devices > > > > get named-and-numbered based on the order of instantiation. > > > > > > > > Since what really matters here is the sysctl names, we could change > > > > the > > > > driver to install the sysctl nodes using the fdt device node names > > > > instead of the freebsd newbus device names. Hmm, actually, since > > > > people may be relying on the current names, I guess what we'd have > > > > to > > > > do is install another set of sysctl names based on fdt name > > > > (basically > > > > a set of alias names). > > > > > > > > -- Ian > > > > > > > > > > I see, I agree changing the default naming scheme may damage who is > > > relaying on it. It is not a good idea. Maybe it could be implemented > > > in > > > release 13. > > > > > > To Sergey. I used devd in the past, it works well. But i would > > > prefer > > > not to use it in this case, even if I had a /dev/xyz file available. > > > The > > > reason is that the /dev/xyz file would appear before the the devd > > > daemon > > > starts up (i guess), so the case would not stricly be covered by > > > what > > > the devd man page says devd should do. > > > $> man devd > > > => " ... Whenever a device is added to or removed from the device > > > tree ... " > > > > > > To Ian. The idea of the alias seems good. I don't know at all what > > > you > > > can manage to do at the kernel level with the tunables. I imagine > > > something like |dev.alias.am335x_ehrpwm.1| which actually refers to > > > > EHRPWM1| not the second |ehrpwm| that got plugged into the system > > > > via > > > > > > overlay. > > > > > > Thank you for your answers > > > > > > > > > > The dev.* hierarchy is managed by newbus; what I was picturing was > > something like hw.ehrpwm1.freq and so on, settable as either tunable or > > sysctl. But it turns out ehrpwm1 is just a label in the dts, not > > accessible at runtime. The actual node name is just 'pwm' and really, > > nothing prevents upstream from changing that name on a whim next time > > we import new dts files. (And linux sure seems to have a lot of > > arbitrary whims when it comes to changing dts.) > > Relying on the name is clearly not a good idea, especially for TI > since they change stuff A LOT. > > > Since an overlay is required to use this stuff anyway, I'm now thinking > > a custom property in the overlay that names the sysctl nodes might be a > > good option. So you'd add a property like: > > > > &ehrpwm0 { > > status = "okay"; > > pinctrl-names = "default"; > > pinctrl-0 = <&ehrpwm0_AB_pins>; > > freebsd,sysctl = "backlight"; > > }; > > > > And that would make it install names like hw.backlight.freq and > > hw.backlight.period and so on. If you don't add that property, it just > > installs the names it uses now (dev.ehrpwm.*) for compatibility. > > > > -- Ian > > What would be better is to add support to the pwm(9) api for this > driver and make the api and pwm(8) using the "pwm-names" property which > is a standard one from the bindings. > For this specific case, I think that's great. I'd go farther than say we should have the FDT/OFW node name, if any, associated with something like dev...node_name. Warner From owner-freebsd-arm@freebsd.org Fri Jun 7 15:22:37 2019 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 C333B15AFB7B for ; Fri, 7 Jun 2019 15:22:36 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E679776926; Fri, 7 Jun 2019 15:22:35 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 6210089f; Fri, 7 Jun 2019 17:22:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=3Me6U3c9EbTLzi9HhhIIDMMXfsY=; b=CgIymgbU/RiXn0WG1bnd5hqnNyNr iJzw25raADIDuoO/SDx85JNNmXrYVk8Pcl7a2HXqtpcALWOePGKvte0mOta57kHl KLtf1ZFvYo8SawiBA+jZvFi2r2Q8Y4SEMrRiwFcKeC533SjqQNrzHNugQENe06vY 00yzaDxXVoLBdIE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=nyPMReAyVDr8Wu6X6JGiS+gM+hEYr1jHnQiUZId3u5WpxGHLKVjcWBKo QkClCb1mU/bBHd09iuZ9Naf93xHGr0AA3xiVcbwZyyNAzKQ+wtNNsr6lBmzCwwns 7SHfKNCiG2Hmll6ytYU/SwfI0dHfsV+pi7K4oDC+aO71YnAoaSA= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 4a386bf4 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Fri, 7 Jun 2019 17:22:33 +0200 (CEST) Date: Fri, 7 Jun 2019 17:22:32 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Ian Lepore , nmingott@gmail.com, "freebsd-arm@freebsd.org" Subject: Re: How to set PWM tunable name to ehrpwm.1 ? Message-Id: <20190607172232.c2fdc70e6ee8ef4dd5d70fa3@bidouilliste.com> In-Reply-To: References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> <20190607171001.636efb2598ab9c88635973b6@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: E679776926 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=CgIymgbU; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [2.15 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.02)[0.016,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.60)[0.600,0]; DKIM_TRACE(0.00)[bidouilliste.com:+]; MX_GOOD(-0.01)[cached: mx-backup.blih.net]; NEURAL_SPAM_LONG(0.15)[0.152,0]; IP_SCORE(0.29)[ip: (-1.16), ipnet: 212.83.160.0/19(2.86), asn: 12876(-0.23), country: FR(-0.01)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Fri, 07 Jun 2019 15:22:37 -0000 On Fri, 7 Jun 2019 09:17:01 -0600 Warner Losh wrote: > On Fri, Jun 7, 2019 at 9:11 AM Emmanuel Vadot wrote: > > > On Fri, 07 Jun 2019 08:58:49 -0600 > > Ian Lepore wrote: > > > > > On Fri, 2019-06-07 at 02:08 -0700, Nicola Mingotti wrote: > > > > > > > > On 6/6/19 3:40 PM, Ian Lepore wrote: > > > > > On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > > > > > > Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: > > > > > > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > > > > > > > overlays, > > > > > > > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 > > > > > > > and > > > > > > > respectively p9.14, p9.16. DTSO files are below. > > > > > > > > > > > > > > If I load both the DTBO at boot I see > > > > > > > correctly|ehrpwm.0|and|ehrpwm.1|, > > > > > > > associated to the correct pins. But, if i remove the > > > > > > > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which > > > > > > > is > > > > > > > not > > > > > > > what i want, i would like to see the name|ehrpwm.1|. > > > > > > > > > > > > > > This is important because i must be 100% sure a certain pin > > > > > > > corresponds > > > > > > > the a certain tunable.This must be true even if i remove non > > > > > > > relevant > > > > > > > overlays in the future. I guess there must be some parameter in > > > > > > > the > > > > > > > DTSO > > > > > > > which i don't know, i hope you can give me some directions > > > > > > > about > > > > > > > that. > > > > > > > > > > > > It is not related to your DTBO's. That's how everything works (at > > > > > > least > > > > > > by default). You will see the same naming issue with serial > > > > > > ports, > > > > > > for > > > > > > example. And not just in BBB. > > > > > > > > > > > > E.g. when I have enabled uart0 and uart2 they are named ttyu0 and > > > > > > ttyu1, > > > > > > if I have only uart2, it becomes ttyu0. > > > > > > > > > > > > It's easier if there is a device node in /dev, so you can create > > > > > > a > > > > > > symlink > > > > > > with a fixed name (I have a script called by devd for my multiple > > > > > > serial > > > > > > ports). However, that's not the case with PWM... > > > > > > > > > > > > Maybe there is an option to use persistent names for devices that > > > > > > somebody > > > > > > can point to. > > > > > > > > > > > > > > > > Nope, there's no magic thing you're missing that fixes > > > > > this. Devices > > > > > get named-and-numbered based on the order of instantiation. > > > > > > > > > > Since what really matters here is the sysctl names, we could change > > > > > the > > > > > driver to install the sysctl nodes using the fdt device node names > > > > > instead of the freebsd newbus device names. Hmm, actually, since > > > > > people may be relying on the current names, I guess what we'd have > > > > > to > > > > > do is install another set of sysctl names based on fdt name > > > > > (basically > > > > > a set of alias names). > > > > > > > > > > -- Ian > > > > > > > > > > > > > I see, I agree changing the default naming scheme may damage who is > > > > relaying on it. It is not a good idea. Maybe it could be implemented > > > > in > > > > release 13. > > > > > > > > To Sergey. I used devd in the past, it works well. But i would > > > > prefer > > > > not to use it in this case, even if I had a /dev/xyz file available. > > > > The > > > > reason is that the /dev/xyz file would appear before the the devd > > > > daemon > > > > starts up (i guess), so the case would not stricly be covered by > > > > what > > > > the devd man page says devd should do. > > > > $> man devd > > > > => " ... Whenever a device is added to or removed from the device > > > > tree ... " > > > > > > > > To Ian. The idea of the alias seems good. I don't know at all what > > > > you > > > > can manage to do at the kernel level with the tunables. I imagine > > > > something like |dev.alias.am335x_ehrpwm.1| which actually refers to > > > > > EHRPWM1| not the second |ehrpwm| that got plugged into the system > > > > > via > > > > > > > > overlay. > > > > > > > > Thank you for your answers > > > > > > > > > > > > > > The dev.* hierarchy is managed by newbus; what I was picturing was > > > something like hw.ehrpwm1.freq and so on, settable as either tunable or > > > sysctl. But it turns out ehrpwm1 is just a label in the dts, not > > > accessible at runtime. The actual node name is just 'pwm' and really, > > > nothing prevents upstream from changing that name on a whim next time > > > we import new dts files. (And linux sure seems to have a lot of > > > arbitrary whims when it comes to changing dts.) > > > > Relying on the name is clearly not a good idea, especially for TI > > since they change stuff A LOT. > > > > > Since an overlay is required to use this stuff anyway, I'm now thinking > > > a custom property in the overlay that names the sysctl nodes might be a > > > good option. So you'd add a property like: > > > > > > &ehrpwm0 { > > > status = "okay"; > > > pinctrl-names = "default"; > > > pinctrl-0 = <&ehrpwm0_AB_pins>; > > > freebsd,sysctl = "backlight"; > > > }; > > > > > > And that would make it install names like hw.backlight.freq and > > > hw.backlight.period and so on. If you don't add that property, it just > > > installs the names it uses now (dev.ehrpwm.*) for compatibility. > > > > > > -- Ian > > > > What would be better is to add support to the pwm(9) api for this > > driver and make the api and pwm(8) using the "pwm-names" property which > > is a standard one from the bindings. > > > > For this specific case, I think that's great. I'd go farther than say we > should have the FDT/OFW node name, if any, associated with something like > dev...node_name. > > Warner I like that idea too, I'll look at it this weekend, that should not be hard to do. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Fri Jun 7 15:27:09 2019 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 C12D215AFCFE for ; Fri, 7 Jun 2019 15:27:09 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1.eu.mailhop.org (outbound1.eu.mailhop.org [52.28.251.132]) (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 2688976B4E for ; Fri, 7 Jun 2019 15:27:08 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1559921227; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=gI13lmupd36OWy81mAawvnCKqMvGK2We1/r5G+fJ7ko2eUiHR98qlLsxUWnZo2zm8KkhILUqLSLpx TBTH8O/Z8sx9lfQ9unZv1xXG+EXMVeOfdimaF3EbsT1YLx5xfl6VQj+0dwKwp+p6AlFyl0o0zXP5bV 4ldGMpBff94BgiK/6Mrej7nLDZsM0e6yW1eJ6ewrmJUz3Khhv92maAGsZTWdFjZbJbTqRmNmay4YLD aB67WfATsMMJrsUCPcokgSogexBZ1f1l+61D1p+lzpn+Ef8Z0/OcCEwdyb8o6K/yE7w8cI7mhS+cP6 sISrFFKaHJWCUyTTwiddhV80vJ7n2fQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=01lx/dN0kNN7KuXH8hEbGKRwduE0P5wouwZw0JfEn7o=; b=twJ3NDGP44jVZ2t1QMJmV0i08GuSskLqSILRhfk7C0V6PuTfQcZ/YDtjvbMPjNwZPbKbrfMFmzY4g Uj7zGFmbZktfUIzWLGZrN5NBcHdmisi3SZQiCSncmMz3OUNX1RdD6xIWOneBtLWQ38J6EU4c4G5tUa 1kN/JVV3izUVyc4ymp1PKT+TCkIIX7JCtxPv2IfuB8sglpi5DVbjV0wCwUXyPGjrSDN6hGvNnsHwuQ vsDlNPoJFdV19X+CreCxOLJDtXx12rdWPLFxrt/UQmSstbXalkK6xTtoE4N3Xd+sL9DDs2eWA+Bdo7 9IxNNPI8npccO8TqZeU09glOc1nGmyg== ARC-Authentication-Results: i=1; outbound3.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=01lx/dN0kNN7KuXH8hEbGKRwduE0P5wouwZw0JfEn7o=; b=DoMhEc9jz78zwL+pPlM9DG8kn81weQXsmDMXNnKFryeUG9xy3VSFD2GVIVSqmQ6oLsbwxzdSA+wXM 4NUPA+EkHoYOBKgtNk4kflXWaeuVK8hf/8i+IYgey7RwbjTGEEVZx2jOe0yxD+kQiIu5AqYcHyzsgw fuVWnt8clSObzPAeraP7g4TrbgaNAY/CN4dSEvfbHAB4ws/7SboXEoWoN4Mo9a6jb5tgyS6HRccC1W z/QT0FEwlgD0EUqfGc6YSUkpvfU4rXpL5FkawwK5ZXhh6030Y6E+BA9oGwuaUkTndguNCeV/UgMhJm B+kpVRM1CZceGmGxlr0yBvmsAL3x6tw== X-MHO-RoutePath: aGlwcGll X-MHO-User: b27043af-8938-11e9-91aa-b56e4e6b5865 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.eu.mailhop.org (Halon) with ESMTPSA id b27043af-8938-11e9-91aa-b56e4e6b5865; Fri, 07 Jun 2019 15:27:04 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x57FR1g1073024; Fri, 7 Jun 2019 09:27:01 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <53f74173b7b2de820d16d3bb750001cfc026a179.camel@freebsd.org> Subject: Re: How to set PWM tunable name to ehrpwm.1 ? From: Ian Lepore To: Warner Losh , Emmanuel Vadot Cc: "freebsd-arm@freebsd.org" Date: Fri, 07 Jun 2019 09:27:01 -0600 In-Reply-To: References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> <20190607171001.636efb2598ab9c88635973b6@bidouilliste.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 2688976B4E X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country: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: Fri, 07 Jun 2019 15:27:10 -0000 On Fri, 2019-06-07 at 09:17 -0600, Warner Losh wrote: > On Fri, Jun 7, 2019 at 9:11 AM Emmanuel Vadot > wrote: > > > On Fri, 07 Jun 2019 08:58:49 -0600 > > Ian Lepore wrote: > > > > > On Fri, 2019-06-07 at 02:08 -0700, Nicola Mingotti wrote: > > > > > > > > On 6/6/19 3:40 PM, Ian Lepore wrote: > > > > > On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: > > > > > > Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 > > > > > > 12:33: > > > > > > > In my BeagleBone Black, FreeBSD-12 RELEASE, i created two > > > > > > > overlays, > > > > > > > pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, > > > > > > > p9.22 > > > > > > > and > > > > > > > respectively p9.14, p9.16. DTSO files are below. > > > > > > > > > > > > > > If I load both the DTBO at boot I see > > > > > > > correctly|ehrpwm.0|and|ehrpwm.1|, > > > > > > > associated to the correct pins. But, if i remove the > > > > > > > overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, > > > > > > > which > > > > > > > is > > > > > > > not > > > > > > > what i want, i would like to see the name|ehrpwm.1|. > > > > > > > > > > > > > > This is important because i must be 100% sure a certain > > > > > > > pin > > > > > > > corresponds > > > > > > > the a certain tunable.This must be true even if i remove > > > > > > > non > > > > > > > relevant > > > > > > > overlays in the future. I guess there must be some > > > > > > > parameter in > > > > > > > the > > > > > > > DTSO > > > > > > > which i don't know, i hope you can give me some > > > > > > > directions > > > > > > > about > > > > > > > that. > > > > > > > > > > > > It is not related to your DTBO's. That's how everything > > > > > > works (at > > > > > > least > > > > > > by default). You will see the same naming issue with serial > > > > > > ports, > > > > > > for > > > > > > example. And not just in BBB. > > > > > > > > > > > > E.g. when I have enabled uart0 and uart2 they are named > > > > > > ttyu0 and > > > > > > ttyu1, > > > > > > if I have only uart2, it becomes ttyu0. > > > > > > > > > > > > It's easier if there is a device node in /dev, so you can > > > > > > create > > > > > > a > > > > > > symlink > > > > > > with a fixed name (I have a script called by devd for my > > > > > > multiple > > > > > > serial > > > > > > ports). However, that's not the case with PWM... > > > > > > > > > > > > Maybe there is an option to use persistent names for > > > > > > devices that > > > > > > somebody > > > > > > can point to. > > > > > > > > > > > > > > > > Nope, there's no magic thing you're missing that fixes > > > > > this. Devices > > > > > get named-and-numbered based on the order of instantiation. > > > > > > > > > > Since what really matters here is the sysctl names, we could > > > > > change > > > > > the > > > > > driver to install the sysctl nodes using the fdt device node > > > > > names > > > > > instead of the freebsd newbus device names. Hmm, actually, > > > > > since > > > > > people may be relying on the current names, I guess what we'd > > > > > have > > > > > to > > > > > do is install another set of sysctl names based on fdt name > > > > > (basically > > > > > a set of alias names). > > > > > > > > > > -- Ian > > > > > > > > > > > > > I see, I agree changing the default naming scheme may damage > > > > who is > > > > relaying on it. It is not a good idea. Maybe it could be > > > > implemented > > > > in > > > > release 13. > > > > > > > > To Sergey. I used devd in the past, it works well. But i would > > > > prefer > > > > not to use it in this case, even if I had a /dev/xyz file > > > > available. > > > > The > > > > reason is that the /dev/xyz file would appear before the the > > > > devd > > > > daemon > > > > starts up (i guess), so the case would not stricly be covered > > > > by > > > > what > > > > the devd man page says devd should do. > > > > $> man devd > > > > => " ... Whenever a device is added to or removed from the > > > > device > > > > tree ... " > > > > > > > > To Ian. The idea of the alias seems good. I don't know at all > > > > what > > > > you > > > > can manage to do at the kernel level with the tunables. I > > > > imagine > > > > something like |dev.alias.am335x_ehrpwm.1| which actually > > > > refers to > > > > > EHRPWM1| not the second |ehrpwm| that got plugged into the > > > > > system > > > > > via > > > > > > > > overlay. > > > > > > > > Thank you for your answers > > > > > > > > > > > > > > The dev.* hierarchy is managed by newbus; what I was picturing > > > was > > > something like hw.ehrpwm1.freq and so on, settable as either > > > tunable or > > > sysctl. But it turns out ehrpwm1 is just a label in the dts, not > > > accessible at runtime. The actual node name is just 'pwm' and > > > really, > > > nothing prevents upstream from changing that name on a whim next > > > time > > > we import new dts files. (And linux sure seems to have a lot of > > > arbitrary whims when it comes to changing dts.) > > > > Relying on the name is clearly not a good idea, especially for TI > > since they change stuff A LOT. > > > > > Since an overlay is required to use this stuff anyway, I'm now > > > thinking > > > a custom property in the overlay that names the sysctl nodes > > > might be a > > > good option. So you'd add a property like: > > > > > > &ehrpwm0 { > > > status = "okay"; > > > pinctrl-names = "default"; > > > pinctrl-0 = <&ehrpwm0_AB_pins>; > > > freebsd,sysctl = "backlight"; > > > }; > > > > > > And that would make it install names like hw.backlight.freq and > > > hw.backlight.period and so on. If you don't add that property, > > > it just > > > installs the names it uses now (dev.ehrpwm.*) for compatibility. > > > > > > -- Ian > > > > What would be better is to add support to the pwm(9) api for this > > driver and make the api and pwm(8) using the "pwm-names" property which > > is a standard one from the bindings. > > > > For this specific case, I think that's great. I'd go farther than say we > should have the FDT/OFW node name, if any, associated with something like > dev...node_name. > > You mean something like this? :) dev.imx6_anatop.0.%pnpinfo: name=anatop@20c8000 compat=fsl,imx6q-anatop That works great if you already know the newbus name and unit and want to relate it back to fdt. What we don't have is a way to get back to the dev...* oids if all you know is the fdt node name. Something like hw.fdt.xref.= But I suspect the character set for oid names is more constrained than that of fdt node names. At least, I've never seen a sysctl name with an '@' in it before. -- Ian From owner-freebsd-arm@freebsd.org Fri Jun 7 17:23:15 2019 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 F409C15B284E for ; Fri, 7 Jun 2019 17:23:14 +0000 (UTC) (envelope-from nmingotti@gmail.com) Received: from mail-pl1-x643.google.com (mail-pl1-x643.google.com [IPv6:2607:f8b0:4864:20::643]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E576083053; Fri, 7 Jun 2019 17:23:13 +0000 (UTC) (envelope-from nmingotti@gmail.com) Received: by mail-pl1-x643.google.com with SMTP id i2so1083576plt.1; Fri, 07 Jun 2019 10:23:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=IhUgUYMa69H4SvxDraCcUKHRjKotwtrMgvey9psmQYo=; b=cFiSeFc2NmGazAvE0mUJVizR9iMgx2r6OuoZYMx+nPqsb7JzVSzA5oBW15gtfpSfNK QEPL2oQ1swcRFOBp19orgOpOCA/jk0/N15DDMURX8kroRNND2wR915VSDN7cPXROkgpA +WlN09GC9fBOLMlVfNiVDjoLBBFEbxePhtSbpUaWhesXl1AxWB5LOqXRRmUEcHZsMaeF CaIte1GvHG6YpboiYzS0wKv5JvA7Jw7nhypuD3/KG8+RjWDGoyMwDzod7Rv4XUxyPmY8 AbscEeW8gF96RjBke0pVB2Ly1Fk2bA3H79D1sN6GVX638a5M8/Opl5XqOkoMqlCckoFD 4dGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=IhUgUYMa69H4SvxDraCcUKHRjKotwtrMgvey9psmQYo=; b=haTeLL7uFAQWnhztiVH6MTzsJPvEqhZaMKkBrwhB85673+6qfN9kH34Vjyyzt54W/P 4aaerdsLDYkQQQrgbhq//RMBPAI7ifls8+c3I6xtBQbJQs+tC93tWzoCJGgjZcsaZ06d H7uJ2WOq53bAzgmWjOqNfeC3IFEWwoS5ckGhx5l6zVHnlNK7RPyTNpyu6B3dX9Ds0KdL LKACYMl1MC/l+r7Ww+GEgDKAFgSH3DCkb9mppMQIbaTypf4bPcGQPb/+n7iM5UTm9QCD WzNPR9a91Jz8lHX3DIIYGn34AI3UvzamR8QBMROxQ8xT/taoepzoZOE8yNnVZvnC4we3 09uQ== X-Gm-Message-State: APjAAAVcHnNEmNkz9uByTA4EG2CSLE03iDqm54rTppSN48PlqJD9vlXT lDLKCv8SIL/PiduvTYNqsfxmCr9/Z4w= X-Google-Smtp-Source: APXvYqx2V7Hb3Q/apxDZhQemY5LFIivrAiuLhaQgiCppq5mfiGfG3ZO6MieDyaidV8dgyohd2AgW7A== X-Received: by 2002:a17:902:22:: with SMTP id 31mr55248282pla.15.1559928188944; Fri, 07 Jun 2019 10:23:08 -0700 (PDT) Received: from [172.16.144.128] (lcls-pc94808.slac.stanford.edu. [134.79.72.78]) by smtp.gmail.com with ESMTPSA id g8sm2897538pfi.8.2019.06.07.10.23.07 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jun 2019 10:23:07 -0700 (PDT) Subject: Re: How to set PWM tunable name to ehrpwm.1 ? To: Ian Lepore , Sergey Manucharian Cc: nmingott@gmail.com, freebsd-arm@freebsd.org References: <68790975-a5a5-2138-ca89-117878d6cf2d@gmail.com> <20190606220639.GE13546@eldorado> <8126fa4ae0ca650ca12f28dd538e6e8c4e81b432.camel@freebsd.org> <2852b9da-e647-69a7-3218-88cfa500eadc@gmail.com> From: Nicola Mingotti Message-ID: Date: Fri, 7 Jun 2019 10:23:06 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Rspamd-Queue-Id: E576083053 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=cFiSeFc2; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of nmingotti@gmail.com designates 2607:f8b0:4864:20::643 as permitted sender) smtp.mailfrom=nmingotti@gmail.com X-Spamd-Result: default: False [-3.97 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.96)[-0.956,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-1.00)[ip: (0.58), ipnet: 2607:f8b0::/32(-3.22), asn: 15169(-2.30), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.4.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_CC(0.00)[gmail.com] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Fri, 07 Jun 2019 17:23:15 -0000 On 6/7/19 7:58 AM, Ian Lepore wrote: > On Fri, 2019-06-07 at 02:08 -0700, Nicola Mingotti wrote: >> On 6/6/19 3:40 PM, Ian Lepore wrote: >>> On Thu, 2019-06-06 at 16:06 -0600, Sergey Manucharian wrote: >>>> Excerpts from Nicola Mingotti's message from Thu 06-Jun-19 12:33: >>>>> In my BeagleBone Black, FreeBSD-12 RELEASE, i created two >>>>> overlays, >>>>> pwm.dtso and pwm1.dtso. They enable the PWM pins p9.21, p9.22 >>>>> and >>>>> respectively p9.14, p9.16. DTSO files are below. >>>>> >>>>> If I load both the DTBO at boot I see >>>>> correctly|ehrpwm.0|and|ehrpwm.1|, >>>>> associated to the correct pins. But, if i remove the >>>>> overlay|pwm.dtbo|then i seen only|ehrpwm.0|in|sysctl -a|, which >>>>> is >>>>> not >>>>> what i want, i would like to see the name|ehrpwm.1|. >>>>> >>>>> This is important because i must be 100% sure a certain pin >>>>> corresponds >>>>> the a certain tunable.This must be true even if i remove non >>>>> relevant >>>>> overlays in the future. I guess there must be some parameter in >>>>> the >>>>> DTSO >>>>> which i don't know, i hope you can give me some directions >>>>> about >>>>> that. >>>> It is not related to your DTBO's. That's how everything works (at >>>> least >>>> by default). You will see the same naming issue with serial >>>> ports, >>>> for >>>> example. And not just in BBB. >>>> >>>> E.g. when I have enabled uart0 and uart2 they are named ttyu0 and >>>> ttyu1, >>>> if I have only uart2, it becomes ttyu0. >>>> >>>> It's easier if there is a device node in /dev, so you can create >>>> a >>>> symlink >>>> with a fixed name (I have a script called by devd for my multiple >>>> serial >>>> ports). However, that's not the case with PWM... >>>> >>>> Maybe there is an option to use persistent names for devices that >>>> somebody >>>> can point to. >>>> >>> Nope, there's no magic thing you're missing that fixes >>> this. Devices >>> get named-and-numbered based on the order of instantiation. >>> >>> Since what really matters here is the sysctl names, we could change >>> the >>> driver to install the sysctl nodes using the fdt device node names >>> instead of the freebsd newbus device names. Hmm, actually, since >>> people may be relying on the current names, I guess what we'd have >>> to >>> do is install another set of sysctl names based on fdt name >>> (basically >>> a set of alias names). >>> >>> -- Ian >>> >> I see, I agree changing the default naming scheme may damage who is >> relaying on it. It is not a good idea. Maybe it could be implemented >> in >> release 13. >> >> To Sergey. I used devd in the past, it works well. But i would >> prefer >> not to use it in this case, even if I had a /dev/xyz file available. >> The >> reason is that the /dev/xyz file would appear before the the devd >> daemon >> starts up (i guess), so the case would not stricly be covered by >> what >> the devd man page says devd should do. >> $> man devd >> => " ... Whenever a device is added to or removed from the device >> tree ... " >> >> To Ian. The idea of the alias seems good. I don't know at all what >> you >> can manage to do at the kernel level with the tunables. I imagine >> something like |dev.alias.am335x_ehrpwm.1| which actually refers to >>> EHRPWM1| not the second |ehrpwm| that got plugged into the system >>> via >> overlay. >> >> Thank you for your answers >> >> > The dev.* hierarchy is managed by newbus; what I was picturing was > something like hw.ehrpwm1.freq and so on, settable as either tunable or > sysctl. But it turns out ehrpwm1 is just a label in the dts, not > accessible at runtime. The actual node name is just 'pwm' and really, > nothing prevents upstream from changing that name on a whim next time > we import new dts files. (And linux sure seems to have a lot of > arbitrary whims when it comes to changing dts.) > > Since an overlay is required to use this stuff anyway, I'm now thinking > a custom property in the overlay that names the sysctl nodes might be a > good option. So you'd add a property like: > > &ehrpwm0 { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <&ehrpwm0_AB_pins>; > freebsd,sysctl = "backlight"; > }; > > And that would make it install names like hw.backlight.freq and > hw.backlight.period and so on. If you don't add that property, it just > installs the names it uses now (dev.ehrpwm.*) for compatibility. > > -- Ian > > Ian, this |freebsd,sysctl = "foobar"| to me sounds as a very good solution. In this way I could name the tunable with the "hardware name" or also with the functional name, as "pwm-motor-front-left". This would improve the readability of underlying software structure. That would be beautiful. n. From owner-freebsd-arm@freebsd.org Fri Jun 7 20:26:35 2019 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 C0A1015B5ECE for ; Fri, 7 Jun 2019 20:26:35 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from forward103o.mail.yandex.net (forward103o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::606]) (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 DD9158868C for ; Fri, 7 Jun 2019 20:26:33 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mxback3g.mail.yandex.net (mxback3g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:164]) by forward103o.mail.yandex.net (Yandex) with ESMTP id 1053A5F8129F for ; Fri, 7 Jun 2019 23:26:30 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback3g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 2nN9JRmlld-QT2mG267; Fri, 07 Jun 2019 23:26:30 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler.com; s=mail; t=1559939190; bh=rS3DpbqVpqu6jxBLFjg2GLxpaDr2gNRRAgVUcrKSX0M=; h=Subject:To:From:Date:Message-ID; b=SRJAI/1Decpuhy97Aunr9IkzmBSu1vPTeoZl3ZV0KeqjKJI+0wEPpJc1zs2/u943u ZlCqMh+qz4TUTnIzsmxGvH0PGWi4qEGivOKvh1MxIURFkSogDup+HBOxxSbw09435q dxO9F6pcI6VQot42in3jJrzZNPfZi6ezAG/wyPoI= Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 4BuxvfPTXx-QSwOqlvC; Fri, 07 Jun 2019 23:26:28 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Date: Fri, 7 Jun 2019 14:26:22 -0600 From: Sergey Manucharian To: FreeBSD-ARM Subject: Using framebuffer in BeagleBone Message-ID: <20190607202622.GG13546@eldorado> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: DD9158868C X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ara-ler.com header.s=mail header.b=SRJAI/1D; spf=pass (mx1.freebsd.org: domain of sm@ara-ler.com designates 2a02:6b8:0:1a2d::606 as permitted sender) smtp.mailfrom=sm@ara-ler.com X-Spamd-Result: default: False [-6.72 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[ara-ler.com:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1a2d::/64]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[ara-ler.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mx.yandex.net]; DKIM_TRACE(0.00)[ara-ler.com:+]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; IP_SCORE(-3.64)[ip: (-9.67), ipnet: 2a02:6b8::/32(-4.73), asn: 13238(-3.79), country: RU(0.01)]; RCVD_IN_DNSWL_LOW(-0.10)[6.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.d.2.a.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; MIME_TRACE(0.00)[0:+] 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: Fri, 07 Jun 2019 20:26:35 -0000 Qt5 supports "bsdfb", and I tried running Qt programs: xyz -platform bsdfb but I get: Error reading framebuffer information (Inappropriate ioctl for device). The same programs perfectly run on framebuffer in amd64 machines, and in Linux on BeagleBone. Thanks for ideas! Ϟϻ From owner-freebsd-arm@freebsd.org Fri Jun 7 22:38:55 2019 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 A159515B8BE4 for ; Fri, 7 Jun 2019 22:38:55 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from forward100p.mail.yandex.net (forward100p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:100]) (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 374EA8C9C5 for ; Fri, 7 Jun 2019 22:38:53 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mxback7o.mail.yandex.net (mxback7o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::21]) by forward100p.mail.yandex.net (Yandex) with ESMTP id 6C1ED5980435 for ; Sat, 8 Jun 2019 01:38:41 +0300 (MSK) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [2a02:6b8:0:1619::15:6]) by mxback7o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 6CqZOI7r2c-cfr8HZtH; Sat, 08 Jun 2019 01:38:41 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler.com; s=mail; t=1559947121; bh=z2k+Dhfj2cDP2IskJvX5ryWkeBQ6joW6GBSI/Si4MmA=; h=In-Reply-To:Subject:To:From:References:Date:Message-ID; b=Rj16onQro/BiDXnGgEHmTM7uVr7RdhokHyA21Zehjw7yOkG6nm7csqezcpppdaipK yiUvQtCjlr2URVnND4Ohhf19wXVPsExNFZU9OjxPknfm9pEbj6NGa+rv4RqiP4AfJc rrdiQbZEDm0ki2l4uVaopO6MUrBYtUy+2ux7J4GQ= Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id VK871fC2Fl-cd6Gh6oe; Sat, 08 Jun 2019 01:38:40 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Date: Fri, 7 Jun 2019 16:38:37 -0600 From: Sergey Manucharian To: FreeBSD-ARM Subject: Re: Using framebuffer in BeagleBone Message-ID: <20190607223837.GB6866@dendrobates> References: <20190607202622.GG13546@eldorado> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190607202622.GG13546@eldorado> User-Agent: Mutt/1.12.0 (2019-05-25) X-Rspamd-Queue-Id: 374EA8C9C5 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ara-ler.com header.s=mail header.b=Rj16onQr; spf=pass (mx1.freebsd.org: domain of sm@ara-ler.com designates 2a02:6b8:0:1472:2741:0:8b7:100 as permitted sender) smtp.mailfrom=sm@ara-ler.com X-Spamd-Result: default: False [-2.35 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[ara-ler.com:s=mail]; NEURAL_HAM_MEDIUM(-0.98)[-0.977,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1000::/52]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[ara-ler.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[ara-ler.com:+]; MX_GOOD(-0.01)[mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net,mx.yandex.net]; NEURAL_HAM_SHORT(-0.26)[-0.263,0]; RCVD_IN_DNSWL_LOW(-0.10)[0.0.1.0.7.b.8.0.0.0.0.0.1.4.7.2.2.7.4.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+] 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: Fri, 07 Jun 2019 22:38:55 -0000 Excerpts from Sergey Manucharian's message from Fri 07-Jun-19 14:26: > Qt5 supports "bsdfb", and I tried running Qt programs: > xyz -platform bsdfb > > but I get: > Error reading framebuffer information (Inappropriate ioctl for device). Answering my own question: the framebuffer device has to be set to the actual virtual console used, e.g. in case of Qt5 it can be specified: xyz -platform bsdfb:fb=/dev/ttyv0 S.M. From owner-freebsd-arm@freebsd.org Sat Jun 8 01:24:25 2019 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 084BA15BCC50 for ; Sat, 8 Jun 2019 01:24:25 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from hobbes.arroway.org (hobbes.arroway.org [173.199.118.77]) by mx1.freebsd.org (Postfix) with ESMTP id 0AADA6BEFB for ; Sat, 8 Jun 2019 01:24:23 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from [10.1.3.200] (unknown [181.223.129.91]) by hobbes.arroway.org (Postfix) with ESMTPA id 7CC481C73BF for ; Fri, 7 Jun 2019 22:24:16 -0300 (BRT) Date: Fri, 07 Jun 2019 22:24:12 -0300 User-Agent: K-9 Mail for Android In-Reply-To: <84111DA7-4313-4DF7-A7F8-1E613499AE4F@nlned.nl> References: <84111DA7-4313-4DF7-A7F8-1E613499AE4F@nlned.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Updating FreeBSD 12.0 on a raspberry pi 3 B+ To: freebsd-arm@freebsd.org From: Nenhum_de_Nos Message-ID: <598C4050-70D6-4AA1-A08D-01179A73FE15@eternamente.info> X-Rspamd-Queue-Id: 0AADA6BEFB X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [0.42 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.63)[-0.634,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.34)[-0.341,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[eternamente.info]; NEURAL_SPAM_SHORT(0.42)[0.422,0]; MX_GOOD(-0.01)[hobbes.arroway.org]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20473, ipnet:173.199.116.0/22, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.01)[asn: 20473(-0.01), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] 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: Sat, 08 Jun 2019 01:24:25 -0000 On June 1, 2019 5:33:00 PM GMT-03:00, Jack Raats wrote: >Hi > >=20 > >I want to update FreeBSD on a raspberry pi 3 B+ > >=20 > >On a VPS with lots of cores and RAM I build FreeBSD using crochet=2E >Every night I make an image, which can be downloaded at >www=2Ejarasoft=2Enet/rpi > >The raspberry pi is running FreeBSD 12=2E0-STABLE build a fee weeks ago >and now I want to update this working FreeBSD=2E > >=20 > >I could make a new image and install everything from the start but that >will take a lot of time or can this be automated? > >=20 > >On the other end I could use the builded binaries from my VPS, copy >them to the Pi and run make install kernel and make install world? > >Is this being done??? > >=20 > >Or is there another way? Jack,=20 Have you ever tried the official image for rpi3 b on them?=20 Cause I tried the default image on mine and it boots once every 5 or 6 att= empts=2E=20 Do you have any idea what I could do?=20 Thanks,=20 Matheus=20 >=20 > >Thanks > >Jack Raats > >=20 > >=20 > >_______________________________________________ >freebsd-arm@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-arm >To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd=2Eorg" -- "We will call you Cygnus, the God of balance you shall be=2E"