Date: Sat, 16 Mar 2013 11:54:53 -0600 From: Ian Lepore <ian@FreeBSD.org> To: loic.blot@unix-experience.fr Cc: freebsd-arm@FreeBSD.org Subject: Re: Custom kernel under RPI Message-ID: <1363456493.1157.67.camel@revolution.hippie.lan> In-Reply-To: <1363455598.2403.11.camel@Nerz-PC.home> References: <1363433673.5871.2.camel@Nerz-PC.home> <20130316173850.68e8cc1e.ray@freebsd.org> <1363448928.2403.4.camel@Nerz-PC.home> <20130316180556.a12c6927.ray@freebsd.org> <1363453851.2403.5.camel@Nerz-PC.home> <D5C4D8AE-757B-42E1-9BDF-51D7B84CAD78@kientzle.com> <1363455598.2403.11.camel@Nerz-PC.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2013-03-16 at 18:39 +0100, Lo=EFc BLOT wrote: > Ok, cross compile is done, i have a modular kernel, but same error > appears when i boot. Kernel is blocked at those lines: >=20 > Kernel entry at 0x100100 .. > Kernel args: (null) >=20 >=20 If it doesn't say anything about what FDT it is using before it says Kernel Entry, then you aren't using the latest ubldr code. =20 If it doesn't have the device tree data, it will lock up exactly as you're experiencing (without the device data the kernel doesn't have enough info to even print an error message). A quick way to see if that's the problem is to add to the kernel config: options FDT_DTB_STATIC makeoptions FDT_DTS_FILE=3Dbcm2835-rpi-b.dts -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1363456493.1157.67.camel>