From owner-freebsd-arm@FreeBSD.ORG Sun Apr 27 14:34:47 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BAE14F61; Sun, 27 Apr 2014 14:34:47 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84D3F1A19; Sun, 27 Apr 2014 14:34:47 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id fb1so4213014pad.38 for ; Sun, 27 Apr 2014 07:34:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=TvBST0FPhXtj0YBvAuQizfFtyMJ5DMFt8TEhhMdJE9M=; b=thdDj+dN0mWkDlKIIkKR1pxjvSHwrP3XLE/38VM+Wz03qE+xCOU6HKe5Cm++72Va05 PiLWRf9sRK68QHkZdvDIXmKQEm3F74utTQmypDz0RQvaurPBFw0wTi/8v3EVdUwol99i O9svYDdVrO1KOSA73vyp7TgE7MqZsLXGks/UjdL9jIq3028JyUuJBYSrajO9cdLn1V0i 8qjuUtYS4sfmA/f4PAoXAGaYG/pko1OeCkGHu/5LgoDQ8lfMh/9/nrNldluM6wfQXF1X ec0kGk1dorxQXs5QKRdhnNA9ZpMQ4oRGYjPwUwwxGBKQ6UBWci2zdkl1rib5Z7a5nw+Y UWOg== X-Received: by 10.66.177.168 with SMTP id cr8mr3044669pac.128.1398609276394; Sun, 27 Apr 2014 07:34:36 -0700 (PDT) Received: from [216.131.71.113] ([216.131.71.113]) by mx.google.com with ESMTPSA id ky8sm28741243pbc.64.2014.04.27.07.34.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 27 Apr 2014 07:34:35 -0700 (PDT) Message-ID: <535D1576.6040005@gmail.com> Date: Sun, 27 Apr 2014 22:34:30 +0800 From: Xuebing Wang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "Sulev-Madis Silber (ketas)" , Winston Smith Subject: Re: BBB 1GHz patches for u-boot 2014-01 References: <7249A68B-E3D4-4795-BD51-4DF149B4104A@gmail.com> <746D7AE2-54D1-4758-816F-4954F3F01A5E@gmail.com> <535C7E1B.1090605@hot.ee> In-Reply-To: <535C7E1B.1090605@hot.ee> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD ARM X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2014 14:34:47 -0000 1) We have 2 packages that concerning u-boot: 1a) Crocket 1b) /usr/ports/sysutils/u-boot-beaglebone-eabi Please note: the patches for u-boot in the above 2 packages are different. In my humble opinion, I'd think the u-boot patches for the above 2 packages are better to be identical. 2) My patches to the latest u-boot are against above 1b) /usr/ports/sysutils/u-boot-beaglebone-eabi 3) To rule out the sd-card issue is caused by the latest u-boot, would you mind to go back to the previous u-boot, and re-run the test? Replacing u-boot and MLO can be done by something similar below: scp MLO root@192.168.1.10:/boot/msdos scp u-boot.img root@192.168.1.10:/boot/msdos/BB_UBOOT.IMG Thanks. On 04/27/2014 11:48 AM, Sulev-Madis Silber (ketas) wrote: > On 2014-04-27 04:08, Winston Smith wrote: >> On Sat, Apr 26, 2014 at 6:36 PM, fabiodive wrote: >>> http://lists.freebsd.org/pipermail/freebsd-arm/2014-April/007944.html >> Forgive my ignorance here, but these don't quite look like regular >> patch files ... presumably they get applied to >> crotchet-freebsd/board/BeagleBone to replace the ones already in >> there? > > No, those patches update BB[WB] uboot port to new version and are > perfectly good patches that patch(1) accepts. I bet you can hack those > into crochet too, if you really wish. > > > I also wonder about those weird SD errors... I have different issues > myself (there's message for that already, so I don't repeat). But my > issues always appear on boot. I currently don't run from external SD but > I just tried it and IIRC there are no changes to this code after that. > Internal SD (or eMMC, however you name it) works well, although I had to > apply strange hack which apparently changes some timings so eMMC > detection works correctly. I don't know how that code works, I never > write HW drivers, so I have no idea on that issue. Well, ian@, who DOES > write HW drivers, has no idea too :P Maybe I should get more than one > BBB (for which you need to make special order, I heard) to properly test > my stuff and also other things like possible external SD weirdness. It's > painful to boot from different medium to test some things while > disturbing other things (long-running stability tests). I could say that > BBB is nice piece of HW and 11-CURRENT is very STABLE (what a pun) > overall, with (obviously) some CURRENTish glitches... I also must say > that I use eMMC mostly read-only, with rare writes to upgrade (whole) > system (which is ~150MB in size). > > > BTW, I usually use IRC (EFnet : #bsdmips + several others, and I never > quit), because I somehow find writing long pieces of text difficult. > Although I like mail as non-instant means of communication. > -- Thanks, Xuebing Wang