netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ellyjones@google.com
Cc: netdev@vger.kernel.org, jglasgow@google.com, mjg59@srcf.ucam.org,
	msb@google.com, olofj@google.com
Subject: Re: [PATCH v2] Add Qualcomm Gobi 2000 driver.
Date: Fri, 08 Oct 2010 10:28:03 -0700 (PDT)	[thread overview]
Message-ID: <20101008.102803.104075511.davem@davemloft.net> (raw)
In-Reply-To: <20101006151208.GB1571@google.com>

From: Elly Jones <ellyjones@google.com>
Date: Wed, 6 Oct 2010 11:12:09 -0400

> From: Elizabeth Jones <ellyjones@google.com>
> 
> This driver is a rewrite of the original Qualcomm GPL driver, released as part
> of Qualcomm's "Code Aurora" initiative. The driver has been transformed into
> Linux kernel style and made to use kernel APIs where appropriate; some bugs have
> also been fixed. Note that the device in question requires firmware and a
> firmware loader; the latter has been written by mjg (see
> http://www.codon.org.uk/~mjg59/gobi_loader/).
> 
> Special thanks go to Joe Perches <joe@perches.com> for major cleanup.
> 
> Signed-off-by: Elizabeth Jones <ellyjones@google.com>
> Signed-off-by: Jason Glasgow <jglasgow@google.com>

I really think the firmware handling belongs in the kernel.

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.

  parent reply	other threads:[~2010-10-08 17:27 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 [this message]
2010-10-08 18:03   ` Matthew Garrett
2010-10-08 18:14     ` David Miller
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.102803.104075511.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).