From owner-freebsd-embedded@FreeBSD.ORG Mon Nov 26 11:06:42 2012 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7FA22533 for ; Mon, 26 Nov 2012 11:06:42 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 646338FC18 for ; Mon, 26 Nov 2012 11:06:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qAQB6gHO019346 for ; Mon, 26 Nov 2012 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAQB6ffp019344 for freebsd-embedded@FreeBSD.org; Mon, 26 Nov 2012 11:06:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Nov 2012 11:06:41 GMT Message-Id: <201211261106.qAQB6ffp019344@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-embedded@FreeBSD.org Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 11:06:42 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/172968 embedded [arge] probe/attach occasionally fails to find a PHY o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c 3 problems total. From owner-freebsd-embedded@FreeBSD.ORG Tue Nov 27 10:28:40 2012 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5427740D for ; Tue, 27 Nov 2012 10:28:40 +0000 (UTC) (envelope-from jack.mclauren@yahoo.com) Received: from nm29-vm0.bullet.mail.bf1.yahoo.com (nm29-vm0.bullet.mail.bf1.yahoo.com [98.139.213.166]) by mx1.freebsd.org (Postfix) with ESMTP id E4FF28FC15 for ; Tue, 27 Nov 2012 10:28:39 +0000 (UTC) Received: from [98.139.214.32] by nm29.bullet.mail.bf1.yahoo.com with NNFMP; 27 Nov 2012 10:28:39 -0000 Received: from [98.139.212.210] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 27 Nov 2012 10:28:39 -0000 Received: from [127.0.0.1] by omp1019.mail.bf1.yahoo.com with NNFMP; 27 Nov 2012 10:28:39 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 163574.54985.bm@omp1019.mail.bf1.yahoo.com Received: (qmail 20326 invoked by uid 60001); 27 Nov 2012 10:28:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1354012119; bh=NmK4ShZflFdJ0ShFkTeH6+MioiTR4rxvbyX2sGyHPd4=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=Ooq2RGEWPdAYYWiZtRVmOwRHEyWmtC0fK38TCVS6omgEgh91ZeQg1drOb9NATS0RSfhg3RKkkXRpotfXrhvzmlQXrNON3PYul7jXV0IiZPSz4ogOG1QQSHn+HESO9JlH6Sa+MoKoFwd4jisot85tR5nGcjj64KWUTwnD5GGU90k= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=smt6F1U+Q3TuzIGCuLzVGV9zlmnrk4+fMS0/unNa4hsSNffTiZEF5On9s75WQGaEn7PSLiPEjf8EluPv9KO9SONOyvby2/oS/AWb5JeLM39USHlS910c8Yv3zD/RwmH/HS9KugDzZeeP7Jq5np9LJuGujTdpzaciJgJZORKkE0k=; X-YMail-OSG: _B3vCHcVM1muwS7YzvhLoDmQRlM8zA.57HMALT.T4KY0PAG u_SrVfjV9UyYwhPKEup8WKr._SCKVtlodB7WCb53Io37CUclwstN4epA65xD vXRraxoPBAlPdxXS_7Ty5K9zSW_EI6a0tNY_FzLMX_YrKOTNLa4JR0Mx.ugZ agk5g91cP1.wXFQKsMp5HA7UoOXq8Fu9f1VpPm5l1KzlGZXPG55PekoCmrKi LgFveacWUI0Vt4HqXT0qAoU2Gje6HnHQaGUzY5enH5mkUW5oTVOYpvkS4iJS ySwRDSWR9KVO81.IFO49KUUUw92umAKmhvvJFCaqGdrPY5zoq6.vUW8Jl.Mj uf4Vg8bsAs2lLkv2mJZ4MdmNZ5v_Fp25WQAlqvEqtPt_8SNbOygpwUo6yDBW lBa7gcjKZDk6ddAIAE63eWj2bUW8qVe4aK9lbCHjWXfIW7HVCipTAYH96ZUw - Received: from [89.165.120.140] by web160104.mail.bf1.yahoo.com via HTTP; Tue, 27 Nov 2012 02:28:39 PST X-Rocket-MIMEInfo: 001.001, SGkgYWxsCgpJIGhhdmUgY29waWVkIHNvbWUgcGFja2FnZXMgaW4gL3Vzci9zcmMvdG9vbHMvdG9vbHMvbmFub2JzZC9Qa2cgaW4gb3JkZXIgdG8gYnVpbGQgdGhlbSBvbiBteSBpbWFnZSAsIGJ1dCBpdCBzZWVtcyB0aGF0IHRoZSBvcmRlciBvZiBidWlsZGluZyBwYWNrYWdlcyBpcyBpbXBvcnRhbnQgLCBhbmQgdGhlIHByaW9yaXRpZXMgb2YgYSBwYWNrYWdlIG11c3QgYmUgaW5zdGFsbGVkIGJlZm9yZSB0aGUgcGFja2FnZSBpdHNlbGYuIEhvdyBjYW4gaSBzZXQgdGhlc2Ugb3JkZXJzID8KClRoYW5rcwEwAQEBAQ-- X-Mailer: YahooMailWebService/0.8.127.475 Message-ID: <1354012119.9287.YahooMailNeo@web160104.mail.bf1.yahoo.com> Date: Tue, 27 Nov 2012 02:28:39 -0800 (PST) From: Jack Mc Lauren Subject: adding packages to nanobsd image To: "freebsd-embedded@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Jack Mc Lauren List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 10:28:40 -0000 Hi all I have copied some packages in /usr/src/tools/tools/nanobsd/Pkg in order to build them on my image , but it seems that the order of building packages is important , and the priorities of a package must be installed before the package itself. How can i set these orders ? Thanks From owner-freebsd-embedded@FreeBSD.ORG Tue Nov 27 16:22:43 2012 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 452D8721 for ; Tue, 27 Nov 2012 16:22:43 +0000 (UTC) (envelope-from espartano.mail@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 04D4D8FC12 for ; Tue, 27 Nov 2012 16:22:42 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so15211523iec.13 for ; Tue, 27 Nov 2012 08:22:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=bX/QWiwXfsT8x//lKVOUlIHstfULAE/YrUHz/+f+/pU=; b=JDXB9QzfqAvSMB6t9K61VIqZYKeSoHpGLorO7wThnwwO1fWl/RCSs9ahHWrRi71flV tIcQjRmU+NqcEFTtlf55XCYZLwAB7lBLbfp+8CSn/F2gybSHVE9QwXOdkFSuwHdZS/iu u1uEFyO7U9b5MwdM6Ld45r3nVL7LxbahOrdkR4oP08VVn81v1IARrtmKBYijV8L3SiHA lyuzhfBoNt2+SiRtWzfBq8jDl5L6ptqqrpTbFuAzFOuZ7xUe/c00zfLiZxL54ubm99XI /UTIm3EpSmxnYV9WYz7Bmqx/U/NFCLsWLRG+L7eUezBoI322J/kBKxQiAB4M3mg+A3fK xLFg== MIME-Version: 1.0 Received: by 10.50.150.144 with SMTP id ui16mr16322328igb.68.1354033362248; Tue, 27 Nov 2012 08:22:42 -0800 (PST) Received: by 10.64.37.41 with HTTP; Tue, 27 Nov 2012 08:22:42 -0800 (PST) In-Reply-To: <1354012119.9287.YahooMailNeo@web160104.mail.bf1.yahoo.com> References: <1354012119.9287.YahooMailNeo@web160104.mail.bf1.yahoo.com> Date: Tue, 27 Nov 2012 10:22:42 -0600 Message-ID: Subject: Re: adding packages to nanobsd image From: Espartano To: Jack Mc Lauren Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 16:22:43 -0000 On Tue, Nov 27, 2012 at 4:28 AM, Jack Mc Lauren w= rote: > Hi all > > I have copied some packages in /usr/src/tools/tools/nanobsd/Pkg in order = to build them on my image , but it seems that the order of building package= s is important , and the priorities of a package must be installed before t= he package itself. How can i set these orders ? > > Thanks I think it is not possible howeber you could install ports after have been created nanobsd image, here possible steeps that you have to follow: 1.- mount nanobsd image into a directory using mdconfig: mdconfig -a -t vnode -u 1 -f /path_to_nanobsd_image mount /dev/md1(nanobsd root partition) /mnt/ 2.- create ports directory into nanobsd usr directory: mkdir /mnt/usr/ports 3.- mount dev filesystem into nanobsd dev directory: mount -t devfs devfs /mnt/dev/ 4.- mount ports directory into nanobsd ports directory: mount_nullfs /usr/ports /mnt/usr/ports 5.- change / directory: chroot /mnt/ 6.- be happy (install your ports) Note: Nanobsd in boot time mount directory /var from another directory, that directory is /conf/base/var .... and remember that port installation process write info about installation into /var/db/packages/ then you have to copy the content of that directory into /conf/base/var ..... in order to have disponible ports package info when you use commands like pkg_info or so. Sorry for my bad english. Regards. From owner-freebsd-embedded@FreeBSD.ORG Tue Nov 27 23:20:39 2012 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB7F95DA for ; Tue, 27 Nov 2012 23:20:39 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id 855798FC20 for ; Tue, 27 Nov 2012 23:20:39 +0000 (UTC) Received: from [88.198.91.248] (helo=[IPv6:::1]) by id.bluezbox.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TdUS1-000LjH-QY; Tue, 27 Nov 2012 15:20:27 -0800 Message-ID: <50B54AB7.8080301@bluezbox.com> Date: Tue, 27 Nov 2012 15:20:23 -0800 From: Oleksandr Tymoshenko User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Rafal Jaworowski Subject: FDT code fixes for ubldr Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Hi guys, Here is a patch for FDT support in ubldr: http://people.freebsd.org/~gonzo/patches/fdt.diff Reviews are appreciated I also plan to add merge of memreserve and memory regions as a part of memory fixup process. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: Tim Kientzle , embedded@freebsd.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 23:20:39 -0000 Hi guys, Here is a patch for FDT support in ubldr: http://people.freebsd.org/~gonzo/patches/fdt.diff Reviews are appreciated I also plan to add merge of memreserve and memory regions as a part of memory fixup process. Changes: - Implement "fdt mres" sub-command that prints reserved memory regions - Add "fdt addr" subcommand that lets you specify preloaded blob address - Do not pre-initialize blob for "fdt addr" - Do not try to load dtb every time fdt subcommand is issued, do it only once - Change the way DTB is passed to kernel. With introduction of "fdt addr" actual blob address can be not virtual but physical or reside in area higher then 64Mb. ubldr should create copy of it in kernel area and pass pointer to this newly allocated buffer which is guaranteed to work in kernel after switching on MMU. From owner-freebsd-embedded@FreeBSD.ORG Wed Nov 28 22:15:29 2012 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F51FC03; Wed, 28 Nov 2012 22:15:29 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id 1CE978FC13; Wed, 28 Nov 2012 22:15:28 +0000 (UTC) Received: from [88.198.91.248] (helo=[IPv6:::1]) by id.bluezbox.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Tdpue-000AGY-Je; Wed, 28 Nov 2012 14:15:26 -0800 Message-ID: <50B68CFA.80208@bluezbox.com> Date: Wed, 28 Nov 2012 14:15:22 -0800 From: Oleksandr Tymoshenko User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Rafal Jaworowski Subject: Re: FDT code fixes for ubldr References: <50B54AB7.8080301@bluezbox.com> In-Reply-To: <50B54AB7.8080301@bluezbox.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 11/27/2012 3:20 PM, Oleksandr Tymoshenko wrote: > Hi guys, > > Here is a patch for FDT support in ubldr: > http://people.freebsd.org/~gonzo/patches/fdt.diff > Reviews are appreciated > > I also plan to add merge of memreserve and memory regions as a part of > memory fixup process. > > Changes: > - Implement "fdt mres" sub-command that prints reserved memory regions > - Add "fdt addr" subcommand that lets you specify preloaded blob address > - Do not pre-initialize blob for "fdt addr" > - Do not try to load dtb every time fdt subcommand is issued, > do it only once > - Change the way DTB is passed to kernel. With introduction of "fdt addr" > actual blob address can be not virtual but physical or reside in > area higher then 64Mb. ubldr should create copy of it in kernel area > and pass pointer to this newly allocated buffer which is > guaranteed to work > in kernel after switching on MMU. > [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: arm@freebsd.org, Tim Kientzle , embedded@freebsd.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 22:15:29 -0000 On 11/27/2012 3:20 PM, Oleksandr Tymoshenko wrote: > Hi guys, > > Here is a patch for FDT support in ubldr: > http://people.freebsd.org/~gonzo/patches/fdt.diff > Reviews are appreciated > > I also plan to add merge of memreserve and memory regions as a part of > memory fixup process. > > Changes: > - Implement "fdt mres" sub-command that prints reserved memory regions > - Add "fdt addr" subcommand that lets you specify preloaded blob address > - Do not pre-initialize blob for "fdt addr" > - Do not try to load dtb every time fdt subcommand is issued, > do it only once > - Change the way DTB is passed to kernel. With introduction of "fdt addr" > actual blob address can be not virtual but physical or reside in > area higher then 64Mb. ubldr should create copy of it in kernel area > and pass pointer to this newly allocated buffer which is > guaranteed to work > in kernel after switching on MMU. > New version of this patch: http://people.freebsd.org/~gonzo/patches/fdt-memreserve.diff Additional changes: - Convert memreserv FDT info to memreserv property of root node - Handle memreserv property in initarm: exclude these regions from available memory regions With these changes I was able to boot Raspberry Pi with all hardware-specific data set correctly by firmware. If there are not objections, I'd like to commit it ASAP. From owner-freebsd-embedded@FreeBSD.ORG Wed Nov 28 22:24:28 2012 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 137E8CF8 for ; Wed, 28 Nov 2012 22:24:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id B11378FC08 for ; Wed, 28 Nov 2012 22:24:27 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so7448667vba.13 for ; Wed, 28 Nov 2012 14:24:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=YE5/Qlf+GBpLOeJWgcuZ9nWf+sHKrqTwMTs1+wWTph0=; b=k4FUs4k/ZNnu52/n/eLoOVjvcQRFYn6OENUGkKfmxbh+40mpcTQjrrc0OEsi7PXdqy nZwg49W7ENjL17NGDbX8OtmTqc0TwXhTt+4KA+1RvsHSqk5LS6G6kBhLPQeIY1SOIlWC 1sO+UxHlHOOEOVd8xMY91IHSvuT15KnhBXpuDnvXhMG/GMfBJcsEy3u/EH+U0tbZAp9m ANhvbeZQo8bGpE+Vre5D00IOY2ME9d/3ZqrmdRBGsC3BvIyPH9lqZ+rU12s+gaIOALNW leSQSGtrJ0K7HdV6dG0bKUAzCCWsowFy53VbDB7Vf3yBjhq7iEdkNXOX5O++G/pvgJvp 4cjQ== Received: by 10.52.98.67 with SMTP id eg3mr1489272vdb.59.1354141466634; Wed, 28 Nov 2012 14:24:26 -0800 (PST) Received: from [10.30.101.53] ([209.117.142.2]) by mx.google.com with ESMTPS id co1sm12177127vdc.10.2012.11.28.14.24.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Nov 2012 14:24:25 -0800 (PST) Sender: Warner Losh Subject: Re: FDT code fixes for ubldr Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <50B68CFA.80208@bluezbox.com> Date: Wed, 28 Nov 2012 15:24:21 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <50B54AB7.8080301@bluezbox.com> <50B68CFA.80208@bluezbox.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQlnc4h2fFhCLMPoa8JY67KNnjc7wJ8Qsqi17wXet76BW/nrXbz0he9K8DigRiYdITQ1ZA1G Cc: arm@freebsd.org, embedded@freebsd.org, Tim Kientzle X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 22:24:28 -0000 On Nov 28, 2012, at 3:15 PM, Oleksandr Tymoshenko wrote: > On 11/27/2012 3:20 PM, Oleksandr Tymoshenko wrote: >> Hi guys, >>=20 >> Here is a patch for FDT support in ubldr: >> http://people.freebsd.org/~gonzo/patches/fdt.diff >> Reviews are appreciated >>=20 >> I also plan to add merge of memreserve and memory regions as a part = of memory fixup process. >>=20 >> Changes: >> - Implement "fdt mres" sub-command that prints reserved memory = regions >> - Add "fdt addr" subcommand that lets you specify preloaded blob = address >> - Do not pre-initialize blob for "fdt addr" >> - Do not try to load dtb every time fdt subcommand is issued, >> do it only once >> - Change the way DTB is passed to kernel. With introduction of "fdt = addr" >> actual blob address can be not virtual but physical or reside in >> area higher then 64Mb. ubldr should create copy of it in kernel = area >> and pass pointer to this newly allocated buffer which is = guaranteed to work >> in kernel after switching on MMU. >>=20 >=20 > New version of this patch: > http://people.freebsd.org/~gonzo/patches/fdt-memreserve.diff >=20 > Additional changes: >=20 > - Convert memreserv FDT info to memreserv property of root node > - Handle memreserv property in initarm: exclude these regions from = available memory regions >=20 > With these changes I was able to boot Raspberry Pi with all = hardware-specific data set correctly by firmware. > If there are not objections, I'd like to commit it ASAP. Nothing horrible is leaping out at me. Please do. On a related note: any plans to have the ability to merge new = nodes/change nodes from the loader? I know this doesn't make sense in = the NAND environment so much, but makes a lot more sense for the SD = environment when you may wish to monkey with the command line, or = disable devices, or even load a set of nodes that describe some new = custom hardware, perhaps conditionally... Warner From owner-freebsd-embedded@FreeBSD.ORG Thu Nov 29 07:52:08 2012 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B80D67DE for ; Thu, 29 Nov 2012 07:52:08 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from vps.van-laarhoven.org (www.hibma.org [178.21.117.90]) by mx1.freebsd.org (Postfix) with ESMTP id 72F668FC12 for ; Thu, 29 Nov 2012 07:52:04 +0000 (UTC) Received: from [10.87.42.16] (unknown [80.187.201.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps.van-laarhoven.org (Postfix) with ESMTPSA id 965555F20D3; Thu, 29 Nov 2012 08:42:56 +0100 (CET) From: Nick Hibma Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: NanoBSD: Create image sparsely Date: Thu, 29 Nov 2012 08:42:23 +0100 Message-Id: <42654855-CF29-488A-A645-2A280FC9D074@van-laarhoven.org> To: =?windows-1252?Q?=93FreeBSD_Embedded_Mailing_List=94?= Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 07:52:08 -0000 In the past I have submitted patches to create images sparsely. There is = however one patch missing still which, with the addition of = NANO_INIT_IMG2, has become much more useful: --- AnyWi/freebsd/nanobsd/nanobsd.sh 2012-11-08 19:48:40.000000000 = +0100 +++ /usr/src/tools/tools/nanobsd/nanobsd.sh 2012-11-06 = 15:24:52.000000000 +0100 @@ -540,7 +540,7 @@ if [ $NANO_IMAGES -gt 1 -a $NANO_INIT_IMG2 -gt 0 ] ; then # Duplicate to second image (if present) echo "Duplicating to second image..." - dd if=3D/dev/${MD}s1 of=3D/dev/${MD}s2 bs=3D64k + dd conv=3Dsparse if=3D/dev/${MD}s1 of=3D/dev/${MD}s2 = bs=3D64k mount /dev/${MD}s2a ${MNT} for f in ${MNT}/etc/fstab ${MNT}/conf/base/etc/fstab do @@ -569,7 +569,7 @@ =20 if ${do_copyout_partition} ; then echo "Writing out _.disk.image..." - dd if=3D/dev/${MD}s1 of=3D${NANO_DISKIMGDIR}/_.disk.image = bs=3D64k + dd conv=3Dsparse if=3D/dev/${MD}s1 = of=3D${NANO_DISKIMGDIR}/_.disk.image bs=3D64k fi mdconfig -d -u $MD =20 It copies out the image sparsely (conv=3Dsparse). The big advantage = comes when creating many images (I have between 10 and 20 images = simultaneously on my disk). Any objections to this? (*) Nick Hibma nick@van-laarhoven.org From owner-freebsd-embedded@FreeBSD.ORG Thu Nov 29 14:27:13 2012 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF7798D7 for ; Thu, 29 Nov 2012 14:27:13 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7ABF78FC15 for ; Thu, 29 Nov 2012 14:27:13 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id x2so13696597iad.13 for ; Thu, 29 Nov 2012 06:27:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=9GCCWgujyvDGR3jD7y/+no3v4rqt8LO2AXi7r0karkU=; b=Hn3ANf8AzTaUqx9fQ12PhPW2wj1UMicdOLS3XW3+A+TtIInSsWeuuqaUsgbg3ShBzs upK+RiUyOJ67qsnE3oGZWyns3M5vz+7LOuwL2TdzN4tpcEW1TteV5NhDl3CL7s72Hoy1 1j4fv6g9+re3hf1CUHNPA+F3NasG1Phpg/6TByfuTZPgutzQJwq+BjuIH3SqunNf9x4C Itlzm6kf//4K0fJsR7yHzqr2lIulIpOvTMAXNtwb5CqSqBTUEa+C3fgPQO5us0x5zApo d2F1Y3qnv6IVbHwGzReGryMhVehEmSxBnEihG4+TPkkBdd80w7mPuln9STyN9LWWM4FF Jukg== Received: by 10.50.158.201 with SMTP id ww9mr26103109igb.22.1354199232442; Thu, 29 Nov 2012 06:27:12 -0800 (PST) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id v12sm1639177igv.3.2012.11.29.06.27.06 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Nov 2012 06:27:09 -0800 (PST) Sender: Warner Losh Subject: Re: NanoBSD: Create image sparsely Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <42654855-CF29-488A-A645-2A280FC9D074@van-laarhoven.org> Date: Thu, 29 Nov 2012 07:27:05 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <42654855-CF29-488A-A645-2A280FC9D074@van-laarhoven.org> To: Nick Hibma X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQm6SoVEax4Yn1vxBBdQYQ0ry4G0n7awOiVdbl7y0w/yu/wWLyVY5QrEplaHVpXI2v/osFax Cc: =?windows-1252?Q?=93FreeBSD_Embedded_Mailing_List=94?= X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 14:27:13 -0000 Looks good to me, go ahead. Warner On Nov 29, 2012, at 12:42 AM, Nick Hibma wrote: > In the past I have submitted patches to create images sparsely. There = is however one patch missing still which, with the addition of = NANO_INIT_IMG2, has become much more useful: >=20 > --- AnyWi/freebsd/nanobsd/nanobsd.sh 2012-11-08 19:48:40.000000000 = +0100 > +++ /usr/src/tools/tools/nanobsd/nanobsd.sh 2012-11-06 = 15:24:52.000000000 +0100 > @@ -540,7 +540,7 @@ > if [ $NANO_IMAGES -gt 1 -a $NANO_INIT_IMG2 -gt 0 ] ; then > # Duplicate to second image (if present) > echo "Duplicating to second image..." > - dd if=3D/dev/${MD}s1 of=3D/dev/${MD}s2 bs=3D64k > + dd conv=3Dsparse if=3D/dev/${MD}s1 of=3D/dev/${MD}s2 = bs=3D64k > mount /dev/${MD}s2a ${MNT} > for f in ${MNT}/etc/fstab ${MNT}/conf/base/etc/fstab > do > @@ -569,7 +569,7 @@ >=20 > if ${do_copyout_partition} ; then > echo "Writing out _.disk.image..." > - dd if=3D/dev/${MD}s1 of=3D${NANO_DISKIMGDIR}/_.disk.image= bs=3D64k > + dd conv=3Dsparse if=3D/dev/${MD}s1 = of=3D${NANO_DISKIMGDIR}/_.disk.image bs=3D64k > fi > mdconfig -d -u $MD >=20 > It copies out the image sparsely (conv=3Dsparse). The big advantage = comes when creating many images (I have between 10 and 20 images = simultaneously on my disk). >=20 > Any objections to this? (*) >=20 > Nick Hibma > nick@van-laarhoven.org From owner-freebsd-embedded@FreeBSD.ORG Fri Nov 30 01:04:11 2012 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3EEF3DBA for ; Fri, 30 Nov 2012 01:04:11 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id DCB4A8FC08 for ; Fri, 30 Nov 2012 01:04:10 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.hvnu.psconsult.nl [46.44.189.154]) by mx1.psconsult.nl (8.14.5/8.14.4) with ESMTP id qAU1438j029881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 30 Nov 2012 02:04:08 +0100 (CET) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.5/8.14.4/Submit) id qAU1431F029880 for freebsd-embedded@freebsd.org; Fri, 30 Nov 2012 02:04:03 +0100 (CET) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Fri, 30 Nov 2012 02:04:03 +0100 From: Paul Schenkeveld To: freebsd-embedded@freebsd.org Subject: Re: NanoBSD: Create image sparsely Message-ID: <20121130010403.GA82618@psconsult.nl> References: <42654855-CF29-488A-A645-2A280FC9D074@van-laarhoven.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42654855-CF29-488A-A645-2A280FC9D074@van-laarhoven.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Nov 2012 01:04:11 -0000 On Thu, Nov 29, 2012 at 08:42:23AM +0100, Nick Hibma wrote: > In the past I have submitted patches to create images sparsely. There is however one patch missing still which, with the addition of NANO_INIT_IMG2, has become much more useful: > > --- AnyWi/freebsd/nanobsd/nanobsd.sh 2012-11-08 19:48:40.000000000 +0100 > +++ /usr/src/tools/tools/nanobsd/nanobsd.sh 2012-11-06 15:24:52.000000000 +0100 > @@ -540,7 +540,7 @@ > if [ $NANO_IMAGES -gt 1 -a $NANO_INIT_IMG2 -gt 0 ] ; then > # Duplicate to second image (if present) > echo "Duplicating to second image..." > - dd if=/dev/${MD}s1 of=/dev/${MD}s2 bs=64k > + dd conv=sparse if=/dev/${MD}s1 of=/dev/${MD}s2 bs=64k > mount /dev/${MD}s2a ${MNT} > for f in ${MNT}/etc/fstab ${MNT}/conf/base/etc/fstab > do > @@ -569,7 +569,7 @@ > > if ${do_copyout_partition} ; then > echo "Writing out _.disk.image..." > - dd if=/dev/${MD}s1 of=${NANO_DISKIMGDIR}/_.disk.image bs=64k > + dd conv=sparse if=/dev/${MD}s1 of=${NANO_DISKIMGDIR}/_.disk.image bs=64k > fi > mdconfig -d -u $MD > > It copies out the image sparsely (conv=sparse). The big advantage comes when creating many images (I have between 10 and 20 images simultaneously on my disk). > > Any objections to this? (*) When copying sparsely, blocks containing zeroes are not copied over but skipped using lseek. When the output file is a newly created regular file this is OK because sparse blocks read as zeroes. But here nanobsd.sh writes to a md(4) device which does not contain zeroes when created as a swap based device (NANO_MD_BACKING=swap). When a file on ${MD}s1 contains a block that deliberately contains zeroes the resulting copy is not the same as the original which may cause all kinds of problems. Only when ${MD}s1 is created as a file based device, blocks seeked over will read back as zeroes. Earlier this month I started a thread on freebsd-security@ related to this issue (subject: md(4) (swap-base) disks not cleaned on creation) and the patch by Konstantin Belousov will solve this problem but that leaves all systems before this patch vulnerable to this problem. HTH Paul Schenkeveld From owner-freebsd-embedded@FreeBSD.ORG Sat Dec 1 06:28:50 2012 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 315A8388; Sat, 1 Dec 2012 06:28:50 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id E1FC18FC14; Sat, 1 Dec 2012 06:28:49 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qB16S722075284; Sat, 1 Dec 2012 06:28:07 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id m9agxtjadnmnqxkvzepk23fbpw; Sat, 01 Dec 2012 06:28:07 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: FDT code fixes for ubldr Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: Date: Fri, 30 Nov 2012 22:28:05 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <50B54AB7.8080301@bluezbox.com> <50B68CFA.80208@bluezbox.com> To: Warner Losh X-Mailer: Apple Mail (2.1283) Cc: arm@freebsd.org, embedded@freebsd.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Dec 2012 06:28:50 -0000 On Nov 28, 2012, at 2:24 PM, Warner Losh wrote: >=20 > On a related note: any plans to have the ability to merge new = nodes/change nodes from the loader? You mean something more than the "fdt" commands provided by sys/boot/fdt/fdt_loader_cmd.c ? Tim From owner-freebsd-embedded@FreeBSD.ORG Sat Dec 1 22:56:42 2012 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7AA6BC53 for ; Sat, 1 Dec 2012 22:56:42 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from vps.van-laarhoven.org (www.hibma.org [178.21.117.90]) by mx1.freebsd.org (Postfix) with ESMTP id 284928FC08 for ; Sat, 1 Dec 2012 22:56:41 +0000 (UTC) Received: from hitske-wlan.fritz.box (thuis.van-laarhoven.org [80.100.41.4]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps.van-laarhoven.org (Postfix) with ESMTPSA id 141315F20C6; Sat, 1 Dec 2012 23:56:55 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: NanoBSD: Create image sparsely From: Nick Hibma In-Reply-To: <20121130010403.GA82618@psconsult.nl> Date: Sat, 1 Dec 2012 23:56:33 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <6BD4F6F8-8D8B-4150-B7A6-C47900C27A06@van-laarhoven.org> References: <42654855-CF29-488A-A645-2A280FC9D074@van-laarhoven.org> <20121130010403.GA82618@psconsult.nl> To: Paul Schenkeveld X-Mailer: Apple Mail (2.1499) Cc: freebsd-embedded@freebsd.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Dec 2012 22:56:42 -0000 > When copying sparsely, blocks containing zeroes are not copied over = but > skipped using lseek. When the output file is a newly created regular > file this is OK because sparse blocks read as zeroes. >=20 > But here nanobsd.sh writes to a md(4) device which does not contain > zeroes when created as a swap based device (NANO_MD_BACKING=3Dswap). = When > a file on ${MD}s1 contains a block that deliberately contains zeroes > the resulting copy is not the same as the original which may cause all > kinds of problems. Only when ${MD}s1 is created as a file based = device, > blocks seeked over will read back as zeroes. >=20 > Earlier this month I started a thread on freebsd-security@ related to > this issue (subject: md(4) (swap-base) disks not cleaned on creation) > and the patch by Konstantin Belousov will solve this problem but that > leaves all systems before this patch vulnerable to this problem. Are you referring to the recent commit that bzero's a page when a new = page is created by the pager (instead of an existing one returned)? Well, if my commit follows that commit (making sure that the MFC does = not precede it either) we should be fine. NanoBSD is provided in the = FreeBSD source tree. Nick=