01-24-2009
Hi,
The reason is because we're replacing the production hw which the application can only be running and the company only support or certified their application on 5.9 but not on 10.
I'll check the firmware though.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I'm having all kinds of trouble jumpstarting some SS20's.
After hunting around the newsgroups I find that this seems to be a fairly common problem with no real answer.
Here's a brief:
SS20, 50mhz, 256mb blah blah. - Client
E250 blah blah - J/start server.
10/100bt Network.... (4 Replies)
Discussion started by: itsupplies
4 Replies
2. Solaris
hi,
i hv received SUNfire 280R system ........for its initial configuration i want to connect to it through hyperterminal from the windows system..........i hv got one serial port to RJ-45 port converter with the system............can anybody tell me the normal console cable which is used to... (3 Replies)
Discussion started by: girish_shukla
3 Replies
3. Solaris
Hi there
Does anybody know what the biggest capacity disk I can get into a Sunfire 280R
I currently have two 73gb disks , but I need to get these up to the biggest available
Any help would be greatly appreciated (4 Replies)
Discussion started by: hcclnoodles
4 Replies
4. Solaris
Hi,
Could someone please explain it to me how much space in MG or GIG available if i can create another mount point or another slice by looking at this output:
# prtvtoc /dev/rdsk/c1t1d0s0
* /dev/rdsk/c1t1d0s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 424 sectors/track... (2 Replies)
Discussion started by: lamoul
2 Replies
5. Solaris
Hi,
I have to question:
1) when O/S is booting, i see messages:
/dev/rdsk/c1t0d0s5: is logging
/dev/rdsk/c1t0d0s3: is logging
/dev/rdsk/c1t0d0s7: is logging
i partitioned these slices during installation of O/S 5.9. I can access to these mountpoint no problem. But... (3 Replies)
Discussion started by: lamoul
3 Replies
6. Solaris
hi,
i just completed installing O/S 5.9 on Sunfire 280R with O/S 5.9. During installation, i wasn't able to add IP, Default gateway, NDS and netmask because the lan port wasn't not active yet. Now that i have a lan port active, how to add network components onto the system?
I did ifconfig to... (1 Reply)
Discussion started by: lamoul
1 Replies
7. Solaris
Hi,
i just finished installing solaris 5.9 and I'm looking for the tools to tell me if i should update the patches or how to make sure that the current patches are ok?
thanks (2 Replies)
Discussion started by: lamoul
2 Replies
8. Hardware
Hi,
I'm a newbie in the Unix world... :confused:
I own a Sun Sunfire 280R computer with one 750Mhz CPU. I ordered two CPU of 900Mhz to replace it; however in the Service manual from Sun I read that to use 900Mhz CPU i will need to have a OBP of at least version 4.5.16. When I type .version in... (2 Replies)
Discussion started by: Monkey114
2 Replies
9. Hardware
I got the system couple of days back from one of my friend. Last night I turned it on and I noticed that maintenance LED is on. At the same time I added an LCD monitor via VGA and nothing was showing on the screen. Though the system does not have any HDD So not sure if system will even show a BIOS... (3 Replies)
Discussion started by: pgirish007
3 Replies
10. Solaris
Dear all!
I've received 4 servers Sparc T4-2 on a rack, those servers was built in Solaris 11 ZFS bundled. Our Application is not coporated with the Sun 11, so, I must reinstall them.
However, whenever I ran cdrom in "ok prompt> bood cdrom", I received the line "Can not load cdrom". Recheck... (9 Replies)
Discussion started by: trantuananh24hg
9 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