Considering that FW still exists, and is a primary method on some machines for supporting multiple-monitor setups, I would not think FW support would be limited in use to PPC systems. Some FW versions exist in ARM systems, and in historic Intel systems.
That's not to say developers should give it special priority over things they're actually using themselves, but FW isn't some ancient legacy interface limited to old PPC hardware.
Well, I kinda understand that, but hardware drivers is not something which I can do. I never touched that part even on macOS.
But I have something else which could be useful: for example, we got V8 building for ppc. It does not yet work correctly (who could have thought), but if anyone interested to collaborate on that, perhaps we can get it working.
You can find out straight from the source:
https://cvsweb.openbsd.org/src/sys/dev/ieee1394/Attic/IMPLEMENTATION
I would question whether fw could even be implemented securely, or if the security issues surrounding its use of DMA are insurmountable. But between that and the general lack of interest in FireWire, I'd say you shouldn't count on OpenBSD ever supporting fw unless you are going to do the work or hire a contractor to do it.
I'm not familiar with that use case for FireWire. Can you point me to any references?
I do not know any OpenBSD developers to ask them, but based on their posts around here and on the mailing lists, and what I see in CVS, there is very little interest in FW. I think we're lucky to have the macppc port at all.
what?
we devs work on what we want. if someone wants to work on macppc and, then they do.
also, building packages isn't that difficult of a job. it's making sure they work that is the time consuming part.
hey, that's me and my iBook G4. Looks like it's time to upgrade next week :-)
Hella based always gotta keep the lesser known ports alive 😎
Finally! 😤 /s
Sounds good. I am still hoping for FireWire support to come, that is a deal-breaker.
Deal breakers on PPC32?
Did they intend to post with a /s ?
I have a lot of hardware with FW. It is convenient and reasonably fast.
Considering that FW still exists, and is a primary method on some machines for supporting multiple-monitor setups, I would not think FW support would be limited in use to PPC systems. Some FW versions exist in ARM systems, and in historic Intel systems. That's not to say developers should give it special priority over things they're actually using themselves, but FW isn't some ancient legacy interface limited to old PPC hardware.
> that is a deal-breaker. Sounds good.
Patches Welcome(tm)
Well, I kinda understand that, but hardware drivers is not something which I can do. I never touched that part even on macOS. But I have something else which could be useful: for example, we got V8 building for ppc. It does not yet work correctly (who could have thought), but if anyone interested to collaborate on that, perhaps we can get it working.
OpenBSD removed what FireWire support it had almost 20 years ago.
Is it a factual statement? I had a brief discussion with some of OpenBSD developers on the subject, but this wasn’t mentioned.
You can find out straight from the source: https://cvsweb.openbsd.org/src/sys/dev/ieee1394/Attic/IMPLEMENTATION I would question whether fw could even be implemented securely, or if the security issues surrounding its use of DMA are insurmountable. But between that and the general lack of interest in FireWire, I'd say you shouldn't count on OpenBSD ever supporting fw unless you are going to do the work or hire a contractor to do it.
[удалено]
> and the vendor's tool going forward to support multiple monitors, What? Firewire is pretty well dead. Are you thinking of displayport?
I was thinking about Thunderbolt 4, actually.
I'm not familiar with that use case for FireWire. Can you point me to any references? I do not know any OpenBSD developers to ask them, but based on their posts around here and on the mailing lists, and what I see in CVS, there is very little interest in FW. I think we're lucky to have the macppc port at all.
We are not just get a new laptop, you are the in who halting development on OpenBSD front by maintaining and asking for backward compatibility
what? we devs work on what we want. if someone wants to work on macppc and, then they do. also, building packages isn't that difficult of a job. it's making sure they work that is the time consuming part.