From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Zaptel hotplug errors
Date: Fri, 29 Oct 2004 04:04:45 +0000 [thread overview]
Message-ID: <4181C15D.8040100@backtobasicsmgmt.com> (raw)
In-Reply-To: <1099017583.21544.16.camel@homer.internal.vpn>
Derek Whitten wrote:
> Oct 28 19:18:29 leroy kernel: Zapata Telephony Interface Registered on
> major 196
> Oct 28 19:18:30 leroy kernel: ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI
> 15 (level, low) -> IRQ 15
> Oct 28 19:18:30 leroy kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI
> 14 (level, low) -> IRQ 14
> Oct 28 19:18:35 leroy wait_for_sysfs[1792]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zaptimer' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1796]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zappseudo' properly,
> please report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1794]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zapchannel' properly,
> please report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1798]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zapctl' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1802]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zap1' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
The Zaptel drivers currently expose on a single sysfs attribute ("dev"),
the minimum required to get device nodes created. Getting them to do
more than that will be a job for the Asterisk developers, and should be
requested on the asterisk-dev list.
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-10-29 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 2:39 Zaptel hotplug errors Derek Whitten
2004-10-29 4:04 ` Kevin P. Fleming [this message]
2004-10-30 3:11 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4181C15D.8040100@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).