request_firmware

[king]

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

[pavan savoy]

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

--
--Pavan Savoy

[king]

Hi,

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

Thanks and Regards,
King.S

[tommy tommy]

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

2.6.28 later support blob firmware built in

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

[Chih-Wei]

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

[pavan savoy]

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

> --
> unsubscribe: android-porti...@googlegroups.com
> website: http://groups.google.com/group/android-porting



--
--Pavan Savoy

[pavan savoy]

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

[Chih-Wei]

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.

[pavan savoy]

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

[Michael Trimarchi]

Hi,

pavan savoy wrote:
> 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
>

Sorry but devices.c can be used to load firmware in the /etc/firmware
directory?
Why add a new hotplug script?

Michael

[pavan savoy]

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

--
--Pavan Savoy