On Oct 20, matthieu castet [EMAIL PROTECTED] wrote:
Please explain why I need to hack this in udev and the aliases cannot be
provided by the modules themselves as usual.
Because pnp sysfs expose pnp devices and not isa cards.
Aliases are not in sysfs but in an ELF section in modules.
Look at
Marco d'Itri wrote:
On Oct 20, matthieu castet [EMAIL PROTECTED] wrote:
Please explain why I need to hack this in udev and the aliases cannot be
provided by the modules themselves as usual.
Because pnp sysfs expose pnp devices and not isa cards.
Aliases are not in sysfs but in an ELF
On Oct 21, matthieu castet [EMAIL PROTECTED] wrote:
But what's wrong with alias ?
The problem is we haven't enought information from sysfs to build the alias.
Non sequitur. Please read again my suggestions and actually look at how
modules can provide aliases.
--
ciao,
Marco
signature.asc
On Oct 19, matthieu castet [EMAIL PROTECTED] wrote:
The list is made for a kernel with all isa module enabled (debian kernel
???) and then it is put in a debian package and that's all.
It's never regenerated on the user machine.
Please explain why I need to hack this in udev and the aliases
Marco d'Itri wrote:
On Oct 19, matthieu castet [EMAIL PROTECTED] wrote:
The list is made for a kernel with all isa module enabled (debian kernel
???) and then it is put in a debian package and that's all.
It's never regenerated on the user machine.
Please explain why I need to hack this in
Hi,
Marco d'Itri wrote:
The only possible solution I saw is to build a modprobe alias file, that
for each isapnp device will give the driver name.
No, the correct solution would be for the kernel to provide a proper
$MODALIAS variable and for the modules to provide proper aliases.
Does the
On Oct 19, matthieu castet [EMAIL PROTECTED] wrote:
Does the kernel provide $MODALIAS for these modules even if there aren't
hotplugable (I don't know how udev does couldplug)?
Where it is done ?
Yes, in sysfs.
The modules have the correct aliases : they can't have simple pnp alias
as
Marco d'Itri wrote:
On Oct 19, matthieu castet [EMAIL PROTECTED] wrote:
What you propose is too much ugly and complex to be implemented.
Why complex ?
It's not acceptable to need to generate an aliases file at every boot.
Where did I say it need to be generated at every boot ?
The list
On Sun, Oct 16, 2005 at 05:08:46PM +0200, matthieu castet wrote:
matthieu castet wrote:
I make a script :
grep pnp:c /lib/modules/2.6.8-2-k7/modules.alias | cut -c19- | while
read line; do NAME=$(echo $line | cut -d'*' -f2); ID=$(echo $line | cut
-d'*' -f1); OLDIFS=$IFS; IFS=$IFS'd'; set
Package: udev
Severity: important
Hi,
isapnp alias are complex as there are exporting card and device id.
For example for the snd_sbawe driver for AWE 64 PnP, the alias is
pnp:cCTL009ddCTL0042dCTL0022*.
In the sysfs interface, only devices id are exported :
pnp/devices/01:01.00/
CTL0042
I make a script :
grep pnp:c /lib/modules/2.6.8-2-k7/modules.alias | cut -c19- | while
read line; do NAME=$(echo $line | cut -d'*' -f2); ID=$(echo $line | cut
-d'*' -f1); OLDIFS=$IFS; IFS=$IFS'd'; set $ID; while [ $# != 1 ] ; do
echo alias pnp:d${2} $NAME; shift; done ;IFS=$OLDIFS; done |
matthieu castet wrote:
I make a script :
grep pnp:c /lib/modules/2.6.8-2-k7/modules.alias | cut -c19- | while
read line; do NAME=$(echo $line | cut -d'*' -f2); ID=$(echo $line | cut
-d'*' -f1); OLDIFS=$IFS; IFS=$IFS'd'; set $ID; while [ $# != 1 ] ; do
echo alias pnp:d${2} $NAME; shift;
12 matches
Mail list logo
