linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: 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: Thu, 31 Jul 2008 14:50:55 -0700	[thread overview]
Message-ID: <20080731215055.GB4817@kroah.com> (raw)
In-Reply-To: <48922FE2.70705@imap.cc>

On Thu, Jul 31, 2008 at 11:34:26PM +0200, Tilman Schmidt wrote:
> On Thu, 31 Jul 2008 09:38:43 -0700, Greg KH wrote:
> > On Thu, Jul 31, 2008 at 04:52:41PM +0200, Tilman Schmidt wrote:
> >> Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
> >> 2.6.25, broke AVM's closed-source driver for this device:
> >>
> >> ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
> >> ID 057c:6201 AVM GmbH WLAN USB v1.1
> >>
> >> Is there an open source alternative for that driver, or do systems
> >> with that device have to stay with kernel 2.6.24?
> > 
> > Please ask AVM, they have known about this for over 2 years now.
> 
> Please let's keep the politics out of this. I know who wrote that
> patch, I know the agenda behind it and the discussion accompanying it.
> Conversely, I'm sure you know fully well that I have no way of putting
> that question to any relevant person at AVM, and even if I had, it would
> achieve exactly nothing at all. I am not interested in such fruitless
> political discussions. I have a simple question, to which I would like
> a simple answer.

There's no "politics" here at all.

And why wouldn't you go ask AVM, they are the ones producing the driver
for this hardware, how could it be our responsibility to get their code
to work properly, when we have absolutely no way to do so?

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.

thanks,

greg k-h

  reply	other threads:[~2008-07-31 21:54 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 [this message]
2008-07-31 22:55       ` Tilman Schmidt
2008-07-31 23:26         ` Felipe Balbi
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=20080731215055.GB4817@kroah.com \
    --to=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).