From: "Henning P. Schmiedehausen" <mailgate@hometree.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table
Date: Mon, 11 Jun 2001 08:45:43 +0000 (UTC) [thread overview]
Message-ID: <9g20fn$on4$1@forge.intermeta.de> (raw)
In-Reply-To: <9fq2ce$gkb$1@forge.intermeta.de> <200106082254.f58MsWE487361@saturn.cs.uml.edu>
"Albert D. Cahalan" <acahalan@cs.uml.edu> writes:
>Yep.
>Consider a chunk of x86 instructions using a home-grown OS
>abstraction layer, and drivers that implement that layer for
>both Linux and any non-GPL operating system. The binary blob
>is obviously not derived from Linux, and may in fact run
>without modification in a BSD or Solaris/x86 kernel.
I had an interesting discussion with my brother-in-law at this
weekend: What is source code?
In my (very much younger days), I used to hack in 8085 and Z80
assembler and even hex codes directly onto the disk / files using all
those scary tools like DDT and M80/L80 under CP/M (those were the days
when Microsoft tools were really bleeding edge. ;-) )
What if there is really a warbled indivdual that can write a driver in
object code? Or at least in x86 assembler and then performs the magic
necessary to link it into the kernel?
Is this a "binary only" driver or just a driver on par with the NVidia
that is just "GPL'ed but unreadable"?
Regards
Henning
--
Henning Schmiedehausen "They took the credit for your second symphony.
hps@intermeta.de Rewritten by machine and "New Technology".
henning@forge.franken.de and now I understand the problems you can see."
-- The Buggles, 1979
next prev parent reply other threads:[~2001-06-11 8:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 16:59 [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table La Monte H.P. Yarroll
[not found] ` <3B1E5CC1.553B4EF1@alacritech.com>
2001-06-06 22:07 ` La Monte H.P. Yarroll
2001-06-06 22:15 ` David S. Miller
2001-06-06 22:36 ` Alexander Viro
2001-06-06 22:42 ` Richard Gooch
2001-06-06 22:52 ` David S. Miller
2001-06-06 23:21 ` Matt D. Robinson
2001-06-06 23:31 ` David S. Miller
2001-06-06 23:51 ` Richard Gooch
2001-06-07 1:22 ` Ben Greear
2001-06-07 0:51 ` David S. Miller
2001-06-07 5:37 ` George Bonser
2001-06-07 5:50 ` David S. Miller
2001-06-07 6:00 ` George Bonser
2001-06-07 15:18 ` watermodem
2001-06-07 15:51 ` Mike Galbraith
2001-06-09 22:09 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregistertable watermodem
2001-06-09 23:15 ` Alexander Viro
2001-06-10 2:59 ` Horst von Brand
2001-06-10 4:38 ` Mike Galbraith
2001-06-07 5:16 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table Matt D. Robinson
2001-06-07 5:46 ` David S. Miller
2001-06-07 6:20 ` Richard Gooch
2001-06-07 6:47 ` Matt D. Robinson
2001-06-07 18:03 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister Alan Cox
2001-06-07 18:10 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table Alan Cox
2001-06-08 1:31 ` David S. Miller
2001-06-07 0:14 ` Ben Greear
2001-06-06 23:43 ` David S. Miller
2001-06-07 10:03 ` Henning P. Schmiedehausen
2001-06-07 10:50 ` Daniel Phillips
2001-06-07 11:25 ` David S. Miller
2001-06-07 17:52 ` Alan Cox
2001-06-08 8:29 ` Henning P. Schmiedehausen
2001-06-08 16:42 ` Alan Cox
2001-06-08 22:54 ` Albert D. Cahalan
2001-06-08 23:46 ` David Woodhouse
2001-06-11 8:45 ` Henning P. Schmiedehausen [this message]
2001-06-11 9:43 ` Helge Hafting
2001-06-11 16:17 ` Alan Cox
2001-06-11 18:31 ` Jacob Luna Lundberg
2001-06-11 18:48 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister Alan Cox
2001-06-11 20:34 ` Jacob Luna Lundberg
2001-06-12 7:08 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregistertable Helge Hafting
2001-06-07 10:05 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table Russell King
2001-06-07 11:25 ` David S. Miller
2001-06-07 15:27 ` Keith Owens
2001-06-07 17:01 ` David Woodhouse
2001-06-07 19:11 ` Matthias Urlichs
2001-06-11 18:26 ` [PATCH] sockreg2.4.5-06 " La Monte H.P. Yarroll
2001-06-13 16:25 ` David S. Miller
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='9g20fn$on4$1@forge.intermeta.de' \
--to=mailgate@hometree.net \
--cc=hps@intermeta.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox