Sponsored Content
Full Discussion: Lspci: PCI Devices?
Special Forums Hardware Lspci: PCI Devices? Post 302866831 by Lost in Cyberia on Tuesday 22nd of October 2013 06:40:24 PM
Old 10-22-2013
None taken at all! I thank you for your response. The naming convention is what threw me.
 

10 More Discussions You Might Find Interesting

1. Solaris

rs232 pci-card

hello mates, do you know a manufactor for rs232 serial pci cards for the sparc architecture? it seems that there is no original product from sun for that purpose. strange, isn't it? problem is that i have a V250 with only one db9 rs232 serial port, and i need it for a modem connection, but i also... (1 Reply)
Discussion started by: pressy
1 Replies

2. Solaris

Pci Id

How do I get the PCI ID for my Realtek adapter? It's a Solaris x86 installation. (5 Replies)
Discussion started by: kuultak
5 Replies

3. UNIX for Dummies Questions & Answers

bad pci slot?

Hi, im having a problem installing my pci wireless card. Im using knoppix, but my problem is with the mobo i think. im using an older laptop, toshiba satellite 2540 and when i plug in the card i get lights on sometimes. this means its getting power right. so then to install the card into the... (0 Replies)
Discussion started by: jestra
0 Replies

4. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies

5. Solaris

How to look for open pci slots

I'm looking for open PCI slots in our array of sun boxes. I need help on how to distinguish if there's an open slot or not using prtdiag and prtconf. Is there a better tool for this? TIA. Here's my prtdiag -v | grep pci: pci 66 PCI5 SUNW,qlc-pci1077,2312 (scsi-+ ... (9 Replies)
Discussion started by: revzalot
9 Replies

6. Linux

Re: The function of /dev/modules/ and PCI devices

Hello all, I am using openSUSE 11.1 and have an issue with my wireless adapter which I am trying to understand and fix. I just have a quick question about the following image: (It was the output of the lspci command) Why are there two modules being loaded? (ath5k and ath9k) is this a... (2 Replies)
Discussion started by: septima.pars
2 Replies

7. SCO

lspci for SCO?

What is the SCO equivalent to lspci in Linux? This is SCO6 if that matters. (4 Replies)
Discussion started by: dalek
4 Replies

8. Linux

PCI Card recognized

I installed PCI Card HP SC44Ge - SAS1068E on my linux CentOS 5.4 is there a way to find out if the PCI is properly installed and recognized by linux. lspci is enough? just to add that PCI card is connected to a tape... also how can I find out driver and firmware version? thanks a... (1 Reply)
Discussion started by: karlochacon
1 Replies

9. Programming

help writing pci firmware

For a project that I'm working on I want to write a low level PCI driver, but I can't seem to find any free/cheap documentation on PCI firmware specifications. I came across the "pci firmware specification 3.0" manual but this costs USD $1000 :eek:. I am not developing a commercial product... (13 Replies)
Discussion started by: neur0n
13 Replies

10. Hardware

Could USB ever take over PCI

Internally speaking, for your motherboard bus. Would it be possible for a usb standard to be used in place of the PCI or PCIe bus that is now nearly standard on all PC's? If not, why wouldn't this work? (8 Replies)
Discussion started by: Lost in Cyberia
8 Replies
mms_rsp_type(3MMS)				     Media Management System Library Functions					mms_rsp_type(3MMS)

NAME
mms_rsp_type, mms_get_tree, mms_get_str, mms_get_attribute, mms_handle_err_rsp - MMS client functions for handling responses SYNOPSIS
cc [ flag...] file... -lmms [ library...] #include <mms_api.h> int mms_rsp_type(void *response); mms_par_node_t *mms_get_tree(void *response); char *mms_get_str(void *response); char *mms_get_attribute(void *response, char *name, void **prev); int mms_handle_err_response(void *response, int * class, int * code, char **message); DESCRIPTION
For these functions, response is the MMS response to an MMP command sent by the client. The mms_rsp_type() macro returns the type of the response. The following is a list of responses: MMS_API_RSP_UNACC unacceptable response MMS_API_RSP_FINAL success response MMS_API_RSP_FINAL_INTR intermediate response MMS_API_RSP_FINAL_ERR error response MMS_API_RSP_FINAL_CANC cancelled response The mms_get_tree() macro returns the parse tree of the response. The mms_get_str() macro returns the response string. The mms_get_attribute() function takes a response with name values looking for name, and returning the value associated with it. A client can call this function multiple times if the response contains multiple instances of name. When all occurrences of name have been found, NULL is returned. The mms_handle_err_rsp() function processes an error response on behalf of the client. It returns the error class, error code, and the internationalized error message if one was included. RETURN VALUES
Upon successful completion, mms_handle_err_rsp() returns MMS_API_OK. If it encounters a processing error, it returns an error code indicat- ing the type of error. ERRORS
These functions will fail if: MMS_API_ERROR Unable to obtain error class or code. MMS_API_NOT_ERR_RSP Response is not an error response. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
libmms(3LIB), mms_init(3MMS), mms_send_cmd(3MMS), attributes(5) SunOS 5.11 28 Oct 2008 mms_rsp_type(3MMS)
All times are GMT -4. The time now is 10:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy