ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
Xyz39808 has quit [Ping timeout: 240 seconds]
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
andlabs has quit [Ping timeout: 260 seconds]
andlabs has joined ##yamahasynths
<Foone> https://twitter.com/Foone/status/1228152290558664704 playing music on an adlib card, over USB.
<cr1901_modern> I was just about to post that link lol
<cr1901_modern> There's an old FTDI APNOTE about using parallel mode to drive an ISA card
<cr1901_modern> Foone: Is there a library to control that card or did you have to RE a custom device class?
<Foone> There's two libraries for it! a free one and a paid one. I'm using the free one, which exposes a pretty basic interface to it
<Foone> basically read/write io/ram and a "have we gotten an IRQ recently?" status command
<cr1901_modern> >"have we gotten an IRQ recently?"
<cr1901_modern> I wonder how you could implement this without polling on a modern OS (since hooking the IVT isn't an option :P)
<fseidel> I mean, you still could if you wrote a kernel mode driver
<cr1901_modern> I'd like to avoid that :D
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<whitequark> hm
<whitequark> why isn't there a way to poll IRQs from user mode?
<whitequark> like signalfd but for irq. irqfd
<whitequark> cr1901_modern: also, usb internally always does polling anyway
<whitequark> you could use an usb interrupt endpoint on the host
andlabs has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
<superctr> <cr1901_modern> superctr: For music playing this won't make a difference, but I believe the number of cycles you have to wait on the datasheet is a worst-case. So ppl concerned with timing/accuracy may be concerned. <- the thing is that the busy flag is just a "dumb" counter, it's not related to the actual time you have to wait (ring buffer position, etc)
<superctr> so there is simply no point to read from the FM chip if you can count cycles accurately another way (which you definitely can with an FPGA)
emily has quit [Quit: killed]
emily has joined ##yamahasynths
Xyz_39808 has joined ##yamahasynths
<cr1901_modern> whitequark: That is true re: polling. But does the OS check for whether an xfer is done at periodic intervals? Or does X/EHCI provide an interrupt (that user mode of course doesn't see) to avoid wasting cycles?
<whitequark> the latter
<whitequark> i *think* in OHCI you poll
<whitequark> or was it UHCI?
<cr1901_modern> THink it was U
<cr1901_modern> I happen to have a machine w/ UHCI because of course I do. I know this because I've run DOS USB drivers on that machine before, and the FOSS ones are UHCI only
<cr1901_modern> (or were at the time)
<andlabs> hey ValleyBell
<andlabs> vgmrips.net question
<andlabs> on the home page there's the Latest Additions list
<andlabs> but if I click the link, the list of results it sends me to is totally different
<andlabs> how can I see more than what the table on the home page provides?
<andlabs> also, most of the entries on the home page say updated 2020-02-09 but the actual pack pages beg to differ
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
Xyz_39808 has quit [Ping timeout: 248 seconds]
SceneCAT has quit [Quit: *Mreow*]
andlabs has quit [Ping timeout: 240 seconds]
SceneCAT has joined ##yamahasynths
andlabs has joined ##yamahasynths
Xyz_39808 has joined ##yamahasynths
andlabs has quit [Client Quit]
Xyz_39808 has quit [Ping timeout: 240 seconds]
Xyz_39808 has joined ##yamahasynths
andlabs has joined ##yamahasynths
Xyz_39808 has quit [Ping timeout: 260 seconds]