From: David Miller <davem@davemloft.net>
To: mjg59@srcf.ucam.org
Cc: ellyjones@google.com, netdev@vger.kernel.org,
jglasgow@google.com, msb@google.com, olofj@google.com
Subject: Re: [PATCH v2] Add Qualcomm Gobi 2000 driver.
Date: Fri, 08 Oct 2010 11:14:06 -0700 (PDT) [thread overview]
Message-ID: <20101008.111406.246542521.davem@davemloft.net> (raw)
In-Reply-To: <20101008180310.GA27126@srcf.ucam.org>
From: Matthew Garrett <mjg59@srcf.ucam.org>
Date: Fri, 8 Oct 2010 19:03:10 +0100
> On Fri, Oct 08, 2010 at 10:28:03AM -0700, David Miller wrote:
>
>> I've looked at the gobi_loader code and it's simpler than many
>> of the gigabit ethernet driver firmware loader sequences in
>> the tree already.
>>
>> Requiring udev et al. magic only makes this networking device
>> that much harder to use from an initrd.
>>
>> I understand how this might be a bit clumsy since we'd need to make a
>> dependency on the serial device since that is the mechanism by which
>> the firmware is uploaded, but really I'd like you to consider it
>> seriously.
>
> The device is capable of functioning in either UMTS or CDMA modes, and
> requires different firmware for each. Further, there's separate firmware
> images per carrier due to regulatory differences. To make things even
> more complicated, there's no consistency in the naming of the firmware
> (and we can't fix that, because the firmware is undistributable). The
> only way to do this in-kernel would seem to be to have a module
> parameter to pass a firmware name, which really doesn't seem elegant.
I don't think we want a driver in the tree for a device for which the
firmware isn't even distributable.
next prev parent reply other threads:[~2010-10-08 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 15:12 [PATCH v2] Add Qualcomm Gobi 2000 driver Elly Jones
2010-10-06 16:46 ` Joe Perches
2010-10-08 17:28 ` David Miller
2010-10-08 18:03 ` Matthew Garrett
2010-10-08 18:14 ` David Miller [this message]
2010-10-08 18:18 ` Matthew Garrett
2010-10-08 18:50 ` David Miller
[not found] ` <AANLkTimbpPZt4FSeHDNcfuoYeKDYtV2YsLPxP-2ngELO@mail.gmail.com>
2010-10-08 19:02 ` David Miller
2010-10-08 19:18 ` Jason Glasgow
2010-10-08 19:05 ` Matthew Garrett
2010-10-15 13:17 ` Elly Jones
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=20101008.111406.246542521.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ellyjones@google.com \
--cc=jglasgow@google.com \
--cc=mjg59@srcf.ucam.org \
--cc=msb@google.com \
--cc=netdev@vger.kernel.org \
--cc=olofj@google.com \
/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).