Raspberry Pi : Activer le décodage des videos MPEG2 et WMV | Techjp.net https://techjp.net/raspberry-pi-activer-le-decodage-des-videos-mpeg2-et-wmv/

Fri May 24 15:39:37 2019

New video features! MPEG-2 and VC-1 decode, H.264 encode, CEC support - Raspberry Pi https://www.raspberrypi.org/blog/new-video-features/

Fri May 24 15:37:55 2019

Raspberry Pi Steam Link App - Steam Link - Knowledge Base - Steam Support https://support.steampowered.com/kb_article.php?ref=6153-IFGH-6589

Sun Apr 14 15:50:18 2019

Steam Link App for Raspberry Pi

The Steam Link app extends Steam Link functionality to the Raspberry Pi 3B and 3B+, running Raspbian Stretch. The App uses the same streaming technology as Valve's Steam Link, allowing you to play your favorite games and even spectate VR games right from your Raspberry Pi.

HP TouchPad Wireless Keyboard (bluetooth) connects but encry - Raspberry Pi Forums https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=42860&p=344390#p344390

Thu Apr 4 13:18:28 2019

Nothing like solving your own problem!

After a few more hours I came across this thread http://forums.fedoraforum.org/archive/i ... 01198.html and I did the second command: (first one won't hurt but I skipped it)

Code: Select all

/usr/sbin/hciconfig hci0 reset
/usr/sbin/hciconfig hci0 auth encrypt

I did have to remove/readd/reconnect before the keyboard worked, but it works!

Code: Select all

#Error code beforehand
May 6 11:26:39 raspberrypi bluetoothd[2069]: Permission denied (13)

Code: Select all

Restart

/etc/init.d/bluetooth restart
bluez-simple-agent hci0 XX:XX:XX:XX remove
bluez-simple-agent hci0 XX:XX:XX:XX
bluez-test-input connect XX:XX:XX:XX

So yeah RPi verified to work! Not sure how flakey it is on restart or if one needs to remove/readd every bootup. Be sure when you pair the HP touchpad you quickly type 0000 Enter on the pi then 0000 Return on the keyboard. This post isn't a complete tutorial on how to connect the HP TouchPad Wireless Keyboard so take a look around at any generic bluetooth keyboard guide.

retropie - How do I control GPIO-connected fan via code at a certain CPU temperature? - Raspberry Pi Stack Exchange https://raspberrypi.stackexchange.com/questions/62220/how-do-i-control-gpio-connected-fan-via-code-at-a-certain-cpu-temperature

Tue Feb 26 19:43:52 2019

from gpiozero import LED
#we are using the LED sub-module just as a generic output
fan = LED(18) #for the positive, put the negative in one of the grounds
def cputemp():
f = open("/sys/class/thermal/thermal_zone0/temp")
CPUTemp = f.read()
f.close()
StringToOutput= str(int(CPUTemp)/1000)

while True:
cputemp()
if StringToOutput >= 45:
fan.on()
elif StringToOutput < 45:
fan.off

This is some fairly simple code that gets the temperature from /sys/class/thermal/thermal_zone0/temp in thousandths Celsius divides by 1000 for Celsius and checks if it is more than 45. if it is it turns the "fan" on and if not , it stays off. But you'll almost certainly never need a fan as long as you're not doing anything stupid.

This code was adapted from a SE question but i am not sure which.

L'environnement de développement éducatif Scratch pour Raspberry passe en version 3 https://www.clubic.com/ordinateur-pc/mini-pc/actualite-849310-environnement-developpement-educatif-scratch-raspberry-3.html

Wed Jan 9 17:34:12 2019

Scratch 3 sur Raspberry Pi ?
En parallèle, la fondation Raspberry Pi vient d'annoncer qu'elle travaille sur une version hors ligne exécutable avec un Raspberry Pi. La création de cette version devra passer par deux étapes : d'abord soutenir le MIT pour optimiser son langage de programmation visuelle afin de s'assurer qu'il offre les meilleures performances possibles, puis par la suite créer cette version hors ligne de Scratch 3 ainsi que de nouvelles extensions GPIO et Sense HAT.

Cool si Scratch est disponible hors ligne bientôt !!

