07-15-2001
Admin Board for Forum Admin Only
Here is what the admin board is for, which is right in the board description, BTW:
Quote:
Make Suggestions About Future Forums, Features, or Content here. Find Forum Rules and Guidelines here too.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Since I failed a test that I didn't have the chance to study for, my wonderful instructor told me to write a paper about BSD sys 5. I can't find anything...does it even exist yet??? If you have any input, I would love you forever if you can enlighten me ASAP. (2 Replies)
Discussion started by: Toughgirl27
2 Replies
2. Shell Programming and Scripting
Hi,
i need a shell script that write in a file called sys.txt this:
<output of date command>
HN <host name>
OS <OS name> <OS version>
I can have this info with uname command, but I can't write these in sys.txt.
Can any one help me? (1 Reply)
Discussion started by: FastMagister
1 Replies
3. Solaris
Hi
I would like to know the difference between System V release and BSD style release.
Regards,
Raja (2 Replies)
Discussion started by: RajaRC
2 Replies
4. Solaris
Hello Guys, im new to this forum. Im from UK and ive recently completed my SCSA I & II and also got trained in Veritas Suite (Veritas Volume Manager and Veritas Clusters, Veritas NetBackup), SAN Configuration. I was trying to get a break as a junior sun solaris admin. I am applying for the jobs... (1 Reply)
Discussion started by: megadeth
1 Replies
5. Programming
How should I use errno in a c program and what info does it have .
I am working with directories and files.
So can any one tell me How to access errno?I am using the stat() function on \etc directory and I am alble to access only the half of the directories.I am not able to access other half and... (6 Replies)
Discussion started by: vijlak
6 Replies
6. HP-UX
HI all,
What the minimum & recommended system requirement for Rhel Linux to get install on it??:(
Plz reply ASAp (0 Replies)
Discussion started by: saurabh84g
0 Replies
7. Solaris
I did a sys-unconfig to change the domainname, Ip, subnet, hostname, and pretty much everything else that sys-unconfig handles. Upon reboot, it is toast. I did this all without the network cable plugged in.
The following shows up on console:
login: pam_unix_cred: cannot load ttyname Error 0
... (3 Replies)
Discussion started by: adelsin
3 Replies
8. Programming
(Apologies for any typos.)
OSX 10.12.3 AND Windows 10.
This is for the serious Python experts on at least 3.5.x and above...
In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly.
Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies
LEARN ABOUT SUSE
struct_spi_board_info
STRUCT
SPI_BOARD_INF(9) Serial Peripheral Interface (S STRUCT SPI_BOARD_INF(9)
NAME
struct_spi_board_info - board-specific template for a SPI device
SYNOPSIS
struct spi_board_info {
char modalias[SPI_NAME_SIZE];
const void * platform_data;
void * controller_data;
int irq;
u32 max_speed_hz;
u16 bus_num;
u16 chip_select;
u8 mode;
};
MEMBERS
modalias[SPI_NAME_SIZE]
Initializes spi_device.modalias; identifies the driver.
platform_data
Initializes spi_device.platform_data; the particular data stored there is driver-specific.
controller_data
Initializes spi_device.controller_data; some controllers need hints about hardware setup, e.g. for DMA.
irq
Initializes spi_device.irq; depends on how the board is wired.
max_speed_hz
Initializes spi_device.max_speed_hz; based on limits from the chip datasheet and board-specific signal quality issues.
bus_num
Identifies which spi_master parents the spi_device; unused by spi_new_device, and otherwise depends on board wiring.
chip_select
Initializes spi_device.chip_select; depends on how the board is wired.
mode
Initializes spi_device.mode; based on the chip datasheet, board wiring (some devices support both 3WIRE and standard modes), and
possibly presence of an inverter in the chipselect path.
DESCRIPTION
When adding new SPI devices to the device tree, these structures serve as a partial device template. They hold information which can't
always be determined by drivers. Information that probe can establish (such as the default transfer wordsize) is not included here.
These structures are used in two places. Their primary role is to be stored in tables of board-specific device descriptors, which are
declared early in board initialization and then used (much later) to populate a controller's device tree after the that controller's driver
initializes. A secondary (and atypical) role is as a parameter to spi_new_device call, which happens after those controller drivers are
active in some dynamic board configuration models.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 STRUCT SPI_BOARD_INF(9)