From: Gary Thomas <gary@mlbassoc.com>
To: Joshua Lock <josh@openedhand.com>
Cc: poky@yoctoproject.org
Subject: Re: Kernel firmware?
Date: Tue, 18 Jan 2011 06:44:45 -0700 [thread overview]
Message-ID: <4D35994D.6050703@mlbassoc.com> (raw)
In-Reply-To: <1295356953.2642.16.camel@scimitar>
On 01/18/2011 06:22 AM, Joshua Lock wrote:
> On Tue, 2011-01-18 at 04:36 -0700, Gary Thomas wrote:
>> On 01/17/2011 09:49 AM, Gary Thomas wrote:
>>> On 01/17/2011 06:28 AM, Gary Thomas wrote:
>>>> On 01/17/2011 06:10 AM, Joshua Lock wrote:
>>>>> On Mon, 2011-01-17 at 05:53 -0700, Gary Thomas wrote:
>>>>>> On 01/17/2011 02:23 AM, Joshua Lock wrote:
>>>>>>> Hi Gary,
>>>>>>>
>>>>>>> On Sun, 2011-01-16 at 05:30 -0700, Gary Thomas wrote:
>>>>>>>> I'm trying to get various USB WiFi dongles working on my
>>>>>>>> BeagleBoard (or look-alike). Many of these require runtime
>>>>>>>> downloads of firmware. However, these files don't seem to
>>>>>>>> be installed in Poky:
>>>>>>>> phy1 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt73.bin'.
>>>>>>>> rt73usb 2-1.2.4:1.0: firmware: requesting rt73.bin
>>>>>>>> phy1 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
>>>>>>>>
>>>>>>>> Is there some way to enable this?
>>>>>>>
>>>>>>> There's a linux-firmware recipe
>>>>>>> (meta/recipes-kernel/linux-firmware/linux-firmware_git.bb) which you'll
>>>>>>> have to modify to package the required firmware (at the moment we only
>>>>>>> package firmware for the Libertas sd8686) and ensure that the packages
>>>>>>> are included in your images.
>>>>>>
>>>>>> I don't see anywhere that linux-firmware-sd8686 is included in
>>>>>> an image. Am I missing something?
>>>>>
>>>>> You need to have something pull in the required linux-firmware, for
>>>>> example the igep0020 and igep0030 machines add linux-firmware-sd8686 to
>>>>> the MACHINE_EXTRA_RRECOMMENDS.
>>>>
>>>> Thanks. Doing it this way wasn't totally clear from "ensure that the
>>>> packages are included in your images."
>>>>
>>>> It's working now.
>>>
>>> My exuberance was a bit premature. Indeed, I rebuilt my install
>>> image, but the firmware package wasn't installed. On my target,
>>> I see:
>>> root@cobra3530p60:~# opkg list-installed linux*
>>> root@cobra3530p60:~# opkg list linux*
>>> linux-firmware-rt73 - 0.0+git0+40c0f950be7040614dc45df54e25e54d00e3b73b-r0 - Firmware files for use with Linux kernel
>>> Firmware files for use with Linux kernel
>>> linux-firmware-sd8686 - 0.0+git0+40c0f950be7040614dc45df54e25e54d00e3b73b-r0 - Firmware files for use with Linux kernel
>>> Firmware files for use with Linux kernel
>>> linux-libc-headers-dbg - 2.6.36-r0 - Debugging files for linux-libc-headers
>>> Debugging files for linux-libc-headers
>>> linux-libc-headers-dev - 2.6.36-r0 - Development files for linux-libc-headers
>>> Development files for linux-libc-headers
>>>
>>> To be clear, all I did was add "linux-firmware-rt73" to MACHINE_EXTRA_RRECOMMENDS
>>> in my<MACHINE>.conf file, then rebuild the image using:
>>> % bitbake poky-image-sato
>>> This was from a previously built tree, etc. Did I need to do anything
>>> else to get the package actually installed at build time?
>>>
>>> Note: If I 'opkg install linux-firmware-rt73' on my target, I get
>>> the correct files. I'd just like to understand how to make it happen
>>> in the "image"
>>
>> I don't see any kernel modules get installed in one of Poky's
>> "supported" platforms either. I just tried
>> MACHINE=igep0030 bitbake poky-image-minimal
>> in a clean tree. No kernel modules:
>>
>> [gthomas@titan igep_test]$ ls tmp/work/igep0030-poky-linux-gnueabi/poky-image-minimal-1.0-r0/rootfs/lib
>> ld-2.12.1.so libattr.so.1.1.0 libgcc_s.so.1 libnss_dns-2.12.1.so librt-2.12.1.so
>> ld-linux.so.3 libc-2.12.1.so libgudev-1.0.so.0 libnss_dns.so.2 librt.so.1
>> libBrokenLocale-2.12.1.so libc.so.6 libgudev-1.0.so.0.0.1 libnss_files-2.12.1.so libudev.so.0
>> libBrokenLocale.so.1 libcidn-2.12.1.so libm-2.12.1.so libnss_files.so.2 libudev.so.0.9.3
>> libacl.so.1 libcidn.so.1 libm.so.6 libproc-3.2.8.so libutil-2.12.1.so
>> libacl.so.1.1.0 libcrypt-2.12.1.so libnsl-2.12.1.so libpthread-2.12.1.so libutil.so.1
>> libanl-2.12.1.so libcrypt.so.1 libnsl.so.1 libpthread.so.0 modules
>> libanl.so.1 libdl-2.12.1.so libnss_compat-2.12.1.so libresolv-2.12.1.so udev
>> libattr.so.1 libdl.so.2 libnss_compat.so.2 libresolv.so.2
>>
>> Am I missing something? Should I file a bug?
>>
>
> Yes, please file a bug.
Done, bug #660
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-01-18 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 12:30 Kernel firmware? Gary Thomas
2011-01-17 9:23 ` Joshua Lock
2011-01-17 12:53 ` Gary Thomas
2011-01-17 13:10 ` Joshua Lock
2011-01-17 13:28 ` Gary Thomas
2011-01-17 16:49 ` Gary Thomas
2011-01-18 11:36 ` Gary Thomas
2011-01-18 13:22 ` Joshua Lock
2011-01-18 13:44 ` Gary Thomas [this message]
2011-01-18 13:29 ` Koen Kooi
2011-01-18 13:41 ` Gary Thomas
2011-01-18 13:44 ` Koen Kooi
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=4D35994D.6050703@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=josh@openedhand.com \
--cc=poky@yoctoproject.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 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.