OpenELEC dev builds for Raspberry Pi 2
11Feb15
I’ve modified my automated build system for OpenELEC so that it now creates RPi2 builds in addition to regular old RPi builds – https://resources.pichimney.com/OpenELEC/dev_builds/?C=M;O=D
Filed under: Raspberry Pi | 11 Comments
Tags: openelec, Raspberry Pi, RPi
Subscribe
Recent Comments
Nick Selby on Leaving the Institution me on Howto: secure your DNS with a… InSpec and the Too-L… on Policy debt Chris Swan on RAGing your actions in post in… 
Charles T. Betz (@Ch… on Policy debt 
Pinboard.in bookmarks- Yorkshire Evening Post response to boy on floor at hospital story
- network analysis of the now debunked claim
- 15 min rule
- Ethics and automation: What to do when workers are displaced
- The only thing that remains intact is the name 'Conservative party'. Everything else has been dismantled by entryists at the bottom and MPs at the top.
- UK ICO and The Alan Turing Institute Issue Draft Guidance on Explaining Decisions Made by AI
- Data Center ARM-ification is Around the Corner
- Caution, Swan is aggressive
- For the many
- Inside the hate factory: how Facebook fuels far-right profit | Australia news | The Guardian
Hi, I have to build OpenElec with patches voor EGalax touchscreen, can you explain more how i can build OpeElec for a PI 2?
All that’s needed is to specify RPi2 in the build line:
PROJECT=RPi2 ARCH=arm make releaseAhhh, I’m missing some basic knowledge about building? Many thanks! I’m now able to build!
Hi, im trying to compile an image for the rasp pi 2.
PROJECT=RPi2 ARCH=arm make image
right?
ok, i need to add some wifi drivers, link.
http://openelec.tv/forum/124-raspberry-pi/74480-problem-using-wifi-adapter
how can i add the drivers? i found some patches, but i dont know im doing.
I normally do
PROJECT=RPi2 ARCH=arm make release, but what you have looks fine if it’s an image you’re after.Adding additional drivers depends a lot on whether the drivers are mainstream, in which case you can just enable them in the kernel config file. If they’re not mainstream then you need to bring along the driver code itself. The example patch in the forum link is pretty good, so you need something like that – either manually add/edit the relevant files, or git cherry pick an existing patch.
Hi Chris can you make a new update tar for the pi2/3? inc. the new firmware and kernel? The pi3 is getting way to hot now… Popcornmix just updated it on git… and i think Jarvis 16,1 is out…Grz Scotty
r22390 is now available
How are bug reports submitted when using your dev build? c3757f9 performs extremely well on pi 3 but has some quirks.
It’s not my dev build – it’s just my robot building what the excellent folk who contribute to OpenELEC.tv put out. Take a look at their GitHub issues if you need to report a problem (though it’s always worth taking a look at the commit logs to see how something might have been introduced, and existing issues in case somebody else is already on it).
Hi im not really familiar with linux i have downloaded the tar file but after i execute in terminal “PROJECT=RPi2 ARCH=arm make” it give me an error
My build bot has already done the make for you, and the tar file is the result of that, but the tar file is only useful as an upgrade if you already have a working SD card (made from an image file).
If you want to build yourself then take a look at the compile from source docs.
If you just want to use OpenELEC then I’d suggest using stable builds rather than dev builds.