Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

lwn.net

Post reply on HN
Print view View original

31–40 of 54 posts

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#31

Post by afdbcreid »

pinkmuffinere wrote: post #30
afdbcreid wrote: post #26

Earlier quoted context omitted.

As a Hebrew speaker I cannot understand how you came into this conclusion. The closest I can think of is ת-י-ר, which is the root of being in a trip.

Oh sorry, i thought it was also in Hebrew but it looks like it is not. I would expect the same root to show up in other Semitic languages, but at least in Arabic it’s ط ي ر

ChatGPT claims that the same or similar root does exist in the meaning "bird" or "to fly" in a lot of other Semitic languages. Interestingly, it also claims that there is some correspondence in Hebrew, in the noun תור (tor) that represents a specific kind of bird (turtledove).

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#32

Post by not_your_vase »

What is not clear for me, is the purpose of this project. What I could find is that it wants to be a drop-in replacement of PanVK. But since PanVK exists, I fail to see the point. Is PanVK similar to xserver, that is not salvageable? Or is it just RiiR? That's also a fine reason, but I'd expect that more for personal hobby projects.

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#33

Post by einpoklum »

afdbcreid wrote: post #31
pinkmuffinere wrote: post #30

Earlier quoted context omitted.

Oh sorry, i thought it was also in Hebrew but it looks like it is not. I would expect the same root to show up in other Semitic languages, but at least in Arabic it’s ط ي ر

ChatGPT claims that the same or similar root does exist in the meaning "bird" or "to fly" in a lot of other Semitic languages. Interestingly, it also claims that there is some correspondence in Hebrew, in the noun תור (tor) that represents a specific kind of bird (turtledove).

Indeed, in Hebrew, תור (تور, Tor) is the word for turtle-dove.

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#34

Post by cwillu »

ceteia wrote: post #29
monocasa wrote: post #28

Earlier quoted context omitted.

Dave Airlie is saying that the subsystem maintainers are themselves choosing to move to Rust.

But what about this statement that Linus wrote: > That's been made clear pretty much from the very beginning, that nobody is forced to suddenly have to learn a new language, and that people who want to work purely on the C side can very much continue to do so. If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.

Nothing is happening “suddenly”, and it remains true that “people who want to work purely on the C side can very much continue to do so”.

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#35

Post by ceteia »

cwillu wrote: post #34
ceteia wrote: post #29

Earlier quoted context omitted.

But what about this statement that Linus wrote: > That's been made clear pretty much from the very beginning, that nobody is forced to suddenly have to learn a new language, and that people who want to work purely on the C side can very much continue to do so. If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.

Nothing is happening “suddenly”, and it remains true that “people who want to work purely on the C side can very much continue to do so”.

But, is this true or false?

> If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#36

Post by fowl2 »

rjsw wrote: post #13
davikr wrote: post #3

> Dave Airlie just announced in the Maintainers Summit that the DRM subsystem is only ""about a year away"" from disallowing new drivers written in C and requiring the use of Rust. wow

Means that other platforms need to allow Rust in the kernel too in order to use future drivers.

Windows already does, so you’re talking about the BSDs or Darwin?

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#37

Post by monocasa »

ceteia wrote: post #29
monocasa wrote: post #28

Earlier quoted context omitted.

Dave Airlie is saying that the subsystem maintainers are themselves choosing to move to Rust.

But what about this statement that Linus wrote: > That's been made clear pretty much from the very beginning, that nobody is forced to suddenly have to learn a new language, and that people who want to work purely on the C side can very much continue to do so. If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.

You're confusing the audience here. That's directed at subsystem maintainers, not just 'anyone who wants to submit a patch'. If a subsystem doesn't want to deal with Rust code, they won't be forced to. But there's no restriction on the inverse.

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#38

Post by wtallis »

ceteia wrote: post #35
cwillu wrote: post #34

Earlier quoted context omitted.

Nothing is happening “suddenly”, and it remains true that “people who want to work purely on the C side can very much continue to do so”.

But, is this true or false? > If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.

Whether that's true or false depends on what your hypothetical developer wants to do in the future. When an all-new driver is written in Rust, then working on that driver will require knowing Rust. But nobody's talking about trying to re-write all the existing drivers in Rust, so there will still be plenty of C code to work on even in the DRM subsystem.

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#39

Post by ladyanita22 »

ceteia wrote: post #35
cwillu wrote: post #34

Earlier quoted context omitted.

Nothing is happening “suddenly”, and it remains true that “people who want to work purely on the C side can very much continue to do so”.

But, is this true or false? > If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.

I think this is true. But that'd be nonetheless up to the subsystem maintainers.

Re: The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

#40

Post by ladyanita22 »

fowl2 wrote: post #36
rjsw wrote: post #13

Earlier quoted context omitted.

Means that other platforms need to allow Rust in the kernel too in order to use future drivers.

Windows already does, so you’re talking about the BSDs or Darwin?

BSDs and other Open Source OSes that rely on Linux drivers.

Windows probably has not many (or any) drivers ported from Linux.

Post reply on HN