From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Building/fetching kernel firmware
Date: Thu, 7 Apr 2016 17:48:41 +0200 [thread overview]
Message-ID: <CABDcavYoj8r+V9SQRiJnR4VwuGF29SmOEcKhu8G9S+cTg-fGSg@mail.gmail.com> (raw)
In-Reply-To: <CAMyOCn-VEGpPfdzncypRq+qAxPMewGQBtvhpAoG-CzQ5EXMMYQ@mail.gmail.com>
2016-04-07 17:36 GMT+02:00 Wim Vinckier <wimpunk@gmail.com>:
> On 7 April 2016 at 14:37, Michael Olbrich <m.olbrich@pengutronix.de> wrote:
>> Hi,
>>
>> On Thu, Apr 07, 2016 at 11:32:30AM +0200, Wim Vinckier wrote:
>>> I'm wondering if there's a default way in ptx to build or fetch the
>>> kernel firmware. Does anyone has any suggestion?
>>
>> There is no predefined rule for that. Just drop the firmware file into
>> projectroot/ and write a rule for it with "ptxdist newpackage file".
>
> I was hoping there was a default way to fetch the useful kernel
> modules from http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git
> but it seems like there isn't one. Fetching the whole tree is just a
> little to much for my system. I already have a package which just
> copies the firmware from my working system but fetching the firmware
> from is projectroot is a better idea. Thanks for the suggestion.
You also can fetch one specific file instead of the whole tree (just
setup the URL so that it points to the file you need)
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-04-07 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 9:32 Wim Vinckier
2016-04-07 12:37 ` Michael Olbrich
2016-04-07 15:36 ` Wim Vinckier
2016-04-07 15:48 ` Guillermo Rodriguez Garcia [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-17 15:08 wim vinckier
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=CABDcavYoj8r+V9SQRiJnR4VwuGF29SmOEcKhu8G9S+cTg-fGSg@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/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