ChanServ changed the topic of #nmigen to: nMigen hardware description language · code at https://github.com/nmigen · logs at https://freenode.irclog.whitequark.org/nmigen · IRC meetings each Monday at 1800 UTC · next meeting November 23th
<_whitenotifier-f> [YoWASP/nextpnr] whitequark pushed 1 commit to develop [+0/-0/±1] https://git.io/JIvHi
<_whitenotifier-f> [YoWASP/nextpnr] whitequark bcc36e3 - Update dependencies.
withig has joined #nmigen
nengel has quit [Ping timeout: 240 seconds]
<_whitenotifier-f> [nmigen] bhansconnect commented on issue #415: Error accessing ResetSignal() - https://git.io/JIv7v
<cr1901_modern> >btw the "spartan 3" part is misnamed
<cr1901_modern> IIRC, I wrote _just_ enough of the s3 code to get my dev board to work. Definitely happy to test whatever unified version comes out of it tho
<d1b2> <dub_dub_11> likewise. My V5 hack was the same but probably more so, just enough to work without fancy stuff like DDR
nfbraun has quit [Quit: leaving]
Degi_ has joined #nmigen
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
electronic_eel has quit [Ping timeout: 256 seconds]
electronic_eel has joined #nmigen
electronic_eel has quit [Ping timeout: 256 seconds]
electronic_eel has joined #nmigen
PyroPeter_ has joined #nmigen
PyroPeter has quit [Ping timeout: 256 seconds]
PyroPeter_ is now known as PyroPeter
emeb_mac has quit [Quit: Leaving.]
jjeanthom has joined #nmigen
m4ssi has joined #nmigen
electronic_eel has quit [Ping timeout: 260 seconds]
electronic_eel has joined #nmigen
chipmuenk has joined #nmigen
<d1b2> <dub_dub_11> ok I have another question about a weird edge case that should not reasonably need doing but is interesting: can I have multiple IO standards for the LEDResources Resource?
<d1b2> <dub_dub_11> it's a real fun one, half the GPIO LEDs are on a 2V5 bank and are buffered by a CPLD while the other half are on a 1V8 bank buffered by NMOSs
<d1b2> <dub_dub_11> they're not even 0-3 and 4-7 either, it goes [0 1 2 4] and [3 5 6 7] respectively. Very interesting choice
<d1b2> <dub_dub_11> afaict LEDResources cannot be numbered, and while I can put a list of strings in the pins parameter, a list of Attrs() objects doesn't seem to work
<d1b2> <dub_dub_11> if I just need to use a generic Resource then that's fair enough
emeb_mac has joined #nmigen
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #nmigen
sakirious has quit [Ping timeout: 272 seconds]
<Degi> Would it make sense to catch comparisons in compile time which can never be true? For example 'a == 2' where 'a = Signal(1)'
<Sarayan> warnings for impossible things tend to be good
<Sarayan> as long as it's not the result of generated code (think templates, but pythonic I guess)
<whitequark> Degi: the reason it's not done is as Sarayan says: generic code
<Degi> Hm, does nMigen have something like verbosity options? Like configuring different warning / verbosity levels on a compiler
<whitequark> #360
<Degi> Thx!
_whitelogger has joined #nmigen
m4ssi has quit [Remote host closed the connection]
sakirious has joined #nmigen
chipmuenk has quit [Quit: chipmuenk]
nelgau has joined #nmigen
<_whitenotifier-f> [nmigen] whitequark edited issue #531: Implement missing CXXRTL features - https://git.io/JThSY
<_whitenotifier-f> [nmigen] whitequark edited issue #531: Implement missing CXXRTL features - https://git.io/JThSY
chipmuenk has joined #nmigen
chipmuenk has quit [Client Quit]
electronic_eel has quit [Ping timeout: 240 seconds]
electronic_eel has joined #nmigen
jjeanthom has quit [Ping timeout: 272 seconds]
smkz has quit [Quit: smkz]