All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Thierry Laronde <thierry@cri74.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PCI] building PCI IDs/drivers DB from Linux kernel sources
Date: Mon, 30 Jul 2001 11:11:33 +0100	[thread overview]
Message-ID: <20010730111133.M8197@redhat.com> (raw)
In-Reply-To: <20010730113319.A24939@pc04.cri.cur-archamps.fr>
In-Reply-To: <20010730113319.A24939@pc04.cri.cur-archamps.fr>; from thierry@cri74.org on Mon, Jul 30, 2001 at 11:33:19AM +0200

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

On Mon, Jul 30, 2001 at 11:33:19AM +0200, Thierry Laronde wrote:

> I have decided to write a script (you will find all the stuff attached)
> parsing the Linux kernel sources in order to do that.

For the MODULE_DEVICE_TABLE case, isn't it less fragile to parse the
binary modules?

If there were a program to spit out the MODULE_DEVICE_TABLE in a
format easily parseable by scripts, it would be great; is there such a
program already?

> Driver names:
> 
> I try to match the filename processed (minus the suffix) against entries in
> the Makefile, and even try a substring against the Makefile in order to
> guess the correct driver name. When everything fails, the log file indicates
> the problem, and I have built a "drivers_aliases" giving the correct name
> for these files.

Again for the MODULE_DEVICE_TABLE case, there is nothing to guess.

> May I suggest some possible tracks?
> 
> * Use of macro definitions for magic numbers
[...]
> * Define the driver name in the file
[...]
> * Define the class name in the file too
[...]

None of this is needed if people just use the MODULE_DEVICE_TABLE
mechanism that is already provided.

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-07-30 10:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30  9:33 [PCI] building PCI IDs/drivers DB from Linux kernel sources Thierry Laronde
2001-07-30 10:11 ` Tim Waugh [this message]
2001-07-30 11:03 ` Marcus Meissner
2001-07-30 11:22   ` Thierry Laronde
2001-07-30 11:06 ` Keith Owens
2001-07-30 11:20   ` Thierry Laronde
2001-07-30 19:30 ` Glenn
2001-08-07 22:51 ` Eric Van Buggenhaut
  -- strict thread matches above, loose matches on Subject: below --
2001-07-30 10:04 Giacomo Catenazzi
2001-07-30 10:10 ` Thierry Laronde

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=20010730111133.M8197@redhat.com \
    --to=twaugh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry@cri74.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 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.