11:20 <d1b2> <Hysiact> IMHO, what you want is actually a CGRA, and at that point, PSoC5LP looks like it’s about right. But I agree, the rp2040 is missing a few key things that make it almost perfect

11:42 <tnt> ebb: https://github.com/smunaut/Glasgow/commits/microwire

11:43 <ebb> blessed. thanks!

11:43 <tnt> It's an old branch, no idea how much forward porting would be needed ...

11:43 <tnt> but depending on which rev you have you can also just use it "as-is" ...

11:44 <ebb> hmm, I'm revC1

11:44 <ebb> I might try my hand at porting it just for the sake of converting the migen to nmigen

11:47 <tnt> Sure, would definitely be nice to see that code finally put in shape :p

15:43 <d1b2> <TomKeddie> Python newbie question here. What's the best way to run glasgow without installing it (ie for development)? I very much stumble though things learning what I need as I go. I have been using a virtualenv and running an edit/setup.py/run cycle to test but this seems very hacky. Thanks.

15:44 <ebb> heya TomKeddie - virtualenv is an option, although you can use `pip install --user` to put it under ~/.local

15:45 <ebb> in addition to the --user flag, try using -e (or --editable) with pip install

15:45 <ebb> in effect that'll make it run directly from your dev checkout rather than copying it into your python libs

15:47 <ebb> With -e at least, regardless of virtualenv or not, you can cut out having to keep doing pip install or using setup.py; just edit code and rerun

15:47 <d1b2> <TomKeddie> Hey ebb. Thank you kind friend, --editable was the secret sauce I needed. Much appreciated.

15:48 <ebb> Great! No worries

15:48 <ebb> For super-interactive development there is the repl option in the Glasgow CLI, but I don't know much about it

15:48 <ebb> I think each Glasgow applet needs to write in repl support before you can use it?

16:32 <whitequark[m]> <ebb "I think each Glasgow applet need"> not anymore, there is the `repl` command that works with every applet

16:32 <ebb> \o/

16:46 <_whitenotifier> [glasgow] TomKeddie opened issue #270: applet.interface.pulse_counter: new applet to count pulse events on pins - https://git.io/JtwJC

16:47 <_whitenotifier> [glasgow] attie commented on issue #270: applet.interface.pulse_counter: new applet to count pulse events on pins - https://git.io/JtwJR

16:50 <d1b2> <TomKeddie> @Attie there's nothing better than wanting something and finding it's already been written! I'll have a play with your branch. Thanks!

16:50 <_whitenotifier> [glasgow] TomKeddie closed issue #270: applet.interface.pulse_counter: new applet to count pulse events on pins - https://git.io/JtwJC

16:51 <d1b2> <Attie> np!

16:56 <ebb> GitHub's network/graph feature for forks could be more than it is in terms of utility

16:58 <ebb> A way to see which forks have changed a certain file, or forks with branch names of interest, etc. would be nice for discovering prior work like the above

16:58 <ebb> and like tnt's microwire stuff

17:11 <d1b2> <TomKeddie> I coulda/shoulda/woulda searched the issues too 😉

17:12 <d1b2> <TomKeddie> Random question is this logic backwards? (from https://github.com/GlasgowEmbedded/glasgow/blob/master/software/glasgow/applet/interface/analyzer/__init__.py#L85) if args.pull_ups: pull_low = set(args.pin_set_i) if args.pull_downs: pull_high = set(args.pin_set_i) Asking before I log another issue and close it 2 mins later.

17:12 <ebb> Well, sometimes I suppose people go run a skunkworks branch without raising an issue or WIP PR

18:16 <d1b2> <Attie> @TomKeddie just fyi, this channel is mirrored from IRC, and multiline messages / code blocks do not play well on that side

18:17 <d1b2> <Attie> it does look backwards...

23:54 <_whitenotifier> [glasgow] TomKeddie opened issue #271: applet.interface.analyzer - pullups look like they have been swapped in applet python - https://git.io/Jtw0H