From: Kasper Sandberg <lkml@metanurb.dk>
To: Theodore Tso <tytso@mit.edu>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>, Jan Dittmer <jdi@l4x.org>,
Pavel Machek <pavel@suse.cz>, Jirka Lenost Benc <jbenc@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>,
ipw2100-admin@linux.intel.com
Subject: Re: ipw3945 status
Date: Sun, 30 Jul 2006 18:09:40 +0200 [thread overview]
Message-ID: <1154275780.13635.36.camel@localhost> (raw)
In-Reply-To: <20060730150944.GG23279@thunk.org>
On Sun, 2006-07-30 at 11:09 -0400, Theodore Tso wrote:
> On Sun, Jul 30, 2006 at 05:00:54PM +0200, Kasper Sandberg wrote:
> > thats entirely different, if some firmware image is loaded into a card,
> > thats that, but running a userspace daemon is just entirely different,
> > what would happen if intel for some reason stopped supporting earlier
> > cards(as hardware manufactureres do after some time), and linux
> > kernel/userspace gets some change, preventing the binary daemon from
> > running? then what? we have lost.
>
> Um, last time I checked we could still run some *minix* binaries from
> before Linux was born, and we still can run statically linked a.out
> programs created over a decade ago. I don't think this is a serious
> objection, given that historically the Linux kernel/userspace syscall
> interface has been quite stable.
thats besides the point, i was arguing the difference between loading a
firmware image and running a binary daemon.
>
> Of course, I'd recomend against said driver using sysfs, but Greg K-H
> tells us that all breakagaes are the fault of buggy device drivers
> (just as supposedly all swsuspend problems are also about buggy device
> drivers), so I guess we're OK. :-)
>
> - Ted
>
next prev parent reply other threads:[~2006-07-30 16:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 10:40 ipw3945 status Pavel Machek
2006-07-30 11:28 ` Matthew Garrett
2006-07-30 11:30 ` Pavel Machek
2006-07-30 11:34 ` Jan Dittmer
2006-07-30 11:47 ` Matthew Garrett
2006-07-30 13:01 ` Kasper Sandberg
2006-07-30 14:53 ` Theodore Tso
2006-07-30 15:00 ` Kasper Sandberg
2006-07-30 15:09 ` Theodore Tso
2006-07-30 16:09 ` Kasper Sandberg [this message]
2006-07-30 16:25 ` Jan Dittmer
2006-07-30 16:32 ` Matthew Garrett
2006-07-30 17:52 ` Alan Cox
2006-07-30 23:12 ` Pavel Machek
2006-07-31 0:23 ` Alistair John Strachan
2006-07-31 1:16 ` Kasper Sandberg
2006-07-31 6:06 ` Alon Bar-Lev
2006-07-31 8:32 ` Kasper Sandberg
2006-07-30 16:58 ` James Courtier-Dutton
2006-07-30 17:25 ` Kasper Sandberg
2006-07-30 17:37 ` Rene Rebe
2006-07-30 18:03 ` Kasper Sandberg
2006-07-30 20:09 ` Rene Rebe
2006-07-30 21:02 ` Kasper Sandberg
2006-07-30 23:44 ` Alan Cox
2006-07-31 0:19 ` Kasper Sandberg
2006-07-31 7:11 ` Rene Rebe
2006-07-30 15:57 ` Tomasz Torcz
2006-07-30 16:01 ` Matthew Garrett
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=1154275780.13635.36.camel@localhost \
--to=lkml@metanurb.dk \
--cc=ipw2100-admin@linux.intel.com \
--cc=jbenc@suse.cz \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@suse.cz \
--cc=tytso@mit.edu \
/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