public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: Machine id hack to prevent loading buggy sunxi-3.4 kernels
Date: Mon, 02 Mar 2015 09:40:26 +0100	[thread overview]
Message-ID: <54F421FA.4010606@redhat.com> (raw)
In-Reply-To: <1425140296.32223.36.camel@hellion.org.uk>

Hi,

On 28-02-15 17:18, Ian Campbell wrote:
> On Sat, 2015-02-21 at 11:49 +0100, Hans de Goede wrote:
>> On 21-02-15 11:26, Ian Campbell wrote:
>>> Speaking of which, if someone were to identify a suitable set of
>>> simple-fb backports for 3.16 and they are reasonably self contained I'd
>>> happily backport them to the kenrel which is going to be in the next
>>> Debian release too...
>>
>> You will need all patches by me and by "Luc Verhaegen" from here:
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/video/fbdev/simplefb.c
>>
>> As well as these dts patches:
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=5790d4ee1e425fefef0e012d1415c25baeb9dae8
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=d501841fc42a97a8b69449135eadf6e9c4589a87
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e53a8b2201384ee1a2cfd1609c9ffdf951b041a1
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=8efc5c2be5b29f7ceec83bb471da81690273e141
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=678e75d
>
> I inserted this one here so the following stuff would cherry-pick ok, I
> think that was the right thing to do.

Yes it was, sorry for overlooking that one.

>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=a9f8cda32a3acc3150755fe973f7fa1867a7a5d6
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=8cedd6628472aa2d8f2f54dfcc36633e46a59db8
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=fd18c7eac03540654abdbfedd52e6dfb3718b489
>>
>> Those combined with a new enough u-boot should get you video output on most devices
>> supported in upstream u-boot.
>
> Indeed, this gets me graphics on my Cubietruck at least.

Cool.

Regards,

Hans

  parent reply	other threads:[~2015-03-02  8:40 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
2015-03-04 15:17                     ` Siarhei Siamashka
2015-03-04 21:37                       ` [U-Boot] [linux-sunxi] " Michal Suchanek
2015-03-02  8:40                 ` Hans de Goede [this message]
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=54F421FA.4010606@redhat.com \
    --to=hdegoede@redhat.com \
    --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