04-13-2010
Yes that's correct. I've upgraded our P5 570's, 520's, and 52A's using the same firmware code.
10 More Discussions You Might Find Interesting
1. AIX
Hi Guys,
It's me again with this unending support of AIX43 ML 9.
I finally able to test a migration from SSA to SAN, no problem. One problem, I bought some expansion of DS4300, two arrays. The IBM tech told me that before I can connect to the existing DS4300, I need to upgrade the firmware... (1 Reply)
Discussion started by: itik
1 Replies
2. AIX
I need upgrade firmware for the device of p570, when I go to IBM FIX download website, there are a lot of device of p570 listed. How can I know what device I have on my p570? (4 Replies)
Discussion started by: rainbow_bean
4 Replies
3. Solaris
Hi,
I going to upgrade the firmware for sunfire v490 server, current fw level is 4.15.6 and to be upgraded to 4.30.
can anyone share the pre and post firmware upgrade activity procedure and backout plan
Thanks
rjs (2 Replies)
Discussion started by: rajasekg
2 Replies
4. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
5. Solaris
Hi All,
Recently I'm being request by customer to upgrade firmware for one of the disk but not from storage and is from server it self.
The patch no is 116370-15, when I found it, I only see instructions on how to download for storage disks but not for server disks.
All guru here please... (0 Replies)
Discussion started by: mailbox80
0 Replies
6. HP-UX
Hi gurus,
I was more on the Sun side and now am getting exposure to the HP-UX side of the world. I have to upgrade firmware on BL870c blade.
Can some one point to a url or give procedure to follow as I couldn't find much on the web.
Thanks
Momin (1 Reply)
Discussion started by: momin
1 Replies
7. AIX
Hi,
I bought a second hand IBM machine model 9110 - 510. This machine is connected to a terminal (orange color text) through a serial port and when I bought the machine it shows its model and it ask for user id and password but i tried many without luck.
I want to reset the root password... (4 Replies)
Discussion started by: yalmutawa
4 Replies
8. AIX
Hello ALL
I have a p510-9110 server with Aix 5.3 installed ..
I have many issues related to (oracle 11.5.3 apps) .
and oracle said :this OS is not supported with the current apps
..just 5.1 .
I tried to install 5.1 on the p510 server , but even no boot from 5.1 cd !!!
after goggling... (10 Replies)
Discussion started by: zzmaher
10 Replies
9. AIX
Hi. I just migrated a 5.3 box to 6.1 (standalone, no HMC). This is a System p5 520 Power 5 box
The migration process went smooth but at the end when the server rebooted it never came up. So the bootup process never completes. It gets stuck at the screen with the big AIX logo saying it's loading... (6 Replies)
Discussion started by: livehho
6 Replies
10. AIX
any ideas ??????? (2 Replies)
Discussion started by: livehho
2 Replies
LEARN ABOUT NETBSD
firmware_free
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