From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: add support for gcc 8.1
Date: Tue, 22 May 2018 09:46:57 +0200 [thread overview]
Message-ID: <8736yki13i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <trinity-f4d4faec-6692-4477-bdc0-4fdafca1e308-1526973512041@3c-app-mailcom-bs08> (daggs@gmx.com's message of "Tue, 22 May 2018 09:18:32 +0200")
>>>>> "daggs" == daggs <daggs@gmx.com> writes:
Hi,
> afaik, the mainline support for this board lacks proper vpu support.
Correct, but that shouldn't be a blocker for a Buildroot defconfig?
> in addition, due to the patchwork issue, my last bunch of patches of
> mainline support were lost and got ignored so I've decided to stop
> pursuing this matter.
:/
> as said in another mail here, I'm unable to boot the board as I've
> misplaced the ac adapter, I can try looking for it again but it won't
> be until the weekend.
> you said a while ago you have access to such board, if you have time
> to bump the vendor kernel and uboot revs to latest and test if it
> works, maybe this issue can be resolved without dropping support for
> this board.
I don't have an odroidc2, but I know some colleagues of mine do. If
needed, I can try to temporarily borrow one.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-05-22 7:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 10:58 [Buildroot] [PATCH] package/gcc: add support for gcc 8.1 Romain Naour
2018-05-20 10:45 ` Thomas Petazzoni
2018-05-21 15:45 ` Romain Naour
2018-05-21 16:42 ` Romain Naour
2018-05-23 22:08 ` Arnout Vandecappelle
2018-07-30 13:09 ` Thomas Petazzoni
2018-05-21 21:52 ` Peter Korsgaard
2018-05-22 7:02 ` Thomas Petazzoni
2018-05-22 7:18 ` daggs
2018-05-22 7:46 ` Peter Korsgaard [this message]
2018-05-22 8:16 ` Thomas Petazzoni
2018-05-22 22:08 ` Arnout Vandecappelle
2018-05-23 20:19 ` Romain Naour
2018-05-23 21:34 ` Arnout Vandecappelle
2018-05-22 7:13 ` daggs
2018-05-23 8:29 ` Thomas Petazzoni
2018-05-23 20:23 ` Romain Naour
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=8736yki13i.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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