On Sat, 26 Jan 2013, Felipe Balbi wrote:
> Hi,
>
> On Sat, Jan 26, 2013 at 08:40:07AM +, Paul Walmsley wrote:
> > Boot tests:
> >
> > * am335xbone: hangs after "Starting kernel"
> > - Cause unknown; may be due to CONFIG_EARLY_PRINTK=y?
> > - http://www.mail-archive.com/linux-omap@vger.ke
Hi,
On Mon, Jan 28, 2013 at 03:40:09PM +0100, AnilKumar, Chimata wrote:
> On Mon, Jan 28, 2013 at 17:48:49, Mohammed, Afzal wrote:
> > Hi Felipe,
> >
> > On Mon, Jan 28, 2013 at 17:46:35, Balbi, Felipe wrote:
> >
> > > didn't help :-s
> >
> > Hands up :(
>
> Hi Felipe,
>
> Could you please tr
On Mon, Jan 28, 2013 at 17:48:49, Mohammed, Afzal wrote:
> Hi Felipe,
>
> On Mon, Jan 28, 2013 at 17:46:35, Balbi, Felipe wrote:
>
> > didn't help :-s
>
> Hands up :(
Hi Felipe,
Could you please try with any of these options?
1. Change/add mem=512M (should be same value as u-boot printed RAM
Hi Felipe,
On Mon, Jan 28, 2013 at 17:46:35, Balbi, Felipe wrote:
> didn't help :-s
Hands up :(
Regards
Afzal
Hi,
On Mon, Jan 28, 2013 at 12:46:21PM +0100, Mohammed, Afzal wrote:
> Hi Felipe,
>
> On Mon, Jan 28, 2013 at 17:08:19, Balbi, Felipe wrote:
>
> > seems to be a bug with __unflatten_device_tree()...
>
> > U-Boot# bootm 0x8020 - 0x80f8
>
> Try loading dtb at a different address, I do,
>
Hi Felipe,
On Mon, Jan 28, 2013 at 17:08:19, Balbi, Felipe wrote:
> seems to be a bug with __unflatten_device_tree()...
> U-Boot# bootm 0x8020 - 0x80f8
Try loading dtb at a different address, I do,
bootm 8100 - 8200
Regards
Afzal
On 28/01/13 10:34, Mohammed, Afzal wrote:
> Hi,
>
> On Sat, Jan 26, 2013 at 14:16:04, Balbi, Felipe wrote:
>> On Sat, Jan 26, 2013 at 08:40:07AM +, Paul Walmsley wrote:
>
>>> * am335xbone: hangs after "Starting kernel"
>>> - Cause unknown; may be due to CONFIG_EARLY_PRINTK=y?
>>> - http:/
Hi,
On Mon, Jan 28, 2013 at 11:34:15AM +0100, Mohammed, Afzal wrote:
> Hi,
>
> On Sat, Jan 26, 2013 at 14:16:04, Balbi, Felipe wrote:
> > On Sat, Jan 26, 2013 at 08:40:07AM +, Paul Walmsley wrote:
>
> > > * am335xbone: hangs after "Starting kernel"
> > > - Cause unknown; may be due to CONF
Hi,
On Mon, Jan 28, 2013 at 11:55:20AM +0100, Mohammed, Afzal wrote:
> Hi Felipe,
>
> On Mon, Jan 28, 2013 at 16:17:52, Balbi, Felipe wrote:
>
> > will try your patch, but are you using Beagle Bone white or black ? I
> > should've made it clear I'm using beagle bone black.
>
> Hmm.., I am using
Hi Felipe,
On Mon, Jan 28, 2013 at 16:17:52, Balbi, Felipe wrote:
> will try your patch, but are you using Beagle Bone white or black ? I
> should've made it clear I'm using beagle bone black.
Hmm.., I am using white, have never tried on black.
Regards
Afzal
N�r��yb�X��ǧv�^�){.n�+
Hi,
On Mon, Jan 28, 2013 at 11:34:15AM +0100, Mohammed, Afzal wrote:
> Hi,
>
> On Sat, Jan 26, 2013 at 14:16:04, Balbi, Felipe wrote:
> > On Sat, Jan 26, 2013 at 08:40:07AM +, Paul Walmsley wrote:
>
> > > * am335xbone: hangs after "Starting kernel"
> > > - Cause unknown; may be due to CONF
Hi,
On Sat, Jan 26, 2013 at 14:16:04, Balbi, Felipe wrote:
> On Sat, Jan 26, 2013 at 08:40:07AM +, Paul Walmsley wrote:
> > * am335xbone: hangs after "Starting kernel"
> > - Cause unknown; may be due to CONFIG_EARLY_PRINTK=y?
> > - http://www.mail-archive.com/linux-omap@vger.kernel.org/ms
Hi,
On Sat, Jan 26, 2013 at 08:40:07AM +, Paul Walmsley wrote:
> Boot tests:
>
> * am335xbone: hangs after "Starting kernel"
> - Cause unknown; may be due to CONFIG_EARLY_PRINTK=y?
> - http://www.mail-archive.com/linux-omap@vger.kernel.org/msg82297.html
> - http://marc.info/?l=linux-oma
13 matches
Mail list logo
