#8476: Spare HDA jacks available - how can we address them? ---------------------------------+---------------------------- Reporter: dsuden | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ---------------------------------+---------------------------- Comment (by ttcoder): ... or if 'talking directly to the driver' (as mentionned by korli, thx!) is not too much of a hair-puller maybe I can take a stab at that... This would make sense especially if implementing the Media-Kit/multiaudio <-> driver glue is enough work that it won't happen anytime soon... @korli I wonder how to talk to the driver: presumably it exposes 'ports' to the userland world, so in my application I would call find_port() on a hardcoded name (?), then talk it into selecting the specific "node" (for a given audio jack of my choosing) and send audio data to that same port ? In truth I'm much tempted to let Sean & Dane organize a bounty ..etc to allow you to finish that aspect of the driver.. Though then I would ''still'' have to figure out the multi-audio API of course (it's not at api.haiku-os.org)... If you're sure I can dive into the header files (which ones, the HDA driver's, not the Media Kit's, right?) and have something to show for it when Dane asks, I'm all for it ;-) [to recall my non-userland track record: my "skills" are limited to having fixed a bug in the HDA driver for my R61 thinkpad, and even that "bugfix" was done with brute force tracing, not actual understanding of the driver or the media kit internals] -- Ticket URL: <http://dev.haiku-os.org/ticket/8476#comment:9> Haiku <http://dev.haiku-os.org> Haiku - the operating system.