From: "Быстров Виталий" <error25@yandex.ru>
To: buildroot@busybox.net
Subject: [Buildroot] modules
Date: Tue, 05 Mar 2019 17:26:42 +0300 [thread overview]
Message-ID: <899921551796002@iva1-5148b5385b62.qloud-c.yandex.net> (raw)
In-Reply-To: <87fts1h54b.fsf@dell.be.48ers.dk>
I have little knowledge for compile bcm-refsw
Possible make proprietary modules for BCM7231 ?
Without simbols (as in satellite receivers)
I have files and will sent bcm-refsw
refsw_release_unified_20140919.tgz
refswBCM.tar.gz
I run Debian via UART , only no TV out HDMI and no Sound
If possible help
Thank you
Regards , Vitaly
>>>>>> "???????" == ??????? ??????? <error25@yandex.ru> writes:
>
>> Hi
>> I when compile , link http://sources.buildroot.net/stblinux-3.3-3.0a.tar.bz2
>> and no file ((
>
> sources.buildroot.net is the default source code mirror for buildroot,
> but we do not have any packages using that stblinux file, so we
> (naturally) don't have the file.
> )
>> https://github.com/philkingston/pios
>> note
>> Please feed suggestions, bug reports, insults, and bribes back to the
>> buildroot mailing list: buildroot at buildroot.org
>
> That is correct for Buildroot itself, but this Phil Kingston has made
> modifications to Buildroot including that stblinux file, so he is most
> likely to be able to help you.
>
> --
> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2019-03-05 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 6:20 [Buildroot] modules Быстров Виталий
2019-03-05 9:28 ` Peter Korsgaard
[not found] ` <925021551779772@sas2-ce04c18c415c.qloud-c.yandex.net>
2019-03-05 12:34 ` Peter Korsgaard
2019-03-05 14:26 ` Быстров Виталий [this message]
2019-03-05 15:42 ` Peter Korsgaard
2019-03-05 15:53 ` Быстров Виталий
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=899921551796002@iva1-5148b5385b62.qloud-c.yandex.net \
--to=error25@yandex.ru \
--cc=buildroot@busybox.net \
/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.