假使打電腦史上第一次流行之個人
Apple II
，到成為歷史的
IBM PC
作個比較，這塊三十五美元的
Raspberry Pi 3 Model B
誠是過往夢寐以求之超級電腦的耶！！？？
也許正因樹莓派 3 令人驚豔之高『性價比』，遂引來『 PCMag 』的青睞，榮登 EDITORS’ CHOICE ︰
Raspberry Pi 3 Model B
Editor Rating: Excellent (4.0)
-
Pros
It’s a ＄35 computer! Drastically improved performance, feature set over the previous iteration. -
Cons
Only for the adventurous. Software, setup may be challenging to some. -
Bottom Line
The Raspberry Pi 2 Model B is the same size and the same price as its predecessor, but major hardware improvements make this mini computer much more delectable overall.
於是有人想？？！！
Can you use the Raspberry Pi 3 as your work PC?
We spent a week working on the Raspberry Pi 3, to see how the ＄35 machine matched up to laptops costing more than 10 times its price.
但思事物應其時代而生，因其環境而長，消長自有其故。也許根本不必墜入能否用為『個人電腦』 PC 之迷思？？只需考慮合不合於『應用目的』就好！！或許該讀讀教主之
The 5 things that would have made Raspberry Pi 3 better
Some key technologies could have made Raspberry Pi 3 much better as a PC and board for IoT devices
What can you fit into a Raspberry Pi board while still keeping the price to ＄35? That’s a question Raspberry Pi CEO Eben Upton wrestled with when planning the third version of the product.
He opted for a faster 64-bit ARM processor and wireless features so Raspberry Pi 3 could be a PC as well as a board for cool new devices. Other features had to be left out.
But Upton has a never-say-die attitude — if a new technology is available at a reasonable cost, it will be added to future versions of the Raspberry Pi.
“We’ll take what we can get,” Upton said.
Here are five technologies that could’ve made the Pi 3 a better computer but didn’t make the cut, due to cost, incompatibility and other issues. They could be available in the next iteration of the computer.
─── 《W!O+ 的《小伶鼬工坊演義》︰通往樹莓派 3 之 HEARSAY PC》
誠如 Eben 先生之態度︰永不言敗 never-say-die 。
再次將樹莓派 3B 升級成 3B+ 了。
至於宜乎不宜『桌面』應用乙事？
Raspberry Pi 3 B+ vs. Desktop
Re: Raspberry Pi 3 B+ vs. Desktop
Impossible to answer without a more specific definition.
As a computer doing general office work, Word processing/ Spreadsheets/ Database/ Presentation/ Internet browsing, the Pi 3B+ can easily cope*
For programming (ie compiling) a bit sluggish but still quite capable.
Gaming would be where you could be disappointed.
Compatibility would be the major issue, you’d need to find an equivalent open source software package that would meet your needs.
FWIW, I’m just as happy using my Pi’s as I am using my laptop.
*Additional storage may be required.
縱然見仁見智，不過多少帶點『感覺』意謂！
據知目前 Linux kernel
drm/vc4 Broadcom VC4 Graphics Driver
The Broadcom VideoCore 4 (present in the Raspberry Pi) contains a OpenGL ES 2.0-compatible 3D engine called V3D, and a highly configurable display output pipeline that supports HDMI, DSI, DPI, and Composite TV output.
The 3D engine also has an interface for submitting arbitrary compute shader-style jobs using the same shader processor as is used for vertex and fragment shaders in GLES 2.0. However, given that the hardware isn’t able to expose any standard interfaces like OpenGL compute shaders or OpenCL, it isn’t supported by this driver.
Display Hardware Handling
This section covers everything related to the display hardware including the mode setting infrastructure, plane, sprite and cursor handling and display, output probing and related topics.
Pixel Valve (DRM CRTC)
In VC4, the Pixel Valve is what most closely corresponds to the DRM’s concept of a CRTC. The PV generates video timings from the encoder’s clock plus its configuration. It pulls scaled pixels from the HVS at that timing, and feeds it to the encoder.
However, the DRM CRTC also collects the configuration of all the DRM planes attached to it. As a result, the CRTC is also responsible for writing the display list for the HVS channel that the CRTC will use.
The 2835 has 3 different pixel valves. pv0 in the audio power domain feeds DSI0 or DPI, while pv1 feeds DS1 or SMI. pv2 in the image domain can feed either HDMI or the SDTV controller. The pixel valve chooses from the CPRMAN clocks (HSM for HDMI, VEC for SDTV, etc.) according to which output type is chosen in the mux.
For power management, the pixel valve’s registers are all clocked by the AXI clock, while the timings and FIFOs make use of the output-specific clock. Since the encoders also directly consume the CPRMAN clocks, and know what timings they need, they are the ones that set the clock.
………
已經相當完整。
有興趣『桌面』環境者或可於 /boot/config.txt 裡添加
dtoverlay=vc4-kms-v3d
自己品味哩◎
pi@raspberrypi:~dmesg | grep vc4 [ 4.904733] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi mapping ok [ 4.941989] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4]) [ 4.942343] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4]) [ 4.942440] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4]) [ 4.942707] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 4.942933] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 4.943143] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 4.965407] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4]) [ 4.968929] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0 [ 5.105740] vc4-drm soc:gpu: fb0: frame buffer device pi@raspberrypi:~ $