linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@kernel.org>
Cc: <linux-omap@vger.kernel.org>
Subject: Re: BBB with v5.7-rc5
Date: Tue, 12 May 2020 08:41:41 -0500	[thread overview]
Message-ID: <586c35cf-80f1-6922-a46b-a6fce312e83c@ti.com> (raw)
In-Reply-To: <20200512134648.GD37466@atomide.com>

Felipe

On 5/12/20 8:46 AM, Tony Lindgren wrote:
> Hi,
>
> * Felipe Balbi <balbi@kernel.org> [200512 13:41]:
>> Hi,
>>
>> Felipe Balbi <balbi@kernel.org> writes:
>>> what's the trick to get BBB to boot recent kernels nowadays? :-p
>>>
>>> I'm using omap2plus_defconfig without CPSW (doesn't link otherwise) with
>>> GCC 10.1.0 (I'll try an older version shortly). Cmdline is the usual
>> same result with 9.2. Nothing from low level debug either.
> Maybe check you have a current dtb file? The older dtb files may not
> have all the needed data.

I have been using the latest uBoot, DTBs and kernel with no issue 
(except CPSW).

I have booted the BBB and a BBG.  9.2 gcc compiler

> Also you probably want to add "earlycon" to your your kernel cmdline
> and then you have early output from CONFIG_SERIAL_EARLYCON=y as long
> as there's a chosen entry for the device uart. So no need to enable
> DEBUG_LL in most cases.
>
> There's "[PATCH net v4] net: ethernet: ti: Remove TI_CPTS_MOD workaround"
> being discussed too for the cpsw regression.

This is a build dependency issue.

Dan

> Regards,
>
> Tony
>
>
>

  reply	other threads:[~2020-05-12 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 11:10 BBB with v5.7-rc5 Felipe Balbi
2020-05-12 13:40 ` Felipe Balbi
2020-05-12 13:46   ` Tony Lindgren
2020-05-12 13:41     ` Dan Murphy [this message]
2020-05-12 13:52       ` Felipe Balbi
2020-05-12 13:55     ` Felipe Balbi
2020-05-12 15:33       ` Felipe Balbi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=586c35cf-80f1-6922-a46b-a6fce312e83c@ti.com \
    --to=dmurphy@ti.com \
    --cc=balbi@kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).