The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,173 other subscribers

Archive for February 22nd, 2016

Replace Boxee by Raspberry Pi as most TV support doing video+USB keybard over HDMI

Posted by jpluimers on 2016/02/22

If for instance your Boxee gets old or breaks down, you can use a Raspberry Pi as a replacement with Kodi as media player.

This combination will understand the Video+USB over HDMI which most TV supports officially named HDMI-CEC , but most vendors “invented” their own names (see list below).

The core is the kodi support for CEC.

Basically it comes down to using three cables going to the Pi: Power from TV (or some other source), HDMI to TV, and wired Ethernet. And a distribution for RaspberryPi containing kodi will work, for instance from OpenELEC Mediacenter – Download: Raspberry Pi Builds

Chad MILLER has more details on how to get this to work: My Boxee box is getting old, but I knew of no replacements. The problem is I …

Names known for HDMI-CEC via Wikipedia:

Anynet+ (Samsung), Aquos Link (Sharp), BRAVIA Link and BRAVIA Sync (Sony), HDMI-CEC (Hitachi), E-link (AOC), Kuro Link (Pioneer), INlink (Insignia), CE-Link and Regza Link (Toshiba), RIHD (Remote Interactive over HDMI) (Onkyo), RuncoLink (Runco International), SimpLink (LG), T-Link (ITT), HDAVI Control, EZ-Sync, VIERA Link (Panasonic), EasyLink (Philips), and NetCommand for HDMI (Mitsubishi).

Because of the naming, turning on CEC can be confusing: How to Enable HDMI-CEC on Your TV, and Why You Should


Posted in *nix, *nix-tools, Development, Hardware Development, Hardware Interfacing, HDMI, Linux, Power User, Raspberry Pi | Leave a Comment »

Linking to part of the same document in Markdown (via: Stack Overflow)

Posted by jpluimers on 2016/02/22

I love markdown, but it lacks the ability to directly create destination anchors (but MarkDownExtra however does for headers)

Anchors can be used to link within and between documents, the foundation of web navigation, and also very important inside documentation.

Luckily, Markdown allows inline HTML, so you can add an HTML destination anchor: an a element with either a name or id attribute.

XHTML deprecated the name attribute, but you should actually use it. The reason is that in HTML5, most browsers create a global JavaScript variable for each id id anchor.

In addition, you should not use a self closing a element: only XHTML supports that.

So the Markdown then becomes something like this:

## <a name='possiblePlatforms'>Possible platforms</a>
Link to [possible platforms](#possiblePlatforms).

view raw

hosted with ❤ by GitHub

In the heading, you will see the html for the destination anchor, in the link you will see the MarkDown for the internal source anchor..

The above example will render like this:


via: How to link to part of the same document in Markdown? – Stack Overflow.

Posted in MarkDown, Power User | Leave a Comment »

%d bloggers like this: