22:38 <d1b2> <DX-MON> oh, fest - you'll be happy to know that with your suggestion, I debugged the applet and I've now got captures with it reliably working

22:43 <d1b2> <DX-MON> er.. wording.. s/you'll/you may/

22:44 <d1b2> <Dylan (he/him) mecodegoodsomeday> Just got the Glasgow update from Crowd Supply. Very clear, nicely written. Super-bummer, but as it says, this is a problem across the whole industry.

22:44 <whitequark[m]> goddamn, delayed until 2022

22:45 <d1b2> <Dylan (he/him) mecodegoodsomeday> Hopefully the early bird folks (I was among the earliest birds) will get 'em this year.

22:45 <d1b2> <Dylan (he/him) mecodegoodsomeday> It didn't explain why the cases are delayed until next year

22:53 <d1b2> <Dylan (he/him) mecodegoodsomeday> (keeping them in sync with the main production run is my guess, but ... just a guess)

22:55 <jschievink> dang, it really is just like the damn toilet paper shortage

23:05 <kmc> esden: thank you for your hard work. chip shortages are a bummer, but i appreciate the transparency and all the efforts to mitigate the impact

23:10 <d1b2> <esden> @kmc Thank you I appreciate it. 🙂 It is indeed a bummer. We do try our best to navigate around it as much as possible, but there is only so much we can do.

23:11 <whitequark[m]> hard to work around an industry wide shortage of anything

23:13 <d1b2> <esden> Yes indeed it is. And we are also the last ones that they care about when prioritizing who should get dibs...

23:14 <smeding> yeah, it's a shame but it's not your fault. i figure it'll get here when it gets here :)

23:17 <d1b2> <esden> Yeah, we will definitely make them all. It will "just" take a little longer. 😄

23:28 <d1b2> <KeithTheEE> Man I'm so bummed by the chip shortage, but my excitement for the glasgow hasn't waned. Whenever it's possible to get everything necessary, I look forward to it! Thanks for the update!

23:29 <d1b2> <KeithTheEE> (And I want to super emphasize thank you for the update, well laid out and upfront. I really really appreciate that)

23:32 <whitequark> it also gives us some more time to polish firmware & software

23:32 <d1b2> <esden> @KeithTheEE Glad to hear that. Who knows there might be some miracle and we get the last showstopper part earlier than expected? One can't loose hope, I am keeping my fingers crossed. 😄

23:33 <d1b2> <esden> @whitequark ahh yes indeed. That is a good positive take. Let's use that as an opportunity. 🙂 "Life gives you lemons, make lemonade."

23:35 <d1b2> <KeithTheEE> Hopefully it'll pan out that way. But the project itself is what I'm ecstatic for moreso than a timeline. The streams and updates have been a delight and now it's just more time to get even more excited! (And to learn more, I'm so excited to take time to focus on figuring out nmigen and more tools).

23:37 <DX-MON> electronic_eel: I'd be interested to hear what you think about https://github.com/DX-MON/glasgow/blob/main/software/glasgow/applet/interface/jtag_pdi/__init__.py which I now have working and deliving useful/usable data

23:38 <d1b2> <uep> @esden really nice summary of the chip situation overall. You channeled frustration into constructive reporting

23:38 <DX-MON> (I intend to make the applet also have an interactive mode where you can write PDI instructions and have them send to the target, then pull the result [if any] before I consider PR'ing it)

23:38 <d1b2> <esden> @uep thank you... 🙂

23:39 <DX-MON> likewise to WQ if she has time to review an applet and indicate if it'd be considered upstreamable - though I understand if not as there is a lot to this one and there is a lot of code to dredge there

23:43 <whitequark> DX-MON: the short answer is no, the detailed answer is not something i can give you right now

23:43 <whitequark> please proceed under the assumption that it'll live in your fork for now

23:43 <whitequark> nothing wrong with that

23:44 <DX-MON> alright, fair enough

23:44 <whitequark> there'll eventually be clear guidelines for what needs to happen for an applet to be upstreamable

23:44 <whitequark> not quite there yet, unfortunately

23:44 <DX-MON> mkay

23:45 <DX-MON> I'll revisit it then once those guidelines are made available

23:45 <whitequark> either that or when i have actual review bandwidth available

23:45 <whitequark> and not just the scraps right now that i use for essential tasks

23:45 <DX-MON> seeing how this particular protocol is spicy enough that nobody should have to visit it twice.. it's a very rough ride to implement

23:45 <DX-MON> sure, that's very reasonable

23:46 <whitequark> i have a liking for cursed JTAG stuff

23:46 <whitequark> so it'd be cool to have it upstream

23:46 <DX-MON> this fits that

23:46 <DX-MON> :3

23:46 <DX-MON> "we took our single-wire-bidirectional protocol and encapsulated it in JTAG then didn't document half the protocol (the debug part)"

23:47 <DX-MON> (Atmel, at some meeting.. I presume)

23:47 <whitequark> oh THAT's how that works

23:47 <whitequark> and why it's so goddamn weird

23:47 <DX-MON> yeah..

23:47 <DX-MON> that's what this applet is all about

23:47 <whitequark> well, yeah, i've even looked at pdi

23:47 <DX-MON> you understand now why it should never have to be visited a second time

23:47 <whitequark> didn't quite have all the context

23:47 <DX-MON> it's.. bad

23:48 <DX-MON> in a "ohgosh, I kinda love it" kind of way

23:48 <whitequark> yup

23:50 <d1b2> <Perigoso> all these people suffering because the chip shortage is delaying the glasgows, and here i am with 5 glasgows waiting to be properly finished

23:51 <d1b2> <esden> "you are a baaaaaad~~~ protocol" puts pinky to mouth corner

23:51 <d1b2> <esden> 😄