From: Wolfgang Denk <wd@denx.de>
To: Marius Groeger <mag@sysgo.de>
Cc: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>,
LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: make module_install
Date: Tue, 17 Dec 2002 19:33:37 +0100 [thread overview]
Message-ID: <20021217183342.47AE8C6139@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 17 Dec 2002 19:12:36 +0100." <Pine.LNX.4.40.0212171909030.11803-100000@mag.devdep.sysgo.de>
In message <Pine.LNX.4.40.0212171909030.11803-100000@mag.devdep.sysgo.de> you wrote:
>
> > driver anyway. I will even go so far to say that if you need to run
> > "depmod" for your embedded system you should fix your system design
> > because you are doing something wrong.
>
> Someone might use loadable modules because he doesn't want to release
> his driver under the GPL. I wouldn't exactly consider this wrong.
I do not intend to comment on the issue of binary modules.
But even in such a situation the necessity to run depmod in an
embedded system is IMHO an indication of a potential design problem.
Things should be kept simple.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
No user-servicable parts inside. Refer to qualified service personnel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-17 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001301c2a5ed$1d546ea0$0700a8c0@pc005>
2002-12-17 17:37 ` make module_install Wolfgang Denk
2002-12-17 18:12 ` Marius Groeger
2002-12-17 18:33 ` Wolfgang Denk [this message]
[not found] <NCBBIINEHIPFGJPLBEIFGEEOEAAA.acurtis@onz.com>
2002-12-18 16:11 ` Marius Groeger
[not found] <002301c2a5fd$918c5fc0$0700a8c0@pc005>
2002-12-17 19:06 ` Wolfgang Denk
2002-12-17 21:10 ` Wolfgang Denk
[not found] <000701c2a5e5$30b5a660$0700a8c0@pc005>
2002-12-17 16:39 ` Wolfgang Denk
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=20021217183342.47AE8C6139@atlas.denx.de \
--to=wd@denx.de \
--cc=gianfranco.morandi@euro-studio.it \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mag@sysgo.de \
/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).