^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) ====
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) TODO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) ====
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) The OpenRISC Linux port is fully functional and has been tracking upstream
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) since 2.6.35. There are, however, remaining items to be completed within
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) the coming months. Here's a list of known-to-be-less-than-stellar items
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) that are due for investigation shortly, i.e. our TODO list:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) - Implement the rest of the DMA API... dma_map_sg, etc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) - Finish the renaming cleanup... there are references to or32 in the code
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) which was an older name for the architecture. The name we've settled on is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) or1k and this change is slowly trickling through the stack. For the time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) being, or32 is equivalent to or1k.