From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] hackathon writeup
Date: Fri, 19 Aug 2022 04:02:54 +0200 [thread overview]
Message-ID: <C3B69925CCEA9BA200C7A58CCC6DE24F@wopr.sciops.net> (raw)
In-Reply-To: <Yv7tRPQJayjspyng@wopr>
> The X230 line in the sand is one we hashed out in IRC back when there
> was much confusion regarding which SKUs Intel blessed with which
> features at which times. There might be the odd *20-series or older
> machine that managed to get a 'good' processor, but the X230 is the
> first generation that *for sure* has the features. The further back in
> time you go, the more of a crap shoot it is. I tend to just claim X230
> as the earliest as it greatly simplifies the issue.
I see, that's what confused me. Thanks!
Cheers,
qwx
next prev parent reply other threads:[~2022-08-19 2:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 3:27 ori
2022-08-18 22:37 ` Stuart Morrow
2022-08-18 22:52 ` Stuart Morrow
2022-08-18 23:09 ` Stanley Lieber
2022-08-18 23:32 ` Stuart Morrow
2022-08-18 23:11 ` Kurt H Maier
2022-08-18 23:33 ` Stuart Morrow
2022-08-18 23:55 ` Jacob Moody
2022-08-19 0:05 ` ori
2022-10-14 5:45 ` 9p2000.ix (Was Re: [9front] hackathon writeup) unobe
2022-08-19 11:34 ` [9front] hackathon writeup Stuart Morrow
2022-08-19 13:21 ` Jacob Moody
2022-08-18 23:04 ` Stuart Morrow
2022-08-18 23:24 ` ori
2022-08-18 23:37 ` Stuart Morrow
2022-08-18 23:43 ` ori
2022-08-19 0:02 ` Kurt H Maier
2022-08-19 0:23 ` qwx
2022-08-19 1:54 ` Kurt H Maier
2022-08-19 2:02 ` qwx [this message]
2022-08-19 7:08 ` Steve Simon
2022-08-20 1:38 ` Xiao-Yong Jin
2022-08-20 3:57 ` ori
2022-08-19 19:52 ` Thaddeus Woskowiak
2022-08-19 21:13 ` David Arnold
2022-08-19 19:11 ` Aram Hăvărneanu
2022-08-19 20:40 ` Stuart Morrow
2022-08-20 13:14 ` Stuart Morrow
2022-08-22 17:54 ` Aram Hăvărneanu
2022-08-22 17:56 ` Kurt H Maier
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=C3B69925CCEA9BA200C7A58CCC6DE24F@wopr.sciops.net \
--to=qwx@sciops.net \
--cc=9front@9front.org \
/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;
as well as URLs for NNTP newsgroup(s).