I believe the OSS part of this oban library covers a lot of the celery feature set and is free as well. You can run multiple nodes and knock yourself out without needing more infra than the existing postgres.
Oban has been a free and OSS project in Elixir for ages. There are some more advanced bits that are paid and that sustains the people that make it.
If you like Celery. Great. This is a different take. I didn't enjoy celery last I needed it but never got super familiar.
I wonder if the limitation of the application processor and Linux starting is mostly a default for the standard OS or an actual limitation. Typically with a hybrid SoC like this part of the point is that you can use the micro-controller as the power efficient thing that decides when the bigger application processor should boot or not. I'd be curious to see if that's possible with this one.
Shipping only Debian to start is fine by me. It has to start somewhere. And they seem quite responsive to making it work with other things. James Harton is plugging away at getting it working with Nerves (https://nerves-project.org) and he has it running with Buildroot already. Current repo: https://github.com/jimsynz/buildroot
I share the sentiment that I don't trust that there won't be issues with Qualcomm over time. That company does have some pretty relevant chips though so I'm hopeful this means that we see them become more accessible on SBCs and embedded boards. I feel like they've been popping up more and more.
If they value this investment in Arduino they should now have a small wing of the company that pushes for things to be more open and even if they only consider that a marketing vector, if things are opened up for that purpose, quite possibly a win. But Arduino might also be absorbed into the amorphous megablob and this is the last we see. I hope not.
I don't think this board is that weird. It is just coming from the Arduino side and moving into Raspberry Pi territory. Personally I want to run Nerves on the application processor and get some practice with Zephyr on the MCU. Seems to already be supported: https://docs.zephyrproject.org/latest/boards/arduino/uno_q/d...
Also why no mention of the LED matrix. This is something RPi devices fail at. Providing som default way of neat output. First time plugging this in it starts doing fun stuff.
I remember back when Nvidia was aiming to aquire ARM, there was a whole thread of discourse that I think even Huang himself had spoken to, about how the acquisition would transform Nvidia, would remake who they are and what they do. ARM themselves have rarely been an exemplary citizen, with driver support for their GPUs for example having only gotten respectable in the past couple years. But ARM was still a multi-lareral company. It would have been a different NV: Nvidia as head of an ecosystem, a steward for many, versus what Nvidia has been, Nvidia as a moat keeper with only their bespoke Linux4Tegra (L4T) for example. That was going to be the big change.
Qualcomm certainly seems to be saying that they want to be a different company. That they want market-share among people building products. The example elsewhere of the e-scooters using RPi's seems like the market space Qualcomm is striving to open up.
Your middle paragraphs capture a lot of the sentiment. Qualcomm is a hard company to trust. There have been a lot of neat weird interesting things that have gotten mainlined, and it's cool to see, but most products are incredibly hard to develop for, push you into vendor Board Support Packages, and don't have docs available. This chip similarly lacks technical docs.
But it sure is exciting to think maybe Qualcomm might actually want embedded market share beyond the high end of phones, routers, and laptops. And if they do want this market share, they're going to have to change.
Modern Qualcomm SoCs have "RPM" - a dedicated always-on ARM core for managing clocks, sleep modes and power states. And usually at least one low power DSP core that can be up when the rest of the system is down.
Good luck getting your hands on any docs on how to use any of that shit tho.
It seems to be RJ11 and they might be spec:ed slightly differently (thicker leads?) to power motors. I get the impression it is mainly to control what can be used in competitions.
I doubt it is Ethernet at all, so it wouldn't be Power-over-Ethernet. Just some useful connectors and wires making for an appropriate cable. Also seems like you can make your own perfectly fine. Or they might melt. I suppose try it.
I think Intel wants to stay alive so they are looking for a lifeline and the current administration wants to bring chip production into the US.
Intel's death would be very embarassing to that whole effort. So Intel has incentives (survival) and the administration has incentives (jobs in the US). The method is "whatever can be claimed as a win".
No US party seems particularly capable or keen to hold an ideological line but especially not the GOP from what I've seen. Not saying other countries have particularly impressive parties either. I'm less than thrilled with ours over here.
> I think Intel wants to stay alive so they are looking for a lifeline
I'm not sure Intel was asking for this.
It seems like a better approach would've been to broker a deal (he likes deals, right?) where companies like Apple and Nvidia (companies that are currently dependent on TSMC) would've been incentivized to make investments in Intel.
I agree, and I think the government’s incentive might also be a having strategic production capability in the US. Maybe they’re concerned about TSMC’s future with the tension between China and Taiwan?
That's all fine, but this is definitely heading into socialist territory. I guess they're out of ideas and this is how they incentivize. The free markets have failed?
My hypothesis is that this is government response (own stake in Intel) to another government’s action (hint take over of Taiwan) and as such is outside the free market. But I have no evidence to support it, it’s just an opinion and it could be that they view Intel as “too big to fail” or something like that as you suggest.
> the current administration wants to bring chip production into the US
Please don't credit the current administration with wanting to do something beneficial here. Biden signed the CHIPS and Science Act in 2022 for $52.7 billion is appropriations for semiconductor R&D.
That's why no credit should be given. With the Infrastructure Investment and Jobs Act (2021, Biden) which allocates 546-715 billion to infrastructure (see: jobs and improvements to daily lives of Americans) and the CHIPS and Science Act (2022, Biden) which allocates 52.7 billion to American semiconductor research and manufacturing we had major sources of government provisions from 2021 to 2024. The Trump admin continuously fails to implement parts of the legislation that they disagree with, and claims all credit for implementing the parts that they agree with.
I've done this. The NIF worked as in that it ran and was a correct enough NIF. It did not work in terms of solving what I needed it to do. Iteration was a bit painful because it was tangled with a nasty library that needed to be cross-compiled. So when I made a change it seg faulted and I bailed.
I essentially ran out of patience and tried another approach. It involved an LLM running C code so I could check the library output compared to my implementation to make sure it was byte-for-byte.
The C will never ship. I don't have practice writing C so I am very inefficient at it. I read it okay. LLMs are pretty decent help for this type of scrap code.
More in the topic. Good that Windows Update will suck less. Did the Discover-something-or-other-imply less start-memu ads, I couldn't tell..
reply