What It Actually Takes to Drive an Intel Arc A770
Good documentation gets you past the product page. What's underneath is PCIe, MMIO, firmware, command submission, and a long staged plan instead of one heroic attempt at everything at once.
Good documentation gets you past the product page. What's actually underneath — the part nobody puts in the marketing material — is PCIe enumeration, memory-mapped I/O, firmware handshakes, VRAM and GPU address space management, command submission and execution queues, synchronization, execution contexts, fault handling, reset behavior, CPU/GPU memory coherency, the media engines, and command validation so a bad or hostile submission can't take the whole GPU down with it. That's the actual job description, and none of it is optional if you want something more serious than "a triangle appeared once."
Why I'm not trying to do all of that at once
I've already got one very fresh scar from trying to skip ahead — that's the whole point of the Iris entry a few weeks back. So the plan for the Arc A770 work is explicitly staged, on purpose, in an order I chose specifically to avoid repeating that mistake.
The staged plan
First: discover and identify the device — get the platform to actually see and recognize the card as a real, present piece of hardware. Second: establish ownership — make sure exactly one part of the system has authority over it, no ambiguity, no two components racing to think they're in charge. Third: basic transfer and copy operations — move data to and from the card reliably before asking it to do anything clever. Fourth: controlled compute or render work — small, bounded, verifiable operations, not open-ended workloads. Fifth: measure and reassess before going further, honestly, based on what actually happened rather than what I hoped would happen. Sixth: media capabilities, later, once the foundation underneath them is solid. Seventh: display ownership, later still, and only if it turns out to actually be warranted rather than assumed.
That ordering is deliberate. Every step depends on the one before it actually being solid, not just apparently working. That's the lesson from Iris, applied on purpose this time instead of learned the hard way a second time.
A practical detail: headless, for now
The development machine's Intel UHD 630 integrated graphics can handle the actual display output while the Arc A770 operates headless — doing compute and, eventually, media work without also being asked to drive a monitor. That separation keeps the two concerns from tangling with each other while the A770 side is still young, and it means a mistake on the Arc side doesn't cost me my actual screen.
What this entry is not claiming
I want to be really clear, because it would be easy for this entry to read as further along than it is: this is not a finished driver. This is not even a mostly-finished driver. This is the plan, the constraints, and the ordering I'm committing to in public so that later entries can be measured honestly against it instead of me quietly redefining "done" after the fact. Progress on where this staged plan actually stands shows up in the status-update entries later in this journal, and I'm going to keep those honest about exactly which of these seven steps are real and which are still aspirational.
Next entry steps back from the GPU work entirely and takes stock of what Project Nu-Day, as a whole, actually managed to prove — because there's real evidence there, and it deserves an honest accounting before I get into why the project ultimately didn't survive in its original form.
Originally published on The Weekend Report: https://theweekendersproject.com/report/what-it-actually-takes-to-drive-an-intel-arc-a770