All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Henrik Nordström" <henrik@henriknordstrom.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] Re: [PATCH] video: add cfb console driver for sunxi
Date: Mon, 04 Aug 2014 17:31:36 +0200	[thread overview]
Message-ID: <1407166296.4733.8.camel@localhost> (raw)
In-Reply-To: <20140804150500.GA13286@skynet.be>

m?n 2014-08-04 klockan 17:05 +0200 skrev Luc Verhaegen:
> But... What do we do when u-boot sets up cfb, without setting up a
> simplefb node in the dt. Or what do we do when a simplefb node is set 
> up, but no simplefb code is included in the kernel? Well, we then either 
> need to claim the clocks, and make sure that nothing else touches the 
> memory, or we need to cleanly disable the display engine. But which do 
> we choose, do we keep the u-boot output forever, or do we sync off when 
> the kernel starts?

And what happens if we simply ignore it? Is there a risk of anything
burning beyond software repair? If not, ignore it. There is no need to
support all incompatible mixes even if it means some people will see
strange fireworks on their screens when not following the software
requirements.

It's really no different from booting a kernel with wrong dt, or using a
u-boot with wrong DRAM settings etc. An incompatible mix which is not
meant to function properly.

If you use a u-boot with this framebuffer support then you must also
either use a kernel which supports being booted in such state, or make
sure u-boot shuts things off before handing over to the kernel.

If we can handle the situation gracefully in the kernel then fine, but
it's by no means required, or even desired to spend any effort or even
any serious thoughts on before compatible setups works.

Regards
Henrik

  reply	other threads:[~2014-08-04 15:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 16:14 [U-Boot] [PATCH] video: add cfb console driver for sunxi Luc Verhaegen
2014-08-04  8:39 ` Hans de Goede
2014-08-04 15:05   ` Luc Verhaegen
2014-08-04 15:31     ` Henrik Nordström [this message]
2014-08-04 16:53       ` [U-Boot] [linux-sunxi] " Michal Suchanek
2014-08-04 21:26         ` Henrik Nordström
2014-08-04 17:28       ` Luc Verhaegen
2014-08-04 22:10         ` Henrik Nordström
2014-08-05 20:55           ` Maxime Ripard
2014-08-05 21:03     ` Maxime Ripard
2014-08-05 21:37       ` Michal Suchanek
2014-08-06  7:24         ` [U-Boot] [linux-sunxi] " Koen Kooi
2014-08-06 11:10           ` Hans de Goede
2014-08-06 12:21         ` [U-Boot] [linux-sunxi] " Maxime Ripard
2014-08-05 11:56 ` [U-Boot] " Hans de Goede
2014-08-05 20:47   ` [U-Boot] [linux-sunxi] " Maxime Ripard
2014-08-06 11:40   ` [U-Boot] " Luc Verhaegen
2014-08-07  9:28     ` Hans de Goede

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=1407166296.4733.8.camel@localhost \
    --to=henrik@henriknordstrom.net \
    --cc=u-boot@lists.denx.de \
    /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.