All of lore.kernel.org
 help / color / mirror / Atom feed
From: bgat@billgatliff.com (Bill Gatliff)
To: linux-arm-kernel@lists.infradead.org
Subject: SPI, DMA and an i.MX31
Date: Tue, 22 Sep 2009 11:22:06 -0500	[thread overview]
Message-ID: <4AB8F9AE.1070006@billgatliff.com> (raw)
In-Reply-To: <59b21cf20909220709w54b9e259ube473b322d661a65@mail.gmail.com>

Magnus Lilja wrote:
>
> That might be a problem. Binary firmware can be handled in Linux, as
> an example one can load it from user space but that makes it difficult
> to enable the SDMA before userspace has started. Another example is to
> let the bootloader load the SDMA scripts but that's not a nice
> solution. Don't know if this firmware can be accepted as a binary
> within the kernel.
>   

It couldn't be a "binary" in the kernel per se, it would be a constant
character array that gets compiled into a binary chunk.  Sort of like
how, for example, Keyspan's drivers are done.  See
linux/firmware/README.AddingFirmware, linux/firmware/keyspan and
drivers/usb/serial/keyspan*.


b.g.

-- 
Bill Gatliff
bgat at billgatliff.com

  reply	other threads:[~2009-09-22 16:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  8:26 SPI, DMA and an i.MX31 Wolf, Rene, HRO-GP
     [not found] ` <BLU105-W229F8F8F533B107510C600BAE10@phx.gbl>
2009-09-21  8:22   ` Wolf, Rene, HRO-GP
2009-09-21 18:04     ` Magnus Lilja
2009-09-22  2:44       ` Tonyliu
2009-09-22  9:00         ` Wolf, Rene, HRO-GP
2009-09-22 12:23           ` Andy Green
2009-09-22 13:22             ` Wolf, Rene, HRO-GP
2009-09-22 14:10               ` Andy Green
2009-09-22 14:09           ` Magnus Lilja
2009-09-22 16:22             ` Bill Gatliff [this message]
2009-09-22 19:45               ` Magnus Lilja
2009-09-24 10:51                 ` Wolf, Rene, HRO-GP
2009-09-25  7:26                   ` Andy Green
2009-10-01 10:42                     ` Wolf, Rene, HRO-GP

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=4AB8F9AE.1070006@billgatliff.com \
    --to=bgat@billgatliff.com \
    --cc=linux-arm-kernel@lists.infradead.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.