Date: Thu, 15 Sep 2016 10:48:31 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Russell Haley <russ.haley@gmail.com> Cc: gabor@zahemszky.hu, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: RPi2 with RedBear IoT pHat cannot boot Message-ID: <CAJ-Vmo=iYAL8hL0qYKhwZZgz=QJ_orGisxqGzZftOLNn3JrL%2Bw@mail.gmail.com> In-Reply-To: <20160915170819.5320786.4442.11843@gmail.com> References: <f398b7d9aaec916522dbff9149326223@zahemszky.hu> <20160914113900.5320786.47379.11733@gmail.com> <53760d65abcb76c0ee3acf5fe86ad603@zahemszky.hu> <20160915165950.5320786.36203.11840@gmail.com> <20160915170819.5320786.4442.11843@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <russ.haley@gmail.com> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=iYAL8hL0qYKhwZZgz=QJ_orGisxqGzZftOLNn3JrL%2Bw>