10 More Discussions You Might Find Interesting
1. HP-UX
Dear All,
Please help to find out the patch and firmware versions in HP-UX systems. as uname -r is showing os version and
uname -a
HP-UX xxxxxx B.11.23 U 9000/800 2781427196 unlimited-user license.
Kindly help to find out the existing Kernel and firmware versions.
Also I need to... (3 Replies)
Discussion started by: anuragr
3 Replies
2. Shell Programming and Scripting
How to copy a file from directroy/ prior version to the directory/ new version automatically. (4 Replies)
Discussion started by: roy1912
4 Replies
3. AIX
Dears i have a power7 P770 working in AIX 5.3 TL 11 with frimware AM730_066
is the AM730_066 frimware the latest one or not ? (6 Replies)
Discussion started by: thecobra151
6 Replies
4. Hardware
All,
I need to upgrade my HMC from version 7.3.4 to vervion 7.3.5. The HMC has a Machine type of 7310-CR2 Xseries 335 . Where could I download the firmware for such hardware (HMC Machine type of 7310-CR2 Xseries 335 )? Please answer because I need to upgrade that HMC the HMC to bring to... (3 Replies)
Discussion started by: jesifra
3 Replies
5. UNIX for Advanced & Expert Users
Would like to confirm the ff. I got confused actually with the version I needed to download that will work on glassfish 3.0.1
a. Debian Squeeze (HP DL360). Need to use java version6
On Debian, I did apt-get install sun-java6-jdk. So when I check it's
java version "1.6.0_22"
Java(TM) SE... (1 Reply)
Discussion started by: lhareigh890
1 Replies
6. AIX
Hi all:
I have a need to down-rev my AIX HBA firmware due to storage instability after upgrading, but IBM support only makes the latest version of firmware available for download.
Can anyone provide pointer/tips for obtaining old HBA firmware ?
Specifics:
280B HBA
df1000fa driver... (1 Reply)
Discussion started by: kwachtler
1 Replies
7. Solaris
Command to check firmware version of HP x86 server on which solaris installed.
I m not getting version by using prtdiag -v command (1 Reply)
Discussion started by: sunray
1 Replies
8. Solaris
i have a program writing in PRO C which currently running in unix version 8 tie with oracle 8i, but in the future company gonna migrate this OS to version 9.
Anything i have to prepare for my PRO C program to run in unix version 9? or anything would that impact my program couldn't run well?
what... (2 Replies)
Discussion started by: lsy
2 Replies
9. UNIX for Advanced & Expert Users
Hi all,
I have an H80 that I'm migrating to 5.3 and prior to doing so it needed the firmware upgraded. I don't have copies of the old firmware that was on it since I was not the one who installed it and there were no copies to be found on the server itself. I installed the latest version and... (4 Replies)
Discussion started by: howardle
4 Replies
10. UNIX for Dummies Questions & Answers
Hi
Im new here and pretty new to Unix.
Just a couple of questions
How can I tell what version of Unix I'm running?
and
Also I hope this makes sence, when writting scripts/programmes does it matter what Im writting it in? ie what shell? Or is it just identical whatever shell Im... (1 Reply)
Discussion started by: Loaded Gun
1 Replies
FIRMLOAD(9) BSD Kernel Developer's Manual FIRMLOAD(9)
NAME
firmload -- Firmware loader API for device drivers
SYNOPSIS
#include <dev/firmload.h>
int
firmware_open(const char *drvname, const char *imgname, firmware_handle_t *fhp);
int
firmware_close(firmware_handle_t fh);
off_t
firmware_get_size(firmware_handle_t fh);
int
firmware_read(firmware_handle_t fh, off_t offset, void *buf, size_t size);
void *
firmware_malloc(size_t size);
void
firmware_free(void *buf, size_t size);
DESCRIPTION
firmload provides a simple and convenient API for device drivers to load firmware images from files residing in the file system that are nec-
essary for the devices that they control. Firmware images reside in sub-directories, one for each driver, of a series of colon-separated
path prefixes specified by the sysctl variable hw.firmware.path.
FUNCTIONS
The following functions are provided by the firmload API:
firmware_open(drvname, imgname, fhp)
Open then firmware image imgname for the driver drvname. The path to the firmware image file is constructed by appending the string
``/drvname/imgname'' to each configured path prefix until opening the firmware image file succeeds. Upon success, firmware_open()
returns 0 and stores a firmware image handle in the location pointed to by fhp. Otherwise, an error code is returned to indicate the
reason for failure.
firmware_close(fh)
Close the firmware image file associated with the firmware handle fh. Returns 0 upon success or an error code to indicate the reason
for failure.
firmware_get_size(fh)
Returns the size of the image file associated with the firmware handle fh.
firmware_read(fh, offset, buf, size)
Reads from the image file associated with the firmware handle fh beginning at offset offset for length size. The firmware image data
is placed into the buffer specified by buf. Returns 0 upon success or an error code to indicate the reason for failure.
firmware_malloc(size)
Allocates a region of wired kernel memory of size size. Note: firmware_malloc() may block.
firmware_free(buf, size)
Frees a region of memory previously allocated by firmware_malloc().
SEE ALSO
autoconf(9), malloc(9), vnsubr(9)
HISTORY
The firmload framework first appeared in NetBSD 4.0.
AUTHORS
Jason Thorpe <thorpej@NetBSD.org>
BSD
January 17, 2006 BSD
