@saimo

Quote:

saimo wrote: @Hans Ah, right... you even explained it in your first post... sorry for getting circular

No problem.
It was an easy detail to overlook.

@all

Given that no-one has posted a valid method, I think that we can conclude that it is probably not possible to change the graphics-card's IRQ with the current uboot. Whether the hardware is capable of doing so remains to be seen.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Hans

Quote:

I think that we can conclude that it is probably not possible to change the graphics-card's IRQ with the current uboot. Whether the hardware is capable of doing so remains to be seen.

On the bright side, UBoot firmware update is currently being tested.
(reported by @Rogue in another thread)
Perhaps this issue is being addressed.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Quote:

On the bright side, UBoot firmware update is currently being tested. (reported by @Rogue in another thread) Perhaps this issue is being addressed.

Really? I must have missed his post about that.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Hans

I want add one point to conversation. OT, but in hope, that it is useful for someone.

In pc mobos, usually IRQ sharing method is something like next.

A. AGP wont share IRQ at all or share it with device wich is 1.cabable to share IRQ adn 2.device is low speed.

B. Ethernet and IDE shares same IRQ. IDE uses same IRQ with second (from top) PCI slot. IDE and Ethernet are both type, wich can share IRQ and allso stream together is easily handled by PCI bus. Bit oversimplified, but true in cases, where there is no other stream in same PCI lane.

C. Devices, wich cannot share IRQ (modem cards, sound cards) is populated from bottom most PCI slots. These slots usually uses same lane, than ISA bus. Wich is not been in use in ages but is been present while ago in chipsets (in some level).

Whether sound and modem cards can or cannot share IRQ nowadays, I don't know.
>
Case B and C are in standard. If they are valid today or not, I don't know. At least mobo guides there is quite few info novadays and all pci slot IRQs are market as "shared".

I used number and characters to help me out with my bad english.

I don't know anything usable info about A1 IRQ handling. One intresting point is, that in ArticiaS there is two lanes. Other for AGP/PCI66 and other for PCI33. Dunno know, how these interfere with A1 IRQs.


Anyway I get every now and then situations from clients, where modem card is inserted to second PCI slot and problems occurs. Every second time no HDs nor CDs are recognized in boot, mystical hd failures in runtime etc. These mobos are practically 2+ years old. Very rarely ppl has modem connection with newer computers.

Edited: typos, as allways...

Last edited by mlehto on 28-Mar-2006 at 09:35 PM.
Last edited by mlehto on 28-Mar-2006 at 09:29 PM.

@Hans

Quote:

Really? I must have missed his post about that.

Whole thread worth a read, but @Rogue's post is #3:
http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=18235&forum=33

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@mlehto &
@thread

Just so you know.
No one has given up on the idea of having a working riser card for Micro A1-C.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Thanks. I actually did look at that thread, but kind skipped over most of it. I wonder what other changes/fixes the new firmware will bring.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Hans

Quote:

Suggestions to deal with these problems were things such as:- The SB Live doesn't like sharing IRQs, make sure it has its own IRQ (clears up the crackling on some systems)- Make sure the AGP graphics card has its own IRQ or your system may lockup randomly

This is what could be causing problems on AHI. With the SB5.1 AHI driver Davy had to cut the timer interrupt frequency back from 80 Hz (faster) to 1000Hz (slower). Hard to explain but is is a divider. It only happens on OS4.

@Hypex

Quote:

Hypex wrote: @Hans Quote: Suggestions to deal with these problems were things such as:- The SB Live doesn't like sharing IRQs, make sure it has its own IRQ (clears up the crackling on some systems)- Make sure the AGP graphics card has its own IRQ or your system may lockup randomly This is what could be causing problems on AHI. With the SB5.1 AHI driver Davy had to cut the timer interrupt frequency back from 80 Hz (faster) to 1000Hz (slower). Hard to explain but is is a divider. It only happens on OS4.

Wow, I haven't seen this thread in a while. It's a pity that we don't have OS4 running on hardware other than the A1 and classic Amigas. It would be interesting to see if the issues are generic PCi or soundblaster issues, or specific to the A1.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Hans

Heh! Welcome back to the old thread.
The soundblaster issues are well documented through the comments from George Breese.
DaveAE concluded same as you though re:the other issues.
Some can not be positively attributed to one thing or another until we see new hardware.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@Hypex

Quote:

Hypex wrote: @Hans Quote: Suggestions to deal with these problems were things such as:- The SB Live doesn't like sharing IRQs, make sure it has its own IRQ (clears up the crackling on some systems)- Make sure the AGP graphics card has its own IRQ or your system may lockup randomly This is what could be causing problems on AHI. With the SB5.1 AHI driver Davy had to cut the timer interrupt frequency back from 80 Hz (faster) to 1000Hz (slower). Hard to explain but is is a divider. It only happens on OS4.

BTW, 1000 Hz seems very high considering that HiFi audio is at 44 KHz. Assuming 16-bit stereo, that would be one interrupt per 176 bytes transferred to the sound card. This sounds like a lot of overhead to me. Note: I haven't done any audio programming on the Amiga so I have no idea as to what advantages a 1 KHz timer would have over 80 Hz.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Hans

Quote:

BTW, 1000 Hz seems very high considering that HiFi audio is at 44 KHz. Assuming 16-bit stereo, that would be one interrupt per 176 bytes transferred to the sound card. This sounds like a lot of overhead to me. Note: I haven't done any audio programming on the Amiga so I have no idea as to what advantages a 1 KHz timer would have over 80 Hz.

It just happens on OS4 (A1) hardware.

You can examine the AHI sourcecode on Aminet. What it does is divide the value into 48000, the soundcards output frequency I pressume. So with 80 it gets 600, 1000 it gets 48. It sets the amount of bytes the soundcard asks for, and expects buffered, when it sets off an interrupt for the computer to transfer more data.

BTW, the numbers were direct, 80 was the slow and 1,000 fast. It is the Hz the driver will run at, asking AHI for more data, so the amount of times a second the drvier asks AHI for more data.