Sponsored Content
Full Discussion: Intel vs. RISC
Top Forums UNIX for Dummies Questions & Answers Intel vs. RISC Post 2058 by softarch on Tuesday 17th of April 2001 01:01:49 AM
Old 04-17-2001
Tools messing with hardware is very time cosuming

As Neo says, you got access to much wider area of hardware and that is where it will pull out of your pocket. If you got the cheap Sparc you learn about the Unix. Messing with hardware comes at the most expense you can get involved in and that is ‘time'. Once you know the system then it is much easier to mess with the hardware but to start messing with the hardware and then learn the system ..., that's up to you. I messed with the hardware plenty and I don't see any advantage in that. You'll find out that you want to mess with the hardware the least. That is my opinion. Thanks, gp
 

8 More Discussions You Might Find Interesting

1. AIX

Ibm Risc/6000 Os

:o Unix Sirs, :eek:RE: IBM RISC/6000 1990 Used on Application: Image buffer: 3D "Catia" (3D "Autocad" sim.) engineering C.A.D. Written by Deso. Cash prior to main frame dump:cool: * :oCan I purchase the oem operating system from you unix people? :cool: ... (1 Reply)
Discussion started by: penguins
1 Replies

2. HP-UX

please help need HP-UX 11 for PA RISC

Im not asking for an illegal copy (but from what i understand if i have the system its not illegal to give it to me) just how to get a copy of hp-ux period i have some old hp visualize systems based on the PA8500 400mhz cpu spent days on the phone with hp they no nothing and there website is a... (6 Replies)
Discussion started by: maliqua
6 Replies

3. HP-UX

Debian HPPA for HP PA-RISC

Hi, I just downloaded the debian HPPA distribution. Once I try to install it on my C3000 box, the machine boots, reads a part of the CD but then stalls with an error message about the image on the CD. The CD drive is IDE, maybe debian expects to have a SCSI one. Somebody already tried to... (1 Reply)
Discussion started by: ddegrendele
1 Replies

4. UNIX for Advanced & Expert Users

PA-RISC 2.0 (LP64) and PA-RISC2.0 exec or libraries

I have a problem with executing an application using the ELF 64 libraries. Previous versions and on other machines where all is well use PA-RISC2.0 (32) . My guess is that the application or executables need to be recompiled and linked with the new ELF 64 libraries. Are these run time compatible ?... (2 Replies)
Discussion started by: gd2352
2 Replies

5. HP-UX

HP-UX 11i v2 for PA-RISC

Hello, i trying to get HP-UX 11i v2 for PA-RISC. I`im to poor to buy this system, so I`am asking that someone can help me. best regards email removed (1 Reply)
Discussion started by: mruczas
1 Replies

6. Programming

IBM Risc migration

Hi all, I have been dealing with the following problem one week now without any progress. I've a source code written in C which is using X libraries in order to create a graphical interface to visualise results produced by another code written in Fortran. The README file of the C code says... (2 Replies)
Discussion started by: Pavlos
2 Replies

7. HP-UX

Access AS400 from HP (RISC) Unix OS

Hi everyone, I am in the need of some software which will allow me to access IBM AS400 from HP unix operating system. I could download the software from IBM site for windows OS and it is working succesfully. I need to do the same on UNIX OS. Could you please guide me to some site... (1 Reply)
Discussion started by: vkoppula
1 Replies

8. HP-UX

Does HP-UX On Itanium always come with PA-RISC compatibility

Does anybody know if HP-UX on Itanium always comes with backwards compatibility for PA-RISC applications? I've heard that there is an emulator called Aries which should do the trick, I just need to know if it always comes as standard with HP-UX Itanium systems. Any help would be greatly... (3 Replies)
Discussion started by: nialler
3 Replies
ddi_intr_get_supported_types(9F)										  ddi_intr_get_supported_types(9F)

NAME
ddi_intr_get_supported_types - return information on supported hardware interrupt types SYNOPSIS
#include <sys/types.h> #include <sys/conf.h> #include <sys/ddi.h> #include <sys/sunddi.h> int ddi_intr_get_supported_types(dev_info_t *dip, int *typesp); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI) dip Pointer to dev_info structure typesp Pointer to supported interrupt types The ddi_intr_get_supported_types() function retrieves the interrupt types supported by a particular hardware device and by the system soft- ware. Upon successful return, the supported types are returned as a bit mask in the integer pointed to by the typesp argument. See <sys/ddi_intr.h> for a list of interrupts that can be returned by a hardware device. For PCI devices that support MSI and/or MSI-X based hardware, this interface returns only the interrupt types that are supported by all the hardware in the path to the hardware device. An interrupt type is usable by the hardware device if it is returned by the ddi_intr_get_supported_types() function. The device driver can be programmed to use one of the returned interrupt types to receive hardware interrupts. The ddi_intr_get_supported_types() function returns: DDI_SUCCESS On success. DDI_EINVAL On encountering invalid input parameters. DDI_INTR_NOTFOUND Returned when the hardware device is found not to support any hardware interrupts. CONTEXT
The ddi_intr_get_supported_types() function can be called from user or kernel non-interrupt context. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ pci(4), attributes(5), pcmcia(7D), sysbus(4), ddi_intr_add_handler(9F), ddi_intr_alloc(9F), ddi_intr_enable(9F) The ddi_intr_get_supported_types() function can be called by the device driver even at any time if the driver has added an interrupt han- dler for a given interrupt type. Soft interrupts are always usable and are not returned by this interface. Any consumer of this interface should verify that the return value is not equal to DDI_SUCCESS. Incomplete checking for failure codes could result in inconsistent behavior among platforms. 07 Apr 2005 ddi_intr_get_supported_types(9F)
All times are GMT -4. The time now is 06:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy