public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ian Campbell <ijc+uboot@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: Machine id hack to prevent loading buggy sunxi-3.4 kernels
Date: Tue, 03 Mar 2015 08:17:56 +0000	[thread overview]
Message-ID: <1425370676.12103.10.camel@hellion.org.uk> (raw)
In-Reply-To: <20150302000728.40e05128@i7>

On Mon, 2015-03-02 at 00:07 +0200, Siarhei Siamashka wrote:
> Just one suggestion. It would be really nice if the Debian installer
> could present itself on all the available consoles, so that the user
> can use any of them for providing input to the installer.

There is some reason why d-i doesn't do this by default. I think it's to
do with bricking or otherwise interfering with devices attached to
serial ports e.g I think Braille terminals were mentioned, but I suppose
any random device might not like getting random strings of characters.

> Otherwise there will be a need to provide separate SD card images for
> the HDMI console (for the Raspberry Pi wannable competitors), the UART
> serial console (A10/A20 development boards without HDMI) and the USB OTG
> serial gadget console (for the tablets without HDMI). Instead of just
> having only a single SD card image to handle everything automatically.

I've backported DT the /chosen/stdout-path support to the kernel a while
ago and I thought together with Hans' u-boot patches to populate this
field with the right thing then console selection would Just Work(tm).

At least for HDMI vs. UART since I'm not quite sure how the OTG gadget
console is presented to Linux and whether it falls into this stuff
correctly.

> Oh, and one more suggestion. The SD card partitioning could be also
> improved in order to make it more user friendly. Right now the user may
> be confused by the Debian installer regarding what to do with the
> existing partition on the SD card (yes, it can be safely erased since
> the installer is running from RAM and does not rely on the data from
> that partition anymore).

I leave this one to Karsten who looks after the SD card images.

Ian.

  reply	other threads:[~2015-03-03  8:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  8:08 [U-Boot] [PATCH] sunxi: Machine id hack to prevent loading buggy sunxi-3.4 kernels Siarhei Siamashka
2015-02-20  9:19 ` Hans de Goede
2015-02-20 10:36   ` Siarhei Siamashka
2015-02-20 14:11     ` Hans de Goede
2015-02-20 18:33       ` Siarhei Siamashka
2015-02-21  9:41         ` Hans de Goede
2015-02-21 10:26           ` Ian Campbell
2015-02-21 10:49             ` Hans de Goede
2015-02-21 13:11               ` Siarhei Siamashka
2015-02-21 14:34                 ` Hans de Goede
2015-02-28 16:18               ` Ian Campbell
2015-03-01 22:07                 ` Siarhei Siamashka
2015-03-03  8:17                   ` Ian Campbell [this message]
2015-03-04 15:17                     ` Siarhei Siamashka
2015-03-04 21:37                       ` [U-Boot] [linux-sunxi] " Michal Suchanek
2015-03-02  8:40                 ` [U-Boot] " Hans de Goede
2015-09-25 18:33           ` [U-Boot] Improving DRAM settings for Allwinner A10/A13/A20 devices Siarhei Siamashka

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=1425370676.12103.10.camel@hellion.org.uk \
    --to=ijc+uboot@hellion.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox