All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, shurik@gwu.edu
Subject: qcserial/gobi firmware loader
Date: Sat, 4 Apr 2009 16:27:31 +0100	[thread overview]
Message-ID: <20090404152731.GA5080@srcf.ucam.org> (raw)
In-Reply-To: <20090403164551.GA23689@srcf.ucam.org>

I've reimplemented Alexander's shell scripts for firmware loading in C 
and added a udev rule to automatically trigger the loading[1]. Thanks to 
Sergey's hint I've added checksumming support so it should work on other 
firmwares as well. The firmware needs to be obtained somehow and then 
put in /lib/firmware/gobi, but should then automatically load when the 
device is ready.

You can download this at http://www.codon.org.uk/~mjg59/gobi_loader/

[1] The firmware to be loaded depends on the user's network, so I can't 
think of an especially clean way of doing this in kernel.
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-04-04 15:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 20:37 qcserial comes up in unhelpful custom mode? Matthew Garrett
2009-04-03  2:56 ` Greg KH
2009-04-03 13:57   ` Matthew Garrett
2009-04-03 15:03     ` Greg KH
2009-04-03 15:12       ` Matthew Garrett
2009-04-03 15:57         ` Greg KH
2009-04-03 16:06           ` Matthew Garrett
2009-04-07 22:41             ` Greg KH
2009-04-03 15:12       ` Greg KH
2009-04-03 15:15         ` Matthew Garrett
2009-04-03 16:45         ` Matthew Garrett
2009-04-04 15:27           ` Matthew Garrett [this message]
2009-04-04 16:24             ` [PATCH] qcserial: Add extra device IDs Matthew Garrett
2009-04-04 17:51             ` qcserial/gobi firmware loader Kay Sievers
2009-04-04 17:54               ` Matthew Garrett
2009-04-04 18:14             ` Alexander Shumakovitch
2009-04-04 18:37               ` Matthew Garrett

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=20090404152731.GA5080@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shurik@gwu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.