Summary: | cannot detect soft-modem on HDA bus | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | admin | ||||||
Component: | kern | Assignee: | freebsd-multimedia (Nobody) <multimedia> | ||||||
Status: | Closed Overcome By Events | ||||||||
Severity: | Affects Only Me | CC: | mav | ||||||
Priority: | Normal | ||||||||
Version: | Unspecified | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Description
admin
2008-07-18 19:00:03 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-multimedia Over to maintainer(s). I have a laptop with built modem. But it is not defined at boot time. Also, it is not visible in the list pciconf-lv. On how much I learned modem located on the bus hda. I would like to use the modem to work, so I ask the developer to finalize the driver hda to work correctly with other devices except for the sound card. When using a patch to hda I managed to see the modem, but to use it, I could not. Hi. We can treat a modem codec as one of the "function group" like the audio function group. But almost all the structure of the modem function group is vendor specific. To control the modem codec, we have to obtain the codec's specifications. But I don't know a manufacturer which offers HDA modem codec's datasheets. So it is hard for us to write these codec's device driver. Listing a modem codec in a verbose dmesg is not so an important matter (because we cannot use it now). FYI, last year I tried to port the "slmodemd" daemon which supports several number of modem codecs on Linux with the ALSA driver. http://homepage2.nifty.com/dumb_show/unix/slmodemd-FreeBSD.en.html I could get some responses from the modem codec. It generated sound which was similar to a dialing and negotiation tone. But I could not use it as a modem at all. --- WATANABE Kazuhiro (CQG00620@nifty.ne.jp) State Changed From-To: open->suspended Latest snd_hda driver detects/reports all present codecs. But due to lack of codec specifications, modem support implementation looks very problematic. batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed. Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi> ^Triage: update PR to modern standards. I think we can now say this is not going to be fixed. Nobody cares about dial-up modems any more, and even before this was really problematic due to lack of specs. |