From: Johannes Stezenbach <js@convergence.de>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What's the point of __KERNEL_SYSCALLS__?
Date: Mon, 22 Sep 2003 19:23:03 +0200 [thread overview]
Message-ID: <20030922172303.GA3733@convergence.de> (raw)
In-Reply-To: <20030919164044.GF21596@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
>
> Given that, why should they exist? It only encourages monstrosities
> like sp8870_read_code() in drivers/media/dvb/frontends/alps_tdlb7.c that
> probably don't work anyway.
...
> read is used by DVB and the wavefront sound driver
> lseek is only used by DVB
> open is used by DVB, init/main.c and wavefront.
> close is used by wavefront. (DVB calls sys_close directly).
Those binary-only firmwares are a curse :-(
Anyway, we want to replace all our firmware loading code and the
compiled-in firmwares with the firmware_class loader as soon as
there is a usable hotplug agent available. There already are some
experimental patches for av7110.c in linuxtv.org CVS.
Johannes
prev parent reply other threads:[~2003-09-22 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 16:40 What's the point of __KERNEL_SYSCALLS__? Matthew Wilcox
2003-09-21 4:54 ` Matthew Wilcox
2003-09-21 5:23 ` viro
2003-09-21 8:11 ` Alan Cox
2003-09-22 17:23 ` Johannes Stezenbach [this message]
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=20030922172303.GA3733@convergence.de \
--to=js@convergence.de \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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