All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
	Agneli <poczt@protonmail.ch>, Paul Fertser <fercerpav@gmail.com>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 04/10] ARM: tegra: Add reg property to Tegra20 EMC table device-tree nodes
Date: Tue, 1 Jun 2021 20:54:38 +0300	[thread overview]
Message-ID: <6e69a991-e5d3-fcad-6b7f-75b9953a8493@gmail.com> (raw)
In-Reply-To: <YLYZHPpjZB9amRBW@orome.fritz.box>

01.06.2021 14:25, Thierry Reding пишет:
>> The TF101 support mostly in a completed state now, we still need to try
>> to figure out why upstream kernel doesn't work using a stock Android
>> bootloader, so far bootloader replacement to u-boot is required.
> I think it's fine to merge support upstream if there is some sort of
> bootloader that it can run with. If that bootloader is open-source like
> U-Boot, the better, but I don't think we need to set the bar as high as
> being able to boot with any available bootloader. There are all sorts
> of reasons why the Android stock bootloader may cause things not to work
> and there's probably no way to get it fixed anyway. It's similarly
> possible that the kernel may need some outlandish quirk to accomodate
> for that breakage and we may not want, or be able, to upstream such
> quirks anyway.

Lots of devices with Android bootloader have odd limitations in regards
to kernel zImage size, this is the main culprit. Nothing we can do about
this in kernel code, but at least we may know how to prepare kernel
config properly to make it working.

> So if you want to pursue making upstream Linux work with the stock
> Android bootloader, that's a fine goal and I won't object, but it's not
> a requirement that I will insist on before merging DTS files.

This is indeed not a blocker for the device-tree. We will probably send
all the transformers together once they all will be ready.

  parent reply	other threads:[~2021-06-01 17:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 20:25 [PATCH v1 00/10] NVIDIA Tegra ARM32 device-tree improvements for 5.14 Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 01/10] ARM: tegra: acer-a500: Improve microphone detection Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 02/10] ARM: tegra: acer-a500: Specify proper voltage for WiFi SDIO bus Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 03/10] ARM: tegra: acer-a500: Bump thermal trips by 10C Dmitry Osipenko
2021-05-14 21:16   ` Michał Mirosław
2021-05-14 22:17     ` Dmitry Osipenko
2021-06-11  9:52     ` Daniel Lezcano
2021-06-12 10:40       ` Dmitry Osipenko
2021-06-12 14:24         ` Daniel Lezcano
2021-06-13  0:25           ` Dmitry Osipenko
2021-06-13 18:19             ` Daniel Lezcano
2021-06-15 12:53               ` Dmitry Osipenko
2021-06-15 13:05                 ` Daniel Lezcano
2021-06-15 13:26                   ` Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 04/10] ARM: tegra: Add reg property to Tegra20 EMC table device-tree nodes Dmitry Osipenko
2021-05-31  9:14   ` Thierry Reding
2021-05-31 20:45     ` Dmitry Osipenko
2021-06-01 11:25       ` Thierry Reding
2021-06-01 17:44         ` Dmitry Osipenko
2021-06-01 17:54         ` Dmitry Osipenko [this message]
2021-05-10 20:25 ` [PATCH v1 05/10] ARM: tegra: wm8903: Fix polarity of headphones-detection GPIO in device-trees Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 06/10] ARM: tegra: paz00: Add CPU thermal zone Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 07/10] ARM: tegra: nexus7: Add i2c-thermtrip node Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 08/10] ARM: tegra: nexus7: Improve thermal zones Dmitry Osipenko
2021-05-10 20:25 ` [PATCH v1 09/10] ARM: tegra: nexus7: Remove monitored-battery property Dmitry Osipenko
2021-05-10 20:26 ` [PATCH v1 10/10] ARM: tegra: nexus7: Correct 3v3 regulator GPIO of PM269 variant Dmitry Osipenko
2021-05-31  8:58 ` [PATCH v1 00/10] NVIDIA Tegra ARM32 device-tree improvements for 5.14 Thierry Reding

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=6e69a991-e5d3-fcad-6b7f-75b9953a8493@gmail.com \
    --to=digetx@gmail.com \
    --cc=clamor95@gmail.com \
    --cc=fercerpav@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=poczt@protonmail.ch \
    --cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.