Here's another solution:
We tag releases on a forked repository and we upload tar files to Github with
only the files we need:
https://github.com/openwrt-es/raspberrypi-firmware/releases/tag/20150213
This way the downloaded files are ~4MB:
https://github.com/openwrt-es/raspberrypi-firmware/releas
I think they don't want to split the firmware:
https://github.com/raspberrypi/firmware/issues/362
So I forked the repo and removed the unneeded files from git history:
https://github.com/openwrt-es/raspberrypi-firmware
Now the downloaded files are ~4MB:
https://github.com/openwrt-es/raspberrypi-
On 2015-02-13 11:21, Álvaro Fernández Rojas wrote:
> Yeah, it would be great, but the real upstream repo is this one:
> https://github.com/raspberrypi/firmware
> As you can see it has even more crap (and we only use some files of the boot
> folder)...
I'll open up an issue there.
- Felix
___
Yeah, it would be great, but the real upstream repo is this one:
https://github.com/raspberrypi/firmware
As you can see it has even more crap (and we only use some files of the boot
folder)...
El 13/02/2015 a las 1:01, Felix Fietkau escribió:
> On 2015-02-12 00:33, Álvaro Fernández Rojas wrote:
On 2015-02-12 00:33, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
Do we really want to pull in the insane amounts of crap from that github
repo instead of just having a small tarball?
Maybe we should also ask upstream if they can split out the firmware
into a separate tree
Signed-off-by: Álvaro Fernández Rojas
---
package/kernel/brcm2708-gpu-fw/Makefile | 26 --
1 file changed, 16 insertions(+), 10 deletions(-)
diff --git a/package/kernel/brcm2708-gpu-fw/Makefile
b/package/kernel/brcm2708-gpu-fw/Makefile
index e202002..3fe2a7f 100644
--- a
