Trencher93 Velociraptor


Joined: Jun 24, 2008 Posts: 465
|
Posted: Thu Nov 15, 2012 2:27 pm Post subject: |
|
|
| Wouldn't the documentation for whatever this is tell you what the parameters are? Or a forum with people who actually use this library? The probability of finding a user of this library on this site seems low. |
|
| Back to top |
|
Ancalagon Computer Geek


Joined: Dec 26, 2007 Posts: 2388
|
Posted: Thu Nov 15, 2012 7:11 pm Post subject: |
|
|
Those are bitmasks. They're being put in the inout parameter and then binary or'ed with a bunch of other stuff. They set a particular bit in the output, which marks whether we're doing a 'copy out' or a 'copy in', whatever those are. You should definitely look up bitwise operators if you're going to do much low level C stuff. _________________ "A dead thing can go with the stream, but only a living thing can go against it." --G. K. Chesterton |
|
| Back to top |
|
AngelKnight Phoenix


Joined: May 04, 2011 Posts: 748 Location: This is not my home; I'm just passing through
|
Posted: Fri Nov 16, 2012 12:47 am Post subject: Re: <sys/ioccom.h> {CALLING all C/C++ buffs!; } |
|
|
| AspieRogue wrote: | | So the <sys/ioccom.h> header package contains low level I/O functions. I downloaded and compiled it as I am trying to write an implement some low(er) level network socket subfunctions that actually write data frames to the ethernet adapter. I am not writing an actual driver as one is already installed and those are device specific. You can have a look at it Here as it's open source Unix code. |
I'm guessing you're going to actually run this stuff within a BSD of some description? If so, why not use the provided interfaces, why try to bitbang the registers on a device by hand while running within BSD? |
|
| Back to top |
|
|
|