Protect your Raspberry PI SD card, use Read-Only filesystem – Charles's Blog http://hallard.me/raspberry-pi-read-only/

Tue Jan 8 21:29:45 2019

Setting up RetroArch on a Raspberry Pi · GitHub https://gist.github.com/AlexMax/32e5d038a66ce57253e740ea75736805

Wed Dec 19 17:17:07 2018

Setting up RetroArch on a Raspberry Pi

I just put the finishing touches on my Raspberry Pi 2 emulation machine running RetroArch. I was not a huge fan of RetroPie due to the reliance on Emulation Station - more moving parts meant that there were more things that could potentially break. I just wanted something that would run raw RetroArch, no frills.

This tutorial is mostly recreated from memory and was done with a Raspberry Pi 2 running Raspbian Jessie and RetroArch 1.3.6. If there is a mistake or a broken link, PLEASE message me and I will fix it.

Step 1: Install Raspbian

I used Raspbian Jessie Lite from this page. Write the image to your SD card using something like Win32 Disk Imager, or if you're using OSX/Linux follow a tutorial on how to write the image using dd.

Step 2: Get Comfortable

First things first, you're going to need to get Wi-Fi set up. Follow this tutorial. After that, make sure your system is totally up to date:

sudo aptitude update
sudo aptitude upgrade

Unless you live in Great Britain, you will probably not be happy with some of the defaults. Use this to fix your keyboard:

sudo dpkg-reconfigure keyboard-configuration

Use this to fix your locale (choose en_US.UTF-8 if you live in the US):

sudo dpkg-reconfigure locales

Use this to fix your timezone:

sudo dpkg-reconfigure tzdata

It's probably a good idea to reboot at this point.

3. Compile RetroArch

Unlike some other tutorials, I believe in keeping things simple, explaining what flags I'm enabling and why, and not going overboard on bells and whistles or disabling things. So let's get started:

sudo aptitude install libasound2-dev libudev-dev

Okay, time out - what are we installing and why?

libasound2-dev is ALSA. This library ensures that RetroArch will have sound - kind of important.
libudev-dev is udev. This library is necessary to ensure compatibility with a wider range of input devices. Without this, my DualShock 3 could be detected, but didn't actually work.

Now that we have libraries, grab the source for the latest stable version of RetroArch:

wget 'https://github.com/libretro/RetroArch/archive/v1.3.6.tar.gz'
tar zxvf RetroArch-1.3.6.tar.gz
cd RetroArch-1.3.6

Now to configure it:

./configure --enable-alsa --enable-udev --enable-floathard --enable-neon --enable-dispmanx

Okay, time out again - why are we passing these parameters to configure?

