request_firmware

by king » Thu, 29 Oct 2009 17:32:12 GMT


Sponsored Links
 Hi,

i have a firmware file which is a .hex file, does anyone know how to
load the firmware under android?

Where should i locate the .hex firmware file?

In the driver i see it use "request_firmware" to load the firmware,
however it give me a debug message to me that "unable to locate
firmware file" when loading the firmware.

Does anyone know what happened?

Thanks and Regards,
King.S
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



request_firmware

by pavan savoy » Thu, 29 Oct 2009 17:41:03 GMT


 request_firmware looks into /lib/firmware directory, if I remember correctly






-- 
--Pavan Savoy

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


request_firmware

by king » Fri, 30 Oct 2009 09:04:35 GMT


 Hi,

Is it same as in Android?
As Android didnt have /lib/firmware directory

Thanks and Regards,
King.S




--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



request_firmware

by tommy tommy » Fri, 30 Oct 2009 12:06:58 GMT


 you can use firmware-built way to solve this case!

2.6.28 later support blob firmware built in

2009/10/30 king <king06552...@gmail.com>




--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



request_firmware

by Chih-Wei » Mon, 02 Nov 2009 16:42:09 GMT


 You don't have the tool to load firmware.
Read kernel/Documentation/firmware_class/README
for details.

The android-x86 project has added a simple hotplug tool
to load firmware. See
 http://git.android-x86.org/?p=platform/system/core.git ;a=commitdiff;h=b36af46cc0da1ec6d687d3cd195512cca2b74c4c




-- 



request_firmware

by pavan savoy » Tue, 03 Nov 2009 17:50:16 GMT


 Hi,

Thanks for the tool. But how do I use it ?
I am working on a normal android FS and don't have a toolbox/
directory and no method to call hotplug_main.

I did build the hotplug executable and change the hotplug_main to
main, but somehow running "hotplug firmware" doesn't seem to be
working out.
So my doubt is the env variables like ACTION, FIRMWARE being set or
not, and didn't see them in the hotplug.log (created by you either).

Note:
Hard-coding what is required, i.e from the cmd line if I perform a
$ echo 1 > /sys/.../loading
$ echo ..firmware_file. > /sys/.../data
$ echo 0 > /sys/.../loading
does seem to be working !!

regards,
Pavan








-- 
--Pavan Savoy

-- 



request_firmware

by pavan savoy » Mon, 09 Nov 2009 17:18:49 GMT


 Hi Chih-Wei,
Would it be ok, for me to make use of the same code, and release it to
my internal GIT.
What should I be licensing it as ? GPL ?

regards,
Pavan








-- 
--Pavan Savoy

-- 



request_firmware

by Chih-Wei » Tue, 10 Nov 2009 18:10:06 GMT


 Yes, you can use it. The code is Apache License 2.0.

It is a utility of the toolbox, you don't need to change hotplug_main.
Just make the android tree and it will be compiled as a part of
toolbox,
and the symlinks /system/bin/hotplug and /sbin/hotplug will be
created.





-- 



request_firmware

by pavan savoy » Tue, 10 Nov 2009 18:44:34 GMT


 yes, got it. Thanks.

I replaced it by "main" so that the release to a local GIT tree
becomes simpler (different project location than the one's which come
from Google)

Also, has this been published in the Googe's GIT ?

regards,
Pavan








-- 
--Pavan Savoy

-- 



request_firmware

by Michael Trimarchi » Thu, 14 Jan 2010 19:15:51 GMT


 -- 



request_firmware

by pavan savoy » Mon, 18 Jan 2010 15:23:44 GMT


 Yeah, looked in just now - I wonder why it isn't reading the uevents
from firmware sub-system then ?
is just a change FIRMWARE_DIRECTORY from /etc/firmware to
/system/etc/firmware enough ? (or a symlink)

Has it worked for you ?

regards,
Pavan

On Thu, Jan 14, 2010 at 4:45 PM, Michael Trimarchi









-- 
--Pavan Savoy



Other Threads

1. How to config G1 to make both browser and MMS work?




I have been told that a blank is not the same than default. You must set it
explicitely.







--~--~---------~--~----~------------~-------~--~----~

2. Android theme inheritance relation implied by name?

Hi,

When I search across the source of framework resources packages, I
found the theme definitions in themes.xml using the naming pattern
like this:

Theme
Theme.Black
Theme.Dialog
....

Does it implied that the Theme.Black is derived from Theme? As it is
another way to set implied inheritance relations between styles, as
the ordinary declaration of inheritance is:

<style name="Theme.Black" parent="Theme">

Can anyone here explain this, Thanks in advance!

Jking


--~--~---------~--~----~------------~-------~--~----~

3. Problem Sending/Receiving data using startActivityForResult

4. uninstall vs. upgrade

5. About SAX

6. need for ACTION_LOCALE_CHANGED intent?

7. How to call other class in OnClickListener()