08:34 <DocScrutinizer05> wpwrak: simmux WP, monsostabel MV doesn't need to be retriggerable, we got the OR gate for that

08:35 <DocScrutinizer05> re the note on right side

08:37 <DocScrutinizer05> when NNV is retriggerable, we could just use the output directly for the two gates in CD_A/B

08:37 <DocScrutinizer05> MMV*

08:39 <DocScrutinizer05> thinking about it, we could do that anyway, no matter what

08:43 <DocScrutinizer05> MMV out 0->1 asserts CD 'removal', 1->0 triggers D-Latch, MMV trigger input is irrelevant

08:44 <DocScrutinizer05> one gate less \o/

19:22 <wpwrak> DocScrutinizer05: now i can see what you're up to :) https://neo900.org/stuff/paste/kohDooC3

19:23 <DocScrutinizer05> hm?

19:23 <wpwrak> try it :)

19:23 <DocScrutinizer05> ooh

19:24 <DocScrutinizer05> nah, way too "dangerous", too many git commands that may fail resp cause unexpected results

19:25 <wpwrak> it all happens in the directory you create when checking out the first "ee"

19:25 <wpwrak> and you can make this git clone http://neo900.org/git/ee.git newdir if you want

19:25 <wpwrak> when you're done with it all, just rm -rf the whole gang

19:33 <wpwrak> i need to rename the thing, though. it now has evolved beyond just "sch2fig" conversion

19:50 <DocScrutinizer05> I don't feel familiar enough with git to follow that instruction

20:01 <DocScrutinizer05> ((too many git)) and too few definition of environment

20:02 <DocScrutinizer05> wich dir? are the paths really matching my dir structure? do I even have the commands installed that are needed?

20:03 <wpwrak> pick a new directory. the path are all under the "ee" you're checking out there, so it doesn't contaminate its surroundings

20:05 <wpwrak> you may have to install qiv. that's an image viewer that is good at making "slide shows", similar to xv.

20:07 <wpwrak> you can also use "display" from imagemagick. but it's slower and you have to be careful that you don't exit it accidently

20:12 <wpwrak> here is an alternative sequence, without the git worktree add: https://neo900.org/stuff/paste/Aip2bahb

21:01 <edwin> https://news.ycombinator.com/item?id=12205514 not sure if this is good or bad news regarding FCC and WiFi

21:03 <edwin> I mean this part looks good "While manufacturers of Wi-Firoutersmust ensurereasonable safeguards to protectradio parameters, users are otherwise free to customize their routers and we support TP-Link’s commitment to work with the open-source community and Wi-Fi chipset manufacturers to enable third-party firmware on TP-Link routers.".

21:03 <edwin> This part can be a bit worrying if it means they have to implement some signed firmware or something for the wifi part: "TP-Link has also agreed to take steps to support innovation in third-party router firmwarebycommittingto investigate security solutions for certain 5GHz band routers that would permit the use of third-party firmware while meeting the Commission’s security requirements and maintaining the integrity of critical radio parameters."