From: Greg KH <gregkh@linuxfoundation.org>
To: George Nychis <gnychis@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what determines how firmware is loaded? (Q. on request_firmware details)
Date: Mon, 23 Apr 2012 15:56:03 -0700 [thread overview]
Message-ID: <20120423225603.GA23276@kroah.com> (raw)
In-Reply-To: <CA+7oygc839sn-s3hHo0XBA_BJop86hZB1h987af1caJ6pAOwyw@mail.gmail.com>
On Mon, Apr 23, 2012 at 05:28:51PM -0400, George Nychis wrote:
> Hi Greg,
>
> On Mon, Apr 23, 2012 at 5:21 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Apr 23, 2012 at 04:18:56PM -0400, George Nychis wrote:
> >> Hi all,
> >>
> >> I notice in an older version of Ubuntu that when I plugin a USB
> >> wireless device its firmware is loaded via sysfs. For example, this
> >> would pop up in sysfs:
> >> /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/compat_firmware/2-1/loading
> >
> > How old are we talking about here? What version of the kernel?
>
> This was on a 2.6.32-21 Kernel. Ubuntu 10.04 LTS.
>
> >
> >> Has the former method of loading firmware been removed as the default?
> >> Is there any way to request that the firmware load be done manually
> >> (the former method)?
> >
> > Why? In the end, they do the same thing, right?
>
> I am having issues with the automatic load on an embedded device
> running a 3.0.8 kernel. I get USB URB related errors like this:
> <7>[ 708.739241] ath9k_htc 1-1.1:1.0: usb_probe_interface - got id
> <3>[ 708.999596] otg_err: in s5pc110_otghcd_urb_dequeue()::00508
> <3>[ 709.000670] => fail to cancel_transfer()
> <7>[ 709.002489] usb 1-1.1: hcd_unlink_urb d2f7c780 fail -1
> <7>[ 709.004372] usb 1-1.1: khubd timed out on ep0out len=0/4096
> <3>[ 709.005181] usb 1-1.1: ath9k_htc: Firmware - htc_7010.fw download failed
You do realize just how old and obsolete your 3.0.8 kernel is, right? I
suggest you update to the latest version, or, if you are stuck with this
kernel, go ask the vendor who provided it to you for support, as they
are the best ones to help you out.
Either way, it looks like this is a USB issue in your usb controller,
not a firmware issue, so I don't think the firmware portion of the
interaction is the problem.
best of luck,
greg k-h
next prev parent reply other threads:[~2012-04-23 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 20:18 what determines how firmware is loaded? (Q. on request_firmware details) George Nychis
2012-04-23 21:21 ` Greg KH
2012-04-23 21:28 ` George Nychis
2012-04-23 22:52 ` George Nychis
2012-04-23 22:56 ` Greg KH [this message]
2012-04-26 15:23 ` Mark Brown
2012-04-26 15:27 ` Greg KH
2012-04-26 15:48 ` Mark Brown
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=20120423225603.GA23276@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gnychis@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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