#
✕ nick:tophevich[m]
#asahi · 2021-09-15 16:49
tophevich[m]*were
#asahi · 2021-09-15 16:49
tophevich[m]Timesink where mostly the emojis I guess?
#asahi · 2021-09-15 16:48
tophevich[m]well worth it (from the entertaining side of things)
#asahi · 2021-09-15 16:40
tophevich[m]I think we are in luck, I just found the ones from last year so they keep those aswell.
#asahi · 2021-09-15 16:38
tophevich[m]alyssa: this is because it is still streaming, and you can go rewind in youtube livestreams. But AFAIK they can remove the stream afterwards (and sadly that happens for conferences too often). Hopefully the keep the stream vod, and in addition publish a vod for each talk seperately.
#asahi · 2021-09-15 16:20
tophevich[m]it's the third talk i think
#asahi · 2021-09-15 16:20
tophevich[m]https://www.youtube.com/watch?v=uTZISTjqy9Q
#asahi · 2021-09-15 15:46
tophevich[m]alyssa: Sadly I couldn't follow your talk live, thus only commenting now, but it was very informative and entertaining at the same time, nice job! Nice touch that you were able to go meta and show it from linux running on an m1 mac mini.
#asahi · 2021-09-15 10:11
tophevich[m]wow, double the streams double the fun :D
#asahi · 2021-08-29 15:17
tophevich[m](handing out contact info to a manager that will tell you how to do it)
#asahi · 2021-08-29 15:17
tophevich[m]sven: not with that attitude :P
#asahi · 2021-08-18 19:33
tophevich[m]FireFox317: which tomorrow do you mean, his or yours. His is in ~19 1/2 hours as it is 04:33 am in Tokyo
#asahi · 2021-08-18 15:42
tophevich[m]NYRA Linux (Arch btw.)
#asahi · 2021-08-18 15:41
tophevich[m]And it will be called NYRA (Not Yet Ripe Asahi) :P
#asahi · 2021-08-16 10:51
tophevich[m](omg, my sentences always get so jumbled, I'm a realy bad multi-tasker, but I keep trying and failing at it anyways ... I hate that it gives the sence of being oh so productive while in reality it is quite the opposite :( ... sorry in advance if you feel like you are having a stroke while reading my word salat)
#asahi · 2021-08-16 10:47
tophevich[m]marcan: it feels spammy in here, and it is quite disconnected if ppl don't know that one writes in response to something happening on stream, #asahi-streams or something along those lines would might be nice. Can also be used by others while like alyssa ...
#asahi · 2021-08-16 10:24
tophevich[m]https://twitter.com/marcan42/status/1423214292145299457
#asahi · 2021-08-16 10:00
tophevich[m]landscape15: Without realy answering your question directly, AFAIK nobody would recommend Asahi for production use in any way, shape or form at the moment. You can use it for testing/hacking purposes with the explicit knowledge that it can break things, like currupt your drive.
#asahi · 2021-08-15 16:53
tophevich[m](xkcd reference detected: https://xkcd.com/927/)
#asahi · 2021-08-15 11:29
tophevich[m]sorry, that was the last of it ...
#asahi · 2021-08-15 11:29
tophevich[m]Third party vendors also sell this as a feature to ISPs. It's a sepcial feature that you can't take the 3rd party product/service with you. If you buy it directly, you can use it everywhere. But if you buy it OTT via your ISP, it is locked to your ISP account, and by explicit design you can't (read: are not allowed to) transfer, yay!
#asahi · 2021-08-15 11:20
tophevich[m](no I'm not bitter)
#asahi · 2021-08-15 11:19
tophevich[m]read VAS (value added services) as laying stones in the way out of the gardn to recude churn -> make it painful as possible to leave
#asahi · 2021-08-15 11:14
tophevich[m]kettenis_: never use anything from your ISP but the internet (I'm in the industry, we (telecoms) only want to bundle you in our products in a bad way to keep you between a rock and a hard place when trying to leave for a less worse service)
#asahi · 2021-08-14 17:32
tophevich[m]gz to all :)
#asahi · 2021-08-14 12:30
tophevich[m]marcan: depending on what you decide you can use or close this one: https://github.com/AsahiLinux/AsahiLinux.github.io/pull/16
#asahi · 2021-08-14 11:51
tophevich[m]marcan: hm, ok but shouldn't be the explanation and the source be in sync. I wouldn't expect ppl using those to gather them only from the article but to check out the repo.
#asahi · 2021-08-14 11:30
tophevich[m]/!\ /!\ /!\ the deep-links in the article to github files could become a problem in the not too distant future. I think it would be a good idea to use a commit specific link, otherwise they could become obsolete in "next weeks" refactoring and you'd get a 404.
#asahi · 2021-08-14 11:09
tophevich[m](updated the wiki as a direct result of the article glossary discussion, hope that's ok)
#asahi · 2021-08-14 10:58
tophevich[m]only the glossary mentions the IOMMU without expanding on it :D
#asahi · 2021-08-14 10:57
tophevich[m]:j_ey ok, I guess it would be a good idea to link to it as part of the article. And it matches realy nicely as IOMMU is not in the glossary but is "expanded" in the article :D
#asahi · 2021-08-14 10:54
tophevich[m]"and metadata fles" -> files
#asahi · 2021-08-14 10:52
tophevich[m]"directory structuers and files" -> structures
#asahi · 2021-08-14 10:52
tophevich[m]sven: I know that but if you don't know IOMMU, do you know DART?
#asahi · 2021-08-14 10:51
tophevich[m]"and initalizing endpoints" -> initializing
#asahi · 2021-08-14 10:48
tophevich[m]One example is "Sven has been dutifully working on the Linux driver for DART, the M1’s IOMMU (I/O Memory Management Unit)"
#asahi · 2021-08-14 10:47
tophevich[m]At some points you go into explaining some of the acronyms, but for others you do not. It always depends on what you have in mind for your target audience, but you could do it more often at the first mention or just add a glossary?
#asahi · 2021-08-14 10:38
tophevich[m]"Apple decided to throw a twist into it" feels like two phrases merged, i think a simple "Apple decided to give it a twist" sounds more "native". You can throw a wrench into "the gears" but a you can't trhow a twist, the twist itself is the action.
#asahi · 2021-08-14 10:31
tophevich[m](hm ... looks like I should proof read my proposals)
#asahi · 2021-08-14 10:30
tophevich[m]execution, without a reboot."
#asahi · 2021-08-14 10:30
tophevich[m]I would move the partially written in python part to the second sentenace. -> "Since the hypervisor is built on m1n1, it works together with Python code running on a separate host machine. Effectively, the Python host can “puppeteer” the M1 and its guest OS remotely. To allow us a very fast test cycle, the hypervisor itself is partially written in Python, which allowes even updating parts of the hypervisor itself live during guest
#asahi · 2021-08-14 10:30
tophevich[m]"Since the hypervisor is built on m1n1, it works together with Python code running on a separate host machine. Effectively, the Python host can “puppeteer” the M1 and its guest OS remotely, and the hypervisor itself is partially written in Python! This allows us to have a very fast test cycle, even updating parts of the hypervisor itself live during guest execution, without a reboot."
#asahi · 2021-08-14 10:22
tophevich[m]^
#asahi · 2021-08-14 10:21
tophevich[m]"This has also gotten members of the kernel community interested in our project; having a good relationionship" the transition there feels akward to me, I felt I missed a step, maybe "This has also gotten members of the kernel community interested in our project, and as mentioned previously having a good relationionship"
#asahi · 2021-08-14 10:12
tophevich[m];)
#asahi · 2021-08-14 10:12
tophevich[m]I'm not a native speaker, and my duckduckgo foo level didn't help me confirming it, but in the first paragraph you have the "so strap on for a biger update this time". I feel like the phrase is "so strap in" instead of "so strap on"
#asahi · 2021-08-12 18:18
tophevich[m]ok, I feel silly to create that PR, but I guess it helps to get my feet wet
#asahi · 2021-08-12 18:04
tophevich[m]contribution guidlines are the same for all projects under the AsahiLinux umbrella right?
#asahi · 2021-08-12 18:01
tophevich[m]*an
#asahi · 2021-08-12 18:01
tophevich[m]yeah, I just had a look in the irclogs, but with a asterix as prefix

plus ›