Re: [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's
From: Lee Revell
Date: Mon Dec 20 2004 - 16:07:24 EST
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?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/