We all knew this was coming, but my question is what's the topology? The same as the regular Pi5, with the RP1 southbridge built-in and only one PCIe lane exposed for the user, or does the CM5 leave off the RP1 and break out all five PCIe lanes for user shenanigans? They have a bare chip supply chain set up from the RP2040, so they could sell the RP1 separately for those who want to integrate it onto their carrier boards.
I kinda don't understand the point of the CM5. If you want a SoM, you're generally building something "fancy" around it… and at that point anything involving Broadcom is just about the worst choice.
I guess it gets some bump from the shared platform with the Pi, but… there's enough SoMs with good platform support at this point. And it's not like they're notably cheaper than those either?
(ed. I guess they are still cheaper than competing SoMs with roughly equal performance… but you pay the price of a poor closed platform instead)
Went down the voice assistant rabbit-hole with Home Assistant. To integrate with an LLM, you will need a separate processor (or connect to the cloud service).
Wondering if CM5 will offer enough of a boost to allow on-device LLM processing on a Home Assistant Yellow.
Guessing the answer is no, but it might be worth trying.
I've been waiting for this, now, the question is, is this a drop-in replacement for the CM4? If so, these will sell really well (and will have shortages)
Eben Upton was refusing to be drawn on specifics when Jeff Geerling and others chatted to him [1] about roadmaps recently. Nevertheless, the rumor is that CM5 will be drop-in compatible with the CM4, the details of that have been available via their NDA portal [2] for a few months now, but I think even this leak on Twitter (just a box with a label) is a breach of an NDA / embargo, so we might not know officially for a little bit yet?
The trouble with these CM's is by the time you get your hands on CM5 and engineer your custom carrier board for it (because they change the pinout every time), Pi 6 has come out.
Hopefully they're sticking with the same connectors and pinout as the CM4. The Raspberry Pi foundation considers the Compute Module line to be non-hobbiest-oriented anyway. They expect people to be building around the solution offered as a long-term product. The NEC display is a good example, because NEC is interested in driving the display for the life of the display, not in customers replacing the CM4 when its EOL.
jsheard|1 year ago
jacobmarble|1 year ago
eqvinox|1 year ago
I guess it gets some bump from the shared platform with the Pi, but… there's enough SoMs with good platform support at this point. And it's not like they're notably cheaper than those either?
(ed. I guess they are still cheaper than competing SoMs with roughly equal performance… but you pay the price of a poor closed platform instead)
postpawl|1 year ago
You’re talking about the new (and expensive) Turing RK1 and the Nvidia Jetson as alternatives?
tambourine_man|1 year ago
jimbobthrowawy|1 year ago
Quasimarion|1 year ago
https://imgur.com/a/EkcXHGh
raminf|1 year ago
Wondering if CM5 will offer enough of a boost to allow on-device LLM processing on a Home Assistant Yellow.
Guessing the answer is no, but it might be worth trying.
johann8384|1 year ago
RIMR|1 year ago
jacobmarble|1 year ago
mdotk|1 year ago
Gasp0de|1 year ago
cicloid|1 year ago
ceinewydd|1 year ago
[1] https://www.tomshardware.com/raspberry-pi/raspberry-pi-compu...
[2] https://pip.raspberrypi.com/categories/945-forward-guidance
MuffinFlavored|1 year ago
Pet_Ant|1 year ago
gorkish|1 year ago
dheera|1 year ago
sircastor|1 year ago
srott|1 year ago