From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: loading firmware via hotplug
Date: Thu, 06 Oct 2005 16:55:42 +0000 [thread overview]
Message-ID: <20051006165542.GB13211@kroah.com> (raw)
In-Reply-To: <57004.217.150.108.178.1128506550.squirrel@newgolddream.dyndns.info>
On Wed, Oct 05, 2005 at 11:02:30AM +0100, Adrian McMenamin wrote:
> Apologies for asking what is probably a pretty basic question...
>
> I am writing a driver for ALSA sound on the Sega Dreamcast in the 2.6
> series of kernels. Previously I wrote one for OSS/Free for the 2.4 series
> and while the Dreamcast's main CPU is an SH4 chip, the sound is driven by
> an ARM7 processor.
>
> To get the ARM7 to work it is necessary to load in some ARM code to a
> specific memory location and reset the processor - effectively loading in
> some firmware. In 2.4 I did this by the then common way of a header with a
> long string of hex but now I want to use kmod/udev/hotplug etc to do it.
>
> I could not get buildroot's diethotplug to build so I just copied the
> hotplug scripts off my Fedora Core 4 box into the Dreamcast's NFS root.
Heh, and why would you think this would "just work"? :)
> So I have the following code in my driver (you can see the whole thing at
> http://newgolddream.dyndns.info/repos):
>
>
> /* Load the firmware */
> const struct firmware *fw_entry;
> err = request_firmware(&fw_entry, "aica_firmware.bin", &pd->dev);
> if (err) goto freepcm;
>
>
> This appears to summon firmware.agent, but after 10 seconds the whole
> thing times out... (I have put in a lot of the log, but about 1/3rd of the
> way down you'll find the firmware stuff - I added the **** myself).
Your firmware.agent file isn't finding the firmware to load? Don't
really know, it looks like the kernel is working properly, so you
proably just need to debug your script...
good luck,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-10-06 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 10:02 loading firmware via hotplug Adrian McMenamin
2005-10-06 16:55 ` Greg KH [this message]
2005-10-06 18:22 ` Adrian McMenamin
2005-10-06 18:45 ` Greg KH
2005-10-06 19:45 ` Adrian McMenamin
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=20051006165542.GB13211@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).