17 ms·
> But I think the overarching point is true: now desktop and laptop makers can't just pretend that having a hot and/or slow, clunky, noisy x86-based architectur
by ekianjo 6y ago
> But I think the overarching point is true: now desktop and laptop makers can't just pretend that having a hot and/or slow, clunky, noisy x86-based architecture is just a fact of life. I hope and expect that it'll help create a new generation of ARM-based laptops and maybe even desktops that will run cool and smooth.
Be careful what you wish for. X86 is the most open architecture right now. ARM, on the other hand, has locked bootloaders, messy device trees and so on. You can see that virtually every Linux distro running on an ARM SOC needs some specific tweaks.
- daenney 6y ago> Be careful what you wish for. X86 is the most open architecture right now You might want to take a look at PowerPC/OpenPOWER. ARM not being very open is mostly because there's been limited development interest in it, aside from specialised devices, and those companies have no real need or interest to have open things. Doesn't mean ARM itself can't evolve past it.
- Koshkin 6y ago> ARM not being very open is mostly because there's been limited development interest in it, aside from specialised devices That's an extremely weird thing to say...
- throwaway894345 6y agoI know very little about this space, but presumably that will change if/when a significant portion of the laptop space (and probably the server space as well) moves from x86 to ARM? It might be painful for early adopters for a few years, but I would expect this stuff to get ironed out in time, no?
- buran77 6y agoNo, that ship has sailed. Anything new that comes now can be built according to the expectations smartphones have set over the past decade and a half. Closed systems that are treated like disposable items. Even PCs in their mobile incarnation are now far less open and flexible than they used to be. The reason PCs are still open is historical, they started like this and people can't really see PCs any other way but they're a dying breed and whatever comes after is a different game with different rules. We'll have some niche manufacturer building something more open for the small segment of enthusiasts.
- throwaway894345 6y agoSadly, I find this persuasive.
- haberman 6y ago"Developer Mode" exists in many new devices, eg. Chromebooks, Oculus Quest, Android phones.
- buran77 6y agoThere's a difference between swapping or adding any of the many standardized components you want or installing pretty much any operating system you can think of on your PC, compared to enabling "developer mode" on an Oculus Quest. The fact that so many people casually say how a platform is open or flexible because if you jump through enough hoops you get to make some minor modifications to your device, or applauding the openness of a system for allowing you to sideload standard apps is the reason manufacturers don't see a need to propagate the PC philosophy anymore. Too many users grew up with this new model so they don't see the loss. None of the devices you mention are user serviceable in any way hardware-wise, the software is almost always locked onto the device and there's no easy, or even supported way of changing it. And if you do change it you just get a small variation of the same software. Your phone may get a slightly degooglified version of Android but it's unlikely you'll get it to run Ubuntu, Windows, or a FreeBSD without a massive investment in time and knowledge.
- haberman 6y agoMy understanding is that developer mode on Android and Chromebook will unlock the bootloader. Software wise, that's about as user-hackable as you can get. It's true that the Oculus Quest is not as open. I don't expect or even really want to swap hardware on these devices: if that was a priority for me I would get a PC, Arduino, Raspberry Pi, etc. I get the desire to tinker and customize, but from where I'm sitting I have plenty of opportunity to do that. I also don't expect the device manufacturers to do the work to make Ubuntu or FreeBSD run. They didn't do that for PCs, the community did.
- 6y ago
- ogre_codes 6y ago> X86 is the most open architecture right now. x86 is not "Open" in any fashion. You can't license x86 even for a fee, let alone free. While ARM isn't open either, it is by comparison far more available to license at reasonable cost. > ARM, on the other hand, has locked bootloaders It also has open/ unlocked boot loaders. One of the advantages of licensable technology like this is you can have a lot of different architectures with the same underlying core. With x86, you get whatever the Intel/ AMD duopoly decide to ship you.
- AsyncAwait 6y ago> x86 is not "Open" in any fashion. You can't license x86 even for a fee, let alone free. OP is not talking about being able to manufacture x86 CPUs kind of open, that's useless for most folks. They're talking about being able to install any OS, drivers being fairly universal, no device specific out of tree kernel patches for the vast majority of PCs, no device trees etc.
- ogre_codes 6y agoIt's a lousy use of the word "Open" in a discipline where Open has a fairly specific meaning. I mentioned that as well though. Using your goofy definition of Open, x86 is no more "Open" than ARM. Pinebook and Raspberry Pi both use no bullshit ARM setups. With ARM, how accessible the architecture is is 100% dependent on the implementation which vary greatly by manufacturer.
- AsyncAwait 6y ago> Using your goofy definition of Open If I buy any x86 PC, chances are I can install mainline Linux on it. Picking up any particular recent ARM SoC and the chance of doing so is much, much less. The M1 included, after all. > Pinebook and Raspberry Pi both use no bullshit ARM setups. Both of these took considerably longer to get mainline support that your average x86 hardware needs.
- ogre_codes 6y ago
- erk__ 6y agoI am pretty sure the most open at the moment are OpenPOWER and RISC-V, while there is is MIPS I am sure how open it is.
- ekianjo 6y agoCan you buy a desktop with those right now?
- josephcsible 6y agoPOWER: Yes, https://www.raptorcs.com/content/base/products.html https://www.raptorcs.com/content/base/products.html RISC-V: Not really. The closest thing is probably https://www.sifive.com/boards/hifive-unmatched https://www.sifive.com/boards/hifive-unmatched
- ekianjo 6y ago> POWER at prohibitive costs. So not really an option...
- josephcsible 6y agoThey don't seem that expensive. They're high-end machines themselves, and their pricing seems on-par with high-end x86 workstations, like the Dell Precision series.
- matheusmoreira 6y ago> messy device trees Can you please elaborate?
- ekianjo 6y ago> * the x86 world resolves around standards such as ACPI, BIOSes and general-purpose dynamic buses. > * ACPI normalises every single piece of hardware from the perspective of most low-level peripherals. > * the BIOS also helps in that normalisation. DOS INT33 is the classic one i remember. > * the general-purpose dynamic buses include: - USB and its speed variants (self-describing peripherals) - PCI and its derivatives (self-describing peripherals) - SATA and its speed variants (self-describing peripherals) > exceptions to the above include i2c (unusual, and taken care of by i2c-sensors, which uses good heuristics to "probe" devices from userspace) and the ISA bus and its derivatives such as Compact Flash and IDE. even PCMCIA got sufficient advances to auto-identify devices from userspace at runtime. > so as a general rule, supporting a new x86-based piece of hardware is a piece of piss. get datasheet or reverse-engineer, drop it in, it's got BIOS, ACPI, USB, PCIe, SATA, wow big deal, job done. also as a general rule, hardware that conforms to x86-motherboard-like layouts such as the various powerpc architectures are along the same lines. > so here, device tree is a real easy thing to add, and to some extent a "nice-to-have". i.e. it's not really essential to have device tree on top of something where 99% of the peripherals can describe themselves dynamically over their bus architecture when they're plugged in! > now let's look at the ARM world. > * is there a BIOS? no. so all the boot-up procedures including ultra-low-level stuff like DDR3 RAM timings initialisation, which is normally the job of the BIOS - must be taken care of BY YOU (usually in u-boot) and it must be done SPECIFICALLY CUSTOMISED EACH AND EVERY SINGLE TIME FOR EVERY SINGLE SPECIFIC HARDWARE COMBINATION. > * is there ACPI present? no. so anything related to power management, fans (if there are any), temperature detection (if there is any), all of that must be taken care of BY YOU. > * what about the devices? here's where it becomes absolute hell on earth as far as attempting to "streamline" the linux kernel into a "one size fits all" monolithic package. > the classic example i give here is the HTC Universal, which was a device that, after 3 years of dedicated reverse-engineering, finally had fully-working hardware with the exception of write to its on-board NAND. the reason for the complexity is in the hardware design, where not even 110 GPIO pins of the PXA270 were enough to cover all of the peripherals, so they had to use a custom ASIC with an additional 64 GPIO pins. it turned out that that wasn't enough either, so in desperation the designers used the 16 GPIO pins of the Ericsson 3G Radio ROM, in order to do basic things like switch on the camera flash LED. > the point is: each device that's designed using an ARM processor is COMPLETELY AND UTTERLY DIFFERENT from any other device in the world. https://lists.debian.org/debian-arm/2013/05/msg00009.html https://lists.debian.org/debian-arm/2013/05/msg00009.html
- sliken 6y agoThe apple M1's don't have locked bootloaders, there's a warning in the firmware about enabling unsigned booting, but it's just warning. That's why there's an attempted linux port underway.