From owner-freebsd-arm@FreeBSD.ORG Sun Apr 29 23:22:53 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A2F8106566C for ; Sun, 29 Apr 2012 23:22:53 +0000 (UTC) (envelope-from kientzle@freebsd.org) 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 634F88FC0A for ; Sun, 29 Apr 2012 23:22:53 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q3TNMaId000908; Sun, 29 Apr 2012 23:22:36 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id aw9y9e2d8fse97guev34337z2a; Sun, 29 Apr 2012 23:22:36 +0000 (UTC) (envelope-from kientzle@freebsd.org) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle In-Reply-To: <495386AF-37AB-450D-B78C-2A6282083587@bsdimp.com> Date: Sun, 29 Apr 2012 16:22:35 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9AD7075B-B85D-40DB-84B7-FD630B858A30@freebsd.org> <495386AF-37AB-450D-B78C-2A6282083587@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.1257) Cc: arm@freebsd.org Subject: Re: Cross-buildworld works but not native build? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2012 23:22:53 -0000 On Apr 27, 2012, at 1:04 PM, Warner Losh wrote: >=20 >> On Fri, Apr 27, 2012 at 1:48 AM, Tim Kientzle = wrote: >>> I've been working with the projects/armv6 tree and have encountered = a very confusing situation. >>>=20 >>> On i386, this works: >>> $ make TARGET_ARCH=3Darm TARGET_CPUTYPE=3Darmv6 buildworld >>>=20 >>> If I take the resulting world and run it on arm, then the following = fails (with the exact same source): >>> $ make buildworld >=20 > I think it would work in the current tree if you added = TARGET_CPUTYPE=3Darmv6 to the buildworld. >=20 > I'm hoping to fix issues like this in my armv6 patches. With that change, the current armv6 tree can successfully complete a native buildworld/installworld on BeagleBone. Next step: get buildkernel/installkernel to work. (I have most of the pieces I need; just some slogging to fit it together properly.) Tim From owner-freebsd-arm@FreeBSD.ORG Mon Apr 30 11:07:23 2012 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C86D7106566B for ; Mon, 30 Apr 2012 11:07:23 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B2A6F8FC12 for ; Mon, 30 Apr 2012 11:07:23 +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 q3UB7N5C053815 for ; Mon, 30 Apr 2012 11:07:23 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3UB7N3q053813 for freebsd-arm@FreeBSD.org; Mon, 30 Apr 2012 11:07:23 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Apr 2012 11:07:23 GMT Message-Id: <201204301107.q3UB7N3q053813@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-arm@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 11:07:23 -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 arm/166256 arm build fail in pmap.c o arm/162159 arm [panic] USB errors leading to panic on DockStar 9.0-RC o arm/161110 arm /usr/src/sys/arm/include/signal.h is bad o arm/161044 arm devel/icu does not build on arm o arm/160431 arm [busdma] [patch] Disable interrupts during busdma cach o arm/158950 arm arm/sheevaplug fails fsx when mmap operations are enab o arm/156814 arm OpenRD Ultimate does not boot on DB-88F6XXX or SHEEVAP o arm/156496 arm [patch] Minor bugfixes and enhancements to mmc and mmc o arm/155894 arm [patch] Enable at91 booting from SDHC (high capacity) o arm/155214 arm [patch] MMC/SD IO slow on Atmel ARM with modern large o arm/154227 arm [geli] using GELI leads to panic on ARM o arm/154189 arm lang/perl5.12 doesn't build on arm o arm/153380 arm Panic / translation fault with wlan on ARM o arm/150581 arm [irq] Unknown error generates IRQ address decoding err o arm/149288 arm mail/dovecot causes panic during configure on Sheevapl o arm/134368 arm [patch] nslu2_led driver for the LEDs on the NSLU2 p arm/134338 arm [patch] Lock GPIO accesses on ixp425 17 problems total. From owner-freebsd-arm@FreeBSD.ORG Mon Apr 30 16:05:55 2012 Return-Path: Delivered-To: arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC378106566B; Mon, 30 Apr 2012 16:05:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 9195D8FC1D; Mon, 30 Apr 2012 16:05:55 +0000 (UTC) Received: from [10.30.101.53] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q3UFqc6k038986 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Mon, 30 Apr 2012 09:52:39 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Mon, 30 Apr 2012 09:52:31 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9AD7075B-B85D-40DB-84B7-FD630B858A30@freebsd.org> <495386AF-37AB-450D-B78C-2A6282083587@bsdimp.com> To: Tim Kientzle X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Mon, 30 Apr 2012 09:52:39 -0600 (MDT) Cc: arm@FreeBSD.org Subject: Re: Cross-buildworld works but not native build? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 16:05:55 -0000 On Apr 29, 2012, at 5:22 PM, Tim Kientzle wrote: > On Apr 27, 2012, at 1:04 PM, Warner Losh wrote: >>=20 >>> On Fri, Apr 27, 2012 at 1:48 AM, Tim Kientzle = wrote: >>>> I've been working with the projects/armv6 tree and have encountered = a very confusing situation. >>>>=20 >>>> On i386, this works: >>>> $ make TARGET_ARCH=3Darm TARGET_CPUTYPE=3Darmv6 buildworld >>>>=20 >>>> If I take the resulting world and run it on arm, then the following = fails (with the exact same source): >>>> $ make buildworld >>=20 >> I think it would work in the current tree if you added = TARGET_CPUTYPE=3Darmv6 to the buildworld. >>=20 >> I'm hoping to fix issues like this in my armv6 patches. >=20 > With that change, the current armv6 tree can successfully > complete a native buildworld/installworld on BeagleBone. >=20 > Next step: get buildkernel/installkernel to work. (I have > most of the pieces I need; just some slogging to fit it together > properly.) Cool. I'll be trying to get that change merged into my = MACHINE_ARCH=3Darmv6 patches. Warner From owner-freebsd-arm@FreeBSD.ORG Mon Apr 30 16:28:46 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 29FA5106564A for ; Mon, 30 Apr 2012 16:28:45 +0000 (UTC) (envelope-from casibbald@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id A261B8FC0A for ; Mon, 30 Apr 2012 16:28:45 +0000 (UTC) Received: by iahk25 with SMTP id k25so6089838iah.13 for ; Mon, 30 Apr 2012 09:28:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=t/l/f01KqGhJa/a6X4PLn0pI7IMmKdAOScmjf45vDFs=; b=PU2lk11vmfeIkhj1otzDfDX2s9kHJ7YSpKHjdTMY5PEgyo173h6hBOprvPB6vI6n0G bg8YbwxM5X0MWcewBi0E0v5zr6ExUCvLz1aMFnrS6Je5P1mZotR0ZTH+ZF8T12BueVCk Tp5KJxetnGrqCdv+Vxv+5Ofb+Sd++1jJE6OUPoiKJ37O7wdbHh0sA/ExT/dtGGOXWFGE 7SDOIQJPDTBL1zGFU7YHaNJYAlunBfTkido/JPELWMEZN3YMrZ0xOQfTwgVLtp+CqCdp gB4uhgMAaVvuowerRRR6dN6E9BIB06Bpm5CvnembuUBntnic7dgwpg1+DmPuKbiK/mR+ Gv8Q== MIME-Version: 1.0 Received: by 10.42.141.133 with SMTP id o5mr16349979icu.13.1335803325153; Mon, 30 Apr 2012 09:28:45 -0700 (PDT) Received: by 10.43.50.129 with HTTP; Mon, 30 Apr 2012 09:28:45 -0700 (PDT) In-Reply-To: References: <2FED907D-D5FF-44E5-A2DC-62957C7904F4@gmail.com> <3F8A354F-1FA6-4923-A678-2102F8CDC0BA@kientzle.com> Date: Mon, 30 Apr 2012 17:28:45 +0100 Message-ID: From: Charles Sibbald To: Tim Kientzle Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-arm@freebsd.org" Subject: Re: Raspberry PI ARM Clone X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: casibbald@gmail.com List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 16:28:46 -0000 Hi All, http://db.tt/LEh6kZey a document on the SOC we my use, we are just trying to confirm volume pricing for this. Regards Charles On 29 April 2012 00:43, Tim Kientzle wrote: > My BeagleBone board here seems to have about 1cm radius corners. > > Tim > > On Apr 28, 2012, at 4:20 PM, Charles Sibbald wrote: > >> Ok will pass that info on dimensions. >> >> What is the radius of the curved edges on the altoids tin? >> >> Sent from my iPhone >> >> On 28 Apr 2012, at 22:28, Tim Kientzle wrote: >> >>> Of course, 90x55 with rounded corners would fit in an Altoids tin. ;-) >>> >>> >>> On Apr 28, 2012, at 12:54 PM, Charles Sibbald wrote: >>> >>>> We are aiming at 60 x 90 or 60 x 100. >>>> We may ditch the Audio/RCA as both those could go out HDMI. >>>> >>>> Will find out about the gig Ethernet. >>>> >>>> Sent from my iPhone >>>> >>>> On 28 Apr 2012, at 20:35, Tim Kientzle wrote: >>>> >>>>> On Apr 28, 2012, at 5:09 AM, Charles Sibbald wrote: >>>>>> >>>>>> I have had discussions with some friends about the possibility of a >>>>>> high spec 'clone' of the PI and this has brought us to the list at t= he >>>>>> bottom of the page. >>>>>> >>>>>> We have been in discussions with a PCB designer and expect we can >>>>>> produce this with a retail price of under US$100. >>>>>> >>>>>> Does anyone have any comments on this idea, what would be the intere= st >>>>>> in such a spec board? >>>>> >>>>> I know a few folks who have been eyeing RPi, Beagle's, etc, >>>>> to use as general-purpose micro-servers: =A0File servers, >>>>> email, web, etc. >>>>> >>>>> Your proposal works well in some respects: >>>>> * fast CPU >>>>> * plenty of memory >>>>> * USB 3 for external drives >>>>> >>>>> But no GigE. :-( =A0A single GigE port would be much more >>>>> valuable than 2 x 10/100 ports. >>>>> >>>>> Things I could do without (if you're trying to figure >>>>> out how to cut cost): >>>>> * Bluetooth >>>>> * RCA video >>>>> * 512M memory instead of 1024M >>>>> * GSM/GPRS >>>>> * Audio >>>>> >>>>> Q: Are you looking at a single-cable dev setup >>>>> like the BeagleBone? =A0It is awfully convenient. >>>>> >>>>> Any thoughts on the likely form factor? >>>>> >>>>> Tim >>>>> >>>> _______________________________________________ >>>> freebsd-arm@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>>> >>> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > From owner-freebsd-arm@FreeBSD.ORG Tue May 1 05:43:08 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8298110657A0 for ; Tue, 1 May 2012 05:43:08 +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 5DDDF8FC15 for ; Tue, 1 May 2012 05:43:08 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q415h2Fu007677 for arm@freebsd.org; Tue, 1 May 2012 05:43:02 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id gun7attxjvy8zt8qm5ex7ycike; for arm@freebsd.org; Tue, 01 May 2012 05:43:02 +0000 (UTC) (envelope-from tim@kientzle.com) From: Tim Kientzle Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Apr 2012 22:43:01 -0700 Message-Id: <1BB6F5DA-36E9-471A-8926-F56275D90962@kientzle.com> To: arm@freebsd.org Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) Cc: Subject: Request for Review: improving Ubldr syscall linkage. X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 05:43:08 -0000 Any comments on the following before I commit? Basically, this just: * Removes some redundant loads * Uses blx for the subroutine call * Uses bx for the subroutine return The only odd point: The ARM reference I have lists blx only for ARMv6 and ARMv7 instruction sets =85 or am I misreading that somehow? It seems to work, but my only ARM board is ARMv7 and I don't want to screw up anything for older CPUs. Index: sys/boot/arm/uboot/start.S =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/boot/arm/uboot/start.S (revision 234747) +++ sys/boot/arm/uboot/start.S (working copy) @@ -49,30 +49,22 @@ * syscall() */ ENTRY(syscall) - /* Save caller's lr */ + /* Save caller's lr and r8 */ ldr ip, =3Dsaved_regs str lr, [ip, #4] - /* Save loader's r8 */ - ldr ip, =3Dsaved_regs str r8, [ip, #8] - /* Restore U-Boot's r8 */ - ldr ip, =3Dsaved_regs ldr r8, [ip, #0] /* Call into U-Boot */ - ldr lr, =3Dreturn_from_syscall ldr ip, =3Dsyscall_ptr - ldr pc, [ip] - -return_from_syscall: - /* Restore loader's r8 */ + ldr ip, [ip, #0] + blx ip + /* Restore loader's r8 and lr */ ldr ip, =3Dsaved_regs ldr r8, [ip, #8] - /* Restore caller's lr */ - ldr ip, =3Dsaved_regs ldr lr, [ip, #4] /* Return to caller */ - mov pc, lr + bx lr =20 /* * Data section From owner-freebsd-arm@FreeBSD.ORG Tue May 1 08:01:10 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 68FF1106564A for ; Tue, 1 May 2012 08:01:10 +0000 (UTC) (envelope-from damjan.marion@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id EB8F88FC12 for ; Tue, 1 May 2012 08:01:09 +0000 (UTC) Received: by wibhq7 with SMTP id hq7so2811930wib.13 for ; Tue, 01 May 2012 01:01:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=guetqZWvpjdxXDav3Myo9wXtzixV3lsHpkOkbLzro4Q=; b=kS07kXS7b10RlC/FayAW9taR3HEhgqFY5EDzS58UH1TJFVkyKruS7zWmO2bUy98PIM Jdo6co0J4yWYaLDOFzIMOclwddl6K53bG3GNGXQokIPjEolJylPGfcKe+Wwn6f6M2zCO 6Qf7uQbffsCXA8Zdu1KsL3IWB/h/f8c+BbywAPfmNXRXAIUlvfk9N63KMpN/Pd8guQQl 6OiGEWLXroJMNM8qyupNBdbAwmKtRYwgAdQnpm1jxUsaj/jtqvHOW11kKolW0vNGy+uv PXYJMn3z09gSpviS7vbEHmVEawsJJ3r4RHslT5Vk/SGdXUmWAfg71d6wqYYUHHT9pRLw RT2w== Received: by 10.180.83.72 with SMTP id o8mr3247719wiy.5.1335859268699; Tue, 01 May 2012 01:01:08 -0700 (PDT) Received: from damarion-mac.home (cpe-109-60-84-201.zg3.cable.xnet.hr. [109.60.84.201]) by mx.google.com with ESMTPS id ff2sm54783677wib.9.2012.05.01.01.01.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 May 2012 01:01:07 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1252 From: Damjan Marion In-Reply-To: <1BB6F5DA-36E9-471A-8926-F56275D90962@kientzle.com> Date: Tue, 1 May 2012 10:01:05 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <5FBCFC46-1DD9-4F29-8DD9-CB1E19D9BB21@gmail.com> References: <1BB6F5DA-36E9-471A-8926-F56275D90962@kientzle.com> To: Tim Kientzle X-Mailer: Apple Mail (2.1257) Cc: arm@freebsd.org Subject: Re: Request for Review: improving Ubldr syscall linkage. X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 08:01:10 -0000 On May 1, 2012, at 7:43 AM, Tim Kientzle wrote: >=20 > The only odd point: The ARM reference I have lists blx > only for ARMv6 and ARMv7 instruction sets =85 or am I > misreading that somehow? BX and BLX are supported since ARMv5 in ARM mode and since ARMv4 in = THUMB mode so this will break some very old stuff like StrongARM which = is ARMv4(non T). Damjan From owner-freebsd-arm@FreeBSD.ORG Tue May 1 16:33:58 2012 Return-Path: Delivered-To: arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E146B106566B for ; Tue, 1 May 2012 16:33:58 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 994988FC0C for ; Tue, 1 May 2012 16:33:58 +0000 (UTC) Received: from [10.30.101.53] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q41GNuFQ049654 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 1 May 2012 10:23:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: Warner Losh In-Reply-To: <5FBCFC46-1DD9-4F29-8DD9-CB1E19D9BB21@gmail.com> Date: Tue, 1 May 2012 10:23:51 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <1E1891C5-3ACC-4C35-B966-D9B96424E245@bsdimp.com> References: <1BB6F5DA-36E9-471A-8926-F56275D90962@kientzle.com> <5FBCFC46-1DD9-4F29-8DD9-CB1E19D9BB21@gmail.com> To: Damjan Marion X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Tue, 01 May 2012 10:23:58 -0600 (MDT) Cc: arm@FreeBSD.org, Tim Kientzle Subject: Re: Request for Review: improving Ubldr syscall linkage. X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 16:33:59 -0000 On May 1, 2012, at 2:01 AM, Damjan Marion wrote: >=20 > On May 1, 2012, at 7:43 AM, Tim Kientzle wrote: >>=20 >> The only odd point: The ARM reference I have lists blx >> only for ARMv6 and ARMv7 instruction sets =85 or am I >> misreading that somehow? >=20 > BX and BLX are supported since ARMv5 in ARM mode and since ARMv4 in = THUMB mode so this will break some very old stuff like StrongARM which = is ARMv4(non T). Of the Atmel stuff, only the AT91RM9200 is ARM v4. The rest is ARMv5. = I don't know that we support the callback to the bootloader for the = Atmel port, but a lot of work went in for the AT91SAM stuff that might = have snuck that kind of change in when I wasn't looking. Warner From owner-freebsd-arm@FreeBSD.ORG Tue May 1 16:55:10 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 494AA106566C for ; Tue, 1 May 2012 16:55:10 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 1C5BF8FC17 for ; Tue, 1 May 2012 16:55:10 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta06.emeryville.ca.mail.comcast.net with comcast id 4fr41j00A1afHeLA6gv4e3; Tue, 01 May 2012 16:55:04 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta17.emeryville.ca.mail.comcast.net with comcast id 4gv21j00L4NgCEG8dgv3TQ; Tue, 01 May 2012 16:55:03 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q41Gt122081337; Tue, 1 May 2012 10:55:01 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Warner Losh In-Reply-To: <1E1891C5-3ACC-4C35-B966-D9B96424E245@bsdimp.com> References: <1BB6F5DA-36E9-471A-8926-F56275D90962@kientzle.com> <5FBCFC46-1DD9-4F29-8DD9-CB1E19D9BB21@gmail.com> <1E1891C5-3ACC-4C35-B966-D9B96424E245@bsdimp.com> Content-Type: text/plain; charset="windows-1251" Date: Tue, 01 May 2012 10:55:00 -0600 Message-ID: <1335891300.1111.17.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: arm@freebsd.org, Tim Kientzle Subject: Re: Request for Review: improving Ubldr syscall linkage. X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 16:55:10 -0000 On Tue, 2012-05-01 at 10:23 -0600, Warner Losh wrote: > On May 1, 2012, at 2:01 AM, Damjan Marion wrote: > > > > > On May 1, 2012, at 7:43 AM, Tim Kientzle wrote: > >> > >> The only odd point: The ARM reference I have lists blx > >> only for ARMv6 and ARMv7 instruction sets … or am I > >> misreading that somehow? > > > > BX and BLX are supported since ARMv5 in ARM mode and since ARMv4 in THUMB mode so this will break some very old stuff like StrongARM which is ARMv4(non T). > > Of the Atmel stuff, only the AT91RM9200 is ARM v4. The rest is ARMv5. I don't know that we support the callback to the bootloader for the Atmel port, but a lot of work went in for the AT91SAM stuff that might have snuck that kind of change in when I wasn't looking. > > Warner The rm9200 is ARMv4T so according to the ARM ARM it should be okay with the BX and BLX instructions. -- Ian From owner-freebsd-arm@FreeBSD.ORG Tue May 1 18:11:29 2012 Return-Path: Delivered-To: arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A290110657C5 for ; Tue, 1 May 2012 18:11:29 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 453C08FC17 for ; Tue, 1 May 2012 18:11:21 +0000 (UTC) Received: from [10.30.101.53] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q41I6lL4050334 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 1 May 2012 12:06:49 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: Warner Losh In-Reply-To: <1335891300.1111.17.camel@revolution.hippie.lan> Date: Tue, 1 May 2012 12:06:42 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <98817205-D039-4EA2-BD6F-7F127926F3F8@bsdimp.com> References: <1BB6F5DA-36E9-471A-8926-F56275D90962@kientzle.com> <5FBCFC46-1DD9-4F29-8DD9-CB1E19D9BB21@gmail.com> <1E1891C5-3ACC-4C35-B966-D9B96424E245@bsdimp.com> <1335891300.1111.17.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Tue, 01 May 2012 12:06:50 -0600 (MDT) Cc: arm@FreeBSD.org, Tim Kientzle Subject: Re: Request for Review: improving Ubldr syscall linkage. X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 18:11:29 -0000 On May 1, 2012, at 10:55 AM, Ian Lepore wrote: > On Tue, 2012-05-01 at 10:23 -0600, Warner Losh wrote: >> On May 1, 2012, at 2:01 AM, Damjan Marion wrote: >>=20 >>>=20 >>> On May 1, 2012, at 7:43 AM, Tim Kientzle wrote: >>>>=20 >>>> The only odd point: The ARM reference I have lists blx >>>> only for ARMv6 and ARMv7 instruction sets =85 or am I >>>> misreading that somehow? >>>=20 >>> BX and BLX are supported since ARMv5 in ARM mode and since ARMv4 in = THUMB mode so this will break some very old stuff like StrongARM which = is ARMv4(non T). >>=20 >> Of the Atmel stuff, only the AT91RM9200 is ARM v4. The rest is = ARMv5. I don't know that we support the callback to the bootloader for = the Atmel port, but a lot of work went in for the AT91SAM stuff that = might have snuck that kind of change in when I wasn't looking. >>=20 >> Warner >=20 > The rm9200 is ARMv4T so according to the ARM ARM it should be okay = with > the BX and BLX instructions. OK. The fact we're not running in Thumb mode won't be a problem? Warner From owner-freebsd-arm@FreeBSD.ORG Tue May 1 19:18:48 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F3B51065670 for ; Tue, 1 May 2012 19:18:48 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 1BD478FC14 for ; Tue, 1 May 2012 19:18:47 +0000 (UTC) Received: from omta11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by qmta08.emeryville.ca.mail.comcast.net with comcast id 4jCa1j0020mlR8UA8jHhvD; Tue, 01 May 2012 19:17:41 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta11.emeryville.ca.mail.comcast.net with comcast id 4jHg1j00M4NgCEG8XjHgJk; Tue, 01 May 2012 19:17:41 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q41JHcPW081397; Tue, 1 May 2012 13:17:38 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Warner Losh In-Reply-To: <98817205-D039-4EA2-BD6F-7F127926F3F8@bsdimp.com> References: <1BB6F5DA-36E9-471A-8926-F56275D90962@kientzle.com> <5FBCFC46-1DD9-4F29-8DD9-CB1E19D9BB21@gmail.com> <1E1891C5-3ACC-4C35-B966-D9B96424E245@bsdimp.com> <1335891300.1111.17.camel@revolution.hippie.lan> <98817205-D039-4EA2-BD6F-7F127926F3F8@bsdimp.com> Content-Type: text/plain; charset="windows-1251" Date: Tue, 01 May 2012 13:17:38 -0600 Message-ID: <1335899858.1111.22.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: arm@FreeBSD.org, Tim Kientzle Subject: Re: Request for Review: improving Ubldr syscall linkage. X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 19:18:48 -0000 On Tue, 2012-05-01 at 12:06 -0600, Warner Losh wrote: > On May 1, 2012, at 10:55 AM, Ian Lepore wrote: > > > On Tue, 2012-05-01 at 10:23 -0600, Warner Losh wrote: > >> On May 1, 2012, at 2:01 AM, Damjan Marion wrote: > >> > >>> > >>> On May 1, 2012, at 7:43 AM, Tim Kientzle wrote: > >>>> > >>>> The only odd point: The ARM reference I have lists blx > >>>> only for ARMv6 and ARMv7 instruction sets … or am I > >>>> misreading that somehow? > >>> > >>> BX and BLX are supported since ARMv5 in ARM mode and since ARMv4 in THUMB mode so this will break some very old stuff like StrongARM which is ARMv4(non T). > >> > >> Of the Atmel stuff, only the AT91RM9200 is ARM v4. The rest is ARMv5. I don't know that we support the callback to the bootloader for the Atmel port, but a lot of work went in for the AT91SAM stuff that might have snuck that kind of change in when I wasn't looking. > >> > >> Warner > > > > The rm9200 is ARMv4T so according to the ARM ARM it should be okay with > > the BX and BLX instructions. > > > OK. The fact we're not running in Thumb mode won't be a problem? > > Warner > I don't think so. The low order bit of the address being loaded controls the transition between regular and thumb mode, and since we would never load an odd address we'd never transition to thumb mode. I've never worked with thumb-mode code, but the way I read the doc, a transition to thumb mode only happens if the low order bit is set on a BX or BLX (or MOV or anything else that loads a value into PC). -- Ian From owner-freebsd-arm@FreeBSD.ORG Sat May 5 05:06:18 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5CE4106564A for ; Sat, 5 May 2012 05:06:18 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from mail-pz0-f48.google.com (mail-pz0-f48.google.com [209.85.210.48]) by mx1.freebsd.org (Postfix) with ESMTP id 7A90D8FC15 for ; Sat, 5 May 2012 05:06:18 +0000 (UTC) Received: by dadz8 with SMTP id z8so920537dad.7 for ; Fri, 04 May 2012 22:06:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version:x-mailer:x-gm-message-state; bh=wk04EFSI5GcP8IvsBQzSR5GGbdrHIJ+/4za+A2gPA9I=; b=PB5UWvt5KjD0dtwyboyPJIH9qMGt0Kygf64cOCBLrDU/qPS4g4rY4fk78jl/zR5MKc csUL3B2sT5yQqcQwcZOi3dDBWvh/mCfBLqFtCC90m9gAi38KbzRWYJmwNlIWynUqMYqE KB4VEVk5mpTUH5jmLq7460JACAiKUcYYZ9D/IoyawRRskqLGC79c7VFQd5+NX3pJUN+t 6pPcThdnVVk72SrhBpZRLro32qwhTXh4qqczkMnmYBPJ1mV0S5W1T9YTs7BkDUjleetb 3fpWk4DvaFQh8LvRRlD2algYUl6e4K6QJkhMac8qGPth/XbTy3z3Ydt4ZMYu/KM7rvig dSDw== Received: by 10.68.195.71 with SMTP id ic7mr25288730pbc.34.1336194377937; Fri, 04 May 2012 22:06:17 -0700 (PDT) Received: from [192.168.1.69] (99-74-169-43.lightspeed.sntcca.sbcglobal.net. [99.74.169.43]) by mx.google.com with ESMTPS id x1sm10722282pbp.50.2012.05.04.22.06.15 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 May 2012 22:06:16 -0700 (PDT) Sender: Tim Kientzle From: Tim Kientzle Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 4 May 2012 22:06:13 -0700 Message-Id: <3B2A320B-3ADE-4F48-B94E-4F0886178251@freebsd.org> To: arm@freebsd.org, freebsd-hackers Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQkF17KAs9iucVLgdpCZ61tAhWRennPPkX2rGayYs0BkxjkGfhOoet+Jxzd+ddWhIDnUsM4C Cc: Subject: How does loader(8) decide where to load the kernel? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 May 2012 05:06:18 -0000 I have ubldr loading the ELF kernel on BeagleBone and am now trying to untangle some of the hacks I used to get this working. Unfortunately, there's one area of the common loader(8) code that I really don't understand: How does sys/boot/common/load_elf.c determine the physical address at which to load the kernel? __elfN(loadfile) has the following comment: [The file] will be stored at (dest). But that's not really true. For starters, loadfile maps dest through archsw.arch_loadaddr. (This mechanism seems to only be used on ia64 and pc98, though the result is later discarded on those platforms.) Loadfile then passes the value to loadimage which does very strange things: On i386, amd64, powerpc, and arm, loadimage subtracts the dest value from the address declared in the actual ELF headers so that the kernel always gets loaded into low memory. (there's some intermediate bit-twiddling I'm glossing over, but this is the general idea). On other platforms, the dest value passed into loadimage is entirely ignored. So it looks like the arch_loadaddr manipulations used on ia64 and pc98 are in fact not used. In my case, I have a kernel linked against a virtual address of 0xc0200000 that I want to load into a physical address of 0x80200000. I can make it work by having arch_loadaddr return a value of 0x40000000 (which then gets subtracted from the virtual address in the ELF file to produce the physical address I need), but this seems really byzantine. How is this *supposed* to work? Anybody know? Tim From owner-freebsd-arm@FreeBSD.ORG Sat May 5 06:50:58 2012 Return-Path: Delivered-To: arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BEF14106566B; Sat, 5 May 2012 06:50:58 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6AA5F8FC0A; Sat, 5 May 2012 06:50:58 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q456jRPB038085 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 5 May 2012 00:45:28 -0600 (MDT) (envelope-from imp@bsdimp.com) From: Warner Losh Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 5 May 2012 00:45:27 -0600 Message-Id: To: "arm@freebsd.org" Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 05 May 2012 00:45:28 -0600 (MDT) Cc: Alan Cox Subject: Review needed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 May 2012 06:50:58 -0000 I just tried to bring up an old Gateworks AVILA board that I'd acquired = a long time ago.... After fighting through a few bugs in the nanobsd build, I managed to get = an image. That image failed to boot. When it harvested entropy, it just started = printing pmap_mincore() over and over again until I hit ^T enough to let = the rest of the boot process continue. Sure enough, arm's = pmap_mincore() returns 0 after printing this. So, I cobbled together the following after looking at mips and amd64's = pmap_mincore() functions. I've just cut and pasted it here since I think that might be easier to = review than a diff, but I've also uploaded that as well to = http://people.freebsd.org/~imp/arm-pmap_mincore.diff Comments? Warner /* = = =20 * perform the pmap work for mincore = = =20 */ int pmap_mincore(pmap_t pmap, vm_offset_t addr, vm_paddr_t *locked_pa) { struct l2_bucket *l2b; pt_entry_t *ptep, pte; vm_paddr_t pa; vm_page_t m; int val; boolean_t managed; PMAP_LOCK(pmap); retry: l2b =3D pmap_get_l2_bucket(pmap, addr); if (l2b =3D=3D NULL) { val =3D 0; goto out; } ptep =3D &l2b->l2b_kva[l2pte_index(addr)]; pte =3D (ptep !=3D NULL) ? *ptep : 0; if (!l2pte_valid(pte)) { val =3D 0; goto out; } val =3D MINCORE_INCORE; if (pte & L2_S_PROT_W) val |=3D MINCORE_MODIFIED | MINCORE_MODIFIED_OTHER; managed =3D false; pa =3D l2pte_pa(pte); m =3D PHYS_TO_VM_PAGE(pa); if (m !=3D NULL && !(m->oflags & VPO_UNMANAGED)) managed =3D true; if (managed) { /* = = =20 * This may falsely report the given address as = = =20 * MINCORE_REFERENCED. Unfortunately, due to the lack = of = =20 * per-PTE reference information, it is impossible to = = =20 * determine if the address is MINCORE_REFERENCED. = = =20 */ if ((m->aflags & PGA_REFERENCED) !=3D 0) val |=3D MINCORE_REFERENCED | = MINCORE_REFERENCED_OTHER; } if ((val & (MINCORE_MODIFIED_OTHER | MINCORE_REFERENCED_OTHER)) = !=3D (MINCORE_MODIFIED_OTHER | MINCORE_REFERENCED_OTHER) && = managed) { /* Ensure that "PHYS_TO_VM_PAGE(pa)->object" doesn't = change. */ if (vm_page_pa_tryrelock(pmap, pa, locked_pa)) goto retry; } else out: PA_UNLOCK_COND(*locked_pa); PMAP_UNLOCK(pmap); return (val); } From owner-freebsd-arm@FreeBSD.ORG Sat May 5 18:10:28 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52EF7106564A; Sat, 5 May 2012 18:10:28 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id B6F188FC1E; Sat, 5 May 2012 18:10:27 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id q45IAH2i048748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 May 2012 11:10:17 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id q45IAHvn048747; Sat, 5 May 2012 11:10:17 -0700 (PDT) (envelope-from jmg) Date: Sat, 5 May 2012 11:10:17 -0700 From: John-Mark Gurney To: Warner Losh Message-ID: <20120505181016.GB2253@funkthat.com> Mail-Followup-To: Warner Losh , "arm@freebsd.org" , Alan Cox References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Sat, 05 May 2012 11:10:17 -0700 (PDT) Cc: "arm@freebsd.org" , Alan Cox Subject: Re: Review needed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 May 2012 18:10:28 -0000 Warner Losh wrote this message on Sat, May 05, 2012 at 00:45 -0600: > I just tried to bring up an old Gateworks AVILA board that I'd acquired a long time ago.... Hmm... weird... Late last year I brought my AVILA board back up on 9.0-RC1 and since I decided to try to boot from CF, I did have to update sys/boot/arm/ixp425/boot2/boot2.c to support the new ada devices instead of the old ad... but that's the only major change I made... > After fighting through a few bugs in the nanobsd build, I managed to get an image. > > That image failed to boot. When it harvested entropy, it just started printing pmap_mincore() over and over again until I hit ^T enough to let the rest of the boot process continue. Sure enough, arm's pmap_mincore() returns 0 after printing this. > > So, I cobbled together the following after looking at mips and amd64's pmap_mincore() functions. > > I've just cut and pasted it here since I think that might be easier to review than a diff, but I've also uploaded that as well to http://people.freebsd.org/~imp/arm-pmap_mincore.diff > > Comments? Must be a head only thing... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@FreeBSD.ORG Sat May 5 19:32:07 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C05DF106564A; Sat, 5 May 2012 19:32:07 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 787648FC08; Sat, 5 May 2012 19:32:07 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q45JQRHA043550 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 5 May 2012 13:26:28 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20120505181016.GB2253@funkthat.com> Date: Sat, 5 May 2012 13:26:27 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120505181016.GB2253@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 05 May 2012 13:26:28 -0600 (MDT) Cc: "arm@freebsd.org" , Alan Cox Subject: Re: Review needed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 May 2012 19:32:07 -0000 On May 5, 2012, at 12:10 PM, John-Mark Gurney wrote: > Warner Losh wrote this message on Sat, May 05, 2012 at 00:45 -0600: >> I just tried to bring up an old Gateworks AVILA board that I'd = acquired a long time ago.... >=20 > Hmm... weird... Late last year I brought my AVILA board back up on > 9.0-RC1 and since I decided to try to boot from CF, I did have to > update sys/boot/arm/ixp425/boot2/boot2.c to support the new ada = devices > instead of the old ad... but that's the only major change I made... This is with the G2348 config file. Maybe that's the difference... >> After fighting through a few bugs in the nanobsd build, I managed to = get an image. >>=20 >> That image failed to boot. When it harvested entropy, it just = started printing pmap_mincore() over and over again until I hit ^T = enough to let the rest of the boot process continue. Sure enough, arm's = pmap_mincore() returns 0 after printing this. >>=20 >> So, I cobbled together the following after looking at mips and = amd64's pmap_mincore() functions. >>=20 >> I've just cut and pasted it here since I think that might be easier = to review than a diff, but I've also uploaded that as well to = http://people.freebsd.org/~imp/arm-pmap_mincore.diff >>=20 >> Comments? >=20 > Must be a head only thing... No, it was a nanobsd-built stable/9 from yesterday Warner