diff options
| author | Arna13 <[email protected]> | 2024-02-13 20:57:51 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2024-02-13 21:57:51 +0100 |
| commit | 0c3bf2d9d0d6efc281010a653dbcea0ab91eba48 (patch) | |
| tree | f12e74e9e151d5d17051b9bbadad733e9a2134b5 | |
| parent | f2a44e0e053c788cbe4279205a7d3b9628fe6e6a (diff) | |
| download | ZLUDA-0c3bf2d9d0d6efc281010a653dbcea0ab91eba48.tar.gz ZLUDA-0c3bf2d9d0d6efc281010a653dbcea0ab91eba48.zip | |
Fixing typo in README.md (#63)
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -221,7 +221,7 @@ cargo xtask --release - Why is this project suddenly back after 3 years? What happened to Intel GPU support? - In 2021 I was contacted by Intel about the development od ZLUDA. I was an Intel employee at the time. While we were building a case for ZLUDA internally, I was asked for a far-reaching discretion: not to advertise the fact that Intel was evaluating ZLUDA and definitely not to make any commits to the public ZLUDA repo. After some deliberation, Intel decided that there is no business case for running CUDA applications on Intel GPUs. + In 2021 I was contacted by Intel about the development of ZLUDA. I was an Intel employee at the time. While we were building a case for ZLUDA internally, I was asked for a far-reaching discretion: not to advertise the fact that Intel was evaluating ZLUDA and definitely not to make any commits to the public ZLUDA repo. After some deliberation, Intel decided that there is no business case for running CUDA applications on Intel GPUs. Shortly thereafter I got in contact with AMD and in early 2022 I have left Intel and signed a ZLUDA development contract with AMD. Once again I was asked for a far-reaching discretion: not to advertise the fact that AMD is evaluating ZLUDA and definitely not to make any commits to the public ZLUDA repo. After two years of development and some deliberation, AMD decided that there is no business case for running CUDA applications on AMD GPUs. |