linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: BBB with v5.7-rc5
Date: Tue, 12 May 2020 16:55:39 +0300	[thread overview]
Message-ID: <878shx45r8.fsf@kernel.org> (raw)
In-Reply-To: <20200512134648.GD37466@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]


Hi,

Tony Lindgren <tony@atomide.com> writes:
>> 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.

yeah, loading all the data from sd card. I am, however, using the u-boot
that came with the board.

> 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.

cool, I'll try earlycon, then.

> There's "[PATCH net v4] net: ethernet: ti: Remove TI_CPTS_MOD workaround"
> being discussed too for the cpsw regression.

Thanks

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2020-05-12 13:55 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
2020-05-12 13:52       ` Felipe Balbi
2020-05-12 13:55     ` Felipe Balbi [this message]
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=878shx45r8.fsf@kernel.org \
    --to=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).