> Qualcomm has most of the critical functions working inside.. Linux 6.9.. critical functions include UEFI-based boot support along with all the standard bootloaders like Grub and systemd.. Functions that are being worked on for future iterations of Linux include additions to battery support, on-board display connectivity, external DisplayPort connectivity, sleep and wake-up functions on the GPU, camera support, video support, better CPU frequency support, and speaker/mic/headset enablement. These functions are expected to arrive in Linux 6.10 and 6.11.
How? The Raspberry Pi and company run on ARM just fine? Assuming all the hardware components are the same or similar, I'm not seeing how it could be drastically worse. I guess missing drivers?
A lot of what makes x86 machines so interchangeable is ACPI, which automates things like device enumeration - having drivers is one thing, not knowing how to even find what hardware is installed is a much bigger hurdle.
It's why ARM support is such a vendor-sensitive roller coaster. MacOS on Apple is easy, since they know their hardware, the RasPi foundation puts serious effort into making Linux etc. work on RasPis, but just look at how much Linux struggles on Macbooks, or how hard it is to run a current kernel on a 3 year old mystery Raspi clone that had no documentation and shipped with a custom Linux kernel binary.
The situation is slooowly improving, but we're far from there yet.
situation will only improve when arm is made acessible to the masses..
i think this will go a bit like secure boot.. it existed for ages, it only became a real available in every computer when MS got behind it and made it happen..
now you can install even most linux distros without a problem and it just work..
arm will be a pain in the beginning but having microsoft backing it might the best way to make it happen..
i am curious to see how microsoft, that historically aim to keep backward compatibility as much as possible, will handle such a braking change like this move to arm..
but one could argue that this breaking change might be what they need to just get rid of some legacy stuff..
> The Raspberry Pi and company run on ARM just fine?
Not in my experience. Maybe things are better now, but as of a year or two ago you still couldn't use a generic kernel on there. You had to have special patches. There's also a fair amount of packages that won't build on ARM. Raspbian is a pretty good experience and it shows they have put serious effort into it, but venture away from that and you're rolling some dice.
That "check_c_source_compiles" function should first test if the provided code snipped is "valid C code in general" and only then check if it compiles in given system.
Maybe not! That would require changeing the whole development of the beetle, and maybe the intermediate stages would not be beneficial. To give a terrible example, if you have a car and need a camper, you could rebuild the car into a camper but you would have to change everything and would not have a useable car for a long time. If instead you bought a trailer with a tent on it, you could build a perfect camping trailer over time step by step and have still use the car.
This is my case, my trick is to imagine pleasurable fantasy scenarios and go over the smallest details.
I go a little bit more meta, and start imagining myself sleeping.
Kind of… say I’m part of the Start Trek crew. I imagine how would it be to sleep in the Enterprise. How is the room? What furniture is there? Is there a window/screen showing the outside? Etc…
Sounds similar to my trick, although I'm not sure if I really delve into details. I think the main purpose is to push out everything else from my mind, since whenever I have insomnia, it's not because I'm looking at my phone, but because I can't get something out of my mind.
I don’t know if that matters unless you think about things that require action.
My own experience is that if I think something needs to be acted on, and it’s very quick or very urgent, I just do it and go back to bed. If it’s neither, I write it down. I find either of those to be easier than trying to sleep with the endless nagging by the back of my brain.
I find it infuriating. I have no idea how people live with those things. There's no reason you can't have buttons below a clickpad. It's like they just hate precision and users being able to right click without moving their thumb.
Western advisors have both underestimated the Ukrainians and overestimated the Russians since day one. First they thought the Russians would capture Kiev in a week, then thought there would be some negotiated settlement.
Plus most Western governments (other than Poland and UK) went "wobbly" as Margaret Thatcher was reported to have said. Biden's security advisors didn't want to have the conflict escalate, and much of the EU felt the same way. This led to hesitancy on providing anything that could be "offensive." Providing Stingers and Javelin were fine, but ATACMS, tanks, F-16? Nope.
Only once Ukraine demonstrated both a chance of surviving and even winning did this mindset begin to change. Every Ukrainian victory or Russian defeat encouraged the West to provide more equipment and munitions. But we're still providing too little.
Both Poland and the UK really deserve huge amounts of credit for their stalwart support of Ukraine (as well as the Baltic states). The US may be providing the most in terms of raw dollars, but without Poland and Ukraine pushing as hard as they have, Ukraine would be in a much tougher situation.
I asked if we should put people in jail for reproduction, as children do not give any consent to being born, will suffer in life and die in the end. Both debaters started patting their backs that reproduction is not unethical but something should be done with people who neglect their child.
I very often see "reconnect loops" in various codebases and I wonder are they necessary? Wouldn't the same effect be achieved by for example increasing timeouts or some other connection parameter?
They’re a bit of a feature of the connection-oriented nature of TCP as the other reply mentions. If the server process crashes and restarts for example, the client will be told that its previous connection is not valid anymore. Basically TCP lets client and server assume that all bytes put into the socket after connect()/accept() will end up at the other side in that same order. Each time there is an error that violates that assumption, the connection needs to be explicitly “reset”.
For TCP the state required to maintain the socket in the kernel is invalidated on error and needs to be reset. The only way to do this is to explicitly perform the connection setup again. An extended timeout only delays this process since the remote side will have invalidated its state as well.
UDP packets require no connection but you still might see some sort of re-synchronization code to reset application state which could be called "reconnect".
