In my situation, I only use old SounBlaster cards, for which drivers are coming with the OS. I would suggest everyone to use these cards and get rid of this drama, having a usable system.

Quote:

This is reality. You have to get down to the earth. If anyone wants to use their hardware, they will try to find a way to do it. Since you decided to "panish" the community months ago just by removing the driver from OS4Depot, do not expect that the users will not try to find it any way they can.

If people share the driver "illegally" as you say, then you should help them do it legally, which you didn't. Instead of being thankful for people finding your work useful, you end up accusing us (and me personally) for being immoral. That is your opinion, but do not expect us to agree with that.

Yes, people should respect the licence file you included in your archive, but you also need to land to reality and start doing something useful.

I do not know if I am immoral because I proposed you solutions. If that's the case, so be it. But please think before you talk.

Software is licensed and you can only use it according to its license. The author has the right to decide what license the sofware is published under. It does not matter what you think, you only have two choices: accept the licence or not use the software. (This is also true for free software under GPL. You can use, distribute, modify it freely, even can ask for money to support it, but you can't make it non-free and have to give the same rights you got to others.) Those who produce commercial products and expect people to follow their licenses should also follow the license of the components they use themselves and should check and comply to those licenses.

In this case the HDA driver's license says it's only for non-commercial personal use and cannot be distributed as part of a commercial product or ask money for it. (I don't think this can be revoked once it's published so this driver version is still available under those terms and it allows to be distributed for personal use.) But the author can ask it to be removed from commercial products (or try to ask for some money for past "damage" but maybe there's not much profit made on any of this and we don't need more court cases so getting some agreement may be a more sensible approach).

The authors also have the right to decide if they want to support it further. license further versions under different license or stop making further versions. You can't force them to do something they don't want to.

Maybe people are too passionate about all these Amiga stuff and still hold on to their pieces which just hinders development so it would be better if there could be more cooperation instead of competition and forget commercial thinking where there's no real market but this seems to be the state of things now. I can only hope it will change in the future.

@walkero

You (and others) completely failed to see my point.
I do not want money. Never asked for it and also declined donations.
I want people to respect my license and don't just steal something because someone else sold them something. Or that you lack the audio hardware on your product. That is the problem between them and the ones they bought their hardware from. Instead everything is somehow my fault. And if I don't like that I can gfm for the drama queen that I apparently am.

Your comment that it was my own fault because I had to find a different distribution method sooner is the most immoral and offensive of them all.

@geennaam

Quote:
And I will once again say that the OS4 community is very appreciative of your work. You just need to give us a chance to obtain your software legally so that we can use it.

Quote:

I am looking forward to hearing ACube's side of the story since geennaam is so offended by their actions and decided to bring this matter public, instead of solving it with them.

@geennaam
It is interesting that instead of trying to solve any issue, you just try to victimise yourself and blame the community ones again, calling us immoral. I once again offer my help to have your drivers hosted and sold by you, if that's what you need to do.

@Hans
Quote:

Then this may be a limitation in RTAS as it only has provision to pass a single address but not PCI domain or host. So if RTAS on pegasos2 interprets bus 1 as the AGP port (which is really another PCI domain) then maybe there's no way to access devices on bus 1 on the default PCI domain. You can test this theory if you get data from the AGP port with bus 1 and device for the card on that bus. Then reading bus 1 for device behind the bridge would try to access the wrong PCI domain and so won't find a device there because you can't have bus mean both bus and PCI domain so you could either access all devices on one domain or bus 0 of all domains depending on what RTAS uses the bus part of the PCI address for.

If my theory is true then you probably can't use RTAS and you'd need to write a proper PCI driver in AmigaOS to be able to access all devices on all domains. I could help with that but I only work for free on open source projects that I can then also use myself. But if I won't get the result and you're payed to do that and not me I'll let you figure that out (or you can hire me for consulting if needed). It's not difficult though, accessing PCI is not much different from other platforms which is well documented and I've already given you the docs where it's explained for pegasos2 as well. Also my code is free to study (not for copying into commercial projects though, so you should not copy&paste it but write your own from what you've learned from it).

Sorry for that but I believe in free software. I don't mind if others don't but then the rules of commercial software should be applied for those projects which means you get what you pay for.

Quote:

Yeah, CubicIDE has an old version. I do not let the plugin do the SDK installation.
SDK has multiple different versions which you can select with its installer. There is GCC 8, 10, 11 and 6 for SPE compatibility (A1222).

@Balaton
Quote:

Aren't we trying to play with all this config-l@ stuff exactly for the reasons to know if smartfirmware read things correctly already, so to see if address we find is correct, so to not use RTAS if RTAS fail, but direct access ?

I mean what make you think that "they may not be accessible via RTAS" ?

@ktadd
Cool, I haven't been up in that area too far, but my wife's family are from the Bay area just south of San Francisco, in Redwood City.

I have never been to Amiwest either, but have been thinking about it. Of course it is about an 8 hr drive for me. But maybe can combine it with a trip to the in-laws for my wife and kids.

@kas1e
I've read somewhere: "If all else fails read documentation." Ever thought about that? If you want to learn Forth try forth.com. Have you even seen old reverse Polish notation calculators that are stack based? Those where you had to type 5 3 + Enter or something like that to add two numbers and display the result? Forth works like that, so you have to push arguments to stack then call operation word and then you can find results on the stack that you need to print to get the result.

But this probably does not matter as it seems even if you can get the needed values from the SmartFirmware prompt they may not be accessible via RTAS.

@All

Don't jump to conclusions too fast, especially if you don't have ACube answer

Wow, just wow.

I knew that some people in the Amiga community had to gain their bearings and set their moral compass. For it was pointing in the wrong direction.

But today the usual suspects displayed actually that they don't have one at all. They're just driven by greed and selfishness.

Well, too bad for those that mean well. My apologies that I have released software in the first place.

@MisterJBAM

@MisterJBAM

Quote:
Absolutely! The latest SDK gives you GCC 6, 8, 10 and 11. You should use at least GCC 8, unless you need to compile for the A1222's SPE, in which case you'll need GCC 6 (because SPE support was dropped in later versions).

@jabirulo

Quote:

SDK:local/newlib/lib

I tried what you gave me but to no avail.
could you please share an entire makefile?

@walkero

GCC 4.2.4 was installed by default (maybe with Cubic), is there a more recent version?

@Raziel

I'm starting to realize these problems

Tried and it spit loooots (but looots) of SEEK FAILED but plays. alas I have a RX550 on my SAM460ex.




try this frrom shell/CLI:
<path_to_mplayer> -vo comp PRUEBAS:The_Sarah_Connor.avi *>ram:aaaaaaa

so all errors go to ram file aaaaa

@Hans
Tried all different ways of syntax and still have no luck (with 16 before, after, with spaces, etc ,etc).

But, what i find in some docs are:

There are two types of words, global and local. Global words come with the version of Open Firmware present on the computer. Some of these are placeholders that get overwritten by device specific local words. Local words are restricted in scope to the device that contains the word. The available global and local commands can be listed with the command "words"

So, if i come to the exactly video card and type "words", i then have nothing, see:



But if i go only to the bridge itself , i.e. just cd /pci/pci@7 and type "words", then:



As i understand, those local words (like config-l@) can be used only when we in some device which can be used with.

Then when i am in the bridge, then typing "config-l@" without args do not cause error. But also other ways too:




Simple help on config-l@ (while being in the bridge directory), print out that:



But i not sure, if that can help us ? I mean, what "config-addr -- data" mean, and, can we provide as argument "display@0" or "display@0,1" to read what we want to read ?

So far tried that with no luck:

config-l@ display@0 16
config-l@16 display@0

Question now what is that "config-addr -- data" , from where get it, and will it of any help for us.

Maybe we somehow need to open/select the card in firmware to be able to have those words like "config-l" to work with ..

@MisterJBAM

Quote:
Yes, but your makefile doesn't seem to include the relevant linking flags...

@kas1e

Quote:

Not here. I just booted my Debian net installer on my XE. Exactly as on the Sam. It wants a mirror and won't continue without it. It needs to download the base system. The net installer must have been updated since.

Quote:

I searched for hours and didn't crack it. It always gives a bad mirror at first. If I manage to give it a mirror it accepts it ends in an arch error as ppc not supported. In addition it wants Jessie but that's obsolete as Jessie isn't stable any more. The problem is you can't exactly tell it you want jessie or enter jessie as it always looks for stable, oldstable, etc. It's just too hard coded. It's ppc which always has the worse support. Especially Ubuntu where they break ppc32 files so they don't work in the archive but don't care because it's ppc and not x86 despite both being an obsolete 32 bit arch.

Anyway you were looking for some ISOs. Here's Ubuntu. But these are a full image so will work!

I found a good list of PPC images is here:
https://vivapowerpc.eu/software/Ubuntu/

lubuntu-16.04-desktop-powerpc.iso
ubuntu-16.04.6-server-powerpc.iso
ubuntu-mate-16.04-desktop-powerpc.iso

There is also an extra archived mate with 16.04.1 from 2019 and a 16.10 from 2020:
https://releases.ubuntu-mate.org/archived/16.04/
https://releases.ubuntu-mate.org/archived/16.10/