From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [u-boot-test-hooks PATCH 7/7] ellesmere: Add qemu rules
Date: Sun, 31 Oct 2021 12:57:18 -0400 [thread overview]
Message-ID: <20211031165718.GU24579@bill-the-cat> (raw)
In-Reply-To: <20211030182539.1371361-7-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On Sat, Oct 30, 2021 at 12:25:39PM -0600, Simon Glass wrote:
> Add some symlinks so that qemu can be used on ellesmere.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> bin/ellesmere/conf.qemu_arm_na | 1 +
> bin/ellesmere/conf.qemu_arm_spl_na | 1 +
> 2 files changed, 2 insertions(+)
> create mode 120000 bin/ellesmere/conf.qemu_arm_na
> create mode 120000 bin/ellesmere/conf.qemu_arm_spl_na
Alright, so I think the best use of the public u-boot-test-hooks is to
have first public CI used scripts (aka everything in {bin,py}/travis-ci)
and then we should move to having a reference directory. It's not
useful to everyone for example to have symlinks like these here, for
your lab. But it is very useful to have things like
bin/kea/conf.orangepi_pc_sjg-opi_pc which I used locally the other day
to make bin/bill-the-cat/conf.pine64_plus_na and I think everyone would
benefit from something like
bin/references/conf.sunxi_with_sdwire_and_digital-loggers so that anyone
else can figure out how to plumb in their own sunxi platform with sdwire
and then whatever reference they also need for power control, if not a
digital-loggers type "curl" solution.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-10-31 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 18:25 [u-boot-test-hooks PATCH 1/7] travis-ci: Add qemu_arm_spl board Simon Glass
2021-10-30 18:25 ` [u-boot-test-hooks PATCH 2/7] sdwire: Tidy up the mount script Simon Glass
2021-11-11 17:37 ` Tom Rini
2021-10-30 18:25 ` [u-boot-test-hooks PATCH 3/7] rpi3: Tweak the grep pattern Simon Glass
2021-11-11 17:37 ` Tom Rini
2021-10-30 18:25 ` [u-boot-test-hooks PATCH 4/7] Add wait_raw_device for common code Simon Glass
2021-11-11 17:37 ` Tom Rini
2021-10-30 18:25 ` [u-boot-test-hooks PATCH 5/7] Update sdwire script to wait for umount Simon Glass
2021-11-11 17:37 ` Tom Rini
2021-10-30 18:25 ` [u-boot-test-hooks PATCH 6/7] kea: Add samus Simon Glass
2021-11-11 17:38 ` Tom Rini
2021-10-30 18:25 ` [u-boot-test-hooks PATCH 7/7] ellesmere: Add qemu rules Simon Glass
2021-10-31 16:57 ` Tom Rini [this message]
2021-10-31 18:22 ` Simon Glass
2021-10-31 19:15 ` Tom Rini
2021-11-03 15:23 ` [u-boot-test-hooks PATCH 1/7] travis-ci: Add qemu_arm_spl board Tuomas Tynkkynen
2021-11-11 17:37 ` Tom Rini
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=20211031165718.GU24579@bill-the-cat \
--to=trini@konsulko.com \
--cc=sjg@chromium.org \
--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