Sponsored Content
Operating Systems Solaris writing device drivers,for a beginner!!! Post 302268874 by jim mcnamara on Tuesday 16th of December 2008 12:49:15 PM
Old 12-16-2008
Can you program C; do you have any experience with system calls?
Based on your question I would seriously consider a close read of Stevens & Rago
'Advanced Programming in the UNIX Envrionment' before going on to drivers.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

View device drivers?

I might sound stupid for asking, but could someone please tell me how to view all the device drivers? I'm just starting to use UNIX after using Windows for years. Thanks. -sysop0130 (1 Reply)
Discussion started by: sysop0130
1 Replies

2. Programming

Linux Device Drivers

Here is a cool book. And the price is right! Linux Device Drivers, 2nd Edition (0 Replies)
Discussion started by: Perderabo
0 Replies

3. Windows & DOS: Issues & Discussions

Are Your Device Drivers Wacked Or Hacked?

Suggestion. Besides running scans it is also a good thing to run "sigverif". This will create a list of ALL drivers on your system, signed and unsigned. The output is located in your C:Windowssigverif.txt file. It surprised me most people do not do this. Many trojans mask themselves as... (0 Replies)
Discussion started by: ZOverLord
0 Replies

4. UNIX for Dummies Questions & Answers

drivers unix 5.01 is compatible with drivers epson fx-2190

Please, I'm From Argentina, And I Need To Know If The Drivers Of Program Unix, Version 5.01 Is Compatible Whit Drivers Of The Printer Epson Fx-2190 Thanks, And I Hope Yuor Answer. (0 Replies)
Discussion started by: juan alberghina
0 Replies

5. Programming

linux device drivers

hi, this is manju .... i want linux device drivers source codes. pls help me (2 Replies)
Discussion started by: miraclemanju
2 Replies

6. Solaris

SPARC and device drivers

Hello all, I'm new here.. Can you please help me with device driver on Solaris10, Sun SPARC server; I need to know how to test if a PCI card is recognized and has a working driver. How to do it? As it is, the driver seems to be 'not attached', but some say it could be because the PCI card is not... (10 Replies)
Discussion started by: orange47
10 Replies

7. UNIX for Advanced & Expert Users

Learn Linux File System and Device Drivers

I am to start working on two project on Linux Device Drivers and other on File System. So I got the book "Understanding Linux Kernel" by Daniel and Marco. But I am confused as how to proce Will anybody pls let me know how to go to about studying the chapter in this book? I mean the order in... (1 Reply)
Discussion started by: shefalibv
1 Replies

8. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

9. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
mt-streams(9F)						   Kernel Functions for Drivers 					    mt-streams(9F)

NAME
mt-streams - STREAMS multithreading SYNOPSIS
#include <sys/conf.h> INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). DESCRIPTION
STREAMS drivers configures the degree of concurrency using the cb_flag field in the cb_ops structure (see cb_ops(9S)). The corresponding field for STREAMS modules is the f_flag in the fmodsw structure. For the purpose of restricting and controlling the concurrency in drivers/modules, we define the concepts of inner and outer perimeters. A driver/module can be configured either to have no perimeters, to have only an inner or an outer perimeter, or to have both an inner and an outer perimeter. Each perimeter acts as a readers-writers lock, that is, there can be multiple concurrent readers or a single writer. Thus, each perimeter can be entered in two modes: shared (reader) or exclusive (writer). The mode depends on the perimeter configuration and can be different for the different STREAMS entry points ( open(9E), close(9E), put(9E), or srv(9E)). The concurrency for the different entry points is (unless specified otherwise) to enter with exclusive access at the inner perimeter (if present) and shared access at the outer perimeter (if present). The perimeter configuration consists of flags that define the presence and scope of the inner perimeter, the presence of the outer perime- ter (which can only have one scope), and flags that modify the default concurrency for the different entry points. All MT safe modules/drivers specify the D_MP flag. Inner Perimeter Flags The inner perimeter presence and scope are controlled by the mutually exclusive flags: D_MTPERQ The module/driver has an inner perimeter around each queue. D_MTQPAIR The module/driver has an inner perimeter around each read/write pair of queues. D_MTPERMOD The module/driver has an inner perimeter that encloses all the module's/driver's queues. None of the above The module/driver has no inner perimeter. Outer Perimeter Flags The outer perimeter presence is configured using: D_MTOUTPERIM In addition to any inner perimeter, the module/driver has an outer perimeter that encloses all the mod- ule's/driver's queues. This can be combined with all the inner perimeter options except D_MTPERMOD. Note that acquiring exclusive access at the outer perimeter (that is, using qwriter(9F) with the PERIM_OUTER flag) can incur significant performance penalties, which grow linearly with the number of open instances of the module or driver in the system. The default concurrency can be modified using: D_MTPUTSHARED This flag modifies the default behavior when put(9E) procedure are invoked so that the inner perimeter is entered shared instead of exclusively. D_MTOCEXCL This flag modifies the default behavior when open(9E) and close(9E) procedures are invoked so the the outer perime- ter is entered exclusively instead of shared. Note that drivers and modules using this flag can cause significant system performance degradation during stream open or close when many instances of the driver or module are in use simultaneously. For this reason, use of this flag is discouraged. Instead, since open(9E) and close(9E) both execute with user context, developers are encour- aged to use traditional synchronization routines such as cv_wait_sig(9F) to coordinate with other open instances of the module or driver. The module/driver can use qwait(9F) or qwait_sig() in the open(9E) and close(9E) procedures if it needs to wait "outside" the perimeters. The module/driver can use qwriter(9F) to upgrade the access at the inner or outer perimeter from shared to exclusive. The use and semantics of qprocson() and qprocsoff(9F) is independent of the inner and outer perimeters. SEE ALSO
close(9E), open(9E), put(9E), srv(9E), qprocsoff(9F), qprocson(9F), qwait(9F), qwriter(9F), cb_ops(9S) STREAMS Programming Guide Writing Device Drivers SunOS 5.10 16 Dec 2002 mt-streams(9F)
All times are GMT -4. The time now is 10:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy