[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20101008.102803.104075511.davem@davemloft.net>
Date: Fri, 08 Oct 2010 10:28:03 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ellyjones@...gle.com
Cc: netdev@...r.kernel.org, jglasgow@...gle.com, mjg59@...f.ucam.org,
msb@...gle.com, olofj@...gle.com
Subject: Re: [PATCH v2] Add Qualcomm Gobi 2000 driver.
From: Elly Jones <ellyjones@...gle.com>
Date: Wed, 6 Oct 2010 11:12:09 -0400
> From: Elizabeth Jones <ellyjones@...gle.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@...ches.com> for major cleanup.
>
> Signed-off-by: Elizabeth Jones <ellyjones@...gle.com>
> Signed-off-by: Jason Glasgow <jglasgow@...gle.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists