From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] brcmrpi_quick defconfig
Date: Wed, 31 Oct 2018 19:21:36 +0100 [thread overview]
Message-ID: <20181031182136.GL28575@scaer> (raw)
In-Reply-To: <CAHS=Uo_1tyUbfxk0_SvWMLNGD3JonDfAVUq=x5gwK4Zv5hpcwQ@mail.gmail.com>
Michael,
Please, do not directly contact the individuals to ask questions. This
is a community project, and as such you should ask questions on the
official support channels, i.e. the mailing list or the IRC channel.
On 2018-10-31 17:34 +0100, Michael Toldo spake thusly:
> Just found this: [1]https://git.busybox.net/buildroot/commit/?id=a10d2c5c40f361eef777a1a7fa0fd88b67efa825
> Could you please give me a quick hint how to apply the brcmrpi_quick defconfig in a buildroot setup?
This is a 5-year old commit; things have changed since then, and there
is no longer a bcmrpi_quick defconfig in the rpi kernel fork. Only the
bcmrpi_defconfig still exists, and that is what Buildroot uses.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next parent reply other threads:[~2018-10-31 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHS=Uo_1tyUbfxk0_SvWMLNGD3JonDfAVUq=x5gwK4Zv5hpcwQ@mail.gmail.com>
2018-10-31 18:21 ` Yann E. MORIN [this message]
2018-10-31 19:32 ` [Buildroot] brcmrpi_quick defconfig Michael Toldo
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=20181031182136.GL28575@scaer \
--to=yann.morin.1998@free.fr \
--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 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.