mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "Sascha Hauer" <sha@pengutronix.de>,
	barebox@lists.infradead.org, "Leonard Göhrs" <lgo@pengutronix.de>
Subject: Re: barebox.org browser demo uses barebox-v2022.02
Date: Mon, 27 Nov 2023 00:21:54 +0300	[thread overview]
Message-ID: <20231127002154.fb6e1eddc6710cc6bbbdf76d@gmail.com> (raw)
In-Reply-To: <abeb91af-f3dc-552d-9889-f250e7dd6a3f@pengutronix.de>

On Fri, 24 Nov 2023 08:22:27 +0100
Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:

Hi Ahmad!

> On 24.11.23 07:57, Ahmad Fatoum wrote:
> > Hi Antony,
> > 
> > On 06.10.23 12:24, Ahmad Fatoum wrote:
> >> Hello Antony,
> >>
> >> On 30.09.23 11:17, Antony Pavlov wrote:
> >>> Hi Ahmad!
> >>>
> >>> barebox browser demo (https://www.barebox.org/jsbarebox/) looks very impressive.
> >>> But it uses old barebox-v2022.02. Could you update it please.
> >>
> >> You're right. I will try to find some time to update it. Eventually, I'd like
> >> the tutorial to actually boot a kernel as well and have at github.com/barebox/
> >> a separate project (maybe Yocto-based?) that builds all the necessary artifacts,
> >> but there's still some work to be done until we can do that...
> > 
> > I have updated it to v2023.10.0. Sorry for the delay.
> > To use it, you'll have to clear browser cache for the site.
> > 
> > If you know how one could force an update for cache older than a given time,
> > I'd be happy to add that.
> 
> We have migrated the barebox.org host a while back and Leonard tells me that
> the HTTP header now sports the correct Last-Modified timestamp, so manual
> cache clearing shouldn't be necessary anymore to force a new version.
> 
> Can you confirm?

Thanks for updating demo!

I have no browser cache issue. The browser demo works perfectly!

I see only one thing that can confuse a new user: the blue uncommented toggle button is used for
selecting demo mode "just console" (default) or "doom autoboot". I propose to add more instruction
on running Doom or even change toggle button to radio buttons with appropriate comments.

> > 
> >>
> >>>
> >>> As barebox browser demo runs on top of RISC-V machine can we add RISC-V mention
> >>> to barebox.org/index.html page?
> >>
> >> I guess. Sascha, is that ok for you?
> > 
> > I went ahead and replaced PowerPC with RISC-V. Sascha, let me know if that's
> > not ok.
> > 
> > Cheers,
> > Ahmad
> > 
> >>
> >> Cheers,
> >> Ahmad

-- 
Best regards,
  Antony Pavlov



  reply	other threads:[~2023-11-26 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-30  9:17 Antony Pavlov
2023-10-06 10:24 ` Ahmad Fatoum
2023-11-24  6:57   ` Ahmad Fatoum
2023-11-24  7:22     ` Ahmad Fatoum
2023-11-26 21:21       ` Antony Pavlov [this message]
2024-01-02  8:48         ` Ahmad Fatoum
2024-01-30  9:49           ` Ahmad Fatoum

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=20231127002154.fb6e1eddc6710cc6bbbdf76d@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=lgo@pengutronix.de \
    --cc=sha@pengutronix.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