linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] pnp rc
Date: Sun, 10 Oct 2004 20:38:55 +0000	[thread overview]
Message-ID: <41699DDF.7040700@free.fr> (raw)
In-Reply-To: <416695D2.2050405@free.fr>

Hi
Alexander E. Patrakov wrote:

 > matthieu castet wrote:
 >
 >
 > This bug applies to both versions of the script. In both pnp.distmap 
and isapnp.aliases, please remove the "analog" line completely (as 
opposed to what your patch does). The reason is that the "ns558" driver 
already contains this alias without our help, see
 >
 > /lib/modules/`uname -r`/modules.alias
 >
 > Thanks for the report. Don't forget to forward that to Debian 
bugtracker, since the bug is also there.
 >
I send it a month ago, but no reply...

 >> pnp.rc it is near 4 time longer than the debian version :
 >
 >
 >
 > well - could you please improve the Debian version in order for it to 
be able to load e.g. the snd-es18xx module?


Yes for isapnp, you need to pass to modproble the card and device id.
For your card it is for example cESS1868dESS1868dESS0000.
Unfortunatly I don't have any isa device, so I don't know if it is 
possible to recover all these id from sysfs. If not perhaps make a patch 
to export them via sysfs.


 > 2) Currently with 2.6 kernels module-init-tools don't convert 
MODULE_DEVICE_TABLE(isapnp, ...) to modules.isapnpmap entries. They 
understand only pnp and pnp_card device maps. Because of this 
limitation, any isapnp hardware detection script that relies only on 
modules.isapnpmap (or, equivalently, aliases) is less useful that it 
might be. E.g. 3com network cards are not detectable. What is the 
correct list to discuss that limitation?
 >
You could found it in modules.alias ?


Matthieu


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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

      parent reply	other threads:[~2004-10-10 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 13:27 [patch] pnp rc matthieu castet
2004-10-08 22:10 ` Greg KH
2004-10-09  5:36 ` Alexander E. Patrakov
2004-10-09  8:51 ` Alexander E. Patrakov
2004-10-10 20:38 ` matthieu castet [this message]

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=41699DDF.7040700@free.fr \
    --to=castet.matthieu@free.fr \
    --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).