From: Lee Revell <rlrevell@joe-job.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Arne Caspari <arnem@informatik.uni-bremen.de>,
bcollins@debian.org, linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's
Date: Mon, 20 Dec 2004 16:05:58 -0500 [thread overview]
Message-ID: <1103576759.1252.93.camel@krustophenia.net> (raw)
In-Reply-To: <20041220175156.GW21288@stusta.de>
On Mon, 2004-12-20 at 18:51 +0100, Adrian Bunk wrote:
> > Please please, do not break the kernel API out of the blue. Supporting a
> > Linux driver is already very frustrating. Currently it is a lot more
> > convenient for our customers to switch to Windows just because the
> > installation and use of the software is much easier there - or at least
> > it is easy enough there to handle the installation where it is not on Linux.
> >
> > Breaking the API now will most likely stop The Imaging Source from
> > supporting open source driver development anymore. We just can not
> > effort any unneccessary development anymore. We are already blocked by
> > shortcomings in the LDM and bugs in the Linux driver handling ( see my
> > posings about a hotplugging issue and about the issue that IEEE-1394
> > modules can not be unloaded ).
>
> the perfect solution would be if you'd simply submit your driver for
> inclusion in the main kernel.
>
> After grepping through your CVS sources, it seems hpsb_read and
> hpsb_write are the EXPORT_SYMBOLS affecting you?
> So keeping them should address your concerns?
Please, can't you just hold off on breaking the ieee1394 API at all for
now? Currently there are no supported IEEE-1394 audio devices. This is
a big deal as most new pro audio interfaces are IEEE-1394 devices.
There are a few under development, see http://freebob.sf.net. But they
don't work yet. If you rip out half the API you will make it that much
harder for these developers, by requiring them to be kernel hackers as
well as driver writers.
How about waiting until there is _one_ IEEE-1394 audio driver in the
tree before breaking the API?
Lee
next prev parent reply other threads:[~2004-12-20 21:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 1:53 [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's Adrian Bunk
2004-12-20 2:10 ` Dan Dennedy
2004-12-20 2:25 ` Adrian Bunk
2004-12-20 2:42 ` Lee Revell
2004-12-20 4:27 ` Dan Dennedy
2004-12-20 22:53 ` Adrian Bunk
2004-12-20 22:58 ` Lee Revell
2004-12-20 23:02 ` Adrian Bunk
2004-12-20 23:21 ` Lee Revell
2004-12-21 0:40 ` Alan Cox
2004-12-21 17:17 ` Greg KH
2004-12-21 17:20 ` Lee Revell
2004-12-21 17:27 ` Greg KH
2004-12-21 22:19 ` Theodore Ts'o
2004-12-22 14:08 ` Alan Cox
2004-12-20 9:01 ` Arne Caspari
2004-12-20 12:15 ` Arjan van de Ven
2004-12-20 13:20 ` Arne Caspari
2004-12-20 14:35 ` Alan Cox
2004-12-22 8:29 ` Arjan van de Ven
2004-12-22 8:57 ` Stefan Richter
2004-12-22 12:01 ` Christoph Hellwig
2004-12-22 12:21 ` Arne Caspari
2004-12-22 16:04 ` Stefan Richter
2004-12-20 14:39 ` Ben Collins
2004-12-20 15:15 ` Alan Cox
2004-12-20 15:46 ` Ben Collins
2004-12-20 20:15 ` Alan Cox
2004-12-21 8:33 ` Arne Caspari
2004-12-21 12:00 ` Adrian Bunk
2004-12-21 12:49 ` Arne Caspari
2004-12-21 17:15 ` Greg KH
2004-12-21 18:51 ` Arne Caspari
2004-12-21 18:58 ` Greg KH
2004-12-20 17:51 ` Adrian Bunk
2004-12-20 21:05 ` Lee Revell [this message]
2004-12-20 21:49 ` girish wadhwani
2004-12-21 8:37 ` Arne Caspari
2004-12-21 9:06 ` Bernard Leach
2004-12-21 23:35 ` Pieter Palmers
2004-12-22 0:56 ` Lee Revell
2004-12-21 0:42 ` updated: " Adrian Bunk
2004-12-21 8:46 ` Arne Caspari
2004-12-21 17:13 ` Greg KH
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=1103576759.1252.93.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=arnem@informatik.uni-bremen.de \
--cc=bcollins@debian.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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