Any progress on accelerated GL?

Some time ago an accelerated version of OpenGL was introduced as an experimental feature on Jessie for the RPI. Far as I can tell there haven't been any changes/upgrades to it since the original demo release, despite regular exercises of apt-get update/upgrade/dist-upgrade.

Am I missing something?

Thanks for reading,

bob prohaska

Reply to
bob prohaska
Loading thread data ...

Put on ice. Software management isn't a strong point of the Foundation.

Reply to
A. Dumas

I thought it was because it's based on proprietary design information, so the specification couldn't be released for anyone outside Broadcom to work on it.

Reply to
Rob Morley

That's the open source video driver. I think OP asked about Wayland.

Reply to
A. Dumas

Truth be told I'm not entirely sure what I was asking about. Only that the "experimental GL driver" seemed to speed up the Neverball demo in fairly impressive fashion and that nothing further seemed to be happening.

There was some publicity about Broadcom releasing the the VC4 manual as an aid to developing a GPU-based video driver, which I _thought_ was the accelerated GL driver. The link is here:

formatting link

It's quite unclear to me just how much help such a document might be: Likely not much to a device driver writer, but maybe necessary to someone writing a code generator for a compiler.

The role of Wayland in the enterprise is rather unclear.

Thanks for reading, and any insights!

bob prohaska

Reply to
bob prohaska

VideoCoreIV-AG100-R.pdf

IIRC Wayland is a new X-server implementation that replaces the older X11 Xserver. Xservers can appear to be back to front at first glance. They own screen, mouse and keyboard and provide access to them as services to their client programs.

--
martin@   | Martin Gregorie 
gregorie. | Essex, UK 
 Click to see the full signature
Reply to
Martin Gregorie

Yes.

formatting link

Wayland is intended as a simpler replacement for X, easier to develop and maintain. GNOME and KDE are expected to be ported to it.

Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.

I haven't tried wayland recently, so I can't comment on its current robustness or suitability for anything other than a test bed. There's something to be said for a simpler implementation of X.

--
Consulting Minister for Consultants, DNRC 
I can please only one person per day. Today is not your day. Tomorrow 
 Click to see the full signature
Reply to
I R A Darth Aggie

It is not an implementation of X at all. See:

formatting link

--
http://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell

Simplified to the point of unrecognisability?

I have to say that X windows was, at its inception (rather like postcript) the implementation that could in theory do everything.

When all that was needed was the ability to do one thing supremely well. Completely Define the pixels on a page or a screen.

--
"When a true genius appears in the world, you may know him by this sign,  
that the dunces are all in confederacy against him." 
 Click to see the full signature
Reply to
The Natural Philosopher

Not even close to X.

No not really, what X windows was at its inception was a hardware independent and network transparent graphics protocol. Both of these features were new and *very* useful and they are still very useful.

Wayland retains the hardware independence but throws away the network transparency, which almost certainly makes for a local display that performs better than X can.

That's partly true if you're dealing with a self contained computer, but that's not the world X was designed in.

--
Steve O'Hara-Smith                          |   Directable Mirror Arrays 
C:>WIN                                      | A better way to focus the sun 
 Click to see the full signature
Reply to
Ahem A Rivet's Shot

WAYLAND on RPi? that's as bad as systemd! NO! THANKS! to _that_.

RPi is supposed to be *tiny* and *fast* with GPIO access and simple experimenter scripting stuff.

Worthy of note, I've been using FBSD 11 [patched for the ATX RASPI so I can shut it down properly]. It works exceptionally well, and access to GPIO ports from within a C language program is _VERY_ efficient.

Reply to
Big Bad Bob

On 02/07/17 14:27, I R A Darth Aggie so wittily quipped:

except it doesn't support a *KEY* feature of X11: it won't let you run an application on a REMOTE X SERVER. Think "headless RPi" and you'll see the OBVIOUS DISADVANTAGE here of using Wayland...

Gnome and KDE aren't the only toolkits out there. They are rather LARGE code-wise. Worth pointing out.

