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:
>=20
> 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 indica=
tes
> 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?
>=20
> * 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.
*/
--m7GK0ytKUM7VScCy
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7ZTLVONXnILZ4yVIRAns5AJ9TcKq/iVT7lYPgWC35iAG5p7jr3ACgoHvF
lp13NT2f2t2sDsLLnxvTR2o=
=rpLc
-----END PGP SIGNATURE-----
--m7GK0ytKUM7VScCy--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/