10 More Discussions You Might Find Interesting
1. Solaris
Hi folk,
I have this hardware faunty message, but dont know which hardware is this ? can you guide me ?
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
2. Solaris
Hi everyone
I've just purchased a Sun T5120 server with 2 internal disks. I've configured hardware RAID (mirror) and as a result the device tree in Solaris only contains 1 hard drive.
My question is, how would I know when one of the drives become faulty?
Thanks (2 Replies)
Discussion started by: soliberus
2 Replies
3. UNIX for Dummies Questions & Answers
A few of our machines need upgrading and we are looking into a selection of processors at present. There are suggestions on the vendor's websites that the L3 cache was specifically introduced for gamers. Is this true? Does having L1, L2 and/or L3 cache help at all in performance or are the... (0 Replies)
Discussion started by: figaro
0 Replies
4. UNIX for Advanced & Expert Users
Not sure I put this in the right forum, and if I was incorrect. I do a appligize.
Recently I have lost two external hard drives due to heat. I bought internal drives, seperate case's, and made them usb externals. They lasted a long time, but the heat killed them.
While rooting through my... (0 Replies)
Discussion started by: droolin
0 Replies
5. AIX
I have an IBM pseries 7028-6E1 server with a six drive bay that is currently plugged into the scsi backplane of the motherboard. I am going to install a PCIX Ultra320 scsi raid adapter, and swing the drive bay over to it. I am just wondering how this is going to work. Should I power the server... (1 Reply)
Discussion started by: markper
1 Replies
6. UNIX for Dummies Questions & Answers
I would like to use my sunblade to firewall the connections to my desktop and laptop, these at the minute are on a wifi router. What is the best solution? (0 Replies)
Discussion started by: Kawakaze
0 Replies
7. AIX
I am looking to buy a 7044 - either a 170 or 270.
From what I can find on web searchs the 170 is NOT upgradable to more that one CPU? Is that correct?
Can I upgrade the planer on a 170 to a 270 to support multiple CPU's?
Does anyone have any other suggestion for AIX hardware? (5 Replies)
Discussion started by: dizman67
5 Replies
8. Programming
Hello !
I have a friend , in one day he tell me this : some guy made a cool program in C , for some sort or hardware control . I say : wow !
Maybe someone , can give me an example , how can C control hardware so good ( as I hear ) , and maybe some cool information , where to learn the idea ,... (1 Reply)
Discussion started by: !_30
1 Replies
9. HP-UX
I've been asked by my copmpany to scour the web for a computer on which we can run HP-UX 11.i --- Is there a certain architecture type that I need or will any Compaq HP computer be fine for running HP-UX 11.i ??
Thanks!! (3 Replies)
Discussion started by: jalburger
3 Replies
10. UNIX for Dummies Questions & Answers
Does anyone know how to install a second Ethernet adapter on a Sun Sparc 10? (2 Replies)
Discussion started by: jskillet
2 Replies
id32_alloc(9F) Kernel Functions for Drivers id32_alloc(9F)
NAME
id32_alloc, id32_free, id32_lookup - 32-bit driver ID management routines
SYNOPSIS
#include <sys/ddi.h>
#include <sys/id32.h>
uint32_t id32_alloc(void *ptr, int flag);
void id32_free(uint32_t token);
void *id32_lookup(uint32_t token);
INTERFACE LEVEL
Solaris architecture specific (Solaris DDI).
PARAMETERS
ptr any valid 32- or 64-bit pointer
flag determines whether caller can sleep for memory (see kmem_alloc(9F) for a description)
DESCRIPTION
These routines were originally developed so that device drivers could manage 64-bit pointers on devices that save space only for 32-bit
pointers.
Many device drivers need to pass a 32-bit value to the hardware when attempting I/O. Later, when that I/O completes, the only way the
driver has to identify the request that generated that I/O is via a "token". When the I/O is initiated, the driver passes this token to the
hardware. When the I/O completes the hardware passes back this 32-bit token.
Before Solaris supported 64-bit pointers, device drivers just passed a raw 32-bit pointer to the hardware. When pointers grew to be 64 bits
this was no longer possible. The id32_*() routines were created to help drivers translate between 64-bit pointers and a 32-bit token.
Given a 32- or 64-bit pointer, the routine id32_alloc() allocates a 32-bit token, returning 0 if KM_NOSLEEP was specified and memory could
not be allocated. The allocated token is passed back to id32_lookup() to obtain the original 32- or 64-bit pointer.
The routine id32_free() is used to free an allocated token. Once id32_free() is called, the supplied token is no longer valid.
Note that these routines have some degree of error checking. This is done so that an invalid token passed to id32_lookup() will not be
accepted as valid. When id32_lookup() detects an invalid token it returns NULL. Calling routines should check for this return value so that
they do not try to dereference a NULL pointer.
CONTEXT
These functions can be called from user or interrupt context. The routine id32_alloc() should not be called from interrupt context when the
KM_SLEEP flag is passed in. All other routines can be called from interrupt or kernel context.
SEE ALSO
kmem_alloc(9F)
Writing Device Drivers
SunOS 5.10 12 Dec 2001 id32_alloc(9F)
