From owner-freebsd-arm@freebsd.org Thu Sep 15 17:48:33 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F212BDB8BF for ; Thu, 15 Sep 2016 17:48:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE851A12 for ; Thu, 15 Sep 2016 17:48:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x231.google.com with SMTP id o3so108158369ita.1 for ; Thu, 15 Sep 2016 10:48:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=VXT7nb0PhaNeHrqAd9hhJGSmlU3O/HYMcshLiY3S/KA=; b=rAXKPFEjINXB7dVByBTi6MHCuoKledqca/HKJ1zpDU1CtVUJmGa9XAK93VZkcnBNuZ 42f9o3MAwk1yi6gwcOh45U16Ho/6tv10zBB2SomUOTR01bNxJhbBHeaTpyS2Uye0mdOB IYstABa+63wC7ziEACD/DyhM+vxiYoatM74ZtfSZIkqW5tVNan+lS3KKu9jSTBR6ADGi gnCsM3lbsW+tWlY/Qqd6FlOsbjA+YiBj9TPE1bRFyHj8kVx2y6xgrCOGKHRu9DcoS5O4 Ws1BPAEFGvX7IJqjCKiCzIKHg7p6nQjHFoBcDktsd33/jismy5vki/lml0nNnVu1lY2q e/Bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=VXT7nb0PhaNeHrqAd9hhJGSmlU3O/HYMcshLiY3S/KA=; b=mAFOXj7rGP2wMBYU4vSZdqRg+n7RVaPNxJDK0b86yLDPv3qaCJ87R4tABrobKE5mdn qzhSJ8xYmX8w602rZtkSKK9ysXNhbjk6qub93a530tTZVT1MELbxSGHb2Ie2B0SAwuq4 8oLLb5Z1FBkYQnCJ5PzogtB7kFOB3my3RjZatl+uvnCiG4CIhxsWyRd1RLsFpi9wLeRJ 9U8qKuOSTq7Rx0ukjqK7MVfT5sNrmCPas1G4DHa09IDGs921EbuPOx198upmTve8V+MD viK6gUbCzzmWqFBUj0xN6BAsQUoPLoLL4neAjNBDswRZJHpv6tWm50C697hxulcauEb5 5I0Q== X-Gm-Message-State: AE9vXwPCN7sugqrJ4AZ35ZhtTHu91FSo9xopAjBPVchmSZzf/fBvXOWOx891iClJQ34EEY/NnGMXQq/fENNkpQ== X-Received: by 10.36.4.143 with SMTP id 137mr786517itb.39.1473961712285; Thu, 15 Sep 2016 10:48:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Thu, 15 Sep 2016 10:48:31 -0700 (PDT) In-Reply-To: <20160915170819.5320786.4442.11843@gmail.com> References: <20160914113900.5320786.47379.11733@gmail.com> <53760d65abcb76c0ee3acf5fe86ad603@zahemszky.hu> <20160915165950.5320786.36203.11840@gmail.com> <20160915170819.5320786.4442.11843@gmail.com> From: Adrian Chadd Date: Thu, 15 Sep 2016 10:48:31 -0700 Message-ID: Subject: Re: RPi2 with RedBear IoT pHat cannot boot To: Russell Haley Cc: gabor@zahemszky.hu, "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2016 17:48:33 -0000 Right, but we're missing the "use sdio for non-mmc" bits, which is what is currently under development. :) -a On 15 September 2016 at 10:08, Russell Haley wrote: > Please see https://wikidevi.com/wiki/Broadcom under the SDIO section. The= two chipsets are in the same group of devices. > > Russ > > Sent from my BlackBerry 10 smartphone on the Virgin Mobile network. > Original Message > From: Russell Haley > Sent: Thursday, September 15, 2016 12:59 PM > To: gabor@zahemszky.hu; freebsd-arm@freebsd.org > Subject: Re: RPi2 with RedBear IoT pHat cannot boot > > Sorry for the top post. > > I said similar or the same, I don't have a lot of bandwidth to check thes= e things right now. > > SDIO (the hardware interface for both chips) is not currently supported b= y the FreeBSD kernel and there does not seem to be support for the underlyi= ng Broadcom chips (as there is no SDIO support!), but Mr. Adrian Chadd may = be able to speak more to that. =E2=80=8EHe has previously mentioned that th= e chips are very complex and porting them will be time consuming. > > There is currently a new SDIO driver making its way into the head branch = but it will not be in FreeBSD 11. Mr. Warner Losh could speak more to that. > > Please see =E2=80=8Ehttps://reviews.freebsd.org/D4761 for more details on= the new CAMMMC driver. > > As I am not a hardware/FTD expert, I would guess that the issue you are s= eeing is the same both ways: the phat is modifying the hardware signature o= f the device, causing the dtb to fail to load. =E2=80=8EBut that's just a g= uess. > > Russ > > Sent from my BlackBerry 10 smartphone on the Virgin Mobile network. > Original Message > From: gabor@zahemszky.hu > Sent: Thursday, September 15, 2016 12:35 PM > To: freebsd-arm@freebsd.org > Subject: Re: RPi2 with RedBear IoT pHat cannot boot > > Hi! > > The saga continues. Under Raspbian, I upgraded the pHAT's firmware from > the factory default v0.2 to v0.3. > > After the FW-upgrade, under Raspbian, it works fine. But under FreeBSD, > it got worse, as now it failed to boot at all. The actual message is: > > Net: Net Initialization Skipped > No ethernet found. > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Hit any key to stop autoboot: 0 > U-Boot> > > So there is another problem. > >> I don't know why your getting a dtb error but the modem on the phat is >> similar or the same as the Bananapi Pro and is not currently >> supported. > > Well, thats wrong. In the Banana Pro, we can find (from : > http://www.lemaker.org/product-bananapro-specification.html ) > > AP6181 Wifi module. > > On the RedBear IoT pHAT (from : https://github.com/redbear/IoT_pHAT ) > there is > > AP6212A Wireless with BCM43438 (Wifi + Bluetooth) module. > > (the same Broadcom BCM43438 is in the Pi3.) > > Thanks, > > G=C3=A1bor > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"