All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Olaf Hering <olh@suse.de>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: module.viomap support for ppc64
Date: Fri, 13 Aug 2004 17:22:18 -0300	[thread overview]
Message-ID: <20040813202218.GD29875@logos.cnet> (raw)
In-Reply-To: <1092404570.29604.5.camel@bach>

On Fri, Aug 13, 2004 at 11:42:50PM +1000, Rusty Russell wrote:
> On Fri, 2004-08-13 at 19:40, Olaf Hering wrote:
> >  On Fri, Aug 13, Rusty Russell wrote:
> > 
> > > 2) Please modify scripts/mod/file2alias.c in the kernel source, not the
> > > module tools.  The modules.XXXmap files are deprecated: device tables
> > > are supposed to be converted to aliases in the build process, and that
> > > is how userspace tools like hotplug are to find them.
> > 
> > I found no user of the modules.alias file. Hotplug still uses the map
> > files. Parsing one big file will not improve performance, but thats a
> > different story.
> 
> You don't use the modules.alias file.  You simply "modprobe vio:xyz^abc"
> and modprobe reads modules.alias if necessary (the user can also insert
> aliases in the modprobe.conf file, for example).  Note that fnmatch is
> used, so you can actually use ? and * in your generated aliases.
> 
> > A hack for 2.6.8-rc4 is below. Can I read the alias file via 
> > while read a b c ; do : done < modules.alias ?
> > Is b supposed to contain not spaces? What special delimiter chars are
> > allowed? The 'name' and 'compat' property can contain almost any char.
> > I used '^' for the time being.
> 
> Spaces are probably a bad idea, yes.  ^ is a little odd, but probably
> not a bad choice.  You could even use a full: "vio:name:%s:compat:%s" if
> you wanted to.
> 
> > > 3) I will still accept patches to module-init-tools if required for 2.4
> > > compatibility, but they will be going away at some point!
> > 
> > Noone cares about that old junk.

I do care! 

> Shh... Marcelo might get offended 8)

Yes, I, I, rrrr :)

  reply	other threads:[~2004-08-13 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 17:37 module.viomap support for ppc64 Olaf Hering
2004-08-12 19:34 ` Hollis Blanchard
2004-08-12 23:43   ` Rusty Russell
2004-08-13  9:40     ` Olaf Hering
2004-08-13 13:42       ` Rusty Russell
2004-08-13 20:22         ` Marcelo Tosatti [this message]
2004-08-19 21:28         ` Olaf Hering
2004-08-20  3:47           ` Rusty Russell
2004-08-20  5:57             ` Olaf Hering
2004-08-20  7:25               ` Rusty Russell

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=20040813202218.GD29875@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=rusty@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.