public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: David Brownell <david-b@pacbell.net>
Cc: Greg KH <greg@kroah.com>,
	rusty@rustcorp.com.au, kaos <kaos@ocs.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5.47bk2 + current modutils == broken hotplug
Date: Wed, 13 Nov 2002 15:59:56 -0500	[thread overview]
Message-ID: <3DD2BD4C.7060502@pobox.com> (raw)
In-Reply-To: <3DD2B1D5.7020903@pacbell.net>

David Brownell wrote:

> Greg KH wrote:
>
> > On Wed, Nov 13, 2002 at 12:11:01PM -0800, David Brownell wrote:
> >
> >> The module-init-tools-0.6.tar.gz utilities (or something
> >> related -- kbuild changes?) break hotplug since they no
> >> longer produce the /lib/modules/$(uname -r)/modules.*map
> >> files as output ... so the hotplug agents don't have the
> >> pre-built database mapping device info to drivers.
> >
> >
> >
> > Last I heard, Rusty's still working on this.  He's also going to be
> > changing the format so we don't expose kernel structures to userspace,
> > which would be a good thing.
>
>
> So long as the _information_ in those structures stays available, good.


Agreed.

> And it'd be handy if the text format for that information didn't change;
> how it's stored in object modules doesn't matter.



Correction -- the tools that read the text format are buggy if they do 
not transparently support changes to the text format.
(Corollary: the text format is buggy if it does not support a method of 
noticing format changes)

I am planning on adding PCI revision id to the information exported via 
MODULE_DEVICE_TABLE(pci,...).  Tools which correctly read the 
first-line-format-definition will continue to function as before, 
regardless of additional fields I want to add.  Tools which make silly 
assumptions will have those assumptions come back to bite them ;-)

(tangent warning!)
Another long term idea I would eventually like to realize is the removal 
of device ids from the C source code.  I don't care where they go -- 
drivers/net/pci_ids [per directory ids?], drivers/net/3c59x.meta, 
whereever.  Anywhere but the C source code.  It's quite silly to require 
a driver rebuild just to add a single PCI id, and further, embedding 
metadata in C source is rarely a good idea in the long term.  [reference 
some of Linus's counter-arguments when it was mentioned that Donald 
Becker's method of including Config.{in,help} data in C source might be 
useful]

	Jeff




  parent reply	other threads:[~2002-11-13 20:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 20:11 2.5.47bk2 + current modutils == broken hotplug David Brownell
2002-11-13 20:17 ` Greg KH
2002-11-13 20:40   ` David Brownell
2002-11-13 20:59 ` Jeff Garzik [this message]
2002-11-13 21:07   ` Greg KH
2002-11-13 22:45   ` David Brownell
2002-11-13 21:24 ` Jeff Garzik
2002-11-13 23:00   ` David Brownell
2002-11-14  3:46 ` Rusty Russell
2002-11-14  8:02   ` David Brownell
2002-11-14 10:01     ` Rusty Russell
2002-11-14 16:19       ` David Brownell
2002-11-14 17:42         ` Rusty Russell
2002-11-14 10:41   ` Gerd Knorr

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=3DD2BD4C.7060502@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox