From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
i2c@lm-sensors.org
Subject: Re: [i2c] [PATCH] update module-init-tools to support the i2c subsystem
Date: Mon, 14 Jan 2008 20:38:28 +0100 [thread overview]
Message-ID: <3ae72650801141138t27666bcerd66e96f836d1ab2b@mail.gmail.com> (raw)
In-Reply-To: <20080114185056.05b75fd1@hyperion.delvare>
On Jan 14, 2008 6:50 PM, Jean Delvare <khali@linux-fr.org> wrote:
> On Mon, 14 Jan 2008 18:08:16 +0100 (CET), Geert Uytterhoeven wrote:
> > On Mon, 14 Jan 2008, Jean Delvare wrote:
> > > I thought that the module aliases were generated by
> > > scripts/mod/modpost? As a matter of fact, I did not apply Jon's patch
> >
> > Sorry, you're right. Too early in the morning :-)
> >
> > > to module-init-tools, and "modinfo" shows me module aliases properly
> > > for i2c drivers that call MODULE_DEVICE_TABLE():
> >
> > I've just looked it up again (I had to do a similar thing for Zorro bus
> > support). Module-init-tools (depmod) also creates the modules.*map files,
> > which are used to map from device IDs to module names. I think these are used
> > by udev to load the appropriate module when a device with a specific device ID
> > pops up in sysfs.
>
> Ah, right. I see it now, there's modules.isapnpmap,
> modules.ieee1394map, modules.pcimap etc. but no modules.i2cmap.
> However, there is modules.alias which contains the i2c aliases for all
> device types (including one ieee1394 and many pci aliases) which seems
> somewhat redundant with the modules.*map files.
>
> > > $ /sbin/modinfo lm90
> > > filename: /lib/modules/2.6.24-rc7-git4/kernel/drivers/hwmon/lm90.ko
> > > author: Jean Delvare <khali@linux-fr.org>
> > > description: LM90/ADM1032 driver
> > > license: GPL
> > > vermagic: 2.6.24-rc7-git4 mod_unload
> > > depends: hwmon
> > > alias: i2c:Nlm90*
> > > alias: i2c:Nadm1032*
> > > alias: i2c:Nlm99*
> > > alias: i2c:Nlm86*
> > > alias: i2c:Nmax6657*
> > > alias: i2c:Nadt7461*
> > > alias: i2c:Nmax6680*
> > > $
> > >
> > > "modprobe i2c:Nadm1032" loads the lm90 driver as expected.
> >
> > Yes, it's also still not 100% clear to me when `i2c:Nadm1032' is used, and when
> > modules.i2cmap would be used...
>
> I am under the impression that modules.*map are the old way to get
> automatic driver loading and aliases are the new way to do the same.
> But maybe that's just me.
Right, nothing on recent systems is using the map files. This patch
should not be needed.
The plan is to deprecate the creation of these files in depmod.
Thanks,
Kay
next prev parent reply other threads:[~2008-01-14 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 2:39 [PATCH] update module-init-tools to support the i2c subsystem Jon Smirl
2008-01-13 14:27 ` [i2c] " Jean Delvare
2008-01-13 15:14 ` Jon Smirl
2008-01-13 15:35 ` Jean Delvare
2008-01-13 16:26 ` Jon Smirl
2008-01-13 17:43 ` Jean Delvare
2008-01-13 18:04 ` Jon Smirl
2008-01-14 10:57 ` Geert Uytterhoeven
2008-01-14 14:25 ` Jon Smirl
2008-01-14 16:38 ` Jean Delvare
2008-01-14 17:08 ` Geert Uytterhoeven
2008-01-14 17:50 ` Jean Delvare
2008-01-14 19:38 ` Kay Sievers [this message]
2008-01-14 19:46 ` Jean Delvare
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=3ae72650801141138t27666bcerd66e96f836d1ab2b@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).