From: Felipe Balbi <me@felipebalbi.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Greg KH <greg@kroah.com>,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Q: support for AVM Fritz! WLAN USB in kernel 2.6.25+
Date: Fri, 1 Aug 2008 02:26:41 +0300 [thread overview]
Message-ID: <20080731232640.GB10436@frodo> (raw)
In-Reply-To: <489242CF.2000100@imap.cc>
On Fri, Aug 01, 2008 at 12:55:11AM +0200, Tilman Schmidt wrote:
> Oh, please ... You aren't seriously trying to tell me there's a *technical*
> reason for changing EXPORT_SYMBOL to EXPORT_SYMBOL_GPL, are you?
You really have no idea what you're talking about. If manufacturers
really don't wanna write gpl code, they have really sane api via
usbdev_fs.h or libusb to do it.
It's like we completely removed any possibility of closed source
drivers.
> That's not true. Reverting commit 782e70c6fc2290a0395850e8e02583b8b62264d8
> would be enough. But again, I am not asking for that. My question isn't
> about getting AVM's closed source driver to work with kernel 2.6.25+.
> I just want to know whether there is an open source alternative, nothing
> more.
Did you read the commit message?
"Over two years ago, the Linux USB developers stated that they believed
there was no way to create a USB kernel driver that was not under the
GPL. This patch moves the USB apis to enforce that decision.
There are no known closed source USB drivers in the wild, so this patch
should cause no problems."
So a) it wasn't an over-the-night decision. It was stated publicly and
given a 2 years period for everybody to know about what would happen and
b) "there are no know closed source usb drivers in the wild",
unfortunately, it looks like nobody knew about AVM's closed source
driver.
And after all, that driver isn't even closed source. I can see in the
files' header the driver is lgpl (that's actually the first lgpl driver
i see :-p)
> > This is between you and AVM. I really suggest contacting the company.
> > I have talked to them in the past and they seem willing to help out
> > where they can.
>
> Obviously even you weren't able to convince them to convert their driver
> for this device to something compatible with post 2.6.24 kernels. How
> then could I possibly hope to achieve anything? I have no contractual
> relationship with AVM. I don't know anybody in that company. I don't work
> for anyone they would recognize. All I can do is contact the regular
> consumer support people who don't even know what I am talking about and
> keep asking me to boot Windows, where the device obviously works, so all
> is well, no? After all, it does say "System requirements: Windows" on the
> box.
Again, you can get the sources under lgpl, which means you can change
the code and fix it up.
With a few changes to the source file, I could make it build. Don't have
the device to test, but I assure you it's pretty simple changes.
--
balbi
next prev parent reply other threads:[~2008-07-31 23:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 14:52 Q: support for AVM Fritz! WLAN USB in kernel 2.6.25+ Tilman Schmidt
2008-07-31 15:25 ` Johannes Berg
2008-07-31 16:34 ` Tilman Schmidt
2008-07-31 16:50 ` John W. Linville
2008-07-31 22:13 ` Tilman Schmidt
2008-07-31 22:43 ` Eugeniy Meshcheryakov
2008-08-01 23:30 ` Tilman Schmidt
2008-08-02 8:28 ` Felipe Balbi
2008-08-02 21:58 ` Tilman Schmidt
2008-08-02 23:12 ` Felipe Balbi
2008-08-03 0:45 ` Tilman Schmidt
2008-08-03 0:57 ` Felipe Balbi
2008-08-03 3:43 ` Greg KH
2008-08-03 9:11 ` Felipe Balbi
2008-08-03 21:10 ` Kamil Dzida
2008-08-01 19:04 ` Daniel Gimpelevich
2008-07-31 16:38 ` Greg KH
2008-07-31 21:34 ` Tilman Schmidt
2008-07-31 21:50 ` Greg KH
2008-07-31 22:55 ` Tilman Schmidt
2008-07-31 23:26 ` Felipe Balbi [this message]
2008-08-01 8:45 ` Tilman Schmidt
2008-08-01 8:50 ` Felipe Balbi
2008-08-01 8:58 ` Tilman Schmidt
2008-08-01 9:05 ` Felipe Balbi
2008-08-01 9:25 ` Tilman Schmidt
2008-08-01 8:45 ` Felipe Balbi
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=20080731232640.GB10436@frodo \
--to=me@felipebalbi.com \
--cc=greg@kroah.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tilman@imap.cc \
/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;
as well as URLs for NNTP newsgroup(s).