Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] some comprehensive arm64 w/cake results
Date: Thu, 28 Sep 2023 15:27:09 +0200	[thread overview]
Message-ID: <B1098CE9-AFEA-4B49-94AB-F423BBBC564A@gmx.de> (raw)
In-Reply-To: <r9268rp5-8sr8-262s-7975-q68q6434sp6s@ynat.uz>



> On Sep 28, 2023, at 15:19, David Lang <david@lang.hm> wrote:
> 
> On Thu, 28 Sep 2023, Sebastian Moeller via Cake wrote:
> 
>> P.S.: I am tempted, but will likely wait until they are available in quantity and hope that the street price comes down a bit before getting one ;)
> 
> They aren't available at all yet, and it's not clear when they will be available.

	The announcement was end of October, but I think I could pre-order right now if I was feeling an urge. You are right though, announced != available or delivered.

Regards
	Sebastian

P.S.: I have a pi400 in use as "desktop" for my oldest kid, this is close to be actually generally usable, I would guess that changing a potential p500 from the pi400's 4GB to 8 GB together with the other imprivements the 5 brings might push it over the threshold into the truly useful category. Which probably means that either a potential pi500 will come late and probably with only 4 GB, but let's see how this works out now that the supply situation is less problematic.
And I understand that there are other capable ARM based SoCs for homerouter/desktop duty, I just happen ot have a soft spot for the raspberry project ;)

> 
> David Lang


  reply	other threads:[~2023-09-28 13:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  1:05 Dave Taht
2023-09-18  1:25 ` Jonathan Morton
2023-09-18 16:57 ` David P. Reed
2023-09-18 19:50 ` dave seddon
2023-09-18 20:24   ` David P. Reed
2023-09-18 22:07     ` Jonathan Morton
2023-09-28 11:44       ` Jonathan Morton
2023-09-28 12:15         ` Sebastian Moeller
2023-09-28 12:33           ` Jonathan Morton
2023-09-28 12:56             ` David Lang
2023-09-28 13:08             ` Sebastian Moeller
2023-09-28 13:19               ` David Lang
2023-09-28 13:27                 ` Sebastian Moeller [this message]
2023-10-13 15:59                   ` dave seddon
2023-10-13 17:25                     ` dave seddon
2023-10-15 15:11                       ` dave seddon
2023-10-15 15:52                         ` Sebastian Moeller
2023-10-15 16:24                           ` dave seddon
2023-10-15 20:29                             ` David P. Reed
2023-10-16  3:52                               ` Jonathan Morton
2023-10-15 15:53                         ` Dave Taht
2023-10-23 20:31                         ` dave seddon
2023-10-23 20:35                           ` dave seddon
2023-10-24 16:27                           ` dave seddon
2023-10-24 21:35                             ` dave seddon
2023-10-24 22:06                               ` Dave Taht
2023-09-18 22:13   ` Jonathan Morton
2023-09-18 22:52     ` dave seddon
2023-09-18 23:08       ` Jonathan Morton

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B1098CE9-AFEA-4B49-94AB-F423BBBC564A@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=david@lang.hm \
    /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