--enable-alsa ensures that we're compiling with ALSA support. If the library isn't installed, the configure script will die screaming instead of disabling the feature.
--enable-udev ensures that we're compiling with udev support.
--enable-floathard ensures that RetroArch uses the Pi's built-in hardware Floating Point Unit. Without this, there is the possibility that floating point calculations might be emulated in software, which is much slower.
--enable-neon ensures that RetroArch can use the Pi's SIMD CPU instructions (called NEON) for extra speed. Some cores take advantage of this.
--enable-dispmanx ensures RetroArch can use the Pi's Dispmanx support for rendering graphics. Dispmanx is a low-level 2D graphics API unique to the Raspberry Pi's video core which you can use as an efficient alternative to OpenGL. Some emulators run faster with Dispmanx, but the downside is that it is not as featureful as OpenGL (for one, the OSD text at the bottom of the screen won't render), and comes with ugly bilnear filtering enabled by default, though this can be turned off. So we compile with support for both GL and Dispmanx, and you can decide for yourself which one you prefer.

And that's it. Disabling 20 different options is pointless - all you're really saving is binary size. If the configure script completes without errors, you can then:

make
sudo make install

4. Configure RetroArch

Now that RetroArch is installed, run it:

retroarch

You will be presented with the GUI front-end. You can use the arrow keys to navigate the UI, x to select an option, z to back out, and esc to quit RetroArch completely. We still have a little ways to go, however, until we're completely up and running.

Quit out of RetroArch and edit the ~/.config/retroarch/retroarch.cfg file with your editor of choice - nano is good if you don't have a preference. Look for the line that mentions core_updater_buildbot_url and set it to http://buildbot.libretro.com/nightly/linux/armhf/latest/.

Next, unless you are incredibly lucky your controller probably is not working. Navigate to Online Updater, then Update Autoconfig Profiles and wait for the OSD text to stop flashing. Quit and restart RetroArch to see if your controller was found. If your controller still isn't configured, you might need to go to Settings, then Input, then Input User 1 Binds. It should be self-explanatory from here.

Now, let's test our updated settings. From the main menu, navigate to Online Updater, then Core Updater, and select 2048. Once it's installed, from the main menu, select Load Core then 2048. Finally, select Start Core. If everything went smoothly, you should be able to play a simple game of 2048 to prove that everything is set up correctly. To exit the game, press escape or use the button on your controller that you bound to said functionality.

At this point, you are now ready to follow other RetroArch tutorials that concern importing and playing your games.

5. Other Stuff

Does it bug you that sometimes your Pi will show a blank screen after a period of inactivity, which can only be undone by touching the keyboard? Use your editor of choice to modify /etc/rc.local and put the line setterm -blank 0 before the last line that says exit 0.

If you remember from earlier, we compiled RetroArch with Dispmanx support. To give it a spin and see if you prefer it to the default GL implementation, first ensure that you are using the default rgui menu driver - if you haven't changed your menu driver, you're fine. Next, at the Main Menu select Settings, Driver, then Video Driver and select dispmanx. You must then quit and relaunch RetroArch. If you ever want to go back, go to the same place and select gl instead.

RetroArch gives you many different choices for cores. Sometimes it's a little confusing trying to figure out which core is the best. Here is my suggestions based both on personal experience and other people giving me advice:

NES: FCEUmm.
Genesis: Genesis Plus GX. If you get slowdown, try PicoDrive.
32X: PicoDrive.
SNES: Snes9x Next. If you get slowdown, try CATSFC.

fusée (à la) framboise - A portable RPi Fusée Gelée rig | GBAtemp.net - The Independent Video Game Community https://gbatemp.net/threads/fusee-a-la-framboise-a-portable-rpi-fusee-gelee-rig.502507/

Tue May 15 12:42:36 2018

About
fusée framboise is a custom bare-bones Raspbian image that has a systemd Unit that loops modshipd.sh of fusee-launcher.

How-to

Ingredients

A Raspberry Pi Zero (any RPi works, but the Zero tends to run off of any power bank)
A power bank (for powering the RPi)
A non-powered USB hub (why?)
A USB-A to C cable (don't get a no-brand one: it may not have a needed resistor, and it may wreck your Switch or your USB source)
A USB-A to Micro cable (for RPi power)
A USB Micro to USB-A Female cable (only for the RPi Zero: for plugging in the USB hub)

SD Setup

Download a fusee-framboise image.
Flash it to your RPi's SD card. (If you don't have a flasher software installed, I recommend Etcher.)

Cables!

Plug the USB Micro to USB-A Female cable into the RPi. (only for RPi Zero)
Plug in the USB hub into the USB-A Female cable.
Plug in the USB-A to C cable into the USB hub.
Plug in the USB-A to Micro cable into the USB hub, and into the RPi.

Usage
You should just be able to plug in your Switch, put it into RCM, and the payload should automatically launch.

Replacing the payload
To replace the payload, you have two methods: (both need sudo)

Replace fusee.bin in /etc/fusee-launcher/ with another payload. (recommended)
Copy another payload into /etc/fusee-launcher/, change modchipd.sh to point to it, and restart the fusee-launcher service, or reboot.

Networking
You can change the payload over the air. Here's how to do it: (your RPi needs wireless, and you'll need a mobile/normal hotspot to do this)

Set a root password with "sudo passwd", and take note of it.
Change your default pi user's password from "raspberry". (optional, recommended)
Turn on SSH: it's in Interfacing Options of raspi-confiig.
Configure your Pi to connect to your phone's network.
Reboot to connect to it, run ifconfig, and take note of the settings.
Set a static IP based on your ifconfig data.
Take note of your static IP. (you should probably take note of it on your phone)
Use an app that supports SFTP to connect to your RPi with the new root password. (iOS)