From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Martin Mares <mj@ucw.cz>
Cc: Yaroslav Rastrigin <yarick@it-territory.ru>,
Joshua Kugler <joshua.kugler@uaf.edu>,
linux-kernel@vger.kernel.org,
Nicolas Mailhot <nicolas.mailhot@laposte.net>,
David Chow <davidchow@shaolinmicro.com>
Subject: Re: Linux drivers management
Date: Mon, 6 Feb 2006 20:56:24 +0100 [thread overview]
Message-ID: <20060206195624.GJ19232@lug-owl.de> (raw)
In-Reply-To: <mj+md-20060206.193433.6964.atrey@ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
On Mon, 2006-02-06 20:39:37 +0100, Martin Mares <mj@ucw.cz> wrote:
> > And then think, why do you need to _build_ drivers in the first place.
> > Wouldn't it be better to have one vmware.ko which insmod's with all
> > 2.6 versions , from 2.6.0 to 2.6.16-rc2 , and throw "upgrade pain"
> > away completely ?
>
> Well, you want the vmware.ko to contain machine code for at least 17
> different architecture the kernel runs on? ;-)
I think we will first need to hack binutils. The last time I heared
about it, Fat Binaries weren't implemented (only containing object
code for two different architectures), let alone for _all_
architectures...
Even getting all GCCs to compile with the same version would be an
adventure...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-06 19:56 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 18:31 Nicolas Mailhot
2006-02-06 18:56 ` Yaroslav Rastrigin
2006-02-06 19:02 ` Joshua Kugler
2006-02-06 19:17 ` Yaroslav Rastrigin
2006-02-06 19:39 ` Martin Mares
2006-02-06 19:56 ` Jan-Benedict Glaw [this message]
2006-02-06 19:53 ` Jan-Benedict Glaw
2006-02-06 20:04 ` Jesper Juhl
2006-02-06 23:52 ` Bernd Petrovitsch
2006-02-06 19:21 ` linux-os (Dick Johnson)
2006-02-06 19:46 ` Michael Krufky
2006-02-06 19:58 ` Nicolas Mailhot
2006-02-06 23:16 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 4:42 linux
2006-02-07 16:18 ` Eric W. Biederman
2006-02-07 19:45 ` David Chow
2006-02-07 20:03 ` Kyle Moffett
2006-02-07 22:15 ` Theodore Ts'o
2006-02-08 0:52 ` David Chow
2006-02-08 4:02 ` Theodore Ts'o
2006-02-08 9:46 ` Bernd Petrovitsch
2006-02-09 6:09 ` Lee Revell
2006-02-08 1:06 ` Alan Cox
2006-02-08 8:26 ` Denis Vlasenko
2006-02-11 18:47 ` Andrew James Wade
2006-02-06 19:30 Nicolas Mailhot
2006-02-06 9:45 David Chow
2006-02-06 10:05 ` Michal Schmidt
2006-02-06 16:50 ` David Chow
2006-02-06 16:55 ` Randy.Dunlap
2006-02-06 19:45 ` Alan Cox
2006-02-06 19:46 ` Jesper Juhl
2006-02-06 10:08 ` Jes Sorensen
2006-02-06 16:52 ` David Chow
2006-02-06 17:03 ` Pedro Alves
2006-02-06 17:35 ` Geert Uytterhoeven
2006-02-06 17:42 ` Jes Sorensen
2006-02-06 16:56 ` Christoph Hellwig
2006-02-07 11:36 ` Denis Vlasenko
2006-02-07 13:22 ` Christoph Hellwig
2006-02-06 19:51 ` Greg KH
2006-02-06 21:38 ` Jim Crilly
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=20060206195624.GJ19232@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=davidchow@shaolinmicro.com \
--cc=joshua.kugler@uaf.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=nicolas.mailhot@laposte.net \
--cc=yarick@it-territory.ru \
/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
Powered by JetHome