yes, but Wayland isn't "it". I'm definitely NOT a fan. As an OPTION? Sure, throw it in! As a REPLACEMENT for X11? They'd be doing the experimenters and open sourcers a GREAT disfavor.

Reply to
Big Bad Bob

On 02/11/17 06:32, Ahem A Rivet's Shot so wittily quipped:

and Wayland removes the ability to run a GUI application on the RPi while displaying it on another computer that's connected via a network cable, something that _I_ do a _LOT_ on headless systems. I want to be able to connect my RPi via ethernet ONLY, no keyboard, no mouse, no video. Just the ethernet. And from here, I can program it to do _anything_. And being able to run 'pluma' to edit system files, shell scripts, python code, and so on *LOCALLY* on the RPi is a *HUGE* benefit. Wayland takes ALL of that AWAY.

some of the BEST feature of the RPi surface when you run it as a HEADLESS system, and for that, running GUI applications over the ethernet is a HUGE benefit.

FYI - if you haven't tried it, here's how it works:

let's say your desktop computer is 192.168.1.50, and the RPi is

192.168.1.51 .

(on the RPI from a secure shell) export DISPLAY=192.168.1.50:0.0

(on 'your desktop computer' running the X11 server) xhost +192.168.1.51

(you may need to alter the X11 config a bit to make sure you can access X11 on the network; check for port 6001 listening on your desktop machine, and don't expose it to the outside world, i.e. block it at the firewall)

then run an application like 'pluma' or even a web client like 'midori'. It will display on the desktop computer, and interact with the keyboard/mouse there. Enjoy!

Reply to
Big Bad Bob

That is what I mean by network transparency, it was one of the more important design features of X.

--
Steve O'Hara-Smith                          |   Directable Mirror Arrays 
C:>WIN                                      | A better way to focus the sun 
 Click to see the full signature
Reply to
Ahem A Rivet's Shot

One of the most useless features, except if for some reason you actually needed it.

--
Gun Control: The law that ensures that only criminals have guns.
Reply to
The Natural Philosopher

Thats not my experience. I have two Fedora systems (F23 and F25) and can ssh into F23 from F25 or into F25 from F23 and run graphical programs without any problems. Each can use a GUI program to access files that I

*know* are only installed on the remote system.

The F25 system is definitely running Wayland but I thought the F23 system wasn't, hence the both-way logins just now. However since F23 has Wayland files installed its probably that both systems are running Wayland.

--
martin@   | Martin Gregorie 
gregorie. | Essex, UK 
 Click to see the full signature
Reply to
Martin Gregorie

You could apply that comment to any feature on anything! :-)

All features are useless unless you need them.

--
Chris Green
Reply to
Chris Green

I've not used an X server to do that in donkeys years. I just set up x11vnc and xrdp, and then access it's desktop from a PC with RDP client, or Linux with Remmina - all still Ethernet only,

---druck

--
This email has been checked for viruses by Avast antivirus software. 
https://www.avast.com/antivirus
Reply to
druck

or s imply add the -X switch to the ssh command when you connect I have this as a default setting & agree that being able to forward the Gui of a remote application is something i would not want to do without, even if it is just something as simple as thunar for file management

--
The time spent on any item of the agenda [of a finance committee] will be 
in inverse proportion to the sum involved. 
 Click to see the full signature
Reply to
alister

Such as running GUI applications from headless servers, which I have done many many times over the last quarter century or so. In my current setup I have calibre installed in a FreeBSD jail on a headless server, when I want to run the calibre GUI I just ssh into the calibre account on the jail and the GUI pops up on my workstation, or if I feel so inclined on my laptop even when I'm in a different continent using my VPN (yes I have had cause to do this).

Useless ? No! Powerful.

--
Steve O'Hara-Smith                          |   Directable Mirror Arrays 
C:>WIN                                      | A better way to focus the sun 
 Click to see the full signature
Reply to
Ahem A Rivet's Shot

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.