kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Tanure <tanure@linux.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: request_firmware in DMA region
Date: Wed, 18 Mar 2020 16:55:47 +0000	[thread overview]
Message-ID: <52f381bd-d2cf-c109-6258-c73b06d4b113@linux.com> (raw)
In-Reply-To: <20200318144631.GB2860387@kroah.com>

On 2020-03-18 14:46, Greg KH wrote:
> On Wed, Mar 18, 2020 at 02:29:24PM +0000, Lucas Tanure wrote:
>> Hi,
>>
>> I'm sending firmware to usb device with this code:
>> But it`s falling because the request firmware call didn't put my firmware in
>> a DMA capable area. That's my guess.
>>
>> So how to request firmware in DMA capable area?
> kmalloc your buffer used for USB transfers.
Thanks, worked.
>
> Do you have a pointer to your driver anywhere?  The code you show below
> isn't in any kernel source that I can see.

I`m working to get permission for that.

Quick question: Why my usb driver doesn't unload after I disconnected it ?

This driver is meant to load a new firmware into the board only. And 
after the bootloader finished the download the board with show it self 
with a different vendor and product id.

All the firmware download in done in probe, so there is no need for this 
driver after that. Can my driver unload it self ?

>
> thanks,
>
> greg k-h

Thanks!

Lucas



_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2020-03-18 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 14:29 request_firmware in DMA region Lucas Tanure
2020-03-18 14:46 ` Greg KH
2020-03-18 16:55   ` Lucas Tanure [this message]
2020-03-18 17:09     ` Greg KH

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=52f381bd-d2cf-c109-6258-c73b06d4b113@linux.com \
    --to=tanure@linux.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.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).