Row 91217

Row ID: 91217 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 91217 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

You probably don’t.

What do you need is an ARM CPU that can be connected to your MacBook, and a way to handover that app code to that CPU. It’s.. technical.

But in theory you should be able to connect an arm CPU on the thunderbolt bus, as the equivalent of a second & third GPU.

I don’t think connecting an android phone up by USB would work, because of the overhead that the USB bus introduces, and its performance characteristics.

However, an arm CPU powered by a USB C Thunderbolt port, exposed as if it was a GPU would work fine, I imagine. It’s extremely complicated, from the perspective that it would need to be both connected like a GPU, but still pass through things to its on-die GPU.

Eg.

Mac Intel CPU

PCIe Bus over thunderbolt

Using GPU Connection, ARM CPU

ARM GPU

I’m still sure the fastest bus on older platforms remains the PCIe Bus, and this is exposed over thunderbolt, and all old apple macs have a thunderbolt port.

My thunderbolt 1 port has a mini display port connector. I use a genuine Apple reversible Thunderbolt miniDP to type C adapter. I use a non-genuine miniDP thunderbolt cable, a very short one.

The type C male connector that carries the thunderbolt protocol with the PCI Bus, I connect it to a thunderbolt 2 hub, mine is a HP. That hub is powered. This is important as the Apple reversible thunderbolt adapter doesn’t pass power. It took while to work out what connectors might work.

From that I have a display port output, a bunch of additional USB3 ports functional additional headphone port, and I have another USBC style Thunderbolt port that I have a high-speed thunderbolt 3 NVMe disk connected to, for large storage like my photo library, which is over one terabyte. That disk works faster than the internal Apple disk, and it works faster than external USB3 disks.

For me to be able to use the things I described above, I would need to disconnect that high-speed thunderbolt 3 NVMe disk from the type C thunderbolt 2 port (that only works at a maximum thunderbolt 1 speed over the MiniDP bus on the MacAir I have). And use that port.

Then there would be some reasonable performance characteristics, I am imagining.

FieldValue
text You probably don’t. What do you need is an ARM CPU that can be connected to your MacBook, and a way to handover that app code to that CPU. It’s.. technical. But in theory you should be able to connect an arm CPU on the thunderbolt bus, as the equivalent of a second & third GPU. I don’t think connecting an android phone up by USB would work, because of the overhead that the USB bus introduces, and its performance characteristics. However, an arm CPU powered by a USB C Thunderbolt port, expos…
label r/chatgpt
dataType comment
communityName r/ChatGPT
datetime 2024-05-25
username_encoded Z0FBQUFBQm5Lak1zTUp5Yks3cWF6Wk1sTEVnVG5mOENzbmFnSi0xcTB1NFYya1Z1YnlvQi1MUW1zSGZNb3RPUjI4MGtNc2JCWjRwNTVEdEp5WE5MeGJUZy0wajFUVnZyZ3c9PQ==
url_encoded Z0FBQUFBQm5Lak85WmFjLW53ZUlCTzFqSVc5ODNmTTZwX2w1OTduOHUyeElQb2tYOVZ1LWF5WGVMaDB2VnB5S3psbktsaVc1RjdYR1N3TU5qZWNPSnhvYS1tbm5EY0xjQUZuM21uNjFwaWNISXNFZEtFeDd6MUNOTjE4Xzd1Z1N2NktuOGVEM0JxTXhGRWNrTDdlVnd4a2ZYSFVNMHp1U3ZFNTRoeWtETzFTcFA5RmZUR2hBYVM3RnNLNGR5VGJnU3Ztcnd5T2ZYVzlFYTQ3dzhiVGl6Vlh2MFBtMkJNRzlUZz09

Raw Record

{
  "text": "You probably don’t. \n\nWhat do you need is an ARM CPU that can be connected to your MacBook, and a way to handover that app code to that CPU. It’s.. technical.\n\nBut in theory you should be able to connect an arm CPU on the thunderbolt bus, as the equivalent of a second & third GPU.\n\nI don’t think connecting an android phone up by USB would work, because of the overhead that the USB bus introduces, and its performance characteristics.\n\nHowever, an arm CPU powered by a USB C Thunderbolt port, exposed as if it was a GPU would work fine, I imagine. It’s extremely complicated, from the perspective that it would need to be both connected like a GPU, but still pass through things to its on-die GPU. \n\nEg. \n\nMac Intel CPU\n\nPCIe Bus over thunderbolt \n\nUsing GPU Connection, ARM CPU\n\nARM GPU\n\nI’m still sure the fastest bus on older platforms remains the PCIe Bus, and this is exposed over thunderbolt, and all old apple macs have a thunderbolt port. \n\nMy thunderbolt 1 port has a mini display port connector. I use a genuine Apple reversible Thunderbolt miniDP to type C adapter. I use a non-genuine miniDP thunderbolt cable, a very short one. \n\nThe type C male connector that carries the thunderbolt protocol with the PCI Bus, I connect it to a thunderbolt 2 hub, mine is a HP. That hub is powered. This is important as the Apple reversible thunderbolt adapter doesn’t pass power. It took while to work out what connectors might work.\n\nFrom that I have a display port output, a bunch of additional USB3 ports functional additional headphone port, and I have another USBC style Thunderbolt port that I have a high-speed thunderbolt 3 NVMe disk connected to, for large storage like my photo library, which is over one terabyte. That disk works faster than the internal Apple disk, and it works faster than external USB3 disks.\n\nFor me to be able to use the things I described above, I would need to disconnect that high-speed thunderbolt 3 NVMe disk from the type C thunderbolt 2 port (that only works at a maximum thunderbolt 1 speed over the MiniDP bus on the MacAir I have). And use that port.\n\nThen there would be some reasonable performance characteristics, I am imagining.",
  "label": "r/chatgpt",
  "dataType": "comment",
  "communityName": "r/ChatGPT",
  "datetime": "2024-05-25",
  "username_encoded": "Z0FBQUFBQm5Lak1zTUp5Yks3cWF6Wk1sTEVnVG5mOENzbmFnSi0xcTB1NFYya1Z1YnlvQi1MUW1zSGZNb3RPUjI4MGtNc2JCWjRwNTVEdEp5WE5MeGJUZy0wajFUVnZyZ3c9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak85WmFjLW53ZUlCTzFqSVc5ODNmTTZwX2w1OTduOHUyeElQb2tYOVZ1LWF5WGVMaDB2VnB5S3psbktsaVc1RjdYR1N3TU5qZWNPSnhvYS1tbm5EY0xjQUZuM21uNjFwaWNISXNFZEtFeDd6MUNOTjE4Xzd1Z1N2NktuOGVEM0JxTXhGRWNrTDdlVnd4a2ZYSFVNMHp1U3ZFNTRoeWtETzFTcFA5RmZUR2hBYVM3RnNLNGR5VGJnU3Ztcnd5T2ZYVzlFYTQ3dzhiVGl6Vlh2MFBtMkJNRzlUZz09"
}
Explore Dataset Explore Row

Entry Information